On Sat, 15 Nov 2025 at 19:33, Ihor Radchenko <[email protected]> wrote:
> RadioNoiseE <[email protected]> writes: > > >> > luatexja also patches LaTeX2e's NFSS2, adding CJK font > >> > support. However unless there's a specific reason we shouldn't use > >> > that in Org export results. > >> > >> That sounds concerning. What are the potential consequences? > > > > I think no observable consequences for Org export. It will not > > interfere with any existing functionality. What is does is extending > > existing framework, providing NFSS2 like interfaces for document > > classes, handling CJK font scaling, vertical typesetting, etc > > features. > > > > However I was thinking to not use luatexja-fontspec, that is we no > > longer have \set...jfont control sequences. Since luatexja-fontspec > > should be loaded after fontspec as it patches fontspec. As a > > replacement, we can use (ref. luatexja document section 8.3) > > > > \ltj@stdmcfont -> The default Japanese font for the mincho family > (serif) > > \ltj@stdgtfont -> The default Japanese font for the gothic family > (sans serif and monospace) > > \ltj@stdyokojfm -> The default JFM for horizontal direction > > \ltj@stdtatejfm -> The default JFM for vertical direction > > Will using these low-level commands be safe? What if luatexja-fontspec > changes them in future? > That is the other way of putting my last question ;-) And this is why I would propose that for CJK we stick to babel+xelatex as the way of handling jp,zh and (hopefully) kr localisation and to fontspec+fallbacks for documents that don't need localisation. WDYT? /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
