From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Display unknown non-ASCII chars as `.', `X' or `?'
Date: Thu, 13 Oct 2005 22:39:37 +0200 [thread overview]
Message-ID: <v9d5m9taly.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <877jcjp3ob.fsf@obelix.mork.no>
On Wed, Oct 12 2005, Bjørn Mork wrote:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
[...]
>> While at it...
>> | If so, why does it not replace everything by dots, X or ?.
>>
>> I.e. if the charset is not available: How can we configure Gnus to
>> display every non-ASCII chars as `.', `X' or `?'?
>
> This is a violation of RFC2049, which gives the following criteria for
> a MIME-conformant MUA:
>
> -- Treat material in an unknown character set as if it were
> "application/octet-stream".
I fail to see the connection (Disclaimer: I didn't read this RFC).
"application/octet-stream" is a content type, whereas I was talking
about the charset.
BTW: Yesterday, in the German newsgroup de.comm.software.newsreader a
thread titled "Zeichensatz erraten"[1] started about this topic. Some
people claim that the receiver _must_ assume `us-ascii' when MIME
headers are absent.
In case it wasn't clear: I don't want to change Gnus default behavior.
But maybe it makes sense to replace unknown chars by `?' for some
users so it should be possible to do this with Gnus.
Bye, Reiner.
[1] http://www.google.de/groups?as_umsgid=9fk6Itd7fjB%40helmut.hullen.de&hl=en
http://groups.google.de/group/de.comm.software.newsreader/browse_frm/thread/7c7ed4e3c7e63560/cede6121a1685dda#cede6121a1685dda
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2005-10-13 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 21:52 Setup additional charsets on demand Reiner Steib
2005-10-11 22:19 ` Display unknown non-ASCII chars as `.', `X' or `?' (was: Setup additional charsets on demand) Reiner Steib
2005-10-12 7:58 ` Display unknown non-ASCII chars as `.', `X' or `?' Bjørn Mork
2005-10-13 20:39 ` Reiner Steib [this message]
2005-10-14 6:38 ` Bjørn Mork
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=v9d5m9taly.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).