emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Stefan Nobis <stefan-ml@snobis.de>
To: emacs-orgmode@gnu.org
Subject: Re: exporting to PDF multi-lingual document
Date: Sun, 02 Jul 2023 17:07:21 +0200	[thread overview]
Message-ID: <m1cz1a73o6.fsf@nobis-it.eu> (raw)
In-Reply-To: <87ttum4s1k.fsf@localhost> (Ihor Radchenko's message of "Sun, 02 Jul 2023 08:49:11 +0000")

Ihor Radchenko <yantar92@posteo.net> writes:

> The downside of lualatex is that it is slower:
> https://list.orgmode.org/orgmode/87a69j9c6s.fsf@localhost/

Yes, for sure. But I have the impression that newer versions of luatex
have become a bit faster (maybe it's just a subjective impression that
I want to be true, because I don't want to regret the complete switch
to luatex). :)

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

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.

Another approach: Use pdftex for simple/short documents and make
selection of luatex as backend engine per document as easy as
possible. 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.

-- 
Until the next mail...,
Stefan.


  reply	other threads:[~2023-07-02 15:08 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 [this message]
2023-07-02 15:50           ` Ihor Radchenko
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=m1cz1a73o6.fsf@nobis-it.eu \
    --to=stefan-ml@snobis.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
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).