unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: Kevin Yu <yujie052@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Ntemacs chooses wrong font.
Date: Fri, 06 Jun 2008 22:23:48 +0100	[thread overview]
Message-ID: <4849AAE4.4080404@gnu.org> (raw)
In-Reply-To: <42b562540806060552q622e3dfvb35820ec28dc66d3@mail.gmail.com>

Kevin Yu wrote:
> If you input any Chinese into a new buffer, Ntemacs will use the same
> font as ASCII characters (iso8859-1). Of course that font is not
> suitable for Chinese, so I get only white spaces on the window.
> describe-char shows that emacs has detected that it's a Chinese
> character, but chosen a wrong font(wrong charset):
> character: 实 (23454, #o55636, #x5b9e)
> preferred charset: gb18030 (GB18030)
> code point: 0xCAB5
> -outline-Monaco-normal-normal-normal-mono-13-*-*-*-c-*-iso8859-1 (#x03)

Another font that maps unsupported glyphs to 0x03 instead of 0x00.
DejaVu Sans Mono seems to do this too. Perhaps it is common amongst
truetype fonts that were not designed for Windows.

> if I open a existed file with Chinese characters, everything goes well.

Can you show the output you get from C-u C-x = in that case? It seems
strange that a different font would be used for the two cases. Perhaps
comparing the two outputs will give some clues.





  reply	other threads:[~2008-06-06 21:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 12:52 Ntemacs chooses wrong font Kevin Yu
2008-06-06 21:23 ` Jason Rumney [this message]
2008-06-07  2:41   ` Kevin Yu
2008-06-11  2:32     ` Kevin Yu
2008-06-11  8:36     ` Jason Rumney
2008-06-11 10:51       ` Kevin Yu
2008-06-11 11:27         ` Jason Rumney
2008-06-11 12:05           ` Kevin Yu
2008-06-11 12:40             ` Jason Rumney
2008-06-11 11:50         ` Kenichi Handa
2008-06-11 12:09           ` Kevin Yu
2008-06-11 12:29             ` Kenichi Handa
2008-06-11 12:34           ` Jason Rumney
2008-06-11 13:11             ` Kenichi Handa
2008-06-11 13:48             ` Juanma Barranquero
2008-06-16 21:37 ` Jason Rumney

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=4849AAE4.4080404@gnu.org \
    --to=jasonr@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=yujie052@gmail.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 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).