Bug#1035857: texlive-fonts-extra: broken font symlinks for junicode
On 10.05.2023 11:18, Andreas Beckmann wrote:
Hi again,
during a test with piuparts I noticed your package ships (or creates)
broken symlinks:
OK, had a closer look: the "Debian Fonts Task Force" replaced the
"Junicode 1" by "Junicode 2" although they may behave differently
"Users of the various versions of Junicode 1 need to be aware that
documents originally set in Junicode 1 may reflow when set in Junicode
2. Further, documents that use the OpenType features of Junicode 1
(aside from basics like kerning and standard ligatures) may not be
displayed properly when changed over to Junicode 2."
I guess it would have been better to create fonts-junicode2 and then
slowly phase out fonts-junicode, when v2 left beta stage.
I could simply fix the links and point them to the v2 OTF fonts. This
could be even done now. This would give Debian users the v2 fonts but I
don't know if they are compatible to the Junicode related files in
texlive-fonts-extra. Junicode v2 wasn't even uploaded to CTAN yet. I
guess it is a better idea to stay with Junicode 1 for now and
re-integrate them into tfe after bookworm..
fonts-alegreya-sans will not be in bookworm (and hasn't been in
bullseye), thus
/usr/share/texlive/texmf-dist/fonts/opentype/huerta/alegreya
also contains broken symlinks.
Well, I tend to say "this is not my fault". I may revert my decision
after bookworm.
H.
--
sigfault
Reply to: