Pedro Andres Aranda Gutierrez <[email protected]> writes:
> After this I have reworded the text about beamer that confused you
> into a couple of footnotes.
The first footnote about beamer seems out of place. Note that Org manual
has a dedicated section about beamer. This section comes _before_ LaTeX
exporter description. Maybe you can add a short reference to LaTeX
section in the beamer section?
> When non-~nil~, ~org-latex-polyglossia-font-config~ contains a list of
> definitions for the different fonts you need in your PDF output. Each
> definition is a property list (~plist~). The following is an example
> of the definition of the font configuration to use =polyglossia= in a
> document with English and Hebrew text:
>
> #+BEGIN_SRC emacs-lisp :results none :exports none
> ((org-mode
> . ((org-latex-polyglossia-font-config
> . (("en"
> :font "FreeSerif")
> ("en" :variant "sf"
> :font "FreeSans")
> ("en" :variant "tt"
> :font "FreeMono")
> ("he"
> :props "Script=Hebrew" :font "Hadasim CLM")
> ("he" :variant "tt"
> :props "Script=Hebrew" :font "Miriam Mono CLM")
> ("he" :variant "sf"
> :props "Script=Hebrew" :font "Miriam CLM"))))))
>
> #+END_SRC
The Elisp snippet will not be exported here.
> When using =polyglossia=, you can also configure the fonts used for
> the document's main language with the configuration for
> =fontspec=. For example:
>
> #+BEGIN_SRC emacs-lisp :results none :exports code
> ((org-mode
> . ((org-latex-fontspec-default-features
> . (("Ligatures" . "TeX")))
> (org-latex-fontspec-config
> . (("main" :font "CMU Serif")
> ("sans" :font "CMU Sans Serif")
> ("mono" :font "DejaVu Sans Mono" :features "Scale=MatchLowercase")))
> (org-latex-polyglossia-font-config
> . (("el" :variant "rm" :font "Noto Serif"
> :props ("Script=Greek" "Scale=MatchLowercase")))))))
> #+END_SRC
This feels off as all the previous examples are intended for init.el,
but this one is for directory-local variables.
At this point I have reviewed all the changes in the manual.
I also pushed a couple of minor changes to the branch directly.
Before we move on, I suggest running make docs and reading the new
sections from pdf or html version. The new presentation of the same text
may help to catch what we have missed.
--
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>
