Committed, along with other minor changes Best, /PA
On Sat, 4 Oct 2025 at 20:01, Ihor Radchenko <[email protected]> wrote: > > Pedro Andres Aranda Gutierrez <[email protected]> writes: > > > 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'. > > My main point was using active voice. I do not have strong preference to > keep "strongly" there. > > > 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. > > LGTM. > > > 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) . > > LGTM. > > > PS: The TODO should not be there. It should go in the polyglossia and > > babel sections separately if not already there, > > But do we have those sections? Currently, you have dedicated sections > for font configuration, but not describing how to specify languages of > text snippets. I felt that such description would belong to "Handling > different languages in LaTeX exports". > > -- > 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
