From: Kenichi Handa <handa@ni.aist.go.jp>
To: "Richard Wordingham" <richard.wordingham@ntlworld.com>
Cc: emacs-devel@gnu.org
Subject: Re: [w32] display international HELLO
Date: Mon, 19 Nov 2007 11:35:26 +0900 [thread overview]
Message-ID: <E1ItwTu-0007aR-Jb@etlken.m17n.org> (raw)
In-Reply-To: <00d801c82732$0001dfb0$d5101252@JRWXP1> (richard.wordingham@ntlworld.com)
In article <00d801c82732$0001dfb0$d5101252@JRWXP1>, "Richard Wordingham" <richard.wordingham@ntlworld.com> writes:
>>> 3. Compositions of Lao characters, (i.e. with the 'composition' string
>>> property) using the Code2000 font (the only fully working Lao font I
>>> have),
>>> do not display properly, whether they are in the Lao or
>>> mule-unicode-0100-24ff charset.
> > I think it's a waste of time to learn composition mechanism
> > of Emacs 22. It will be a lot improved in emacs-unicode-2.
> Are you talking of future work or the present state of emacs-unicode-2, as
> in Emacs 23.0.60.0?
I'm talking about the future work, but the latest
emacs-unicode-2 code already contains half-done codes.
> Are you talking of applying the composition property,
> or of the rendering of composed sequences?
I'm going to allow each font-backends to generate proper
composition information that will vary depending on a font,
instead of the current fixed way of composition. So, On
Windows, perhaps the font backend can utilize uniscribe. On
GNU/Linux, I have not yet decided what to do; using Pango,
using m17n-lib, or using a newly written code that directly
uses libotf or harfbuzz for OTF handling. I think the last
choice will result in the fastest rendering.
> With the help of Jason Rumney I
> got 23.0.60.0 to build and run on Windows XP, but the Lao compositions are
> still displaying unreadably bizarrely. Unfortunately the more thorough
> application of composition in emacs-unicode-2 currently makes matters worse!
> Before, one could easily if tediously avoid the composition mechanism. For
> example, to make a Lao closed syllable consonant-vowel sequence <ka>, in
> Emacs 22.1 one can type d, space, delete, a. The best I can find in Emacs
> 23.0.60.0 is d, space, a, left, delete. However, as soon as one moves the
> cursor the characters compose and are then misdisplayed.
That is because of the auto-composition mechanism introduced
in emacs-unicode-2. The problem is that the current fixed
composition is suitable only for a specific font (usually a
fixed-width terminal font). Even on Windows, I think
there's a way to use BDF fonts distributed as intlfonts. If
you use those fonts on Windows, the rendering should be
good.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2007-11-19 2:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 8:37 [w32] display international HELLO Richard Wordingham
2007-11-09 10:55 ` Eli Zaretskii
2007-11-09 12:40 ` Kenichi Handa
2007-11-15 2:48 ` Richard Wordingham
2007-11-19 2:35 ` Kenichi Handa [this message]
2007-11-19 8:51 ` Jason Rumney
2007-11-20 1:49 ` Richard Wordingham
2007-11-20 11:30 ` Jason Rumney
2007-11-20 12:50 ` Kenichi Handa
2007-11-21 1:51 ` Richard Wordingham
-- strict thread matches above, loose matches on Subject: below --
2007-01-31 6:34 Takashi Hiromatsu
2007-01-31 6:51 ` Kenichi Handa
2007-01-31 7:07 ` Takashi Hiromatsu
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=E1ItwTu-0007aR-Jb@etlken.m17n.org \
--to=handa@ni.aist.go.jp \
--cc=emacs-devel@gnu.org \
--cc=richard.wordingham@ntlworld.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.