GNU bug report logs - #11072
Display of glyphless non-spacing modifiers via a static composition

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 11072 in the body.
You can then email your comments to 11072 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Kenichi Handa <handa <at> m17n.org>
Cc: bug-gnu-emacs <at> gnu.org
Subject: Display of glyphless non-spacing modifiers via a static composition
Date: Fri, 23 Mar 2012 12:12:02 +0200

> From: Kenichi Handa <handa <at> m17n.org>
> Cc: list-general <at> mohsen.1.banan.byname.net, emacs-devel <at> gnu.org
> Date: Fri, 23 Mar 2012 10:41:07 +0900
> 
> In article <83fwd0wnwl.fsf <at> gnu.org>, Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Btw, there's some strange problem in displaying one label of the
> > hebrew-biblical-tiro input method: the character u+05ba (inserted by
> > Shift-5 key) is displayed as a blank rectangle.  It looks like my
> > fonts have no glyph for this character, but then why don't we display
> > this like any other glyphless character: as a hex code inside a small
> > rectangle?  That's what I get if I insert this character into a
> > buffer, but somehow the way we display it in the keyboard layout (and
> > in the "C-u C-x =" display under "decomposition") behaves differently.
> > Why is that?
> 
> As that character is a non-spacing modifier, we display it
> with a static composition, and a glyph in a static
> composition are displayed by a blank rectangle if no font is
> available.  This is because a hex code makes the resulting
> display of composition (several glyphs may occupy a single
> column) unreadable.
> 
> It may be possible to change the current code to use a hex
> code displaying if a composition contains just one glyph and
> that glyph has no font, but it may be for 24.2.

So this bug will wait for after Emacs 24.1 release to be fixed.

Thanks.

Message #8 received at 11072 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 11072 <at> debbugs.gnu.org, Kenichi Handa <handa <at> m17n.org>
Subject: Re: bug#11072: Display of glyphless non-spacing modifiers via a
 static composition
Date: Thu, 31 Oct 2019 00:13:16 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Kenichi Handa <handa <at> m17n.org>
>> Cc: list-general <at> mohsen.1.banan.byname.net, emacs-devel <at> gnu.org
>> Date: Fri, 23 Mar 2012 10:41:07 +0900
>> 
>> In article <83fwd0wnwl.fsf <at> gnu.org>, Eli Zaretskii <eliz <at> gnu.org> writes:
>> 
>> > Btw, there's some strange problem in displaying one label of the
>> > hebrew-biblical-tiro input method: the character u+05ba (inserted by
>> > Shift-5 key) is displayed as a blank rectangle.  It looks like my
>> > fonts have no glyph for this character, but then why don't we display
>> > this like any other glyphless character: as a hex code inside a small
>> > rectangle?  That's what I get if I insert this character into a
>> > buffer, but somehow the way we display it in the keyboard layout (and
>> > in the "C-u C-x =" display under "decomposition") behaves differently.
>> > Why is that?
>> 
>> As that character is a non-spacing modifier, we display it
>> with a static composition, and a glyph in a static
>> composition are displayed by a blank rectangle if no font is
>> available.  This is because a hex code makes the resulting
>> display of composition (several glyphs may occupy a single
>> column) unreadable.
>> 
>> It may be possible to change the current code to use a hex
>> code displaying if a composition contains just one glyph and
>> that glyph has no font, but it may be for 24.2.
>
> So this bug will wait for after Emacs 24.1 release to be fixed.
>
> Thanks.

Hi Eli,

No update on this bug in 7 years.  Has this been fixed in the
intervening time?

Best regards,
Stefan Kangas

Message #16 received at 11072-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: 11072-done <at> debbugs.gnu.org, handa <at> m17n.org
Subject: Re: bug#11072: Display of glyphless non-spacing modifiers via a
 static composition
Date: Thu, 31 Oct 2019 16:13:34 +0200

> From: Stefan Kangas <stefan <at> marxist.se>
> Cc: Kenichi Handa <handa <at> m17n.org>,  11072 <at> debbugs.gnu.org
> Date: Thu, 31 Oct 2019 00:13:16 +0100
> 
> >> As that character is a non-spacing modifier, we display it
> >> with a static composition, and a glyph in a static
> >> composition are displayed by a blank rectangle if no font is
> >> available.  This is because a hex code makes the resulting
> >> display of composition (several glyphs may occupy a single
> >> column) unreadable.
> >> 
> >> It may be possible to change the current code to use a hex
> >> code displaying if a composition contains just one glyph and
> >> that glyph has no font, but it may be for 24.2.
> >
> > So this bug will wait for after Emacs 24.1 release to be fixed.
> >
> > Thanks.
> 
> Hi Eli,
> 
> No update on this bug in 7 years.  Has this been fixed in the
> intervening time?

It seems so: I now see a box with a hex code.

Closing.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.