Gnus development mailing list
 help / color / mirror / Atom feed
From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: unencoded characters again
Date: 19 Oct 1998 23:31:45 +0400	[thread overview]
Message-ID: <m3iuhgjqla.fsf@vvv.vsu.ru> (raw)

Hi,

i saw some article which contains the following headers:

Mime-Version: 1.0
Content-Type: text/plain;

i.e. there is a semicilon after text/plain, but there is no charset
specification (in fact, such article was created by broken
fidonet<->internet gateway, and charset was incorrectly translated;
such articles are not very rare).

This article was 8-bit koi8-r. I have mm-default-coding-system set to
'koi8, but gnus displays russian chars in this article unencoded
(\310\302\317...). Would it be possible to use mm-default-coding-system
if no charset is present in headers?

	Best regards, -- Vladimir.


             reply	other threads:[~1998-10-19 19:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-19 19:31 Vladimir Volovich [this message]
1998-10-24 17:45 ` Lars Magne Ingebrigtsen
1998-10-24 20:13   ` Vladimir Volovich

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=m3iuhgjqla.fsf@vvv.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).