Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Only some kramdown options are supported #1095
Is there any reason that only a few of the Kramdown options are passed? I'm trying to use org-mode to generate jekyll pages via octopress, and I'm trying to make this org-mode syntax work. I need to insert markdown, as the link generation of org-mode cannot be used...So it's useful to allow passing some jekyll markdown from the org-mode conversion.
Here's a full description of how I have this setup. http://octopress.dev/blog/2013/04/27/octopress-setup-with-github-and-org-mode/
The only other option seems to be to use all absolute URLs, which is not idea.
Here is a snippet from markdown.rb, line 112 (and same exact code 129). The last option shown below is not in the code base.
Here's the proposed _config.yml
It might be worthwhile to pass all kramdown options so that when a new option is added to a markdown engine, the options are simply passed through to the markdown engine.
I can look into making this change, but I need to get employer approval before contributing to any open source project, which can be a very slow process.
I'm afraid that your octopress.dev link won't work since
On Mon, May 13, 2013 at 3:21 AM, Justin firstname.lastname@example.org wrote:
So we could easily support all these options if we read everything in like this:
# in lib/jekyll/core_ext.rb # :heart:-ly ripped from rails core extensions class Hash def symbolize_keys! keys.each do |key| self[(key.to_sym rescue key) || key] = delete(key) end self end def symbolize_keys dup.symbolize_keys! end end # in lib/jekyll/converters/markdown/kramdown.rb Kramdown::Document.new(content, @config["kramdown"].symbolize_keys)
Then you just specify your option and value under
You can view the source for this here: https://github.com/justin808/justin808.github.io
@parkr is what I'm thinking would be much better for all markdown modes.
referenced this issue
Mar 3, 2014
I am sorry to comment on such an old issue but it seemed like the most appropriate place to ask my question without opening a new issue.
We are currently in the process of translating http://sass-guidelin.es in several languages. Site runs on Jekyll, hosted on GitHub Pages, Kramdown as a Markdown parser of course.
We use auto IDs (option
Kramdown supports an option to convert non-latin characters into latin in order to preserve IDs usability: http://kramdown.gettalong.org/options.html#option-transliterated-header-ids.
I tried putting this configuration in my
# Build settings markdown: kramdown kramdown: transliterated_header_ids: true
Any idea how to proceed perhaps?