Closes #360: non-ascii heading id generation#362
Closed
orelby wants to merge 2 commits into
Closed
Conversation
Author
|
On a second thought, this patch doesn't really help. When non-ascii characters are used in headings IDs, it means the heading will not be linked to in most ebook files. Not only those characters, but also question marks could cause that in some ebook files. This could be solved by using the syntax suggested in issue #382 in non-English books, meaning simply moving to kramdown, or even Extra Markdown. |
|
Fixed by GitbookIO/kramed#8 |
This was referenced Nov 26, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.