GNU bug report logs -
#51495
29.0.50; [PATCH] Avoid fonts with incomplete coverage of MATHEMATICAL chars
Previous Next
Reported by: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Date: Fri, 29 Oct 2021 21:41:02 UTC
Severity: normal
Tags: patch
Found in version 29.0.50
Fixed in version 29.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 51495 in the body.
You can then email your comments to 51495 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#51495
; Package
emacs
.
(Fri, 29 Oct 2021 21:41:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Fri, 29 Oct 2021 21:41:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello,
This is a followup to a discussion on help-gnu-emacs[1] which revealed
that script-representative-chars does not account for problematic fonts
like KpMath[2] which provide only partial coverage for the MATHEMATICAL
SCRIPT codepoints U+1D49C–U+1D4CF (𝒜–𝓏).
To be more specific, this font only covers MATHEMATICAL SCRIPT CAPITAL
codepoints and does not cover MATHEMATICAL SCRIPT SMALL codepoints.
Since setup-default-fontset only puts MATHEMATICAL SCRIPT CAPITAL A in
script-representative-chars, Emacs fails to ensure that the fonts
returned by Fontconfig also provide glyphs for SMALL codepoints.
As soon as I get a bug number, I'll followup with a patch (reviewed by
Eli[3]) that deals with the situation by adding both ends of each
"math-subgroup" to script-representative-chars, using lists rather than
vectors to make each codepoint mandatory.
From the discussion, it seems that this problem is not very common (the
gap in KpMath seems very uncommon[2]), and has multiple workarounds
(uninstalling the font, tweaking fontconfig rules, tweaking fontsets),
so although the patch applies to both master and emacs-28, I guess there
is no pressing need to have this on the release branch, and master would
be more appropriate?
Thank you for your time.
[1] help-gnu-emacs <878s02u5m6.fsf <at> gmail.com>
https://lists.gnu.org/archive/html/help-gnu-emacs/2021-09/msg00150.html
[2] http://mirrors.ctan.org/fonts/kpfonts-otf/doc/unimath-kpfonts.pdf
§ 15.1.7, 15.1.8
[3] help-gnu-emacs <83k0jjcsal.fsf <at> gnu.org>
https://lists.gnu.org/archive/html/help-gnu-emacs/2021-09/msg00192.html
In GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.30, cairo version 1.16.0)
of 2021-10-26 built on amdahl30
Repository revision: f56408a6f0152cd46d1ea8a0985fbfeeb839ea06
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12013000
System Description: openSUSE Tumbleweed
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#51495
; Package
emacs
.
(Fri, 29 Oct 2021 21:44:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 51495 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
And the Patch That Was Promised, slightly polished compared to the one
posted in help-gnu-emacs[1].
I know that debbugs.el does not make it easy[2], but it'd be nice if the
rationale (the bit between the summary line and the changelog entries)
made it into the final commit message. It's not essential, since I
added an explanatory comment to the code so that one can find the
rationale without reaching for the changelog, but the proposed commit
message also provides further references if needed.
Again, thanks for your time.
[0001-Avoid-fonts-with-incomplete-coverage-of-MATHEMATICAL.patch (text/x-patch, attachment)]
[Message part 3 (text/plain, inline)]
[1] Added an explanatory comment; used nth consistently instead of
car/cadr/nth to make the logic more obvious.
(pcase-dolist would make it even more obvious; should I send a
followup patch or would that be overkill?)
[2] One of the many reasons it took me… gee, more than a month? to post
this patch, is my (on-and-off, still ongoing) attempt to teach
debbugs-gnu.el to keep this rationale, since it's been stripped from
my previous patches[3][4][5].
It's slow going, mostly because I go back and forth between a
"conservative" approach (introducing a variable similar to
debbugs-gnu-patch-subject) and an "impotent rage" approach (« Why
not just call git am?? I made the patch with format-patch, like
CONTRIBUTE says; why are we even parsing it?! Is this our lot? Did
we fly too close to the sun and burn our wings? Must we toil
endlessly, craft regexp after regexp, until the trumpets blow and
sweet armageddon delivers us from the cycle of re-search-forward?
What am I (looking-at)? Hath (eobp) finally come? (forward-line) I
go, forever more, UNTIL THE FIRE OF A THOUSAND "^[*]" CLEANSES MY
CURSED SOUL »).
[3] https://debbugs.gnu.org/35564#231
Compare with f8d8d28bc6.
[4] https://debbugs.gnu.org/41810#26 (patch 1)
Compare with elpa.git 01e7d1fe21.
[5] And then there was bug#39504, although the "root cause" for this one
was attaching more than one patch to a single message.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#51495
; Package
emacs
.
(Sat, 30 Oct 2021 12:46:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 51495 <at> debbugs.gnu.org (full text, mbox):
Kévin Le Gouguec <kevin.legouguec <at> gmail.com> writes:
> And the Patch That Was Promised, slightly polished compared to the one
> posted in help-gnu-emacs[1].
Makes sense to me (and some light testing doesn't show any regressions
here), so I've pushed it to the trunk.
> I know that debbugs.el does not make it easy[2], but it'd be nice if the
> rationale (the bit between the summary line and the changelog entries)
> made it into the final commit message.
Done.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
bug marked as fixed in version 29.1, send any further explanations to
51495 <at> debbugs.gnu.org and Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sat, 30 Oct 2021 12:46:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 28 Nov 2021 12:24:10 GMT)
Full text and
rfc822 format available.
This bug report was last modified 3 years and 266 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.