all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: xfq.free@gmail.com, 15273@debbugs.gnu.org
Subject: bug#15273: 24.3.50; Combining character sequences are displayed weirdly
Date: Sat, 07 Sep 2013 12:59:32 +0300	[thread overview]
Message-ID: <83eh91kl4r.fsf@gnu.org> (raw)
In-Reply-To: <D609609C-E7AE-4662-AA33-220B8565FACE@swipnet.se>

> From: Jan Djärv <jan.h.d@swipnet.se>
> Date: Sat, 7 Sep 2013 10:54:58 +0200
> Cc: xfq.free@gmail.com,
>  15273@debbugs.gnu.org
> 
> Except the larger bug that Emacs does not handle combining characters correctly in the general case, i.e. not combining the ! and the triangle on X11 and W32 (and Mac port).

Is there any application out there that does combine these 2
characters, with any font?  If not, perhaps it's not an Emacs issue
after all.

E.g., Code2000, which is really good, produces a composed character
for a followed by u+20d0, but not for a followed by u+20e4.  You can
experiment with other combining diacriticals from that Unicode block,
and you will see that some of them combine, while others do not.

If the fonts do not tell us to combine characters, the only way to do
that is to provide an Emacs composition rule for those characters.

> And if it is a bug in the NS font driver, that is also an Emacs issue.  There must be one, either metrics should be corrected or the NS font driver should be modified to behave in the same (incorrect) way as the other platforms.

If you mean the incorrect display of the lone u+20e4, then I just
installed the STIX fonts (from
http://sourceforge.net/projects/stixfonts/files/?source=navbar) on my
Windows box, and didn't see any problems as originally reported here.
Can you install the latest STIX fonts and try with that on NS?  If the
problem persists, then I agree that nsfont.m is probably the culprit.

> > But Xue now seems to say that there are other similar
> > situations with other combining characters, so we need to know if any
> > compositions are involved in those.
> 
> The exact key sequences that produced them would help also.

You can always use "C-x 8 RET" to type the characters, so I don't see
why the key sequences would be an issue.





  reply	other threads:[~2013-09-07  9:59 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83eh91kl4r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=15273@debbugs.gnu.org \
    --cc=jan.h.d@swipnet.se \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.