From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: xfq.free@gmail.com, 15273@debbugs.gnu.org
Subject: bug#15273: 24.3.50; Combining character sequences are displayed weirdly
Date: Fri, 06 Sep 2013 08:42:23 +0200 [thread overview]
Message-ID: <87vc2ee9io.fsf@igel.home> (raw)
In-Reply-To: <83r4d2mpi2.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 Sep 2013 09:29:57 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Character composition in Emacs can happen in 1 of 2 ways:
>
> . The font driver tells Emacs to compose several characters into a
> single grapheme cluster, by drawing all of them as a single unit,
> and by drawing the 2nd, 3rd, etc. character glyphs at certain pixel
> offsets relative to the base glyph.
>
> . Emacs itself has composition rules for 2 or more characters; in
> this case, the same pixel offsets come from those rules.
The first way can only work if both characters are coming from the same
font. Not sure if that is also true for the second way, but I'd guess
yes.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-09-06 6:42 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 14:08 bug#15273: 24.3.50; Combining character sequences are displayed weirdly Xue Fuqiao
2013-09-05 14:33 ` Eli Zaretskii
2013-09-05 23:26 ` Xue Fuqiao
2013-09-05 16:48 ` Jan Djärv
2013-09-05 17:12 ` Eli Zaretskii
2013-09-05 17:24 ` Eli Zaretskii
2013-09-05 17:33 ` Jan Djärv
2013-09-05 17:56 ` Eli Zaretskii
2013-09-06 5:08 ` Jan Djärv
2013-09-06 6:29 ` Eli Zaretskii
2013-09-06 6:42 ` Andreas Schwab [this message]
2013-09-06 7:32 ` Eli Zaretskii
2013-09-06 14:37 ` Xue Fuqiao
2013-09-06 15:53 ` Eli Zaretskii
2013-09-06 22:17 ` Xue Fuqiao
2013-09-06 22:37 ` Xue Fuqiao
2013-09-07 7:27 ` Eli Zaretskii
2013-09-07 7:26 ` Eli Zaretskii
2013-09-07 7:36 ` Jan Djärv
2013-09-07 7:57 ` Eli Zaretskii
2013-09-07 8:02 ` Jan Djärv
2013-09-07 8:10 ` Eli Zaretskii
2013-09-07 8:27 ` Jan Djärv
2013-09-07 8:40 ` Eli Zaretskii
2013-09-07 8:54 ` Jan Djärv
2013-09-07 9:59 ` Eli Zaretskii
2013-09-07 13:44 ` Jan Djärv
2013-09-07 15:20 ` Eli Zaretskii
2013-09-08 8:26 ` Jan Djärv
2013-09-07 22:50 ` Xue Fuqiao
2013-09-07 8:47 ` Jan Djärv
2013-09-07 9:22 ` Eli Zaretskii
2013-09-09 0:52 ` YAMAMOTO Mitsuharu
2013-09-09 5:17 ` Jan Djärv
2013-09-07 12:25 ` Wolfgang Jenkner
2013-09-07 15:18 ` Eli Zaretskii
2013-09-07 21:38 ` Wolfgang Jenkner
2013-09-07 22:29 ` Xue Fuqiao
2013-09-07 22:48 ` Xue Fuqiao
2013-09-08 11:03 ` Eli Zaretskii
2013-09-08 13:05 ` Kenichi Handa
2013-09-08 14:59 ` Eli Zaretskii
2013-09-10 13:58 ` Kenichi Handa
2013-09-10 15:37 ` Eli Zaretskii
2013-09-12 14:52 ` Kenichi Handa
2013-09-12 16:08 ` Eli Zaretskii
2020-11-18 15:13 ` Stefan Kangas
2020-11-18 17:09 ` Eli Zaretskii
2013-09-14 8:51 ` Jan Djärv
2013-09-14 9:12 ` Jan Djärv
2013-09-05 17:29 ` Jan Djärv
2013-09-05 17:56 ` Eli Zaretskii
2013-09-05 23:27 ` Xue Fuqiao
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=87vc2ee9io.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=15273@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=xfq.free@gmail.com \
/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).