From: Joost Kremers <joostkremers-97jfqw80gc6171pxa8y+qA@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: ligatures in html
Date: Tue, 22 Sep 2015 12:26:09 +0200 [thread overview]
Message-ID: <87twqmycla.fsf@fastmail.fm> (raw)
In-Reply-To: <874daeba-ced3-4d7d-b2ad-b0178e5a079b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
On Tue, Sep 22 2015, david.pw.smith-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
> Indeed, for me, Pandoc's default tex template outputs the unicode
> characters correctly, but this could be because my environment is set up to
> use XeLaTeX.
Well, that's probably not the reason, unless you've symlinked the
command `pdflatex` to `xelatex`. Pandoc's default latex template uses
the inputenc package with the [utf8] option. This ensures that LaTeX
accepts utf8 encoded input files, whereby non-ASCII-characters are
translated into LaTeX commands that produce them. So `æ` in the input
file will be translated to `\ae`, which will then be replaced with the
glyph `æ` in the pdf output.
One reason to still use XeLaTeX (or LuaLaTeX) is that inputenc does not
support all Unicode characters, though. And It's easier to use system
fonts.
--
Joost Kremers
Life has its moments
--
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/87twqmycla.fsf%40fastmail.fm.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2015-09-22 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 10:57 Chris Wright
[not found] ` <7d633ff1-c25d-436c-a66f-9a8456699db6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-09-21 14:50 ` 'Jason Seeley' via pandoc-discuss
[not found] ` <bbaae9b2-c139-415f-9063-86a887358b4c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-09-21 20:54 ` John MACFARLANE
[not found] ` <20150921205458.GA92420-4kKid1p5UN4xFjuZnxJpBp3lxR28IOakuDuwTybUTCk@public.gmane.org>
2015-09-22 1:03 ` Chris Wright
2015-09-22 9:52 ` david.pw.smith-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <874daeba-ced3-4d7d-b2ad-b0178e5a079b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-09-22 10:12 ` Stefan Björk
2015-09-22 10:26 ` Joost Kremers [this message]
[not found] ` <87twqmycla.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2015-09-23 3:37 ` Chris Wright
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=87twqmycla.fsf@fastmail.fm \
--to=joostkremers-97jfqw80gc6171pxa8y+qa@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).