Pedro Andres Aranda Gutierrez <[email protected]> writes:
> <embarrassed>you are completely right</embarrassed>... It may have
> been all the things that were commented out. Take a Look now
See some additional suggestions in the attached patch.
Also, more generally, I feel that we need to emphasize better that fonts
*must* be configured for non-Latin languages.
> PS: Just noticed this... We should be considering leaving a space
> after \LaTeX or \TeX and not the {}. They trickle into the ToC in PDFs
> and it doesn't look pretty (at least in some PDF viewers.
I am not sure what you are referring to.
>From 5c4cdafb7e6854ce10e65030a1a1d10d3be83c3b Mon Sep 17 00:00:00 2001
Message-ID: <5c4cdafb7e6854ce10e65030a1a1d10d3be83c3b.1759764144.git.yanta...@posteo.net>
From: Ihor Radchenko <[email protected]>
Date: Mon, 6 Oct 2025 17:22:12 +0200
Subject: [PATCH] doc/org-manual.org (Handling different languages in LaTeX
exports): edits
---
doc/org-manual.org | 17 +++++++++++------
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index f32f05ce6..8d3053143 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -14349,10 +14349,10 @@ *** Handling different languages in LaTeX exports
#+vindex: org-export-multi-lang
#+vindex: org-export-default-language
- The LaTeX export backend can handle non-English and
- multiple-language using the LaTeX packages =babel= or
- =polyglossia=. The document languages should be specified using
- =LANGUAGE= keyword. If =LANGUAGE= is not specified, the value of
+ The LaTeX export backend can handle non-English and multi-language
+ documents using the LaTeX packages =babel= or =polyglossia=. The
+ document languages should be specified using =LANGUAGE= keyword. If
+ =LANGUAGE= is not specified, the value of
~org-export-default-language~ is used.
The way to handle documents with localisation requirements is set
@@ -14365,7 +14365,7 @@ *** Handling different languages in LaTeX exports
convenience, if the LaTeX headers load =babel= or =polyglossia=, you
can use word =AUTO= in the package options to automatically specify
the document's main language according to Org's =#+LANGUAGE=
- keyword:
+ keyword.
#+BEGIN_EXAMPLE
#+LANGUAGE: es
@@ -14384,7 +14384,9 @@ *** Handling different languages in LaTeX exports
supported by the default fonts. See [[#lualatex-fontspec]] for more
details. Beware that ~fontspec~ does not work with =pdflatex=
compiler. We recommend using =lualatex= or =xelatex= for reliable
- non-Latin language support.
+ non-Latin language support. If =pdflatex= has to be used, please
+ set =#+LATEX_MULTI_LANG= to ~nil~ and follow the instructions in
+ [[#pdflatex-fonts]].
When =#+LATEX_MULTI_LANG= is either ~babel~ or ~polyglossia~, Org
mode will use the indicated LaTeX package to handle multi-language
@@ -14994,6 +14996,9 @@ *** Controlling the way the table of contents is generated
#+end_example
*** Controlling the font configuration for ~pdflatex~
+:PROPERTIES:
+:custom_id: pdflatex-fonts
+:END:
#+vindex: org-latex-default-packages-alist
~pdflatex~ uses packages to import the fonts that will be used in the
--
2.50.1
--
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>
