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] [day] [month] [year] [list]

Message-ID: <fa7rreuvodpe673lwcwlj6kddkpnmkoxlz4y5mythgntkmveey@m5fqvtsuel6l>
Date: Fri, 22 Aug 2025 15:27:28 +0200
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Akira Yokosawa <akiyks@...il.com>
Cc: mchehab+huawei@...nel.org, corbet@....net, linux-doc@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 07/14] docs: conf.py: extra cleanups and fixes

On Fri, Aug 22, 2025 at 09:01:03PM +0900, Akira Yokosawa wrote:
> Hi Mauro,
> 
> I see this has already been merged, but let me comment after the fact.
> 
> On Thu, 21 Aug 2025 10:16:43 +0200, Mauro Carvalho Chehab wrote:
> > Makes it more adehent with modern Sphinx LaTeX build setup as
> > defined at:
> > 
> > 	https://www.sphinx-doc.org/en/master/latex.html
> > 
> > There, it suggests:
> > 
> > 1) to add: 'printindex'
> > 
> >     “printindex” call, the last thing in the file. Override if you want to generate
> >     the index differently, append some content after the index, or change the font.
> >     As LaTeX uses two-column mode for the index it is often advisable to set this
> >     key to r'\footnotesize\raggedright\printindex'.
> > 
> > This indeed solved a corner case on a distro where the index was not properly
> > generated.
> 
> This looks good.
> 
> > 
> > 2) to add at the main example:
> >          \PassOptionsToPackage{svgnames}{xcolor}
> 
> OK.  So I guess Sphinx's latex builder is going to start using SVG color
> naming in the near future.
> 
> > 
> > 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.

Thanks,
Mauro