---------- Forwarded message --------- From: Pedro Andres Aranda Gutierrez <[email protected]> Date: Mon, 17 Nov 2025 at 07:21 Subject: Re: Fwd: Status of the all-tex-fonts feature branch To: RadioNoiseE <[email protected]>
Answers inline, On Mon, 17 Nov 2025 at 03:16, RadioNoiseE <[email protected]> wrote: > On Sun, 16 Nov 2025 14:13:22 +0800, > Pedro Andres Aranda Gutierrez wrote: > > > > [1 <text/plain; UTF-8 (quoted-printable)>] > > [2 <text/html; UTF-8 (quoted-printable)>] > > 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? > > If I understand correctly, fontspec+fallback will not work for CJK, > since TeX's Kunth-Plass line-breaking algorithm only works for latin. > Also punctuations need special handling, in a way similiar to > ligatures. > fontspec + fallback is for very specific cases where you have small phrases in non-Latin scripts that you want to typeset with lualatex. You are right in saying that this is a non-solution for texts that need to handle punctuation, line breaking, LTR, etc. To give you an example, I'm using it just for presentations and lecture notes in English where I want include emoji. The moment I switch to Spanish/German/Italian, I use polyglossia. A complete analysis is needed, you are right, because the strategy (fontspec+fallback vs. babel vs. polyglossia using pdflatex/lualatex/xelatex) depends on the use-case. > IMO it's necessary to at least support LuaTeX as an alternative to > XeTeX. > And with the time and more contributions, we might have it. /PA > > > /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 > -- 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 -- 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
