-
Notifications
You must be signed in to change notification settings - Fork 7
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
handling of automatic <a> anchors with headers #8
Comments
Yes, GitHub and most other Markdown renderers output sane anchors (such as “See Also: Chapter 5” → Since the script now supports links to anchors ( That may of course result in duplicate anchors but since they're both in the same position, that shouldn't be a problem. |
(But I've noticed a related problem: sometimes different sections have the same name, such as “Examples” sub-sections. Those should of course get different anchor names. GitHub's renderer uses |
the lack of standardization in automatic anchor link generation is a great point as a generalized tool. maybe for people who only ever target one renderer could have an option to skip the automatic generation ? that way you could put a comment in noting the lack of standardization which is why the are created in the first place. |
most common markdown renderers i'm familiar with automatically create anchors for
#
headers. there's no need to generate<a name=...>
tags for them.The text was updated successfully, but these errors were encountered: