unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@gnu.org>
Cc: 12352@debbugs.gnu.org
Subject: bug#12352: 24.2.50; Failure to compose characters in mode-line input method indicator
Date: Sat, 22 Sep 2012 11:21:41 +0300	[thread overview]
Message-ID: <83lig2wjqi.fsf@gnu.org> (raw)
In-Reply-To: <87zk4id7po.fsf@gnu.org>

> From: Kenichi Handa <handa@gnu.org>
> Cc: handa@gnu.org
> Date: Sat, 22 Sep 2012 13:04:03 +0900
> 
> In article <876279dvv7.fsf@gnu.org>, Kenichi Handa <handa@gnu.org> writes:
> 
> > I think I tracked down the problem to the function
> > composition_reseat_it which calls autocmp_chars.  This bug
> > happens when a Hebrew (or any other R2L script) syllable has
> > N characters and a font selected for the last character of
> > the syllable is different from a font selected for the first
> > character.  But, autocmp_chars was not coded to work on such
> > a situation.  I'm now trying to find a solution.
> 
> I've just installed a fix to the trunk.  Could you please
> try it?

Thanks, it works now the same in both buffer and mode-line display.  I
think you can close this bug now.

The last character, HEBREW ACCENT OLE, is still not composed with the
first two, both in the buffer display and on the mode line.  But I
understand that this is because that character is taken from a
different font, and we don't currently support compositions for
characters that come from different fonts, is that right?  If I use
the "Keter YG" font for Hebrew, then all 3 of the characters are
composed.





       reply	other threads:[~2012-09-22  8:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87zk4id7po.fsf@gnu.org>
2012-09-22  8:21 ` Eli Zaretskii [this message]
2019-10-30 23:08   ` bug#12352: 24.2.50; Failure to compose characters in mode-line input method indicator Stefan Kangas
2019-10-31 14:12     ` Eli Zaretskii
2012-09-04 20:00 Eli Zaretskii

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=83lig2wjqi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=12352@debbugs.gnu.org \
    --cc=handa@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).