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

<ol> was not rendered properly if there are Chinese characters. #636

Closed
hbrls opened this issue Sep 4, 2012 · 6 comments
Closed

<ol> was not rendered properly if there are Chinese characters. #636

hbrls opened this issue Sep 4, 2012 · 6 comments

Comments

@hbrls
Copy link

hbrls commented Sep 4, 2012

I think I can use this md format to get rendered <ol>

1. bla bla bla
2. bla bla bla

But this only works with English letters, but not Chinese characters. It just ignored the 1., and rendered it as plain text like:

1. 句子 2. 句子

I've a demo of this issue:

github rendered this correctly

my blog using jekyll not

@jeremyroman
Copy link

This appears to be a bug in Maruku, rather than Jekyll. I would suggest filing an issue against them.

As a workaround, use one of the alternative Markdown implementations instead. Adding markdown: rdiscount to your configuration or using --rdiscount as a command-line option will do the trick (you'll need to install the rdiscount gem, of course). kramdown and redcarpet are your other options.

@hbrls
Copy link
Author

hbrls commented Dec 20, 2012

I don't have jekyll on my own machine. And I'm totally rely on GitHub's Page service. Are you suggesting that GitHub->jekyll->Maruku has a bug while GitHub->itself uses a different markdown interpreter that doesn't have this bug?

@jeremyroman
Copy link

GitHub uses a different Markdown interpreter than Maruku, yes (redcarpet, IIRC). I'm pretty sure GitHub Pages supports the other ones, though. Have you tried putting something like this in your _config.yml?

markdown: rdiscount

(or kramdown, or redcarpet)

@hbrls
Copy link
Author

hbrls commented Dec 20, 2012

I'm using markdown: redcarpet now, and it's all right. Thanks for your help! Can I move this issue to Maruku or created a new issue there?

@jeremyroman
Copy link

I'm not aware of a way to move issues from one repository to another. You'll probably have to check to see if they have an existing issue open on this, and if not, open a new issue there and close this one.

@parkr
Copy link
Member

parkr commented Dec 22, 2012

Looks like you got it working fine on your site.

File an issue with Maruku over there – there's no way to move the issue. Thanks!

@parkr parkr closed this as completed Dec 22, 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.
Projects
None yet
Development

No branches or pull requests

4 participants