linux-kernel - Re: [PATCH 00/11] Fix PDF doc builds on major distros

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: <b6d18aa7-de85-4fd2-8456-c2f6342f1b06@gmail.com>
Date: Mon, 18 Aug 2025 01:07:24 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: Mauro Carvalho Chehab <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 00/11] Fix PDF doc builds on major distros

On Sun, 17 Aug 2025 15:45:44 +0200, Mauro Carvalho Chehab wrote:

[...]

> The corrupted table error happened with very simple PDF files and has
> nothing to do with image generation.
> 
> It rises even with very simple PDF targets like this:
> 
> 	make SPHINXDIRS=peci pdfdocs
> 
> Which produces \sphinxhyphen{} inside peci.tex, like this one:
> 
> 	controller is acting as a PECI originator and the processor \sphinxhyphen{} as
> 
> Basically, if this is included, directly or indirectly at the
> .tex file:
> 
> 	\usepackage[T1]{fontenc}
> 
> the fonts from T1 fontset aren't UTF-8 compatible, causing troubles
> with xelatex. The fixes on this series solved some corner cases, where 
> babel tries to include it and use a Polish font (pzdr.tfm) to
> handle hyphenation.
> 
> Such issue likely depends on Sphinx versions (as it is related to a 
> sphinx-specific macro) and what LaTeX packages are installed at 
> the system (fonts, babel, polygrossia).

Ah, I have finally understood what 5/11 is trying to do.

Its changelog mainly talks about an issue you saw after adding options
to xindy in that same commit, and you added

   \newfontfamily\headingfont{DejaVu Serif}

to resolve it.

Current changelog didn't make sense at all for me.

Can you please reword it and make it easier to follow?

With that, feel free to add my

Reviewed-by: Akira Yokosawa <akiyks@...il.com>

        Thanks, Akira