Hi On Sat, 29 Nov 2025 at 15:18, Ihor Radchenko <[email protected]> wrote:
> Pedro Andres Aranda Gutierrez <[email protected]> writes: > > > I have reorganised the CJK section too, grouping the power user options > at > > the end. > > I looked at the section. It looks fine in general. Although I was a bit > surprised about repetitive example for Chinese/Japanese. > I have simplified the section and examples. It also made me wonder what happens when one needs to mix Chinese and > Japanese. From the examples, it looks like mixing is not possible. > (This is not too important to solve immediately though). > >From the MWE's we got, I was able to extract the solutions for Chinese and Japanese separately. I don't know how to mix them. I have an example, which I showed in one of the meetups, which seemed to mix them, if memory serves me well. It would be better to leave this FFS until Huang can provide more informed insight. That should also be after mid January from my side. Also, I noticed that the section titles do not fit within A4 in the PDF > version of the manual. Maybe we can shorten them. For example, "font > configuration" seems repetitive considering that these sections are > already subsections of "Font configuration for LuaLATEX and XeLATEX" > Got me again. I have pushed an alternative with shorter titles but, alas, they are somehow repetitive too. Note that I am still waiting for your feedback on the alternative (flat) > structure of the *-font-config customization values. I find that > question important. > OK, this is the hard one. It depends a lot on personal tastes, I admit but I think I have a answer... Take this example: #+begin_src emacs-lisp ((org-mode . ((org-latex-compiler . "lualatex") (org-latex-multi-lang . "babel") (org-latex-babel-font-config . (("el" :fonts (("rm" :font "Noto Serif" :props "Scale=MatchLowercase")) :provide "onchar=ids fonts") (nil :fonts (("rm" :font "CMU Serif") ("tt" :font "Noto Sans Mono" :props "Scale=MatchLowercase")))))))) #+end_src It translates to: \usepackage[bidi=basic,import=*]{babel} \babelprovide[main,import]{german} \babelprovide[onchar=ids fonts]{greek} \babelfont[greek]{rm}[Scale=MatchLowercase]{Noto Serif} \babelfont{rm}{CMU Serif} \babelfont{sf}{Noto Sans} \babelfont{tt}[Scale=MatchLowercase]{DejaVu Sans Mono} As you see, each language has a part linked to the language that is passed to \babelprovide (which is optional, but crucial), while the other part is passed to \babelfont (and this part is not). If we went for a flat config, we would need another variable for the provides and that would make housekeeping more difficult. Touching one variable is less prone to forgetting details than having to touch two (IMvHO). If it weren't for that, I could live with a flatter version à la #+begin_src emacs-lisp ((org-mode . ((org-latex-compiler . "lualatex") (org-latex-multi-lang . "babel") (org-latex-babel-font-config . (("el" :variant "rm" :font "Noto Serif" :props "Scale=MatchLowercase") (nil :variant "rm" :font "CMU Serif") (nil :variant "tt" :font "Noto Sans Mono" :props "Scale=MatchLowercase")))))) #+end_src which might be more appealing to you, if I understand you correctly... Best, /PA > -- > 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" (ORF: Als Radiohören gefährlich war) => write BE! Year 1 of the New Koprocracy
