From: Torsten Bronger <bronger@physik.rwth-aachen.de>
To: Kenichi Handa <handa@m17n.org>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: [Torsten Bronger] 23.0.60; Unicode display problems
Date: Wed, 10 Sep 2008 09:11:57 +0200 [thread overview]
Message-ID: <874p4o4gqq.fsf@physik.rwth-aachen.de> (raw)
In-Reply-To: E1KdJR7-0003VZ-El@etlken.m17n.org
Hallöchen!
Kenichi Handa writes:
> In article <87sks9eqxt.fsf@physik.rwth-aachen.de>, Torsten Bronger
> <bronger@physik.rwth-aachen.de> writes:
>
>>> By the way, do you compile Emacs with m17n-lib?
>
>> No.
>
> Ah, I see. Without m17n-lib (and libotf), Emacs can't
> utilize OpenType table in the font. In such a case, Emacs
> artificially adjusts the placement of combining characters.
> I've just fixed a code for doing that. So, please try again
> with the latest code.
The accents look very nice now, even multiple diacritics on the same
letter are stacked correctly. However, I still can't pass the letter
with the cursor. And, when I want to view this email with Gnus, it
says "apply: Args out of range: 1399, 1399".
character: x (120, #o170, #x78)
preferred charset: ascii (ASCII (ISO646 IRV))
code point: 0x78
syntax: w which means: word
category: a:ASCII graphic characters 32-126 (ISO646 IRV:1983[4/0]) l:Latin r:Japanese roman
buffer code: #x78
file code: #x78 (encoded by coding system utf-8-unix)
display: composed to form "ẍ" (see below)
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 120 91 8 0 8 7 0 nil]
[0 1 776 644 8 2 6 10 -8 [-8 0 0]]
Character code properties: customize what to show
name: LATIN SMALL LETTER X
general-category: Ll (Letter, Lowercase)
Tschö,
Torsten.
--
Torsten Bronger, aquisgrana, europa vetus
Jabber ID: torsten.bronger@jabber.rwth-aachen.de
next prev parent reply other threads:[~2008-09-10 7:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871w022tmy.fsf@cyd.mit.edu>
2008-09-03 8:13 ` [Torsten Bronger] Re: 23.0.60; Unicode display problems Kenichi Handa
2008-09-03 14:40 ` Miles Bader
2008-09-03 14:51 ` Jason Rumney
2008-09-05 1:27 ` Kenichi Handa
2008-09-06 20:34 ` [Torsten Bronger] " Torsten Bronger
2008-09-09 2:30 ` Kenichi Handa
2008-09-09 3:22 ` Kenichi Handa
2008-09-09 7:09 ` Torsten Bronger
2008-09-10 6:44 ` Kenichi Handa
2008-09-10 7:11 ` Torsten Bronger [this message]
2008-09-10 8:03 ` Torsten Bronger
2008-09-10 8:11 ` Kenichi Handa
2008-09-10 8:20 ` Juanma Barranquero
2008-09-10 10:21 ` Kenichi Handa
2008-09-10 10:49 ` Juanma Barranquero
2008-09-10 11:11 ` Juanma Barranquero
2008-09-10 12:04 ` Kenichi Handa
2008-09-10 12:30 ` Torsten Bronger
2008-09-10 14:19 ` Juanma Barranquero
2008-09-11 0:31 ` Kenichi Handa
2008-09-11 0:54 ` Juanma Barranquero
2008-09-11 6:12 ` Torsten Bronger
2008-09-11 11:22 ` Kenichi Handa
2008-09-11 12:12 ` Torsten Bronger
2008-09-18 10:44 ` Kenichi Handa
2008-09-18 11:50 ` Torsten Bronger
2008-09-09 6:54 ` Torsten Bronger
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=874p4o4gqq.fsf@physik.rwth-aachen.de \
--to=bronger@physik.rwth-aachen.de \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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).