Gnus development mailing list
 help / color / mirror / Atom feed
From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: more multibyte bugs
Date: 05 May 2000 12:57:17 +0400	[thread overview]
Message-ID: <eyog6ll6he.fsf@video.uic.vsu.ru> (raw)

Hi Shenghuo,

with current cvs i'm able to send messages in koi8-r with CTE=8bit.
Thanks for good work! BTW, i wonder why sending via smtp worked fine
in prev. versions, and was broken in some recent one (and was fixed
without touching smtp sending code?).

With the current cvs version, there is one more bug that i just
noticed: open any message with 8-bit CTE, press TWICE C-u g, and then
get it again.  I.e. press

g
C-u g
C-u g
g

Then 8-bit text will be broken. Those multibyte problems are really
bad and tricky. :-)

BTW, as you agreed to use unibyte encoding for mbox, but you think
that it could be a disuster, i suggest to create a cvs "multibyte
cleanup branch" in which you could try to Do The Right Thing (TM);
i'll be happy to debug this branch and report problems. When
everything works fine, we could merge it into the main branch.

Am i right that mule will _by design_ interpret combinations of 8-bit
octets which form multibyte characters as multibyte characters in a
multibyte buffer regardless of the coding system settings?

In this case, it seems that ALL gnus buffers which are supposed to
contain arbitrary 8-bit text must be unibyte.

Best,
v.




             reply	other threads:[~2000-05-05  8:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-05  8:57 Vladimir Volovich [this message]
2000-05-05 12:34 ` Florian Weimer
2000-05-05 18:32   ` Vladimir Volovich
2000-05-06  7:10     ` Florian Weimer
2000-05-05 15:23 ` Shenghuo ZHU

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=eyog6ll6he.fsf@video.uic.vsu.ru \
    --to=vvv@vvv.vsu.ru \
    /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).