From: Kan-Ru Chen <kanru@kanru.info>
To: ding@gnus.org
Subject: Re: shr.el: folding Japanese text
Date: Mon, 11 Oct 2010 15:23:48 +0800 [thread overview]
Message-ID: <87eibxkxa3.fsf@anar.kanru.info> (raw)
In-Reply-To: <m31v7z59sw.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I tried yanking some text from an article in
> gwene.cn.com.sina.blog.hanhan (Chinese text, I guess) into a .txt
> buffer, and then just `M-q'-ing it. It didn't look very nice. It
> looked as if thought the characters were much narrower than they really
> were, because it filled the lines way too late. Like this:
>
> 最近一个月没有更新,是因为不知道说什么好,我本人也正在赶新的小说,会在9月
> 出版,前几天去香港书展,长望着维港,更觉得应该有好的作品奉献给大家,虽然
> 他人无德无能,但我又何德何能,我深感忧虑,何以解愁,唯有作品。
>
> (I hope that's not a naughty text and I'll end up in jail now for
> threatening terroristey behaviour...)
The text displayed totally OK with the terminal emulator, because
historically the ideographics are `double-width'. If you use a monospace
CJK font which is exactly twice wide of the latin font, you will find
the text is wrapped around 73th column as well.
(The text itself is OK, too ;-)
> In my Emacs, that text is displayed at least five characters too wide
> before the lines were folded. But that probably depends on what font
> you use.
>
> Doesn't Emacs have any way to say "how many pixels have I left now"?
That would be better than counting characters. But consider that we can
use both GUI and terminal interfaces at the same time (multi-tty),
counting pixels seems bogus, too.
Kanru
--
Q: Why are my replies five sentences or less?
A: http://five.sentenc.es/
next prev parent reply other threads:[~2010-10-11 7:23 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 [this message]
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
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=87eibxkxa3.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).