Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: [gnus git] branch master updated: =1= shr.el (shr-find-fill-point): Work better for kinsoku chars and apostrophes.
Date: Wed, 01 Dec 2010 11:39:50 +0900	[thread overview]
Message-ID: <b4meia2b4i1.fsf@jpl.org> (raw)
In-Reply-To: <b4m62ves87g.fsf@jpl.org>

Katsumi Yamaoka wrote:
> Hm, try as I might, I couldn't reproduce it.
[...]
> Is it due to a locale?

Not really.  Though the string width of "’" is 1 in an English
locale whereas it is 2 in a Japanese locale[1], it is not a root
cause of why I couldn't reproduce the problem.  I've modified it
so as not to break a line between kinsoku-bol characters, i.e.
"." and ")".

[1]
(let ((c ?’)
      (lang current-language-environment)
      e j)
  (set-language-environment "English")
  (setq e (list (char-width c) (split-char c)))
  (set-language-environment "Japanese")
  (setq j (list (char-width c) (split-char c)))
  (set-language-environment lang)
  (list e j))
 => ((1 (unicode 0 32 25)) (2 (japanese-jisx0208 33 71)))



  reply	other threads:[~2010-12-01  2:39 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 ` Lars Magne Ingebrigtsen
2010-11-30 23:27   ` Katsumi Yamaoka
2010-12-01  2:39     ` Katsumi Yamaoka [this message]
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               ` shr line breaking Katsumi Yamaoka
2010-12-16 17:41                 ` 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=b4meia2b4i1.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).