From: Eli Zaretskii <eliz@gnu.org>
To: handa@gnu.org
Cc: hdfssk@gmail.com, flexibeast@gmail.com, 23292@debbugs.gnu.org
Subject: bug#23292: 24.5; Combining characters do not reliably combine
Date: Fri, 15 Apr 2016 12:15:50 +0300 [thread overview]
Message-ID: <83y48fcjw9.fsf@gnu.org> (raw)
In-Reply-To: <83zisvclwi.fsf@gnu.org> (message from Eli Zaretskii on Fri, 15 Apr 2016 11:32:29 +0300)
> Date: Fri, 15 Apr 2016 11:32:29 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: hdfssk@gmail.com, 23292@debbugs.gnu.org
>
> For the record, the composition works for me on MS-Windows using the
> Arial Unicode MS font, and the composition data looks quite different
> (and makes much more sense to me) than what the OP shows:
>
> Composed with the following character(s) "̷" using this font:
> uniscribe:-outline-Arial Unicode MS-normal-normal-normal-sans-13-*-*-*-p-*-iso8859-1
> by these glyphs:
> [0 1 111 82 7 1 6 14 4 nil]
> [0 1 823 671 0 -5 -2 14 4 nil]
>
> The OP said the composition data he gets is this:
>
> Composed with the following character(s) "̷" using this font:
> xft:-PfEd-DejaVu Sans Mono-normal-normal-normal-*-13-*-*-*-m-0-iso10646-1
> by these glyphs:
> [0 1 111 82 8 1 7 7 0 nil]
> [0 1 823 703 8 0 8 8 1 nil]
>
> and the offsets in the second vector look wrong to me, FWIW.
I now tried this on Windows 8.1, where the (default) Courier New font
does have a glyph for u+0337, and I see there the same problem as
reported by the OP, including the composition data that shows positive
offsets where I thought negative offsets should be.
Maybe this is something related to the fact that bot DejaVu Sans Mono
and Courier New are monospaced fonts, whereas Arial Unicode MS isn't?
I Hope Handa-san will provide some insight.
next prev parent reply other threads:[~2016-04-15 9:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 19:26 bug#23292: 24.5; Combining characters do not reliably combine Honore Doktorr
2016-04-14 19:50 ` Eli Zaretskii
[not found] ` <CABtnboWhZYg16Wd9XPi4KjUjSTaC77BttkAU5OhrQXdsH=6+qQ@mail.gmail.com>
2016-04-15 6:53 ` Eli Zaretskii
2016-04-15 7:47 ` Alexis
2016-04-15 7:55 ` Eli Zaretskii
2016-04-15 8:17 ` Alexis
2016-04-15 8:32 ` Eli Zaretskii
2016-04-15 9:03 ` Alexis
2016-04-15 9:21 ` Eli Zaretskii
2016-04-15 11:52 ` Alexis
2016-04-16 10:01 ` Eli Zaretskii
2016-04-15 9:15 ` Eli Zaretskii [this message]
2016-04-24 14:18 ` handa
2016-05-17 4:40 ` Alexis
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=83y48fcjw9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23292@debbugs.gnu.org \
--cc=flexibeast@gmail.com \
--cc=handa@gnu.org \
--cc=hdfssk@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).