public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Kolen Cheung <christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Pandoc, XeLaTex, and Hebrew Characters
Date: Sun, 18 Jun 2017 22:17:45 -0700 (PDT)	[thread overview]
Message-ID: <82970484-7c5f-40aa-9190-b01626559faa@googlegroups.com> (raw)
In-Reply-To: <3d7a8fd7-346d-4c74-ad52-e137c9509719-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

Another problem you may hit is that Hebrew is Right to Left, and it is kind of non-trivial to get it right. The tricky thing is to tell (Xe)LaTeX that a certain text is Right to Left instead.

If your whole document are in Hebrew, you can probably configure your whole document to be right to left. If not, you need to enclose each use of Hebrew by a command that specifies its language.

I tried using ucharclasses in LaTeX for auto detect this Hebrew boundary, but the problem is the space between each Hebrew word will break the boundary, and hence each Hebrew word will be right to left but the whole sentense will be left to right.

To specify the language of a region, I think pandoc has a native way to do it (see the manual for the lang attribute) and I guess it will translate into the proper LaTeX command (you should test though).

  parent reply	other threads:[~2017-06-19  5:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-17 16:35 Alan Storm
     [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 [this message]
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=82970484-7c5f-40aa-9190-b01626559faa@googlegroups.com \
    --to=christian.kolen-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).