On Sun, 16 Nov 2025 02:33:21 +0800, Ihor Radchenko 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?
They are safe. These commands are originally intended for plainTeX users for setting up font, since they only have luaotfload and no fontspec under plainTeX. So they are guaranteed to change the font related defaults. And the fact that they are not provided by luatexja-fontspec, since we want to prevent loading luatexja-fontspec since it patches fontspec, and will probably interfere with the already loaded fontspec. > -- > 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>
