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

How to pass options to pandoc? #636

Open
zzjjzzgggg opened this issue Oct 16, 2019 · 0 comments · May be fixed by #677
Open

How to pass options to pandoc? #636

zzjjzzgggg opened this issue Oct 16, 2019 · 0 comments · May be fixed by #677

Comments

@zzjjzzgggg
Copy link

I set org as the default page type in gitit. However, the default pandoc options in gitit cannot correctly parse Asian language because an additional space character will be inserted in the HTML if there is a line break in the sentence in the source file (say, org).

The correct way to let pandoc parse Asian language is as follows.
pandoc -f org+east_asian_line_breaks -t html -o test.html test.org.

The problem is how to pass the correct option to pandoc? If I set default-page-type: org+east_asian_line_breaks in gitit.conf, there raises an error:

gitit: Unknown page type: org+east_asian_line_breaks
CallStack (from HasCallStack):
error, called at src/Network/Gitit/Util.hs:112:26 in gitit-0.12.3.1-HUbEGb7wE0e3DNcRrkhwOv:Network.Gitit.Util

This may be related to issue #215

Please guide. Thanks!

singpolyma added a commit to singpolyma/gitit that referenced this issue Dec 7, 2021
Instead of a closed list, allow anything Pandoc understands.  If there is no
markup/markupHelp file for the reader, then there will be no help, otherwise
this works as before.

Instead of special-casing +lhs this is now just a normal extension specification
understood by Pandoc.  +emoji is always added as before. Reader specs are run
through toLower for compatibility with the existing system.

Closes jgm#636
Closes jgm#580
@singpolyma singpolyma linked a pull request Dec 7, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant