From: Alan Storm <alan.storm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Pandoc, XeLaTex, and Hebrew Characters
Date: Sat, 17 Jun 2017 09:35:05 -0700 (PDT) [thread overview]
Message-ID: <3d7a8fd7-346d-4c74-ad52-e137c9509719@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2509 bytes --]
New to the group, and only (so far!) the most casual of pandoc users. I'm
having some trouble getting pandoc to do things that the xelatex command
can do. I'm looking for someone (or someones) that can help get me to a
solution **and** explain what pandoc is doing behind the scenes so I can
debug these sort of problems in the future.
In short -- I have an tex document with some hebrew characters. If I use
the xelatex command directly to convert this document, the hebrew
characters are rendered correctly in the PDF
$ xelatex simple.tex
However, if I attempt to do the conversion with pandoc using the
xelatex engine
$ pandoc --latex-engine=xelatex simple.tex -o from-pandoc.pdf
pandoc will render the PDF **without** the hebrew characters. There's just
blank white space where the hebrew should be.
So, first question if anyone knows: How do I make pandoc render the hebrew
into a PDF?
If there's no clear path to that answer, how to do I debug the
pandoc/xelatex interaction in order to understand why pandoc's use of the
engine produces different results, and how I might be able to change that
invocation. Regarding this -- my understanding of pandoc is very limited,
so baby words/steps that let me become less of a baby are appreciated :)
Also, I have some specific examples posted over on the tex StackExchange
with hebrew examples
https://tex.stackexchange.com/questions/375380/getting-hebrew-support-working-with-pandoc/375443
https://tex.stackexchange.com/questions/375380/getting-hebrew-support-working-with-pandoc
Finally -- my ultimate goal here is to convert HTML documents with hebrew
into PDFs. As that also doesn't work, I'm focused on understanding the
[tex] to [pdf] conversion. If there's some extra wrinkle involved with
[html] to [pdf] ( which I presume -- (correctly?) -- involves xelatex in
the middle) feel free to chime in there as well.
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/3d7a8fd7-346d-4c74-ad52-e137c9509719%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 4841 bytes --]
next reply other threads:[~2017-06-17 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 16:35 Alan Storm [this message]
[not found] ` <3d7a8fd7-346d-4c74-ad52-e137c9509719-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-06-17 18:55 ` Joost Kremers
[not found] ` <87tw3efnqr.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2017-06-17 22:04 ` John MacFarlane
2017-06-19 5:17 ` Kolen Cheung
2017-06-20 22:21 ` Alan Storm
[not found] ` <ab8c9513-f33d-4965-8c3c-a10c855c9a3d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-06-22 0:01 ` Kolen Cheung
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d7a8fd7-346d-4c74-ad52-e137c9509719@googlegroups.com \
--to=alan.storm-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).