emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Florian Beck <abstraktion@t-online.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Unicode and Latex export
Date: Sun, 7 Aug 2011 18:50:34 +0200	[thread overview]
Message-ID: <CAMXnza3PM=WPBmPGMZ3O16LnL-PGi4Dcj9LEg3pnE=v_0gxKpg@mail.gmail.com> (raw)
In-Reply-To: <87mxflb2qx.fsf@sophokles.streitblatt.de>

Hi Florian,

On Sun, Aug 7, 2011 at 6:33 PM, Florian Beck <abstraktion@t-online.de> wrote:
>> My lisp is not very good, but what is the need for such an extensive
>> setup? Isn't setting org-latex-to-pdf-process to xelatex enough to
>> switch packends?
>
> It is, more or less. XeLaTeX needs a different header, that is what the
> instructions set up. However, I would recommend keeping it simple and
> put your packages etc in your own style file.
>
> In `org-export-latex-classes', replace
>
>         "\\documentclass[11pt]{article}"
>
> with
>
>         "[NO-DEFAULT-PACKAGES]
>         \\documentclass[11pt]{article}\n\\usepackage{myxe}"
>
> and put everything you need in myxe.sty.
>

That is a good solution. I think I will consider this.

> BTW, this only works if you use a font that provides all the characters
> you need (and looks nice enough for your taste).

I don't usually customise my fonts and go with the default latex
fonts. Do you have any suggestions what fonts that would be
appropriate here? I tried using XITS, but that didn't help.

> Alternatively, you could
> use `org-export-latex-final-hook' and write a function that translates
> unicode characters to latex code.
>

I have considered this, but as I mentioned I am not well versed in
lisp. Going this route might be more fun, but not good for work. ;)

Thanks,

-- 
Suvayu

Open source is the future. It sets us free.

next prev parent reply	other threads:[~2011-08-07 16:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-06 23:25 Unicode and Latex export suvayu ali
2011-08-07 10:01 ` Christopher Witte
2011-08-07 12:15   ` suvayu ali
2011-08-07 16:33     ` Florian Beck
2011-08-07 16:50       ` suvayu ali [this message]
2011-08-07 16:54         ` suvayu ali
2011-08-07 18:07           ` Florian Beck
2011-08-07 18:28             ` suvayu ali
2011-08-07 18:41               ` Florian Beck
2011-08-07 18:49                 ` suvayu ali
2011-08-31  7:30         ` Aditya Mandayam
2011-08-31 17:18           ` Aditya Mandayam
2011-08-07 16:36     ` Christopher Witte
2011-08-07 16:45       ` suvayu ali
2011-08-08  6:13 ` Sebastien Vauban
2011-08-08  6:57   ` suvayu ali
2011-08-08  7:09     ` Nick Dokos
2011-08-08  7:17       ` suvayu ali
2011-08-08  7:53   ` Stefan Nobis
2011-08-08  8:42     ` suvayu ali

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMXnza3PM=WPBmPGMZ3O16LnL-PGi4Dcj9LEg3pnE=v_0gxKpg@mail.gmail.com' \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=abstraktion@t-online.de \
    --cc=emacs-orgmode@gnu.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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).