From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: shr line breaking
Date: Tue, 07 Dec 2010 10:18:49 +0900 [thread overview]
Message-ID: <b4moc8ye5xi.fsf@jpl.org> (raw)
In-Reply-To: <m31v5v6uu9.fsf_-_@quimbies.gnus.org>
Lars Magne Ingebrigtsen wrote:
> Like the following line:
names like www.example.com into the numeric IP addresses like 192.0.2.1
> (shr-find-fill-point) will put point before the "1", which is wrong in
> this instance.
It happens with Japanese text, too. ;-)
www.example.com のような名前は次のような数字の IP アドレスに>192.0.2.1
I've fixed it so that it may not break a line after a kinsoku-bol
character (i.e., "." etc.) if a non-breakable character follows.
> Non-CJVK texts can only be broken where there's a space
> character, so perhaps we need additional logic to find out whether a
> (part of a) line is CJVK or not before trying to find the fill point?
> This may be difficult on mixed texts, perhaps...
Yes, I also think it's difficult to distinguish CJVK text and others,
especially in unicode Emacsen. For instance, even a latin-1 character
is regarded as Japanese:
(string-match "\\cj" "Ø") -> 0
In Emacs 22.3 and earlier, it was nil.
next prev parent reply other threads:[~2010-12-07 1:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1PNL64-0000my-00@quimby.gnus.org>
2010-11-30 14:44 ` [gnus git] branch master updated: =1= shr.el (shr-find-fill-point): Work better for kinsoku chars and apostrophes Lars Magne Ingebrigtsen
2010-11-30 23:27 ` Katsumi Yamaoka
2010-12-01 2:39 ` Katsumi Yamaoka
2010-12-01 6:45 ` Lars Magne Ingebrigtsen
2010-12-04 19:35 ` Lars Magne Ingebrigtsen
2010-12-04 21:03 ` Adam Sjøgren
2010-12-04 22:20 ` Lars Magne Ingebrigtsen
2010-12-04 23:27 ` Adam Sjøgren
2010-12-06 2:54 ` Katsumi Yamaoka
2010-12-06 10:47 ` shr line breaking (was: [gnus git] branch master updated: =1= shr.el (shr-find-fill-point): Work better for kinsoku chars and apostrophes.) Lars Magne Ingebrigtsen
2010-12-07 1:18 ` Katsumi Yamaoka [this message]
2010-12-16 17:41 ` shr line breaking 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=b4moc8ye5xi.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).