Pedro Andres Aranda Gutierrez <[email protected]> writes: > done with a couple of very minor deviations. > The only significant change WRT this thread is that I'm not including > the babel example, since the explanation below the example refers to > polyglossia only.
Thanks! I did a couple of edits, fixing list indentation and specifying that nil is the default value. I pushed the changes to the branch. I am also attaching tentative changes to the next section of the manual.
>From c21342c7d02695f7e41ed6170fc974bfcba4f14a Mon Sep 17 00:00:00 2001 Message-ID: <c21342c7d02695f7e41ed6170fc974bfcba4f14a.1759580258.git.yanta...@posteo.net> From: Ihor Radchenko <[email protected]> Date: Sat, 4 Oct 2025 14:14:35 +0200 Subject: [PATCH] doc/org-manual.org (Handling different languages in LaTeX exports): suggestions --- doc/org-manual.org | 33 ++++++++++++++++++--------------- 1 file changed, 18 insertions(+), 15 deletions(-) diff --git a/doc/org-manual.org b/doc/org-manual.org index 404199d32..c2ebe1882 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -14172,6 +14172,7 @@ *** LaTeX/PDF export commands *** LaTeX specific export settings :PROPERTIES: :DESCRIPTION: Unique to this @LaTeX{} backend. +:CUSTOM_ID: latex-export-settings :END: The LaTeX export backend can use different LaTeX compilers, each of @@ -14393,23 +14394,25 @@ *** Handling different languages in LaTeX exports #+cindex: @samp{LANGUAGE}, keyword #+vindex: org-export-default-language -The LaTeX export backend can handle documents for non-English -audiences and documents with multiple languages using the LaTeX -packages =babel= or =polyglossia=. It will use the =LANGUAGE= keyword, -if present in the document, or the value of -~org-export-default-language~ to determine the languages used in a -document. If this value is a space-separated list of languages, it -will assume the first one to be the main language in the list. - - -For example, suppose a document declares Polytonic Greek as -the primary language, and French as the secondary language using the -=polyglossia= package to handle document languages: +The LaTeX export backend can handle non-English and multiple-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. +For example, consider an Org document written using Polytonic Greek +with some parts written in French: #+begin_example ,#+LANGUAGE: el-polyton fr ,#+LATEX_MULTI_LANG: polyglossia #+end_example +#+texinfo: @noindent +The above snippet will make Org mode use =polyglossia= LaTeX package +with Polytonic Greek as the primary language (used for standard names +like "Table of Contents", "Table", "Figure", etc), and French as the +secondary language. + +# TODO: We should describe how to mark snippets in other # language in +# Org. This would produce in LaTeX (with the actual =polyglossia= syntax): @@ -14428,9 +14431,9 @@ *** Handling different languages in LaTeX exports languages in the PDF output with the variable ~org-latex-babel-font-config~. -In general, when exporting to LaTeX or PDF, it is advisable that you -select a Unicode font that covers the scripts you use in you -document. This will highly simplify font configuration. +In general, when exporting to LaTeX or PDF, we strongly recommend +using Unicode font that covers the scripts you use in you +document. This will highly simplify the font configuration. When ~org-latex-multi-lang~ is ~nil~, the value of ~org-export-default-language~ will replace appearances of the string -- 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>
