Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Kenichi Handa <handa@m17n.org>
Subject: Re: [BUG]What does this mean:"Mention that multibyte characters
Date: Wed, 27 Oct 2004 20:55:32 +0900	[thread overview]
Message-ID: <b9ylldse5or.fsf@jpl.org> (raw)
In-Reply-To: <b9yacuji7t6.fsf@jpl.org>

>>>>> In <b9yacuji7t6.fsf@jpl.org> Katsumi Yamaoka wrote:

>>>>>> In <m2pt3ryt2b.fsf@yahoo.com.cn>
>>>>>>	zrr <beijing_2008_gold@yahoo.com.cn> wrote:

>>    I pressed 'E' to expire the artile, but the article still be
>>    regarded as not expired.  There is no mark symbol appeared and no
>>    highlight on the current line.

> I've fixed it in both the Gnus trunk and the v5-10 branch.  It
> will help not only Emacs 22 users but also Russian users,
> Ukrainian users and much more.

Kenichi Handa suggested there is potentially another problem.
It existed, even before I modified gnus-sum.el.

In order to know column positions of summary lines where marks
should be inserted, Gnus makes a dummy summary line.  There four
characters which correspond to the data \200, \201, \202 and
\203 are used as dummy marks, and Gnus look for them.  See the
gnus-update-summary-mark-positions function:

    (let ((gnus-replied-mark 129)
	  (gnus-score-below-mark 130)
	  (gnus-score-over-mark 130)
	  (gnus-undownloaded-mark 131)

Although those characters will never be printable in the Latin-1
language environment and so forth, they might be usually being
used in the Russian language environment, for example.  So, it
is possible that gnus-summary-line-format contains them and
gnus-user-format-function-* may return them.  In those cases,
Gnus will recognize incorrect mark positions.  You can try it
using the following way:

(set-language-environment 'Russian)
(setq gnus-summary-line-format
      (concat (string-make-multibyte "\200\201\202\203")
	      "%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n")
(gnus-update-format-specifications t 'summary)

He hinted using \0, \1, etc. instead.  However, I'm not sure of
whether they don't bring about damage.  For the moment, I'm
planning to replace \200, \201, etc. to just space, if
gnus-summary-line-format contains them or
gnus-user-format-function-* returns them.

Is it unnecessary worries? ;-)



  parent reply	other threads:[~2004-10-27 11:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 15:51 [BUG]What does this mean:"Mention that multibyte characters don't work as marks."? zrr
2004-10-14 17:24 ` [BUG]What does this mean:"Mention that multibyte characters Reiner Steib
2004-10-14 18:33   ` zrr
2004-10-14 17:44 ` [BUG]What does this mean:"Mention that multibyte characters don't work as marks."? Xavier Maillard
2004-10-14 18:41   ` [BUG]What does this mean:"Mention that multibyte characters zrr
2004-10-14 21:33     ` Xavier Maillard
2004-10-15  5:43       ` Katsumi Yamaoka
2004-10-15 14:12         ` Katsumi Yamaoka
2004-10-15 14:45           ` zrr
2004-10-15 14:51           ` Reiner Steib
2004-10-15 18:49             ` Derek
2004-10-17 23:18               ` Katsumi Yamaoka
2004-10-19  5:41                 ` Katsumi Yamaoka
2004-10-19  8:41                   ` zrr
2004-10-20  5:36                   ` Katsumi Yamaoka
2004-10-27 11:55                   ` Katsumi Yamaoka [this message]
2004-10-27 23:56                     ` Katsumi Yamaoka
2004-10-15 16:19           ` Juri Linkov

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=b9ylldse5or.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=handa@m17n.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).