Answer inline
On Wed, 2 Apr 2025 at 20:20, Ihor Radchenko <yanta...@posteo.net> wrote:
> Pedro Andres Aranda Gutierrez <paag...@gmail.com> writes:
>
> > Actually, what I would do after looking around is
> > * short term (even as a bug fix in 9.7): modifying the error message and
> > say that unsupported Unicode characters can only be dealt with in XETEX
> or
> > LUALATEX.
>
> I doubt that it will be a trivial enough fix for bugfix branch, but I
> agree that such message (or warning) would be nice to have.
>
What about
("^!.+Unicode character" . "[unicode character(s) not supported by
pdflatex. Set org-latex-compiler to lualatex or xelatex instead]")
instead of
("^!.+Unicode character" . "[unicode character(s) not set up for use
with pdflatex. You can run lualatex or xelatex instead]")
in line 1527 of ox-latex.el ?
Doesn't that explain the situation more accurately?
> > * Long term as a new feature in 9.8: introducing two custom variables,
> one
> > to enable/disable setting fonts from customisation (we could have them
> > enabled by default) and one with a list of three font names ("serif"
> "sans"
> > and "mono") to add in the preamble.
>
> +1
>
OK, and now that I see, and since pdflatex has no real fix for *ALL* utf8
characters, this header would only be emitted if org-latex-compiler is
*not* pdflatex.
> --
> Ihor Radchenko // yantar92,
> Org mode maintainer,
> 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>
>
With the current situation, I fear we can't do better
My .2 cents, /PA
--
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Sagen's Paradeiser, write BE!
Year 1 of the New Koprocracy
