Pedro Andres Aranda Gutierrez <[email protected]> writes:
> consider the following examples:
>
> #+begin_src org
> ,#+OPTIONS: toc:nil
> ,#+LATEX_COMPILER: lualatex
>
> ,#+LATEX_HEADER: \setmainfont{DejaVu Serif}
>
> We only need to change the _main_ class to get a /viable/ document as long
> as we
> don't use the *other* families.
>
> ,# Local variables:
> ,# org-latex-classes: (("article" "\\documentclass[a4paper,12pt]{article}"))
> ,# end:
> #+end_src
> ...
> After trying them out, do you not feel that the extra burden on the user by
> _mandating_ that *all four* font families be defined is unacceptable?
Not sure.
Yes, you may get along with partially specifying fonts, but...
Try the following:
#+OPTIONS: toc:nil
#+LATEX_COMPILER: lualatex
#+LATEX_HEADER: \setmainfont{DejaVu Serif}
We only need to change the _main_ class to get a /viable/ document as long
as we
don't use the *other* families. =тук= тук
# Local variables:
# org-latex-classes: (("article" "\\documentclass[a4paper,12pt]{article}"))
# end:
When compiling it, you will see
⛔ Warning (ox-latex): PDF file produced with warnings: [Missing character(s):
please load an appropriate font with the fontspec package]
which refers to =тук=. However, it may be confusing for users - тук
renders just fine. In a much more complex document I would be left
wondering how come I specified unicode DejaVu Serif, but still get
missing characters.
Not to say that we should *demand* users to set all the fonts, but we
should clearly warn that 4 fonts may be necessary.
--
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>
