linux-kernel - Re: [PATCH v2 07/14] docs: conf.py: extra cleanups and fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250825140719.18ba8459@foz.lan>
Date: Mon, 25 Aug 2025 14:07:19 +0200
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Jonathan Corbet <corbet@....net>
Cc: Akira Yokosawa <akiyks@...il.com>, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 07/14] docs: conf.py: extra cleanups and fixes

Em Fri, 22 Aug 2025 16:34:38 -0600
Jonathan Corbet <corbet@....net> escreveu:

> Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:
> > On Fri, Aug 22, 2025 at 09:01:03PM +0900, Akira Yokosawa wrote:  
> 
> >> > 3) I got a corner case on one of the distros was using xindy to produce
> >> >    indexes. This ended causing the build logic to incorretly try to use
> >> >    T1 fontenc, which is not UTF-8 compatible.
> >> > 
> >> >    This patch adds:
> >> > 
> >> >         \PassOptionsToPackage{xindy}{language=english,codepage=utf8,noautomatic}
> >> > 
> >> >    to cover such case. It should be noticed that, as the config doesn't
> >> >    have \usepackage{xindy}, this will be used only if latexmk ends
> >> >    using xindy.  
> >> 
> >> But I can't see how this macro (executed by XeTeX engine) would have any
> >> effect on xindy (command) invoked from latexmk.
> >> 
> >> Can you elaborate on your theory of how it works?
> >> And which distro runs xindy?  
> >
> > I can't remember on what distro I saw the issue, but I got it during
> > my builds, where, instead of running makeindex, it tried to run xindy,
> > with failed because of utf-8 fonts.
> >
> > My theory is that, on one of the ditros, there is a /etc/latexmk
> > or similar containing instructions to use xindy instead of makeindex.
> >
> > In any case, this rule is harmless on setups that use makeindex:
> > it only affect setups where there is a latexmk or .latexmk file
> > setting xindy as the default index builder: if this is used, 
> > xindy will use utf-8 fonts instead of Type 1.  
> 
> Can we try to get a handle on that and, if it's truly needed, document
> why?  I will confess that I'm confused by it:
> 
> > \PassOptionsToPackage{xindy}{language=english,codepage=utf8,noautomatic}  
> 
> As I understand it, the arguments are {options}{package}, right?  so I'm
> not sure how this would work...?

Heh, you're right: the argument is reversed. Also, I repeated the
tests here, and were unable to reproduce the issue I had with xindy.

So, let's just drop it. If we needed, we can re-add, reverting the
parameter order there. Patch is at:

	https://lore.kernel.org/linux-doc/83068bc31839e7095f1f408e49658362d467797e.1756123459.git.mchehab+huawei@kernel.org/T/#u

> 
> jon  (who will be traveling and slow to respond for a bit)

Thanks,
Mauro