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

Markup inside the PDF's validation section in the table of content #1810

Open
verbessern opened this issue Sep 23, 2024 · 5 comments
Open

Markup inside the PDF's validation section in the table of content #1810

verbessern opened this issue Sep 23, 2024 · 5 comments

Comments

@verbessern
Copy link

verbessern commented Sep 23, 2024

As the title states, there is some markup in the TOC, like for example in Validation->Types->Function Types there is a single child node named "[t1n] [syntax/types:syntax-functype] [t2m]". This is sins quite a while, and is in many different proposals, including the wasm v3 draft. I think it is a markup spill.

@verbessern verbessern changed the title Markup inside the PDF's Validation's section in the table of content Markup inside the PDF's validation section in the table of content Sep 23, 2024
@rossberg
Copy link
Member

Hm, I don't quite get what you mean. I'm not seeing anything unusual, e.g. in the online PDF. Can you provide a screen shot?

@verbessern
Copy link
Author

In the outline of the document (table of content) if you browse the tree, some children are with this text. For example Outline->Validation->Types->Block Type has 2 children, the first one is [syntax/modules:syntax-typeidx]typeidx, as it probably has to be just typeidx.

@verbessern
Copy link
Author

That is not in the pages themselves, but in the table of content of the document (usually available for navigation in the GUI of the PDF viewers).

@rossberg
Copy link
Member

I see, yes, I can observe that.

Unfortunately, this appears to be a Sphinx limitation, which I'm not sure can be fixed or worked around. Are you sure it ever was different? The source hasn't changed in that regard since the first spec release.

@verbessern
Copy link
Author

I do not know when it appeared, but the first specs had no such depth TOC nesting, so it had no such issue. Version 2 however has, as well as the v3. I'm not familiar with this program Sphinx, but I would assume that these level 4 sections need a name, maybe only for the TOC, that is not displayed as a text in the page.

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

No branches or pull requests

2 participants