From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: [PATCH -perfbook] Stick to mfirstuc v2.07
Date: Wed, 19 Oct 2022 22:47:53 +0900 [thread overview]
Message-ID: <db2a9f79-dcf9-6d04-3517-be4317fed1bd@gmail.com> (raw)
Version 2.08 of LaTeX package "mfirstuc" (indirectly loaded via
"glossaries-extra") is a re-implementation using modern LaTeX3
commands.
Unfortunately, it is not compatible with our indexing macros and
build scripts due to the use of mfirstuc's internal macros.
Newer versions of mfirstuc understand an option [=v2.07] and roll
back to the earlier version [1]. Therefore, as a work around, load
it explicitly with that option before loading glossaries-extra.
It does not affect builds on a system where an earlier version
of mfirstuc is installed.
Link: [1] http://mirrors.ctan.org/macros/latex/contrib/mfirstuc/mfirstuc-manual.html
Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
Hi Paul,
A recent update of mfirstuc broke perfbook builds.
Looks like I had trespassed the mfirstuc's internal code when
I tweaked the automatic capitalization of indexed terms/names.
In LaTeX community, LaTeX3 provides an easier-to-program syntax for
package writers and it is getting popular day by day. Most of those
re-implementation have not affected perfbook, but here comes such
a day.
In the longer term, I might be able to come up with a better
approach for future compatibility. I can't promise anything at the
moment, though.
Thanks, Akira
--
perfbook-lt.tex | 2 ++
1 file changed, 2 insertions(+)
diff --git a/perfbook-lt.tex b/perfbook-lt.tex
index 9cde2e4d42e5..80e36084ed3b 100644
--- a/perfbook-lt.tex
+++ b/perfbook-lt.tex
@@ -79,6 +79,8 @@
\usepackage[bookmarks=true,bookmarksnumbered=true,pdfborder={0 0 0},linktoc=all]{hyperref}
\usepackage{footnotebackref} % to enable cross-ref of footnote
\usepackage[all]{hypcap} % for going to the top of figure and table
+\usepackage{mfirstuc}[=v2.07] % v2.08 or later is not compatible with our
+ % indexing macros
\usepackage[acronym]{glossaries-extra}[2020/02/13]
\usepackage[longragged]{glossaries-extra-stylemods}
\usepackage{epigraph}[2020/01/02] % latest version prevents orphaned epigraph
base-commit: c2dc57ae109050a8a252278c73158292bb4b9512
--
2.25.1
next reply other threads:[~2022-10-19 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 13:47 Akira Yokosawa [this message]
2022-10-20 23:51 ` [PATCH -perfbook] Stick to mfirstuc v2.07 Paul E. McKenney
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=db2a9f79-dcf9-6d04-3517-be4317fed1bd@gmail.com \
--to=akiyks@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).