---------- Forwarded message --------- From: Pedro Andres Aranda Gutierrez <[email protected]> Date: Mon, 17 Nov 2025 at 07:09 Subject: Re: Status of the all-tex-fonts feature branch To: RadioNoiseE <[email protected]>
Hi, answers inline On Mon, 17 Nov 2025 at 03:04, RadioNoiseE <[email protected]> wrote: > On Sat, 15 Nov 2025 19:46:04 +0800, > Pedro Andres Aranda Gutierrez wrote: > > > > Hi > > > > > El 15 nov 2025, a las 11:35, Ihor Radchenko <[email protected]> > escribió: > > > > > > "Pedro A. Aranda" <[email protected]> writes: > > > > > >> Thanks a ton to @RadioNoiseE for the examples: with your help we can > > >> now export org documents in Chinese or Japanese to PDF using XeLaTeX. > > >> The current implementation has the following constraints: > > >> > > >> 1. we use babel > > >> 2. the main document language has to be jp or zh > > >> > > >> It offers the possibility of having other secondary languages (I've > > >> tested with en-gb and es) > > > > > > You still have an old > > > > > >> ;; If the CJK font families have been included > > >> ;; Check for polyglossia and/or babel and warn? > > >> ;; Or advise for these packages to be added to > `org-latex-package-alist' ?? > > >> (when (and cjk-packages (equal compiler "xelatex")) > > >> (message "Adding the CJK packages") > > >> (goto-char (point-min)) > > >> (forward-line 2) > > >> (insert "\\usepackage[CJKspace]{xeCJK}\n")) > > > > > > in the code. Should it be removed? > > That’s what made things work for lualatex/xelatex with plain font spec. > > Remember that I was just talking about this working with *babel*… > > We should discuss whether the current way is enough or we also want a > pure fontspec/polyglossia solution too, given the added complexity shown in > the MWEs > > I don't quiet understand this. So when we do not want babel, just > remove the babel related part in the MWEs. They are not necessary, as > they just provide localization, i.e., changing Chapter %1 to 第 %1 章 > On the contrary, we already have the babel part implemented (thanks again for the MWE) for zh and jp. > > Also, the new piece of code does not check for xelatex and will likely > > > make lualatex compilation fail. xeCJK only works with xelatex. > > > > Right, I’ll add that > > > > > >> @all: Please install or refresh the feature/all-tex-fonts to check > the > > >> results. A short section in the manual has been added, documenting my > > >> current understanding of the state of the branch. > > > > > > I think that the documentation should mention that things only work for > > > xelatex. > > OK, I’ll add that too.. > > is there any plan for LuaTeX support? with the MWEs it should be the > same as XeTeX. > We have never said that we should. Ihor was just reminding me that the docs should reflect the status of the code and that we can only guarantee things to work with xetex with the code in the git. I'm now entering the hottest part of the year (lectures + grading of mid terms) and lualatex will have to wait, unless I find someone ;-) to help me with that. > > > > > > -- > > > 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> > > > Best, /PA -- 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
