From: Kan-Ru Chen <kanru@kanru.info>
To: ding@gnus.org
Subject: Re: shr.el: folding Japanese text
Date: Fri, 15 Oct 2010 09:28:17 +0800 [thread overview]
Message-ID: <87zkugs0r2.fsf@anar.kanru.info> (raw)
In-Reply-To: <m3iq146159.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> Ok; I've now installed the jisx font, I think, but Emacs isn't using
>> it. Is there a way to query Emacs what font it's using for a particular
>> char so that I can remove that font?
>
> (internal-char-font (point)) seems to do the trick.
Or M-x describe-char
> On the following text:
>
> GnetooJP は11月6日に開催される関西オープンソース2010に参加します。
>
> The 開 kanji is:
>
> (#<font-object "-misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0"> . 9295)
>
> The 催 kanji is:
>
> (#<font-object "-isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0"> . 21570)
>
> So my buffers look like a complete mess.
>
> And I just can't find out where the "song ti" font comes from. I've
> tried removing all the half-likely font packages, but I haven't found
> the right one.
>
> Help?
The "song ti" font comes from xfonts-base package.
I use ttf-wqy-microhei (WenQuanYi Micro Hei), which is a font derived
form google Droid Sans font, covering large iso-10646 range. To set
font for specific character set you can use the fontset
mechanism. `(emacs) Fontsets'
However, since I'm not using fixed point font, the pixel size is not
strictly twice as ascii font.
next prev parent reply other threads:[~2010-10-15 1:28 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 8:10 Katsumi Yamaoka
2010-10-08 17:05 ` Lars Magne Ingebrigtsen
2010-10-08 17:23 ` Ted Zlatanov
2010-10-09 16:09 ` Lars Magne Ingebrigtsen
2010-10-09 21:35 ` Lars Magne Ingebrigtsen
2010-10-09 21:48 ` Lars Magne Ingebrigtsen
2010-10-10 4:57 ` CHENG Gao
2010-10-10 13:42 ` Andreas Schwab
2010-10-10 13:47 ` Lars Magne Ingebrigtsen
2010-10-10 16:22 ` Andreas Schwab
2010-10-11 4:03 ` James Cloos
2010-10-11 7:23 ` Kan-Ru Chen
2010-10-11 18:07 ` Lars Magne Ingebrigtsen
2010-10-12 8:19 ` Katsumi Yamaoka
2010-10-12 12:48 ` Lars Magne Ingebrigtsen
2010-10-12 14:13 ` Katsumi Yamaoka
2010-10-13 8:13 ` Katsumi Yamaoka
2010-10-13 16:53 ` Lars Magne Ingebrigtsen
2010-10-13 19:01 ` Lars Magne Ingebrigtsen
2010-10-14 8:16 ` Katsumi Yamaoka
2010-10-14 10:12 ` Katsumi Yamaoka
2010-10-14 14:13 ` Katsumi Yamaoka
2010-10-14 18:34 ` Lars Magne Ingebrigtsen
2010-10-14 19:10 ` Lars Magne Ingebrigtsen
2010-10-15 0:40 ` Katsumi Yamaoka
2010-10-15 7:35 ` Lars Magne Ingebrigtsen
2010-10-15 10:28 ` Lars Magne Ingebrigtsen
2010-10-15 10:48 ` Lars Magne Ingebrigtsen
2010-10-15 1:28 ` Kan-Ru Chen [this message]
2010-10-15 6:29 ` Reiner Steib
2010-10-15 18:05 ` Andreas Schwab
2010-10-15 20:16 ` Reiner Steib
2010-10-15 1:18 ` Katsumi Yamaoka
2010-10-14 19:05 ` Lars Magne Ingebrigtsen
2010-10-15 8:08 ` Katsumi Yamaoka
2010-10-15 14:02 ` Lars Magne Ingebrigtsen
2010-10-17 1:04 ` Lars Magne Ingebrigtsen
2010-10-18 5:19 ` Katsumi Yamaoka
2010-10-18 19:01 ` Lars Magne Ingebrigtsen
2010-10-18 5:19 ` Katsumi Yamaoka
2010-10-19 7:52 ` Katsumi Yamaoka
2010-10-19 18:12 ` Lars Magne Ingebrigtsen
2010-10-20 7:29 ` Katsumi Yamaoka
2010-10-20 17:22 ` Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zkugs0r2.fsf@anar.kanru.info \
--to=kanru@kanru.info \
--cc=ding@gnus.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 NNTP newsgroup(s).