From: Kenichi Handa <handa@m17n.org>
To: Miles Bader <miles@gnu.org>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: character composition seems much worse than before
Date: Mon, 08 Nov 2010 20:18:50 +0900 [thread overview]
Message-ID: <tl7k4kot65h.fsf@m17n.org> (raw)
In-Reply-To: <buooca0b6co.fsf@dhlpc061.dev.necel.com> (message from Miles Bader on Mon, 08 Nov 2010 16:51:51 +0900)
In article <buooca0b6co.fsf@dhlpc061.dev.necel.com>, Miles Bader <miles@gnu.org> writes:
> So with the following command:
> emacs -Q -font 'dejavu sans mono 12'
> everything works properly!
> but this:
> emacs -Q -font 'bitstream vera sans mono 12'
> fails as I described before (most importantly, fails to combine
> characters at all when auto-composition-mode is enabled).
Then, I suspect that the font doesn't have glyphs for
combining characters (U+0300...U+037F), and thus Emacs uses
the other font for those characters, which results in
no-composition (Emacs can compose characters of the same
font only). If you have a tool to see glyphs of ttf fonts,
please check it. If you don't have such a tool, please try
the program "otfview" included in libotf-bin package.
> This is pretty irritating, as Bitstream Vera Sans Mono seems to be what
> Emacs uses by default on Debian...!
How about the other programs? For instance, can gedit
display the same text correctly with that font?
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2010-11-08 11:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 3:40 character composition seems much worse than before Miles Bader
2010-11-08 3:53 ` Miles Bader
2010-11-08 4:06 ` Eli Zaretskii
2010-11-08 4:11 ` Miles Bader
2010-11-08 6:46 ` Eli Zaretskii
2010-11-08 7:30 ` Kenichi Handa
2010-11-08 7:46 ` Miles Bader
2010-11-08 7:51 ` Miles Bader
2010-11-08 9:17 ` Eli Zaretskii
2010-11-08 10:58 ` Andreas Schwab
2010-11-08 11:18 ` Miles Bader
2010-11-08 12:11 ` Andreas Schwab
2010-11-08 11:18 ` Kenichi Handa [this message]
2010-11-08 12:03 ` Andreas Schwab
2010-11-09 5:46 ` Miles Bader
2010-11-09 5:49 ` Miles Bader
2010-11-09 10:04 ` Julien Danjou
2010-11-10 1:41 ` Kenichi Handa
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=tl7k4kot65h.fsf@m17n.org \
--to=handa@m17n.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=miles@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).