unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: miles@gnu.org, emacs-devel@gnu.org
Subject: Re: japanese vs. chinese fonts
Date: Thu, 02 Oct 2008 21:45:04 +0900	[thread overview]
Message-ID: <E1KlNYG-0002IA-Id@etlken.m17n.org> (raw)
In-Reply-To: <jwv63obkwfs.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 02 Oct 2008 08:34:44 -0400)

In article <jwv63obkwfs.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> What does :lang really mean, anyway?
> > Fontconfig has it's own database to decide which font is for
> > which language.  The database maps each language to a set of
> > characters that a font must support to claim that the font
> > is for that langauge.

> So I think this problem should be pushed up to fontconfig's team.

I'm not sure.  It's not wrong that fontconfig decides that
the font support Japanese.  Perhaps, the problem should be
reported to the font developper not to include ungly glyphs
in a font.  Fontconfig can't know how ugly glyphs are.

By the eay, I'm not familiar with fontconfig's configulation
file, but aren't their a way to customize fontconfig to
refuse that font as a Japanese font?

---
Kenichi Handa
handa@ni.aist.go.jp





  reply	other threads:[~2008-10-02 12:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02  5:38 japanese vs. chinese fonts Miles Bader
2008-10-02  6:06 ` Kenichi Handa
2008-10-02  6:11   ` Miles Bader
2008-10-02  6:49     ` Kenichi Handa
2008-10-02  7:27       ` Miles Bader
2008-10-02  9:30         ` Werner LEMBERG
2008-10-02 11:54           ` Kenichi Handa
2008-10-02 14:24             ` Juanma Barranquero
2008-10-03  0:32               ` Kenichi Handa
2008-10-02 11:57         ` Kenichi Handa
2008-10-02 12:34           ` Stefan Monnier
2008-10-02 12:45             ` Kenichi Handa [this message]
2008-10-02 13:32               ` Stefan Monnier

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=E1KlNYG-0002IA-Id@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).