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: <f5d4804c-9a51-443a-a73e-d9c043673cbc@gmail.com>
Date: Fri, 22 Aug 2025 21:01:03 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: mchehab+huawei@...nel.org
Cc: corbet@....net, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
 Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH v2 07/14] docs: conf.py: extra cleanups and fixes

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?

Thanks,
Akira