From: Emiliano <gattulli.emiliano-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Bidirectional Markdown documents to PDF
Date: Sun, 6 Mar 2022 07:03:53 -0800 (PST) [thread overview]
Message-ID: <dbe5712e-c50d-43e9-8046-48d16f5ee1b8n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1109 bytes --]
Hi everyone! I love Markdown and Pandoc, they are an incredible couple! For
my studies, I need to write bidirectional documents prevalently using
English/Italian with ancient Hebrew. I have no issue whatsoever when I work
with Markdown files. However, when I convert the Markdown document to PDF
through Pandoc (using XeLaTex as PDF engine), the Hebrew words are inverted
due to the left-to-right default setting. My question is: How can I tell
Pandoc to treat specific sentences or words as right-to-left and then go
back to the default left-to-right? It is obvious to me that this work
should be done in the Markdown document, but I just don't know how! Thanks
in advance for your help!
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/dbe5712e-c50d-43e9-8046-48d16f5ee1b8n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1385 bytes --]
next reply other threads:[~2022-03-06 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 15:03 Emiliano [this message]
[not found] ` <dbe5712e-c50d-43e9-8046-48d16f5ee1b8n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-03-06 16:53 ` BPJ
[not found] ` <CADAJKhBx55tiRuvJqQGQGapLsi21PcWayCagBtj8wUb27S4sTQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-03-07 10:30 ` Emiliano
[not found] ` <aed50487-27b8-4ff0-83a6-3bd4bd68b59dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-03-07 20:37 ` BPJ
[not found] ` <CADAJKhAo7+fR77OO-kxnG98PD6j+Abtb3xyHLx9tr_HJJXXXwQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-03-08 9:15 ` AW: " denis.maier-NSENcxR/0n0
[not found] ` <f169e0fcedb04d2d8bb9d6b0c8ee4219-NSENcxR/0n0@public.gmane.org>
2022-03-08 16:44 ` John MacFarlane
[not found] ` <m25yoov1fn.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2022-03-09 14:43 ` Emiliano
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=dbe5712e-c50d-43e9-8046-48d16f5ee1b8n@googlegroups.com \
--to=gattulli.emiliano-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).