From: Suvayu Ali <email@example.com>
To: Rustom Mody <firstname.lastname@example.org>
Cc: emacs-orgmode <email@example.com>
Subject: Re: exporting α/β to latex/pdf
Date: Tue, 6 May 2014 14:48:57 +0200 [thread overview]
Message-ID: <20140506124857.GA7068@chitra.no-ip.org> (raw)
On Tue, May 06, 2014 at 08:21:18AM +0530, Rustom Mody wrote:
> Suvayu said:
> The easiest solution is to use a modern TeX engine like XeTeX or LuaTeX
> > along with a font with the required glyphs. I personally use XeTeX with
> > Linux libertine fonts. You can find my setup here:
> > <https://github.com/suvayu/.emacs.d/blob/master/org-mode-config.el#L176>
> I am interested in switching over to xetex. I find however that things dont
> work very easily and googleing around I find that some fixes are needed. eg
I'm not sure what that FAQ is telling me. It seems to me, it talks
about some Perl libraries that use LaTeX. If that is the case, then I
can understand why that would be more involved. After all it is
probably accessing more low-level features.
> Do you also need to do these? Or is there something more generic/uptodate?
From a users perspective (I just call `xelatex' from the terminal, no
fancy stuff), I found I need to do the same amount of searching as I did
with pdfLaTeX. This is entirely driven by gaps in my LaTeX
That said, there are cases where it has fewer features/bugs (I listed a
few in my earlier email).
Does that answer your question in anyway? If you faced any specific
issues, I would be interested to know more.
Open source is the future. It sets us free.
prev parent reply other threads:[~2014-05-06 12:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 15:13 exporting α/β to latex/pdf Sharon Kimble
2014-05-04 16:03 ` Scott Randby
2014-05-04 19:26 ` Joost Helberg
2014-05-04 21:42 ` Suvayu Ali
2014-05-04 22:14 ` Nick Dokos
2014-05-05 15:06 ` Suvayu Ali
2014-05-05 18:38 ` Grant Rettke
2014-05-05 16:52 ` "Clément B."
2014-05-06 22:33 ` Nick Dokos
2014-05-07 23:30 ` "Clément B."
2014-05-05 0:08 ` Sharon Kimble
2014-05-06 2:51 ` Rustom Mody
2014-05-06 12:48 ` Suvayu Ali [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).