Pedro Andres Aranda Gutierrez <[email protected]> writes: >> What about also moving LATEX_MULTI_LANG = nil below babel/polyglossia? > > I’d leave it like it is now: we start describing the default value at the > beginning and then show what other settings there are and what they imply.
Ok. My concern is that people may be confused when we present more manual setup before what we actually recommend, but I will not insist. >>> Anyhow, I don't want to open Pandora's box until someone asks what >>> about setting the language in the document class, which is also >>> possible... >> >> We do not have to support this other than by setting LATEX_MULTI_LANG >> to nil and letting user do whatever they want to. > > We do when we describe the default value. You mean AUTO? Maybe, but it is not something people asked for in the past. I see no reason to bother unless someone asks for such a feature. >>> :properties: >>> #+LABEL: LaTeX languages and character sets >>> :end: >> >> This incorrect syntax is still there. > > Right. (Adding a suggestion in the patch would be useful next time ;-) ) Well. I am not 100% sure what you wanted there, which is why I had no idea what would be an appropriate fix. >>> Consult the package manuals to get the language name[fn:50] for the >>> LaTeX markup. >> >> Should we also refer to `org-latex-language-alist'? Otherwise, people >> may not know how to link between Org mode's abbreviations and >> babel/polyglossia language names. > > Isn't that already a part of the LANGUAGE keyword description? When we talk about LANGUAGE setting, we only refer to Org abbreviation vs. language name (human-readable name). Language name in LaTeX is a slightly different beast. >> I also moved a note that polyglossia does not work with pdflatex to a >> footnote. > > This is important enough to keep it in the main text IMHO. Maybe. But I also felt that the paragraph talking about it was misplaced. So, came up with a footnote. Maybe put inside parenthesis? Or some other way. >> - Finally, remember that ~polyglossia~ does not work with =pdflatex= >> - compiler. We recommend using =lualatex= or =xelatex= for reliable >> - non-Latin language support. >> + context (header, figure, table names and typesetting options will be >> + set for American English). ~fontspec~ will only configure the fonts >> + used in the document. It 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~ does >> + not work with =pdflatex= compiler. We recommend using =lualatex= or >> + =xelatex= for reliable non-Latin language support. > > What you add here is already in other parts of the text. I think a removed those other parts. But please check how things read. >> 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]]). > > Last time I went through the prep exercises for the C2 certification, this > was more style than grammar. Maybe it has changed now… You may be mixing it with structure like "recommend <you> to choose". Check https://english.stackexchange.com/questions/140163/recommend-to-have-vs-recommend-having and https://english.stackexchange.com/questions/308043/correct-verb-patterns-for-the-verb-recommend -- 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>
