Giter Club home page Giter Club logo

jekyll-pandoc's Introduction

jekyll-pandoc's People

Contributors

emiapwil avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

jekyll-pandoc's Issues

Footnotes and References

Hello there, I wonder if this project is still maintained... I just installed jekyll-pandoc successfully, using Pandoc 2.1 and modifying the _config.yam accordingly. I then build the site all all seems fine, but footnotes nor citepro references are not rendering at all in html.

What do you think might be the problem?

Best!
d

uninitialized constant errors...

When I attempt to build my Jekyll site, I get these errors:

Conversion error: Jekyll::Converters::Markdown encountered an error converting 'content/acme/demo.md'.
  Conversion error: uninitialized constant Jekyll::Converters::Markdown::PandocParser::FatalException
jekyll 2.4.0 | Error:  uninitialized constant Jekyll::Converters::Markdown::PandocParser::FatalException

is this because some of my markdown syntax doesn't conform to pandoc?

Syntax highlighting

Using this gem I can't get syntax highlighting to work either via jekyll or via pandoc. Is this a known problem/feature?

Trying to use jekyll-pandoc with jekyll 4.

I followed instructions (GEMFILE, bundle install, _config.yaml), but the build seems to not recognise Pandoc as markdown processor.

Markdown processor: "Pandoc" is not a valid Markdown processor.
                    Available processors are: kramdown
                    
  Conversion error: Jekyll::Converters::Markdown encountered an error while converting '_portfolio/example.md':
                    Invalid Markdown processor given: Pandoc
             ERROR: YOUR SITE COULD NOT BE BUILT:
                    ------------------------------------
                    Invalid Markdown processor given: Pandoc
> bundle info jekyll
  * jekyll (4.1.1)
	Summary: A simple, blog aware, static site generator.
	Homepage: https://jekyllrb.com
	Path: /home/me/gems/gems/jekyll-4.1.1
> bundle info jekyll-pandoc
  * jekyll-pandoc (2.0.1)
	Summary: Jekyll Pandoc markdown converter
	Homepage: https://github.com/mfenner/jekyll-pandoc
	Path: /home/me/gems/gems/jekyll-pandoc-2.0.1

markdown+extension

How should I configure the --from option of pandoc?
I want to enable some extension like autolink_bare_uris

in the command line I would do:
pandoc --from=markdown+autolink_bare_uris

Table of contents (support the --toc option)

I am looking for a way to create a table of contents for long pages. Pandoc supports this for standalone documents only:

pandoc -s --toc doc.md  # works
pandoc --toc doc.md  # does not work

This is intentional: A closed pandoc ticket explains that one could use standalone mode with a minimal custom pandoc template to get what I want.

I realize you are busy so I will try to come up with a patch.

bib references on a per page basis

hi @mfenner, thanks for such a great plugin. it promises to allow us to do print and web based on the same markdown. that is a huge win in my neck of the woods. quick question, is there any way as-is to add separate .bib reference files, per post? we're designing a journal, with issues, so it would be nice to have separate .bib files, at the very least at the issue level. am i missing something obvious?

Extensions with underscores not parsing correctly

I'm trying to use the 'markdown_in_html_blocks' extension. When I add it in _config,yml and try to build with Jekyll, I get the following error:

Conversion error: Jekyll::Converters::Markdown encountered an error while converting '_posts/2014-08-20-another-post.md':
pandoc: unrecognized option `--markdown-in-html-blocks' Try pandoc --help for more information.

Notice that the error shows the option as having hyphens instead of underscores. I tested this out with a few other extensions that have underscores and saw the same pattern. Random extensions that do not have underscores did not result in an error.

_config.yml:

# Markdown config
gems: [ jekyll-pandoc ]
markdown: Pandoc
pandoc:
  extensions:
    - markdown_in_html_blocks

Pandoc has changed the --smart option

Pandoc 2.0.1 (or earlier?) has replaced the --smart option with (for example) markdown+smart. This plugin doesn't work with Pandoc 2.0.1, because it still specifies the command-line option --smart.

jekyll v3

It would be great to have jekyll v3 support, especially for incremental build support.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.