From: Kenichi Handa <handa@m17n.org>
To: sand@blarg.net
Cc: emacs-devel@gnu.org
Subject: Re: Accumulated fontset definition tweaks for testing
Date: Fri, 16 May 2008 16:50:32 +0900 [thread overview]
Message-ID: <E1Jwui0-0001be-QF@etlken.m17n.org> (raw)
In-Reply-To: <18477.2875.876651.446827@priss.frightenedpiglet.com> (sand@blarg.net)
In article <18477.2875.876651.446827@priss.frightenedpiglet.com>, sand@blarg.net writes:
> Below is the complete set of fontset changes that my system needed to
> display the HELLO file and Markus Kuhn's "UTF-8-demo.txt" file. There
> are various problems with the fontset definitions that we can fix in
> Emacs Lisp.
> 1. The "symbol" and "phonetic" scripts don't have any representative
> characters defined, and they don't have any fontset defined.
> 2. The Latin script doesn't have representative characters over
> 7-bits. This means the Xft backend doesn't have any constraint that
> would reject ISO8859-1 fonts. Emacs appears to have special support
> for real ISO8859-1 characters, so the new definition should not
> break anything.
> 3. The Armenian script has representative characters, but no fontset
> defined.
> 4. The Thai fontset definition assumes that you have OpenType set
> up. It needs a fallback in case you don't.
> 5. The Hangul fontset definition assumes that you have a language
> definition in your Hangul font. It needs a fallback in case you
> don't.
Thank you for them. I'm going reflect 1 to 3 in fontset.el.
I think 4 and 5 is not necessary if we implement
registry-representative-chars as I wrote in the previous
mail.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-05-16 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 4:19 Accumulated fontset definition tweaks for testing sand
2008-05-16 7:50 ` Kenichi Handa [this message]
2008-05-18 5:04 ` sand
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=E1Jwui0-0001be-QF@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=sand@blarg.net \
/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).