From: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: utf-8 cjk translation bug?
Date: Tue, 07 Oct 2003 18:57:39 +0900 [thread overview]
Message-ID: <87r81p2wvg.fsf@tleepslib.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <87u16mf867.fsf@tc-1-100.kawasaki.gol.ne.jp> (Miles Bader's message of "07 Oct 2003 05:00:32 +0900")
>>>>> "Miles" == Miles Bader <miles@gnu.org> writes:
Miles> Miles Bader <miles@lsi.nec.co.jp> writes:
>> Yeah, that's definitely the case, and it's not just a problem
>> with double-width characters -- the coverage of many iso10646
>> fonts seems completely crap.
Microsoft Arial, for one of the egregious worst. :-) Why should a
Russian font designer be good at designing Sanskrit glyphs? Who knows
which Thai fonts go well with a given Arabic one? ISO 10646 fonts
should cover what their designers are good at, no more---and not
necessarily no less.
It's not even obvious that there should be terminal fonts with
universal coverage. Some Unihan users will surely object to any
given choice of glyphs, for example.
Miles> BTW, does this mean that the new unicode emacs will have
Miles> problems rendering many charsets that are currently
Miles> displayed properly by emacs?
In practice, probably yes ... but that will be a bug easily fixed, and
long before release. :-) Post-modern Emacsen will have to have
support for efficiently querying font repertoire (I see emacs-unicode
already has a defined API). For example, you'll get this for free
with Xft2/fontconfig.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
next prev parent reply other threads:[~2003-10-07 9:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 8:30 utf-8 cjk translation bug? Miles Bader
2003-09-30 9:50 ` Jason Rumney
2003-09-30 10:05 ` Miles Bader
2003-09-30 12:59 ` Kenichi Handa
2003-10-01 12:44 ` Dave Love
2003-10-02 1:08 ` Kenichi Handa
2003-10-03 16:04 ` Dave Love
2003-10-03 16:34 ` Jason Rumney
2003-10-06 2:29 ` Miles Bader
2003-10-06 20:00 ` Miles Bader
2003-10-06 20:53 ` Jason Rumney
2003-10-06 23:18 ` Kenichi Handa
2003-10-07 9:57 ` Stephen J. Turnbull [this message]
2003-10-07 11:41 ` Dave Love
2003-10-07 11:40 ` Dave Love
2003-10-06 23:53 ` Kenichi Handa
2003-10-10 16:56 ` Dave Love
2003-10-13 23:55 ` 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=87r81p2wvg.fsf@tleepslib.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@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).