"Pedro A. Aranda" <[email protected]> writes: > I have split the commit in two (apart from minor stylistic quirks). The > first big commit is a rewrite based on comments of the head of the > section and the second is a modified version on the LaTeX markups which > were missing.
Now, comments to the actual latest version of the section :) > :properties: > #+LABEL: LaTeX languages and character sets > :end: This is a wrong Org syntax. What did you want to do? > [fn:49] For example, if you use emojis in your document or intersperse > words or short expressions in Greek, you will need to configure the > fonts you use in the PDF export, even if the main document is intended > for an American English context. I think this does not have to be a footnote. It is important enough to leave in the main text. More general comments: 1. Do you have specific objections to discussing babel and polyglossia first, and moving fontspec/nil to the end? 2. You write using British English, while our documentation should be in American (localisation -> localization; spelt -> spelled; etc) See doc/Documentation_Standards.org And attaching some minor corrections.
>From 2b2fa681cf6e36edd2315f0b45fe034c9e1fc6ae Mon Sep 17 00:00:00 2001 Message-ID: <2b2fa681cf6e36edd2315f0b45fe034c9e1fc6ae.1760260325.git.yanta...@posteo.net> From: Ihor Radchenko <[email protected]> Date: Sun, 12 Oct 2025 11:11:48 +0200 Subject: [PATCH] doc/org-manual.org: Minor corrections --- doc/org-manual.org | 37 ++++++++++++++++++------------------- 1 file changed, 18 insertions(+), 19 deletions(-) diff --git a/doc/org-manual.org b/doc/org-manual.org index b6a343457..3cda5c790 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -14380,11 +14380,11 @@ *** Handling different languages and character sets in LaTeX exports Modern, UTF-8 enabled LaTeX compilers (i.e. =lualatex= and =xelatex=) handle font configuration using the package - =fontspec=. We recommend to choose Unicode fonts that include the + =fontspec=. We recommend choosing Unicode fonts that include the non-Latin character sets you use to simplify the configuration (cf. [[#nonpdflatex-fonts]]). - For documents that a written for outside an American English + For documents that are written for outside an American English linguistic context and for multilingual documents, LaTeX provides the packages =babel= or =polyglossia= to localise document features like the table of contents, dates, hyphenation, etc. @@ -14401,17 +14401,16 @@ *** Handling different languages and character sets in LaTeX exports # recommend selecting Unicode fonts that cover the character sets of # in the languages used in your document. - Use the =LANGUAGE= keyword to specify the languages used in a - document and the =LATEX_MULTI_LANG= keyword to set the way to handle + Use the =LANGUAGE= setting to specify the languages used in a + document and the =LATEX_MULTI_LANG= setting to set the way to handle localisation and font configuration. - =LATEX_MULTI_LANG= is ~nil~ by default. In this case, you need to - handle localisation manually. In this case you need to configure - LaTeX language features manually in LaTeX headers (see + =LATEX_MULTI_LANG= is ~nil~ by default. In this case you need to + configure LaTeX language features manually in LaTeX headers (see ~#+LATEX_HEADER~ keyword). For convenience, if the LaTeX headers load =babel= or =polyglossia=, you may use =AUTO= in the package - options to refer to the document's main language. Org's will - translate it according to the value of the =#+LANGUAGE= keyword. Use + options to refer to the document's main language. Org mode will + translate it according to the value of the =LANGUAGE= setting. Use this setting when you must use =pdflatex= and follow the instructions in [[#pdflatex-fonts]] to set up fonts in your document. For example: @@ -14430,21 +14429,21 @@ *** Handling different languages and character sets in LaTeX exports Multiple languages are also handled. When =#+LATEX_MULTI_LANG= is set to ~fontspec~, Org mode will - configure the document's fonts using LaTeX's ~fontspec~ package. It - configures the fonts used in the document. It distinguishes between - the Roman (=main=), Sans-serfi (=sans=) and monotype (=mono=) fonts, - and can provide fallbacks for character sets (for example, ~emoji~, - ~han~, ~kana~, etc.) not supported by the default fonts. See - [[#lualatex-fontspec]] for more details. - Note that ~fontspec~ is not intended for document localisation and - that it does not work with =pdflatex= compiler. We recommend using - =lualatex= or =xelatex= for reliable non-Latin language support. + configure the document's fonts using LaTeX's ~fontspec~ package. + ~fontspec~ distinguishes between the Roman (=main=), Sans-serif + (=sans=) and monotype (=mono=) fonts, and can provide fallbacks for + character sets (for example, ~emoji~, ~han~, ~kana~, etc.) not + supported by the default fonts. See [[#lualatex-fontspec]] for more + details. Note that ~fontspec~ is not intended for document + localisation and that it does not work with =pdflatex= compiler. We + recommend using =lualatex= or =xelatex= for reliable non-Latin + language support. When =#+LATEX_MULTI_LANG= is set to either ~babel~ or ~polyglossia~, Org will use the indicated LaTeX package to handle multi-language support. Either should be used for non-English documents. Both provide setting up your font configuration globally for your - document and on a per-language basis. The =LANGUAGE= option will be + document and on a per-language basis. The =LANGUAGE= setting will be used to determine the main and secondary languages. For example: #+BEGIN_SRC org :results none :exports code -- 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>
