From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Akira Yokosawa <akiyks@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 07/14] docs: conf.py: extra cleanups and fixes
Date: Mon, 25 Aug 2025 14:07:19 +0200 [thread overview]
Message-ID: <20250825140719.18ba8459@foz.lan> (raw)
In-Reply-To: <87sehjdlz5.fsf@trenco.lwn.net>
Em Fri, 22 Aug 2025 16:34:38 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> Mauro Carvalho Chehab <mchehab+huawei@kernel.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
next prev parent reply other threads:[~2025-08-25 12:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 8:16 [PATCH v2 00/14] Fix PDF doc builds on major distros Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 01/14] docs: Makefile: Fix LaTeX paper size settings Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 02/14] docs: conf.py: better handle latex documents Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 03/14] docs: conf.py: fix doc name with SPHINXDIRS Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 04/14] docs: conf.py: rename some vars at latex_documents logic Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 05/14] docs: conf.py: use dedent and r-strings for LaTeX macros Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 06/14] docs: conf.py: fix some troubles for LaTeX output Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 07/14] docs: conf.py: extra cleanups and fixes Mauro Carvalho Chehab
2025-08-22 12:01 ` Akira Yokosawa
2025-08-22 13:27 ` Mauro Carvalho Chehab
2025-08-22 22:34 ` Jonathan Corbet
2025-08-25 12:07 ` Mauro Carvalho Chehab [this message]
2025-08-25 12:15 ` Jonathan Corbet
2025-08-25 17:11 ` Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 08/14] scripts: sphinx-pre-install: fix PDF build issues on Ubuntu Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 09/14] scripts: sphinx-pre-install: add missing gentoo pdf dependencies Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 10/14] scripts: sphinx-pre-install: fix PDF dependencies for openSuse Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 11/14] scripts: sphinx-pre-install: fix dependencies for OpenMandriva Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 12/14] scripts: sphinx-pre-install: fix pdf dependencies for Mageia 9 Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 13/14] scripts: sphinx-pre-install: fix PDF dependencies for gentoo Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 14/14] scripts/sphinx-pre-install: fix Archlinux PDF dependencies Mauro Carvalho Chehab
2025-08-21 19:22 ` [PATCH v2 00/14] Fix PDF doc builds on major distros Jonathan Corbet
2025-08-21 19:43 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250825140719.18ba8459@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®