From: Daniel Anderson <dankles@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Japanese fonts
Date: Mon, 04 Jul 2011 00:09:09 -0400 [thread overview]
Message-ID: <87liwesn4q.fsf@gmail.com> (raw)
Greetings help-gnu-emacs,
For people not familiar with japanese, this may be a bit confusing...
The issue is that the kanji character set for japanese fonts in emacs
shows up as one font, while the hiragana font shows up as another
font. The inconsistency is a bit ugly. Any one have any solutions?
Here are the properties of each in just a Fundamental mode buffer:
Kanji:
character: 録 (37682, #o111462, #x9332)
preferred charset: unicode (Unicode (ISO10646))
code point: 0x9332
syntax: w which means: word
category: .:Base, C:2-byte han, c:Chinese, j:Japanese, |:line breakable
buffer code: #xE9 #x8C #xB2
file code: #xE9 #x8C #xB2 (encoded by coding system utf-8-unix)
display: by this font (glyph code)
xft:-unknown-Droid Sans Fallback-normal-normal-normal-*-15-*-*-*-*-0-iso10646-1 (#x4AC2)
Character code properties: customize what to show
name: CJK IDEOGRAPH-9332
general-category: Lo (Letter, Other)
Hiragana:
character: お (12362, #o30112, #x304a)
preferred charset: unicode (Unicode (ISO10646))
code point: 0x304A
syntax: w which means: word
category:
.:Base, H:2-byte Hiragana, c:Chinese, h:Korean, j:Japanese, |:line breakable
buffer code: #xE3 #x81 #x8A
file code: #xE3 #x81 #x8A (encoded by coding system utf-8-unix)
display: by this font (glyph code)
xft:-unknown-TakaoPMincho-normal-normal-normal-*-15-*-*-*-*-0-iso10646-1 (#x238B)
Character code properties: customize what to show
name: HIRAGANA LETTER O
general-category: Lo (Letter, Other)
Thanks for any input!
Daniel
next reply other threads:[~2011-07-04 4:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 4:09 Daniel Anderson [this message]
2011-07-04 14:54 ` Japanese fonts Peter Dyballa
-- strict thread matches above, loose matches on Subject: below --
2011-07-04 6:16 Daniel Anderson
2011-07-05 10:09 ` Ivan Kanis
2011-07-06 5:33 ` Daniel Anderson
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=87liwesn4q.fsf@gmail.com \
--to=dankles@gmail.com \
--cc=help-gnu-emacs@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.
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).