Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Juri Linkov <juri@jurta.org>
Subject: Re: [BUG]What does this mean:"Mention that multibyte characters
Date: Tue, 19 Oct 2004 14:41:09 +0900	[thread overview]
Message-ID: <b9yacuji7t6.fsf@jpl.org> (raw)
In-Reply-To: <b9yd5zhrl1u.fsf@jpl.org>

>>>>> 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.

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

> I'll fix it within a couple of days and, if possible,...

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.

There are two ways that gnus-update-summary-mark-positions
inserts a dummy mark in a multibyte buffer.  Which of them is
used depends on the value of gnus-summary-line-format.

(insert ?\200)
(insert (format "%c" ?\200))

In order to look for the position of a line where it is inserted,
the recent gnus-update-summary-mark-positions searched for the
string:

(mm-string-as-multibyte "\200")

I noticed those three strings will differ by the language
environment and the version of Emacs.  The following form shows
how they are different.

(with-temp-buffer
  (set-buffer-multibyte t)
  (insert ?\200
	  (format "%c" ?\200))
  (list
   (car (split-char (char-after (point-min))))
   (car (split-char (char-after (1+ (point-min)))))
   (car (split-char (string-to-char (string-as-multibyte "\200"))))))

In the Russian language environment, it returns as follows:

;; Emacs 21.3.50
(eight-bit-control mule-unicode-2500-33ff eight-bit-control)
;; Emacs 22.0.0
(iso-8859-1 iso-8859-1 eight-bit)

Even in the English language environment, Emacs 22.0.0 returns:

(iso-8859-1 iso-8859-1 eight-bit)

Those are the cause of the problem which troubled Tang and Derek.

> I'll also summarize how string-(as|make|to)-multibyte works.

I'll try translation of Kenichi Handa's advice next time.

By the way, I'm not sure whether Juri Linkov's similar changes
for the other places don't cause similar problems.



  reply	other threads:[~2004-10-19  5:41 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 [this message]
2004-10-19  8:41                   ` zrr
2004-10-20  5:36                   ` Katsumi Yamaoka
2004-10-27 11:55                   ` Katsumi Yamaoka
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=b9yacuji7t6.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=juri@jurta.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).