From: Madhu <enometh@meer.net>
To: eliz@gnu.org
Cc: 45557@debbugs.gnu.org
Subject: bug#45557: 27.1; Incorrect rendering of COMBINING OVERLINE
Date: Thu, 07 Jan 2021 11:40:31 +0530 (IST) [thread overview]
Message-ID: <20210107.114031.1253265759097486788.enometh@meer.net> (raw)
In-Reply-To: <83turu11xm.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> <83turu11xm.fsf@gnu.org>
Wrote on Wed, 06 Jan 2021 18:10:29 +0200
>> From: Madhu <enometh@meer.net>
>> > Anyway, I see no Emacs problems in your description, only font
>> > problems. The text you sent is displayed correctly on my system, both
>> > of its lines.
Can you try using a font with emacs which does not compose the x and
overbar?
>> I assume the mswindows and applemac systems dont pull in harfbuzz?
> No, the Windows build does use HarfBuzz.
Whatever is doing the visual composition of x + overbar (when emacs is
explicitly asked not to do it by turning auto-composition-mode off) -
it isn't harfbuzz. It happens on an emacs (--without-all) which links
to freetype without harfbuzz/cairo (and even when emacs isn't using m17n-lib)
Very puzzling.
next prev parent reply other threads:[~2021-01-07 6:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 13:42 bug#45557: 27.1; Incorrect rendering of COMBINING OVERLINE Stephen Eglen
2020-12-31 5:24 ` Lars Ingebrigtsen
2020-12-31 7:33 ` Eli Zaretskii
2020-12-31 9:06 ` Stephen Eglen
2020-12-31 14:15 ` Eli Zaretskii
2020-12-31 13:45 ` Eli Zaretskii
2020-12-31 14:12 ` Stephen Eglen
2020-12-31 15:14 ` Eli Zaretskii
2020-12-31 16:11 ` Stephen Eglen
2021-01-01 8:28 ` Stephen Eglen
2021-01-01 11:09 ` Lars Ingebrigtsen
2021-01-02 18:47 ` James Cloos
2021-01-06 2:38 ` Madhu
2021-01-06 15:10 ` Eli Zaretskii
2021-01-06 16:00 ` Madhu
2021-01-06 16:10 ` Eli Zaretskii
2021-01-07 6:10 ` Madhu [this message]
2021-01-07 14:16 ` Eli Zaretskii
2021-01-07 15:28 ` Robert Pluim
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210107.114031.1253265759097486788.enometh@meer.net \
--to=enometh@meer.net \
--cc=45557@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).