From: Alexis <flexibeast@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: hdfssk@gmail.com, 23292@debbugs.gnu.org
Subject: bug#23292: 24.5; Combining characters do not reliably combine
Date: Fri, 15 Apr 2016 19:03:15 +1000 [thread overview]
Message-ID: <87oa9btfak.fsf@gmail.com> (raw)
In-Reply-To: <83zisvclwi.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Alexis <flexibeast@gmail.com> Cc: hdfssk@gmail.com,
>> 23292@debbugs.gnu.org Date: Fri, 15 Apr 2016 18:17:48 +1000
>>
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > No. Type 'o', then "C-x 8 RET 337".
>>
>> Done. i get the same result as the OP - i.e. the 'o' and the
>> '/' are visually separated - using both DejaVu Sans Mono
>> (Book) and Inconsolata-G (my default font).
My apologies, i accidentally used a non -Q instance to test
this. :-/ In a -Q instance, it turns out that DejaVu Sans Mono
(Book) /does/ compose visually:
Composed with the following character(s) "̷" using this font:
xft:-unknown-DejaVu Sans
Mono-normal-normal-normal-*-13-*-*-*-m-0-iso10646-1
by these glyphs:
[0 1 111 82 8 0 8 8 1 nil] [0 1 823 703 0 0 8 8 1 [-8 0 0]]
Sorry!
However, Inconsolata-g definitely doesn't compose visually.
Interestingly, when i use `describe-char' on the 'o', i'm told
that the glyph is sourced from Inconsolata-g, but when i use it on
the '/', it tells me it's sourced from Gentium ....
next prev parent reply other threads:[~2016-04-15 9:03 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oa9btfak.fsf@gmail.com \
--to=flexibeast@gmail.com \
--cc=23292@debbugs.gnu.org \
--cc=eliz@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 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.