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.

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

Inconsistent italicization of \nontermdef's colon in bnf and bnfkeywordtab envs #1351

Closed
Eelis opened this issue Jan 10, 2017 · 7 comments
Closed
Assignees

Comments

@Eelis
Copy link
Contributor

Eelis commented Jan 10, 2017

Compare:

@tkoeppe
Copy link
Contributor

tkoeppe commented Jan 11, 2017

I have a long standing rant about not italicising colons. It not only affects grammar, but also Note: and Example: introducers. One day we'll get to it.

@jensmaurer
Copy link
Member

@tkoeppe: Do I interpret this correctly that you want the colons to be italics in these cases?

@tkoeppe
Copy link
Contributor

tkoeppe commented Jan 11, 2017

@jensmaurer: No, heaven forbid! The point is that punctuation should never be italicizable. Italics are letters, but it really doesn't make sense to incline commas, periods, colons, or even brackets. Slanted brackets are an unfortunate outcome of digital typography (where the layman's idea of "italics" is to just shear the shapes a bit) gone wild. Good fonts keep the punctuators straight even in the italics.

I want to style notes and examples as [\textit{Note}: and --- \textit{end note}]. And we should find a similar way to make the colon after grammar productions appear straight. It's even more obvious why that's the right thing to do in that context: the colon isn't part of the production!

@jensmaurer
Copy link
Member

jensmaurer commented Jan 11, 2017

@tkoeppe: Thanks. Does @zygoloid agree with this direction?

@jensmaurer
Copy link
Member

Ah, it seems the colon after preprocessing-op-or-punc, while upright, is actually \ttfamily, which is also not what we want.

@jensmaurer jensmaurer self-assigned this Jan 11, 2017
jensmaurer added a commit to jensmaurer/draft that referenced this issue Jan 11, 2017
following the "[ Note" and "[ Example" introducers.

Fixes cplusplus#1351.
@tkoeppe
Copy link
Contributor

tkoeppe commented Jan 11, 2017

@jensmaurer: No, we never reached a conclusion on that. It's one of my big plans for C++20.

jensmaurer added a commit to jensmaurer/draft that referenced this issue Jan 11, 2017
following the "[ Note" and "[ Example" introducers.

Fixes cplusplus#1351.
@tkoeppe
Copy link
Contributor

tkoeppe commented Jan 12, 2017

Fixed by ffb9408. Thanks for providing the solution!

@tkoeppe tkoeppe closed this as completed Jan 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants