HI OK with the fixes. I have added an additional article that was missing.
WRT the new changes, I just have some reservations for: +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. I never "strongly recommend" in a manual. This is why I said 'it is advisable'. I could live with something like: +In general, when exporting to LaTeX or PDF, we recommend +using a Unicode font set that covers the scripts you use in your +document. This will highly simplify the font configuration. Saying "font set" covers the case for a "normal" document using the rm, sf and tt fonts (e.g. an article with the text in Roman, the headers in Sans and s couple of source code listings) . WDYT?, /PA PS: The TODO should not be there. It should go in the polyglossia and babel sections separately if not already there, On Sat, 4 Oct 2025 at 14:20, Ihor Radchenko <[email protected]> wrote: > > 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. > > > -- > 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> -- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler Sagen's Paradeiser, write BE! Year 1 of the New Koprocracy
