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

Inconsistent use of \colcol vs. ::\brk{} #1359

Closed
jensmaurer opened this issue Jan 13, 2017 · 3 comments
Closed

Inconsistent use of \colcol vs. ::\brk{} #1359

jensmaurer opened this issue Jan 13, 2017 · 3 comments
Assignees
@jensmaurer

Comments

@jensmaurer
Copy link
Member

jensmaurer commented Jan 13, 2017 •
edited

\colcol is defined to allow line breaks before and after the colon. Yet, we also use ::\brk{} fairly often.

\colcol 48
::\brk{} 31

For comparison, total lines with :: 4086.

We should harmonize this somehow. Suggestions:

  • (1) Replace ::\brk{} with \colcol
  • (2) Replace \colcol with ::\brk{} where still necessary (otherwise plain ::) and remove the macro.
  • (3) Replace all :: in running text with \colcol to give LaTeX more line break opportunities, possibly improving layout in a few cases.

My recommendation is (1) or (2). Opinions?
@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Jan 13, 2017
@jensmaurer jensmaurer mentioned this issue Jan 13, 2017
Merged
@tkoeppe
Copy link
Contributor

tkoeppe commented Jan 13, 2017

Partial idea: whenever \colcol can be replaced by just :: with no visual change, we should do that.

@tkoeppe
Copy link
Contributor

tkoeppe commented Feb 5, 2017

Option 2 seems best to me. It's consistent with our use of non-breaking spaces before references (foo~(\ref{bar})): We know that we could break there in a crunch, but we don't want to by default, and breaks should be applied manually. By the same token, we should have :: as the default, and we should insert \brk{} as a manual override if needed.

I am also loosely considering the idea of deleting all \brk{}s after publication and only reinserting them before the next publication. This isn't a serious suggestion, but I'd like to think of this as the mental process. We should probably try and tidy up hyphenation hints regularly, since they're the very model of brittle things that rot almost immediately.

@jensmaurer jensmaurer self-assigned this Feb 8, 2017
@jensmaurer
Copy link
Member Author

@tkoeppe: I'm not sure about hyphenation and line-break hints rotting instantly; most of the text in the standard seems to be quite stable.

jensmaurer added a commit to jensmaurer/draft that referenced this issue Feb 8, 2017
@jensmaurer
Replace \colcol by ::
734ae4b 
Explicit line-break hints are added after the :: where necessary.

Fixes cplusplus#1359.
@jensmaurer jensmaurer mentioned this issue Feb 8, 2017
Merged
tkoeppe pushed a commit that referenced this issue Feb 15, 2017
@jensmaurer @tkoeppe
Replace \colcol by :: (#1451)
bcb5630 
Explicit line-break hints are added after the :: where necessary.

Fixes #1359.
@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Sep 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jensmaurer jensmaurer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tkoeppe @jensmaurer