Avoid widow/orphan headings and lines
cover Avoid widow/orphan headings and lines
Hi Paul,
(LaTeX adviser hat on)
This patch set is prompted by a recent update of the "epigraph" package mentioned in the change log of 3/6.
epigraph v1.5e now suppress epigraphs from orphaned (appear at the bottom of a page/column).
In 2C layout of v2019.12.22a, epigraphs of Sections 9.5, 10.2, and 10.4 are orphaned.
Upgrading to epigraph v1.5e resolves the issue, but there is another occurence of orphaned heading of Section 10.2.2 (1C layout of v2019.12.22a).
The reason of the orphaned heading is the float object at the beginning of the sub section. I've found a recommendation of where to put floats in LaTeX sources at
https://www.latex-project.org/publications/2014-FMi-TUB-tb111mitt-float-placement.pdf
,as mentioned in the change log of 2/6. It is a good read for the algorithm of float placement by LaTeX.
Quote from Section 4.7:
Do not place a float directly after a heading, unless it is a heading that always starts a page. The reason is that headings normally form very large objects (as a heading prevents a page break directly after it). However placing a float in the middle of this means that the output routine gets triggered before LATEX makes its decision where to break and any footnotes get moved into the wrong place.
So, I moved such floats in 2/6. I might have missed one or two of other such floats, though.
Patch 1/6 fixes a minor typo in epigraph.
Patch 2/6 moves floats as mentioned above.
Patch 3/6 enforces the upgrade of epigraph package, and also applies "nowidow" package to prevent orphan/widow lines. As mentioned in the change log, this change will cause large gaps between paragraphs on a few pages. You might find them ugly, but I prefer the ease of read, especially short QQZs. Patch 4/6 retouches a quick quiz to avoid such a large gap at the end of the Quiz part.
Patch 5/6 changes the definition of \clnrefrange and \Clnrefrange to prevent breaks at endashes.
Patch 6/6 is unrelated to widow/orphan, but improves the readability of longer footnotes in 1C layout.
Patches 3/6, 5/6, and 6/6 modifies preamble (and related FAQ-BUILD.txt) only. You can skip any of them if you'd be inclined to.
Thanks, Akira
--
Akira Yokosawa (6):
together/count: Fix double quotes in epigraph Prevent section heading from orphaned
Prevent section epigraph from orphaned
count: Promote code snippet in Quiz part of QQZ to listing Use unbreakable endash in \clnrefrange{}{} Reduce footnote width in 1c layout
FAQ-BUILD.txt | 7 +- SMPdesign/beyond.tex | 13 ++- appendix/toyrcu/toyrcu.tex | 167 +++++++++++++++---------------- count/count.tex | 111 +++++++++++---------- datastruct/datastruct.tex | 77 +++++++-------- defer/rcuapi.tex | 32 +++--- defer/rcuusage.tex | 15 ++- formal/axiomatic.tex | 24 ++--- formal/dyntickrcu.tex | 194 ++++++++++++++++++------------------- formal/ppcmem.tex | 14 +-- formal/spinhint.tex | 59 ++++++----- locking/locking.tex | 79 ++++++++------- memorder/memorder.tex | 60 ++++++------ perfbook.tex | 13 ++- together/applyrcu.tex | 48 ++++----- together/count.tex | 2 +- 16 files changed, 453 insertions(+), 462 deletions(-)
Signature · 1 line
2.17.1
PATCH 1/6 together/count: Fix double quotes in epigraph
From ecbe4b6536dbc2801a9bc919287ae172d058ac84 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <[email protected]>
Date: Mon, 6 Jan 2020 00:32:04 +0900
Subject: [PATCH 1/6] together/count: Fix double quotes in epigraph
--- together/count.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
together/count.tex +1 -1
@@ -8,7 +8,7 @@ \epigraph{Ford carried on counting quietly. This is about the most aggressive thing you can do to a computer, the equivalent of going up to a human being and saying - "Blood \dots blood \dots blood \dots blood \dots"} + ``Blood \dots blood \dots blood \dots blood \dots''} {\emph{Douglas Adams}} This \lcnamecref{sec:together:Counter Conundrums}
Signature · 1 line
2.17.1
PATCH 2/6 Prevent section heading from orphaned
In reply to Akira YokosawaFrom a13120c31bf160a5996c06d66f5e23ed9f1939f0 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <[email protected]>
Date: Mon, 6 Jan 2020 17:34:16 +0900
Subject: [PATCH 2/6] Prevent section heading from orphaned
Putting "\NoIndentAfterThis" where source of floats comes just below section headings has a failure mode of possible orphaned heading (heading at the bottom of a page/column). E.g.:
Section 10.2.2's heading in perfbook-1c.pdf (before this update)
Moving such source of floats to next to the first paragraph of the section is the right way mentioned in Section 4.7 of [1].
Exception to this rule is at or near the beginning of a chapter, where a float object has no chance to cause an actual page break.
This commit therefore moves such floats and removes \NoIndentAfterThis. Some of the floats not at the beginning of a section are also moved to avoid congestion of floats.
[1]: https://www.latex-project.org/publications/2014-FMi-TUB-tb111mitt-float-placement.pdf
--- SMPdesign/beyond.tex | 13 ++- appendix/toyrcu/toyrcu.tex | 167 +++++++++++++++---------------- count/count.tex | 86 ++++++++-------- datastruct/datastruct.tex | 77 +++++++-------- defer/rcuapi.tex | 32 +++--- defer/rcuusage.tex | 15 ++- formal/axiomatic.tex | 24 ++--- formal/dyntickrcu.tex | 194 ++++++++++++++++++------------------- formal/ppcmem.tex | 14 +-- formal/spinhint.tex | 59 ++++++----- locking/locking.tex | 79 ++++++++------- memorder/memorder.tex | 60 ++++++------ together/applyrcu.tex | 48 ++++----- 13 files changed, 423 insertions(+), 445 deletions(-)
SMPdesign/beyond.tex +6 -7
@@ -57,7 +57,12 @@ presents future directions and concluding remarks. \subsection{Work-Queue Parallel Maze Solver} \label{sec:SMPdesign:Work-Queue Parallel Maze Solver} -\NoIndentAfterThis + +PWQ is based on SEQ, which is shown in +Listing~\ref{lst:SMPdesign:SEQ Pseudocode} +(pseudocode for \path{maze_seq.c}). +The maze is represented by a 2D array of cells and +a linear-array-based work queue named \co{->visited}. \begin{listing}[tbp] \begin{linelabel}[ln:SMPdesign:SEQ Pseudocode]
@@ -90,12 +95,6 @@ int maze_solve(maze *mp, cell sc, cell ec) \label{lst:SMPdesign:SEQ Pseudocode} \end{listing} -PWQ is based on SEQ, which is shown in -Listing~\ref{lst:SMPdesign:SEQ Pseudocode} -(pseudocode for \path{maze_seq.c}). -The maze is represented by a 2D array of cells and -a linear-array-based work queue named \co{->visited}. - \begin{lineref}[ln:SMPdesign:SEQ Pseudocode] Line~\lnref{initcell} visits the initial cell, and each iteration of the loop spanning \clnrefrange{loop:b}{loop:e} traverses passages headed by one cell.
appendix/toyrcu/toyrcu.tex +84 -83
269 lines not on this page · raw message
count/count.tex +40 -46
147 lines not on this page · raw message
datastruct/datastruct.tex +37 -40
135 lines not on this page · raw message
defer/rcuapi.tex +16 -16
@@ -26,7 +26,22 @@ presents concluding remarks. \subsubsection{RCU has a Family of Wait-to-Finish APIs} \label{sec:defer:RCU has a Family of Wait-to-Finish APIs} -\begin{table*}[htbp] +The most straightforward answer to ``what is RCU'' is that RCU is +an API. +For example, the RCU implementation used in the Linux kernel is +summarized by +Table~\ref{tab:defer:RCU Wait-to-Finish APIs}, +which shows the wait-for-readers portions of the RCU, ``sleepable'' RCU +(SRCU), Tasks RCU, and generic APIs, respectively, +and by +Table~\ref{tab:defer:RCU Publish-Subscribe and Version Maintenance APIs}, +which shows the publish-subscribe portions of the +API~\cite{PaulEMcKenney2019RCUAPI}.\footnote{ + This citation covers v4.20 and later. + Documetation for earlier versions of the Linux-kernel RCU API may + be found elsewhere~\cite{PaulEMcKenney2008WhatIsRCUAPI,PaulEMcKenney2014RCUAPI}.} + +\begin{table*}[tbp] \rowcolors{1}{}{lightgray} \renewcommand*{\arraystretch}{1.3} \centering
@@ -101,21 +116,6 @@ presents concluding remarks. \end{tabularx} \end{table*} -The most straightforward answer to ``what is RCU'' is that RCU is -an API. -For example, the RCU implementation used in the Linux kernel is -summarized by -Table~\ref{tab:defer:RCU Wait-to-Finish APIs}, -which shows the wait-for-readers portions of the RCU, ``sleepable'' RCU -(SRCU), Tasks RCU, and generic APIs, respectively, -and by -Table~\ref{tab:defer:RCU Publish-Subscribe and Version Maintenance APIs}, -which shows the publish-subscribe portions of the -API~\cite{PaulEMcKenney2019RCUAPI}.\footnote{ - This citation covers v4.20 and later. - Documetation for earlier versions of the Linux-kernel RCU API may - be found elsewhere~\cite{PaulEMcKenney2008WhatIsRCUAPI,PaulEMcKenney2014RCUAPI}.} - If you are new to RCU, you might consider focusing on just one of the columns in Table~\ref{tab:defer:RCU Wait-to-Finish APIs},
defer/rcuusage.tex +7 -8
@@ -44,7 +44,13 @@ Section~\ref{sec:defer:RCU Usage Summary} provides a summary. \subsubsection{RCU for Pre-BSD Routing} \label{sec:defer:RCU for Pre-BSD Routing} -\NoIndentAfterThis + +Listings~\ref{lst:defer:RCU Pre-BSD Routing Table Lookup} +and~\ref{lst:defer:RCU Pre-BSD Routing Table Add/Delete} +show code for an RCU-protected Pre-BSD routing table +(\path{route_rcu.c}). +The former shows data structures and \co{route_lookup()}, +and the latter shows \co{route_add()} and \co{route_del()}. \begin{listing}[tbp] \input{CodeSamples/defer/[email protected]}
@@ -58,13 +64,6 @@ Section~\ref{sec:defer:RCU Usage Summary} provides a summary. \label{lst:defer:RCU Pre-BSD Routing Table Add/Delete} \end{listing} -Listings~\ref{lst:defer:RCU Pre-BSD Routing Table Lookup} -and~\ref{lst:defer:RCU Pre-BSD Routing Table Add/Delete} -show code for an RCU-protected Pre-BSD routing table -(\path{route_rcu.c}). -The former shows data structures and \co{route_lookup()}, -and the latter shows \co{route_add()} and \co{route_del()}. - \begin{lineref}[ln:defer:route_rcu:lookup] In Listing~\ref{lst:defer:RCU Pre-BSD Routing Table Lookup}, line~\lnref{rh} adds the \co{->rh} field used by RCU reclamation,
formal/axiomatic.tex +12 -12
@@ -139,12 +139,6 @@ This is now possible, as will be described in the following sections. \subsection{Axiomatic Approaches and Locking} \label{sec:formal:Axiomatic Approaches and Locking} -\begin{listing}[tb] -\input{CodeSamples/formal/herd/[email protected]} -\caption{Locking Example} -\label{lst:formal:Locking Example} -\end{listing} - Axiomatic approaches may also be applied to higher-level languages and also to higher-level synchronization primitives, as exemplified by the lock-based litmus test shown in
@@ -160,6 +154,12 @@ of one.\footnote{ and~\ref{lst:formal:PPCMEM on Repaired Litmus Test} for examples showing the output format.} +\begin{listing}[tb] +\input{CodeSamples/formal/herd/[email protected]} +\caption{Locking Example} +\label{lst:formal:Locking Example} +\end{listing} + \QuickQuiz{} What do you have to do to run \co{herd} on litmus tests like that shown in Listing~\ref{lst:formal:Locking Example}?
@@ -254,12 +254,6 @@ The next section looks at RCU. \subsection{Axiomatic Approaches and RCU} \label{sec:formal:Axiomatic Approaches and RCU} -\begin{listing}[tb] -\input{CodeSamples/formal/herd/[email protected]} -\caption{Canonical RCU Removal Litmus Test} -\label{lst:formal:Canonical RCU Removal Litmus Test} -\end{listing} - \begin{lineref}[ln:formal:C-RCU-remove:whole] Axiomatic approaches can also analyze litmus tests involving RCU~\cite{Alglave:2018:FSC:3173162.3177156}.
@@ -275,6 +269,12 @@ Line~\lnref{head} shows \co{x} as the list head, initially referencing \co{y}, which in turn is initialized to the value \co{2} on line~\lnref{tail:1}. +\begin{listing}[tb] +\input{CodeSamples/formal/herd/[email protected]} +\caption{Canonical RCU Removal Litmus Test} +\label{lst:formal:Canonical RCU Removal Litmus Test} +\end{listing} + \co{P0()} on \clnrefrange{P0start}{P0end} removes element \co{y} from the list by replacing it with element \co{z} (line~\lnref{assignnewtail}),
formal/dyntickrcu.tex +94 -100
271 lines not on this page · raw message
formal/ppcmem.tex +7 -7
@@ -58,6 +58,13 @@ discusses the implications. \subsection{Anatomy of a Litmus Test} \label{sec:formal:Anatomy of a Litmus Test} +An example PowerPC litmus test for PPCMEM is shown in +\cref{lst:formal:PPCMEM Litmus Test}. +The ARM interface works exactly the same way, but with ARM instructions +substituted for the Power instructions and with the initial ``PPC'' +replaced by ``ARM''. You can select the ARM interface by clicking on +``Change to ARM Model'' at the web page called out above. + \begin{listing}[tbp] \begin{linelabel}[ln:formal:PPCMEM Litmus Test] \begin{VerbatimL}[commandchars=\@\[\]]
@@ -87,13 +94,6 @@ exists @lnlbl[assert:b] \label{lst:formal:PPCMEM Litmus Test} \end{listing} -An example PowerPC litmus test for PPCMEM is shown in -\cref{lst:formal:PPCMEM Litmus Test}. -The ARM interface works exactly the same way, but with ARM instructions -substituted for the Power instructions and with the initial ``PPC'' -replaced by ``ARM''. You can select the ARM interface by clicking on -``Change to ARM Model'' at the web page called out above. - \begin{lineref}[ln:formal:PPCMEM Litmus Test] In the example, \clnref{type} identifies the type of system (``ARM'' or ``PPC'') and contains the title for the model. \Clnref{altname}
formal/spinhint.tex +28 -31
107 lines not on this page · raw message
locking/locking.tex +38 -41
121 lines not on this page · raw message
memorder/memorder.tex +30 -30
120 lines not on this page · raw message
together/applyrcu.tex +24 -24
84 lines not on this page · raw message
Signature · 1 line
2.17.1
PATCH 3/6 Prevent section epigraph from orphaned
In reply to Akira YokosawaFrom a0018ab43dcde623de230b7077820c4ee86a5144 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <[email protected]>
Date: Sat, 11 Jan 2020 08:17:27 +0900
Subject: [PATCH 3/6] Prevent section epigraph from orphaned
Latest "epigraph" package has a nice feature to make sure that section epigraph is not orphaned.
Add version info to its \usepackage.
Also add it to #10 in FAQ-BUILD.txt.
Also suppress widows and orphans by using the "nowidow" package. This prevents a single line of a paragraph to appear at the bottom or the top of a page/column. For example, Short QQZ (less than 4 lines) won't be broken in the middle any more.
This narrows the freedom of LaTeX's typesetting and slightly increases page count, but should improve the ease of read.
NOTE 1: epigraph's document now mentions a macro \epigraphnoindent which would have the same effect as \NoIndentAfterCmd{\epigraph}, but it has weird side effect on the spacing of other section headings.
NOTE 2: This update causes stretched vertical spaces between paragraphs in pages where section headings with epigraphs are forwarded to the next pages. They might need tweaks in LaTeX sources later, especially in the -RC stages of the next edition.
--- FAQ-BUILD.txt | 7 +++++-- perfbook.tex | 3 ++- 2 files changed, 7 insertions(+), 3 deletions(-)
FAQ-BUILD.txt +5 -2
@@ -178,11 +178,13 @@ tlmgr install newtx 10. Building perfbook fails with a warning of buggy cleveref/listings - or version mismatch of titlesec/draftwatermark. What can I do? + or version mismatch of titlesec/draftwatermark/epigraph. + What can I do? A. They are known issues on Ubuntu Xenial (titlesec), Ubuntu Bionic (cleveref), TeX Live 2014/2015 (listings), - and TeX Live releases prior to 2015 (draftwatermark). + TeX Live releases prior to 2015 (draftwatermark), + and TeX Live releases prior to 2020 (epigraph). This answer assumes Ubuntu, but it should work on other distros.
@@ -191,6 +193,7 @@ http://mirrors.ctan.org/macros/latex/contrib/cleveref.zip http://mirrors.ctan.org/macros/latex/contrib/listings.zip http://mirrors.ctan.org/macros/latex/contrib/draftwatermark.zip + http://mirrors.ctan.org/macros/latex/contrib/epigraph.zip 2. Install it by following instructions at: https://help.ubuntu.com/community/LaTeX#Installing_packages_manually
perfbook.tex +2 -1
@@ -71,7 +71,7 @@ \usepackage[bookmarks=true,bookmarksnumbered=true,pdfborder={0 0 0},linktoc=all]{hyperref} \usepackage{footnotebackref} % to enable cross-ref of footnote \usepackage[all]{hypcap} % for going to the top of figure and table -\usepackage{epigraph} +\usepackage{epigraph}[2020/01/02] % latest version prevents orphaned epigraph \setlength{\epigraphwidth}{2.6in} \usepackage[xspace]{ellipsis} \usepackage{braket} % for \ket{} macro in QC section
@@ -80,6 +80,7 @@ \usepackage{multirow} \usepackage{noindentafter} \NoIndentAfterCmd{\epigraph} +\usepackage[all]{nowidow} \titleformat{\paragraph}[runin]{\normalfont\normalsize\bfseries}{}{0pt}{} % custom packages
Signature · 1 line
2.17.1
PATCH 4/6 count: Promote code snippet in Quiz part of QQZ to listing
In reply to Akira YokosawaFrom 04c6c10ec7d6f9b215141bee0ec7f8001891bcf1 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <[email protected]>
Date: Sat, 11 Jan 2020 13:48:01 +0900
Subject: [PATCH 4/6] count: Promote code snippet in Quiz part of QQZ to listing
Current scheme of QQZ can't handle a snippet at the end of a Quiz part due to the implied break-ability in front of the ending "square mark".
QQZ 5.29 suffers from such a symptom.
Promote the snippet to a proper listing and rephrase the Quiz and Answer part accordingly.
Also add WRITE_ONCE() and adjust indent in the snippet for consistency with the right snippet.
--- count/count.tex | 25 +++++++++++++++---------- 1 file changed, 15 insertions(+), 10 deletions(-)
count/count.tex +15 -10
@@ -1398,24 +1398,29 @@ This is the \co{add_counter()} fastpath, and it does no atomic operations, references only per-thread variables, and should not incur any cache misses. \end{lineref} +\begin{listing}[tbp] +\begin{VerbatimL}[firstnumber=3] + if (counter + delta <= countermax) { + WRITE_ONCE(counter, counter + delta); + return 1; + } +\end{VerbatimL} +\caption{Intuitive Fastpath} +\label{lst:count:Intuitive Fastpath} +\end{listing} + \QuickQuiz{} What is with the strange form of the condition on line~\ref{ln:count:count_lim:add_sub_read:add:checklocal} of Listing~\ref{lst:count:Simple Limit Counter Add, Subtract, and Read}? - Why not the following more intuitive form of the fastpath? - -\begin{VerbatimN}[firstnumber=3] -if (counter + delta <= countermax) { - counter += delta; - return 1; -} -\end{VerbatimN} -\vspace{-9pt} + Why not the more intuitive form of the fastpath shown in + \cref{lst:count:Intuitive Fastpath}? \QuickQuizAnswer{ Two words. ``Integer overflow.'' - Try the above formulation with \co{counter} equal to 10 and + Try the formulation in \cref{lst:count:Intuitive Fastpath} + with \co{counter} equal to~10 and \co{delta} equal to \co{ULONG_MAX}. Then try it again with the code shown in Listing~\ref{lst:count:Simple Limit Counter Add, Subtract, and Read}.
Signature · 1 line
2.17.1
PATCH 5/6 Use unbreakable endash in \clnrefrange{}{}
In reply to Akira YokosawaFrom 58779425864798ce510aad617746f3b3360868bc Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <[email protected]>
Date: Sat, 11 Jan 2020 18:29:59 +0900
Subject: [PATCH 5/6] Use unbreakable endash in \clnrefrange{}{}
Using a shortcut macro "\==" instead of a plain endash ("--") can prevent widowing of the 2nd cross reference.
NOTE:
cleveref's \crefrangeconjunction macro could also be changed as well to change the behavior of \crefrange and \Crefrange commands. However, such a change would end up in large under/over fill where generated cross-references are more than a few characters long.
--- perfbook.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
perfbook.tex +2 -2
@@ -236,8 +236,8 @@ } \newcommand{\clnref}[1]{\clnrefp{#1}{line}} \newcommand{\Clnref}[1]{\clnrefp{#1}{Line}} -\newcommand{\clnrefrange}[2]{lines~\lnref{#1}--\lnref{#2}} -\newcommand{\Clnrefrange}[2]{Lines~\lnref{#1}--\lnref{#2}} +\newcommand{\clnrefrange}[2]{lines~\lnref{#1}\==\lnref{#2}} +\newcommand{\Clnrefrange}[2]{Lines~\lnref{#1}\==\lnref{#2}} \newcommand{\clnrefthro}[2]{lines~\lnref{#1} through~\lnref{#2}} \newcommand{\Clnrefthro}[2]{Lines~\lnref{#1} through~\lnref{#2}} \newcommand{\pararef}[1]{Paragraph ``\nameref{#1}'' on Page~\pageref{#1}}
Signature · 1 line
2.17.1
PATCH 6/6 Reduce footnote width in 1c layout
In reply to Akira YokosawaFrom 72662b6c10b8d10e713ff7a28df43a4606d96ea0 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <[email protected]>
Date: Sun, 12 Jan 2020 00:13:58 +0900
Subject: [PATCH 6/6] Reduce footnote width in 1c layout
Textwidth of 1c layout is too wide for footnotesize font. Reduce the width by increasing right-side margin used by the "footmisc" package as is suggested in [1].
[1]: https://tex.stackexchange.com/questions/321264/
--- perfbook.tex | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
perfbook.tex +5 -1
@@ -119,7 +119,11 @@ \newcommand{\IfToArxiv}[2]{\ifthenelse{\boolean{toarxiv}}{#1}{#2}} \IfTwoColumn{}{ -\setboolean{colorlinks}{true} + \setboolean{colorlinks}{true} + \renewcommand\footnotelayout{% + \advance\leftskip 0.0in + \advance\rightskip 0.7in + } } \IfColorLinks{
Signature · 1 line
2.17.1
Quoted 50 lines · Akira Yokosawa
Hi Paul,
(LaTeX adviser hat on)
This patch set is prompted by a recent update of the "epigraph" package mentioned in the change log of 3/6.
epigraph v1.5e now suppress epigraphs from orphaned (appear at the bottom of a page/column).
In 2C layout of v2019.12.22a, epigraphs of Sections 9.5, 10.2, and 10.4 are orphaned.
Upgrading to epigraph v1.5e resolves the issue, but there is another occurence of orphaned heading of Section 10.2.2 (1C layout of v2019.12.22a).The reason of the orphaned heading is the float object at the beginning of the sub section. I've found a recommendation of where to put floats in LaTeX sources at
https://www.latex-project.org/publications/2014-FMi-TUB-tb111mitt-float-placement.pdf
,as mentioned in the change log of 2/6. It is a good read for the algorithm of float placement by LaTeX.
Quote from Section 4.7:Do not place a float directly after a heading, unless it is a heading that always starts a page. The reason is that headings normally form very large objects (as a heading prevents a page break directly after it). However placing a float in the middle of this means that the output routine gets triggered before LATEX makes its decision where to break and any footnotes get moved into the wrong place.
So, I moved such floats in 2/6. I might have missed one or two of other such floats, though.
Patch 1/6 fixes a minor typo in epigraph.
Patch 2/6 moves floats as mentioned above.
Patch 3/6 enforces the upgrade of epigraph package, and also applies "nowidow" package to prevent orphan/widow lines. As mentioned in the change log, this change will cause large gaps between paragraphs on a few pages. You might find them ugly, but I prefer the ease of read, especially short QQZs. Patch 4/6 retouches a quick quiz to avoid such a large gap at the end of the Quiz part.
Patch 5/6 changes the definition of \clnrefrange and \Clnrefrange to prevent breaks at endashes.
Patch 6/6 is unrelated to widow/orphan, but improves the readability of longer footnotes in 1C layout.
Quoted 3 lines
Patches 3/6, 5/6, and 6/6 modifies preamble (and related FAQ-BUILD.txt) only. You can skip any of them if you'd be inclined to.
They all look good, thank you! Applied and pushed.
Thanx, Paul
Quoted 31 lines
Thanks, Akira
--
Akira Yokosawa (6):
together/count: Fix double quotes in epigraph Prevent section heading from orphaned
Prevent section epigraph from orphaned
count: Promote code snippet in Quiz part of QQZ to listing Use unbreakable endash in \clnrefrange{}{} Reduce footnote width in 1c layoutFAQ-BUILD.txt | 7 +- SMPdesign/beyond.tex | 13 ++- appendix/toyrcu/toyrcu.tex | 167 +++++++++++++++---------------- count/count.tex | 111 +++++++++++---------- datastruct/datastruct.tex | 77 +++++++-------- defer/rcuapi.tex | 32 +++--- defer/rcuusage.tex | 15 ++- formal/axiomatic.tex | 24 ++--- formal/dyntickrcu.tex | 194 ++++++++++++++++++------------------- formal/ppcmem.tex | 14 +-- formal/spinhint.tex | 59 ++++++----- locking/locking.tex | 79 ++++++++------- memorder/memorder.tex | 60 ++++++------ perfbook.tex | 13 ++- together/applyrcu.tex | 48 ++++----- together/count.tex | 2 +- 16 files changed, 453 insertions(+), 462 deletions(-)Signature · 1 line
2.17.1