Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[std] 'subclause \\ref' cleanups #4123

Open
JohelEGP opened this issue Aug 24, 2020 · 1 comment
Open

[std] 'subclause \\ref' cleanups #4123

JohelEGP opened this issue Aug 24, 2020 · 1 comment

Comments

@JohelEGP
Copy link
Contributor

As a follow up to #3354 and its resolving PR, grepping for 'subclause \ref' reveals:

algorithms.tex:the algorithms specified in this subclause \ref{specialized.algorithms}
concepts.tex:The concepts in subclause \ref{concepts.callable} describe the requirements on function
expressions.tex:considered further according to the rules in subclause \ref{expr.compound};
numerics.tex:Throughout this subclause \ref{rand},
numerics.tex:Throughout this subclause \ref{rand},
numerics.tex:Throughout this subclause \ref{rand},
numerics.tex:of this subclause \ref{rand.req.seedseq}.
numerics.tex:of this subclause \ref{rand.req.eng}.
numerics.tex:of this subclause \ref{rand.req.dist}.
numerics.tex:In this subclause \ref{rand},
support.tex:For the purposes of subclause \ref{cmp.categories},
utilities.tex:For the purposes of subclause \ref{smartptr},
utilities.tex:Each specialization of a class template specified in this subclause \ref{func.search}

If "this subclause" is really the current subclause, then the \ref is redundant and should be dropped to be consistent with 147 other "this subclause". Also, for these and capital Subclause, a ~ is inconsistently placed between subclase and \ref. I don't know what that does, though. I suppose it makes the text a single entity for some purpose.
@jensmaurer
Copy link
Member

The ~ prevents LaTeX from applying a line break at that point (= non-breaking space).
We occasionally have "this subclause", but actually mean the parent subclause. This happens when text got moved to a sub-subclause, e.g. a "preamble" section was introduced.

@JohelEGP JohelEGP mentioned this issue Aug 24, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JohelEGP @jensmaurer