Gnus development mailing list
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.cygnus.argh.org>
Subject: Re: more multibyte bugs
Date: 05 May 2000 14:34:34 +0200	[thread overview]
Message-ID: <87itwtrx9h.fsf@deneb.cygnus.argh.org> (raw)
In-Reply-To: Vladimir Volovich's message of "05 May 2000 12:57:17 +0400"

Vladimir Volovich <vvv@vvv.vsu.ru> writes:

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

Yes, some Emacs MULE guru confirmed it in an earlier posting to this
list, I think.

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

If this can't be done (because making a buffer unibyte is some kind
of global thing), one could add a special coding system designed for
encoding raw bytes in the range 16#80# .. 16#FF#.



  reply	other threads:[~2000-05-05 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-05  8:57 Vladimir Volovich
2000-05-05 12:34 ` Florian Weimer [this message]
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=87itwtrx9h.fsf@deneb.cygnus.argh.org \
    --to=fw@deneb.cygnus.argh.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).