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

Mix of "see" and page numbers in the same index entry #5061

Closed
timsong-cpp opened this issue Oct 21, 2021 · 3 comments · Fixed by #5113
Closed

Mix of "see" and page numbers in the same index entry #5061

timsong-cpp opened this issue Oct 21, 2021 · 3 comments · Fixed by #5113
Assignees

Comments

@timsong-cpp
Copy link
Contributor

image

These look really odd, not the least because the "see" happens in the middle of a long list of page numbers.

It looks like the "multiple encaps" warnings in std-generalindex.ilg can be used to detect these. (But that same warning is benign in other indices where we intentionally format one of the page numbers in bold.)

@timsong-cpp timsong-cpp changed the title Mix of *see* and page numbers in the same index entry Mix of "see" and page numbers in the same index entry Oct 22, 2021
@jensmaurer
Copy link
Member

That's a tough one. Our \keyword macro automatically adds index entries with page numbers. Maybe that means "type, char32_t" simply needs to point to "char32_t".

@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Oct 23, 2021
@tkoeppe
Copy link
Contributor

tkoeppe commented Nov 19, 2021

Can we try making \keyword{foo} emit an index entry "foo (keyword)"?

@tkoeppe
Copy link
Contributor

tkoeppe commented Nov 19, 2021

Or alternatively:

 char32_t:
     see type, char32_t
     (as keyword): 12, 23, 34, 56

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Nov 19, 2021
@jensmaurer jensmaurer self-assigned this Nov 19, 2021
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