Gnus development mailing list
 help / color / mirror / Atom feed
From: jsbien@mimuw.edu.pl (Janusz S. Bien)
Cc: Shenghuo ZHU <zsh@cs.rochester.edu>, Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: Re: should mbox be opened in unibyte mode
Date: 5 May 2000 05:42:15 -0000	[thread overview]
Message-ID: <20000505054215.7031.qmail@duch.mimuw.edu.pl> (raw)

Shenghuo ZHU <zsh@cs.rochester.edu> writes:

>>>>>> "VV" == Vladimir Volovich <vvv@vvv.vsu.ru> writes:
[...]
VV> i thought a bit on this, and it seems that mbox MUST be opened in
VV> unibyte mode, otherwise the results will be broken.
[...]
>
>I think unibyte mode does not really matter how mbox is opened, but
>the coding-system does. Have you tried
>
>(setq nnmbox-file-coding-system 'binary)
>(setq nnmbox-active-file-coding-system 'binary)
>

You both are right.

`binary' is just an alias for `no-conversion'. Here's what the manual
says about it:

   In contrast, the coding system `no-conversion' specifies no
character code conversion at all--none for non-ASCII byte values and
none for end of line.  This is useful for reading or writing binary
files, tar files, and other files that must be examined verbatim.  It,
too, sets `enable-multibyte-characters' to `nil'.
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

>It might solve the problem.

I think it should.

Best regards

Janusz

---------------------------------------------------------------------
                     ,   
dr hab. Janusz S. Bien, prof. UW
Prof. Janusz S. Bien, Warsaw Uniwersity
---------------------------------------------------------------------
---------------------------------------------------------------------
Na tym koncie czytam i wysylam poczte i wiadomosci offline -
prosze nie oczekiwac szybkiej odpowiedzi!
Data w naglowku to data rozpoczecia pisania listu, a nie jego wyslania.
---------------------------------------------------------------------
On this account I read/post mail/news offline - do not expect 
an immediate answer!
The date in the header refers to the moment when I started to write
the letter, not to the moment when I sent it.
---------------------------------------------------------------------



             reply	other threads:[~2000-05-05  5:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-05  5:42 Janusz S. Bien [this message]
2000-05-05 15:31 ` Stainless Steel Rat
2000-05-05 16:38   ` Hrvoje Niksic
2000-05-05 17:00     ` Shenghuo ZHU
2000-05-05 17:15       ` Hrvoje Niksic
2000-05-05 17:46         ` Kai Großjohann
2000-05-06 18:55           ` Hrvoje Niksic
2000-05-06  0:50     ` Stainless Steel Rat
2000-05-21  8:31 ` Vladimir Volovich
  -- strict thread matches above, loose matches on Subject: below --
2000-05-23  5:26 Janusz S. Bien
2000-05-22  6:06 Janusz S. Bien
2000-05-22 19:47 ` Vladimir Volovich
2000-05-21 14:08 Janusz S. Bien
2000-05-21 16:15 ` Vladimir Volovich
2000-05-05 21:50 Janusz S. Bien
2000-05-04 11:04 Vladimir Volovich
2000-05-04 14:39 ` Shenghuo ZHU
2000-05-04 20:27   ` Vladimir Volovich
2000-05-04 21:33     ` Shenghuo ZHU
2000-05-05  5:05     ` 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=20000505054215.7031.qmail@duch.mimuw.edu.pl \
    --to=jsbien@mimuw.edu.pl \
    --cc=vvv@vvv.vsu.ru \
    --cc=zsh@cs.rochester.edu \
    /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).