public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: how to get a Hebrew markdown converted correctly to pdf?
Date: Thu, 22 Jun 2017 08:47:16 +0200	[thread overview]
Message-ID: <20170622064716.GF14957@Johns-MBP.home> (raw)
In-Reply-To: <9412beaf-ee33-40e5-86d0-8543e819f2a2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Do you have an older version of pandoc, perhaps, on the
linux machine?

+++ Noam Izhaki [Jun 21 17 13:00 ]:
>   Hi Gil,
>   I'm trying to generate a docx from HTML and I get a left aligned
>   document. I've tried to pass dir:RTL variable but it doesn't help.
>   interesting thig is that I'm trying doing it on my machine(windows,
>   support Hebrew) everything is fine, but when trying on
>   production(Linux) it doesn't work.
>   do you have any idea?
>   would love to discuss with you here or over a short cellphone (I'm from
>   Israel, too)
>   Many thanks,
>   Noam
>   בתאריך יום רביעי, 10 באוגוסט 2016 בשעה 15:02:00 UTC+3, מאת Gilco333:
>
>   Hi guys!
>   I have read thoroughly the Pandoc user's guide,
>   and focused on the language variables,  have set the relevant
>   variables:
>   pandoc  --variable=title:"my example --variable=dir:rtl hebrew.txt
>   --latex-engine=xelatex  -o hebrew.pdf
>   I noticed the variable --variable=otherlangs:he , does no change at
>   all. how come?
>   the actual output is all Hebrew characters got disappeared after
>   exporting to pdf file.
>   since I have used the dir:rtl, the other characters were aligned to the
>   right.
>   can someone please suggest a solution?
>   Thank you all for the assistance
>   Gil
>
>   --
>   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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/9412beaf-ee33-40e5-
>   86d0-8543e819f2a2%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/9412beaf-ee33-40e5-86d0-8543e819f2a2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout

-- 
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/20170622064716.GF14957%40Johns-MBP.home.
For more options, visit https://groups.google.com/d/optout.


      parent reply	other threads:[~2017-06-22  6:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 12:01 Gilco333
     [not found] ` <55be8a86-a634-4e5d-8725-302d4cca9f3a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-08-10 23:08   ` Joost Kremers
     [not found]     ` <87d1lgjk7z.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2016-08-12  9:49       ` Gilco333
2017-06-21 20:00   ` Noam Izhaki
     [not found]     ` <9412beaf-ee33-40e5-86d0-8543e819f2a2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-06-22  6:47       ` John MacFarlane [this message]

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=20170622064716.GF14957@Johns-MBP.home \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).