From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Vegard Nossum <vegard.nossum@oracle.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-doc@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: PDF misery
Date: Mon, 19 Feb 2024 10:49:08 -0700 [thread overview]
Message-ID: <87o7ccpcob.fsf@meer.lwn.net> (raw)
In-Reply-To: <64908dd3-17c9-47e3-a076-d78105fb823b@gmail.com>
Akira Yokosawa <akiyks@gmail.com> writes:
> It sounds like you have google-noto-sans-cjk-vf-fonts installed on your
> system besides google-noto-sans-cjk-fonts.
>
> What does
>
> fc-list | grep NotoSansCJK-VF.ttc
>
> say?
No output at all, even though I had google-noto-sans-cjk-vf-fonts
installed.
> Uninstalling google-noto-sans-cjk-vf-fonts (and
> google-noto-serif-cjk-vf-fonts in case you have it) should resolve
> the issue for you, that is if you can safely uninstall it/them.
Getting rid of google-noto-sans-cjk-vf-fonts did indeed make the problem
go away.
> As the xeCJK package requires xelatex, variable fonts are not in
> our options, I guess.
So it seems. I guess $WE should probably change
scripts/sphinx-pre-install to give a warning; I wonder if some defensive
changes to Documentation/sphinx/kerneldoc-preamble.sty would also make
sense? My TeXpert days (such as they were) are decades behind me at
this point, so I'll be slow to do the latter part if it comes to that.
Thanks for your help on this!
jon
next prev parent reply other threads:[~2024-02-19 17:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 21:29 PDF misery Jonathan Corbet
2024-02-18 0:40 ` Mauro Carvalho Chehab
2024-02-18 9:58 ` Akira Yokosawa
2024-02-18 10:17 ` Mauro Carvalho Chehab
2024-02-19 17:49 ` Jonathan Corbet [this message]
2024-02-18 10:08 ` Vegard Nossum
2024-02-18 13:07 ` Vegard Nossum
2024-02-18 15:49 ` Akira Yokosawa
2024-02-18 19:57 ` Mauro Carvalho Chehab
2024-02-18 22:15 ` Jonathan Corbet
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=87o7ccpcob.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=vegard.nossum@oracle.com \
/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 NNTP newsgroup(s).