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

[C++17 DIS comment 019] Document has lists of tables and figures, xrefs, and indices #1731

Closed
zygoloid opened this issue Sep 6, 2017 · 5 comments
Labels
ballot-comment Response to an NB or ISO comment on a ballot
Milestone

Comments

@zygoloid
Copy link
Member

zygoloid commented Sep 6, 2017

Unclear what action is expected here. The "Proposed Change" does not propose a change. Suggestion: accepted, no change.

@zygoloid zygoloid added the ballot-comment Response to an NB or ISO comment on a ballot label Sep 6, 2017
@zygoloid zygoloid modified the milestone: C++17 IS Sep 6, 2017
@tkoeppe
Copy link
Contributor

tkoeppe commented Sep 7, 2017

I assume the perceived problem here is that different styles of naming are used for index-like constructions: "List of X" for tables and figures, just "Cross references" without any keyword, and "Index of X" for various indexes.

However, all this seems entirely sensible, because each heading says precisely what it means. We could contort ourselves and say "Index of cross references", but it would be baroque.

@zygoloid
Copy link
Member Author

zygoloid commented Sep 7, 2017

The proposed resolution says: "The ISO template does not support these elements but, as a PDF-only submission, SC22 is responsible for the accuracy of these elements."

I don't see how that's a proposed resolution at all, unless what they want us to say is "we resolve to take responsibility for the accuracy of these elements"...

Seems like we want to respond with "This is not a proposal for a change to the document", but I don't know whether that makes the comment ACCEPTED or REJECTED.

@tkoeppe
Copy link
Contributor

tkoeppe commented Sep 7, 2017

Hm, I believe the drafting directives also don't say that you should, or can (?) have a table of contents. Yet the checklist at the end says you should check the table of contents. Nor does it seem to mention indexes. It seems reasonable to me that the directives give leeway to include such tables, and it doesn't seem like a stretch that indexes should be allowed.

@jensmaurer
Copy link
Member

If we don't change anything in response to the comment, I guess it's REJECTED with the rationale "The mentioned parts are vital in navigating our 1600-page document. They are machine-generated and therefore automatically remain synchronized with the document pagination and section numbering."

@zygoloid
Copy link
Member Author

Jens' rationale sounds good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ballot-comment Response to an NB or ISO comment on a ballot
Projects
None yet
Development

No branches or pull requests

3 participants