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

Auto generated ID for h1-h6 should support multi-language #471

Closed
mytharcher opened this Issue Jan 16, 2012 · 2 comments

Comments

Projects
None yet
3 participants
@mytharcher

mytharcher commented Jan 16, 2012

This issue is additional about #110's duplicated ID problem.

It still happen in case that the title contains other language characters like Chinese words. For example:

## abc之一
## abc之二

than the compiled html output this:

<h2 id="abc">abc之一</h2>
<h2 id="abc">abc之二</h2>

It ignored the characters unless [a-z]. In neither maruku nor rdiscount it can work right.

And I highly recommend that it should output all the title string as same as anyone wrote. Unless these cases:

  1. If the title has been used once, than add a unique random suffix;
  2. If the title contains space, than use hyphen "-" instead;

I know that it may be the markdown engine's affair, but I saw the maruku's bug list hadn't update since 2011-04-14 02:23. And this issue happen in my using Jekyll, so I post here for asking help.

Hope you can help, thank you!

@stereobooster

This comment has been minimized.

Show comment
Hide comment
@stereobooster

stereobooster Feb 6, 2012

Contributor

Try MultiMarkdown (#379) or Redcarpet (#450, #487)

Contributor

stereobooster commented Feb 6, 2012

Try MultiMarkdown (#379) or Redcarpet (#450, #487)

@mytharcher

This comment has been minimized.

Show comment
Hide comment
@mytharcher

mytharcher Feb 7, 2012

Thank you! I also found Kramdown works right.

mytharcher commented Feb 7, 2012

Thank you! I also found Kramdown works right.

@mytharcher mytharcher closed this Feb 7, 2012

@jekyll jekyll locked and limited conversation to collaborators Feb 27, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.