From: "Kevin Yu" <yujie052@gmail.com>
To: "Jason Rumney" <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Ntemacs chooses wrong font.
Date: Sat, 7 Jun 2008 10:41:05 +0800 [thread overview]
Message-ID: <42b562540806061941p2c2d2ebfg734c2d7c4afbbd28@mail.gmail.com> (raw)
In-Reply-To: <4849AAE4.4080404@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2047 bytes --]
character: 实 (23454, #o55636, #x5b9e)
preferred charset: gb18030 (GB18030)
code point: 0xCAB5
syntax: w which means: word
category: C:Chinese (Han) characters of 2-byte character sets
c:Chinese
|:While filling, we can break a line at this character.
buffer code: #xE5 #xAE #x9E
file code: #xCA #xB5 (encoded by coding system chinese-gb18030-unix)
display: by this font (glyph code)
-outline- -normal-normal-normal-mono-13-*-*-*-c-*-gb2312.1980-0
(#x1172)
Emacs displays the font family name as:"\320\302\313\316\314\345"
those octal bytes represent for "新宋体", in fact it isn't the font I tell
emacs to choose for Chinese characters.
By the way, in the elisp manual, all localized strings are showed as octal
bytes, Here's an example:
-- \272\257\312\375: funcall function &rest arguments
`funcall' calls FUNCTION with ARGUMENTS, and returns whatever
FUNCTION returns.
On Sat, Jun 7, 2008 at 5:23 AM, Jason Rumney <jasonr@gnu.org> wrote:
> 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.
>
>
[-- Attachment #2: Type: text/html, Size: 2921 bytes --]
next prev parent reply other threads:[~2008-06-07 2:41 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
2008-06-07 2:41 ` Kevin Yu [this message]
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=42b562540806061941p2c2d2ebfg734c2d7c4afbbd28@mail.gmail.com \
--to=yujie052@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@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).