emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan Nobis <stefan-ml@snobis.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: exporting to PDF multi-lingual document
Date: Sun, 02 Jul 2023 15:50:23 +0000	[thread overview]
Message-ID: <87v8f28g8w.fsf@localhost> (raw)
In-Reply-To: <m1cz1a73o6.fsf@nobis-it.eu>

Stefan Nobis <stefan-ml@snobis.de> writes:

> On the other hand: Luatex is much more flexible and has better support
> for modern fonts and modern font render engines.

So does xelatex, AFAIU.

> It depends what one assumes to be the most common use case for Org. If
> it's many rather short and simple documents then pdftex should suffice
> most of the time and the fast compile speed will matter. If we want to
> support as many different situations out of the box, I think luatex
> would be the better/easier way - at the cost of slower compilation
> speeds.

The problem with luatex (and xelatex) is export to .tex files. Org is
sometimes used when writing research papers and journals generally
demand pdflatex, not luatex.

Also, some people explicitly add LaTeX headers to their documents -
headers that may or may not be compatible with LuaTeX.

What could be done is having #+LATEX_COMPILER set to something like
'auto by default - use luatex for some non-English #+LANGUAGE settings,
but fall back when headers are customized.

> Additionally, we might try to detect situations in which
> luatex would be the better choice (e.g. certain languages). But this
> would certainly be more work and lead to more complex code.

The most immediate problem to solve is figuring out a good universal
preamble that will work with UTF8 Org sources that can contain arbitrary
(known) languages.

The code will be more complex, but Timothy's work on conditional
preamble should make things much easier. So, complexity should not stop
us - the necessary infrastructure will be in place sooner or later.
https://list.orgmode.org/orgmode/875yc95rxp.fsf@tec.tecosaur.net/

> Another approach: Use pdftex for simple/short documents and make
> selection of luatex as backend engine per document as easy as
> possible.

It is already easy - #+LATEX_COMPILER

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2023-07-02 15:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 19:19 exporting to PDF multi-lingual document Andrés Ramírez
2023-06-30 19:42 ` Ihor Radchenko
2023-07-01 17:39   ` andrés ramírez
2023-06-30 20:50 ` Dr. Arne Babenhauserheide
2023-07-01 10:54   ` Ihor Radchenko
2023-07-01 17:39   ` andrés ramírez
2023-07-02  0:00     ` Dr. Arne Babenhauserheide
2023-07-02  8:11     ` Stefan Nobis
2023-07-02  8:49       ` Ihor Radchenko
2023-07-02 15:07         ` Stefan Nobis
2023-07-02 15:50           ` Ihor Radchenko [this message]
2023-07-02 15:52           ` Dr. Arne Babenhauserheide
2023-07-02 16:50             ` Stefan Nobis
2023-07-02 15:28         ` Stefan Nobis
2023-07-02 15:55           ` Ihor Radchenko
2023-07-02 16:53             ` Stefan Nobis
2023-07-02 16:59               ` Ihor Radchenko
2023-07-03  5:46                 ` Stefan Nobis
2023-07-03  7:24                   ` Thomas Dye
2023-07-03  8:15                   ` Ihor Radchenko
2023-07-02 14:35       ` andrés ramírez
2023-07-02 14:55         ` Stefan Nobis
2023-07-02 16:36           ` andrés ramírez

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=87v8f28g8w.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=stefan-ml@snobis.de \
    /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.
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).