unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: kasahara@nc.kyushu-u.ac.jp, emacs-devel@gnu.org
Subject: Re: X fonts selection weirdness
Date: Wed, 25 Jun 2008 22:45:23 +0900	[thread overview]
Message-ID: <87wskdtyq4.fsf@catnip.gol.com> (raw)
In-Reply-To: <E1KBTEC-0006aO-Pu@etlken.m17n.org> (Kenichi Handa's message of "Wed, 25 Jun 2008 20:31:56 +0900")

Kenichi Handa <handa@m17n.org> writes:
>> If the user choose a default font capable of displaying one of those
>> charsets, it seems like he would _want_ the default font to be used!
>
> Not for non-Latin scripts, especially CJK and those require
> CTL (Complex Text Layout).  Usually the default font, even
> if it claims that it has the specific character, the design
> is not good or doesn't contain proper OTF tables.

I'm confused.

If I specify, for instance, a default font of "Sazanami 12", that works
great for both ascii and CJK characters, and has the rather nice
property that the 2-1 width ration of CJK and ascii characters is
preserved exactly (so, e.g., character graphics look correct).

Morever, since such a font's main repertoire is CJK characters, if
somebody specifies it as the _default_ font, it would seem fairly
obvious that they want to use it to display both ascii and CJK
characters.

When a user specifies such a default font, which has a very wide
repertoire, that's a very simple way for them to get consistent
rendering.

I gather you're instead talking about fonts that mainly cover ascii, and
"accidentally" happen to include some other characters?

-Miles

-- 
Run away!  Run away!




  reply	other threads:[~2008-06-25 13:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24  3:42 X fonts selection weirdness Yoshiaki Kasahara
2008-06-24  4:21 ` Miles Bader
2008-06-24  6:20   ` Yoshiaki Kasahara
2008-06-24  4:53 ` Kenichi Handa
2008-06-24  5:57   ` Yoshiaki Kasahara
2008-06-24  7:02     ` Kenichi Handa
2008-06-24  9:08       ` Yoshiaki Kasahara
2008-06-25  7:47         ` Kenichi Handa
2008-06-25  7:55           ` Miles Bader
2008-06-25  8:05             ` Jason Rumney
2008-06-25 11:31             ` Kenichi Handa
2008-06-25 13:45               ` Miles Bader [this message]
2008-06-25 14:04                 ` Miles Bader
2008-06-26 11:40                 ` Kenichi Handa
2008-06-26 21:20               ` Richard M Stallman
2008-06-27  0:32                 ` Kenichi Handa
2008-06-27 15:38                   ` Richard M Stallman
2008-06-25  8:15           ` David Kastrup
2008-07-09  1:42             ` Kenichi Handa
2008-07-15  3:34               ` Yoshiaki Kasahara
2008-06-26  7:39           ` Yoshiaki Kasahara
2008-06-24 12:42       ` Stefan Monnier
2008-06-24 15:10         ` Kenichi Handa
2008-06-24 18:46           ` Stefan Monnier
2008-06-25  0:36             ` 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=87wskdtyq4.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=kasahara@nc.kyushu-u.ac.jp \
    /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).