From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/61168 Path: news.gmane.org!not-for-mail From: =?iso-8859-1?Q?Bj=F8rn_Mork?= Newsgroups: gmane.emacs.gnus.general Subject: Re: Display unknown non-ASCII chars as `.', `X' or `?' Date: Fri, 14 Oct 2005 08:38:11 +0200 Organization: Day of Dual Message-ID: <87d5m8eh7w.fsf@obelix.mork.no> References: <877jcjp3ob.fsf@obelix.mork.no> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1129272484 24860 80.91.229.2 (14 Oct 2005 06:48:04 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 14 Oct 2005 06:48:04 +0000 (UTC) Original-X-From: ding-owner+m9701@lists.math.uh.edu Fri Oct 14 08:48:02 2005 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EQJKW-0002Gu-48 for ding-account@gmane.org; Fri, 14 Oct 2005 08:46:12 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1EQJKN-0000gu-00; Fri, 14 Oct 2005 01:46:03 -0500 Original-Received: from nas02.math.uh.edu ([129.7.128.40]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1EQJF9-0000go-00 for ding@lists.math.uh.edu; Fri, 14 Oct 2005 01:40:39 -0500 Original-Received: from quimby.gnus.org ([80.91.224.244]) by nas02.math.uh.edu with esmtp (Exim 4.52) id 1EQJF2-00015r-U2 for ding@lists.math.uh.edu; Fri, 14 Oct 2005 01:40:39 -0500 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1EQJF1-0000zt-00 for ; Fri, 14 Oct 2005 08:40:31 +0200 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EQJDE-00082p-TT for ding@gnus.org; Fri, 14 Oct 2005 08:38:40 +0200 Original-Received: from obelix.mork.no ([148.122.252.2]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 14 Oct 2005 08:38:40 +0200 Original-Received: from bmork by obelix.mork.no with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 14 Oct 2005 08:38:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: ding@gnus.org Original-Lines: 82 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: obelix.mork.no User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux) Cancel-Lock: sha1:TINaAooBG1oxJgRJ4/W1lg8kvQU= X-Spam-Score: -2.6 (--) Precedence: bulk Original-Sender: ding-owner@lists.math.uh.edu Xref: news.gmane.org gmane.emacs.gnus.general:61168 Archived-At: Reiner Steib writes: > On Wed, Oct 12 2005, Bjørn Mork wrote: >> Reiner Steib 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. Sorry, my fault. I didn't quote enough to make it understandable. The part above comes from 2. MIME Conformance [..] A mail user agent that is MIME-conformant MUST: [..] (6) Explicitly handle the following media type values, to at least the following extents: Text: [..] -- Treat material in an unknown character set as if it were "application/octet-stream". > 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. That's not true. RFC2049 says (8) Conformant user agents are required, if they provide non-standard support for non-MIME messages employing character sets other than US-ASCII, to do so on received messages only. Conforming user agents must not send non-MIME messages containing anything other than US-ASCII text. In particular, the use of non-US-ASCII text in mail messages without a MIME-Version field is strongly discouraged as it impedes interoperability when sending messages between regions with different localization conventions. Conforming user agents MUST include proper MIME labelling when sending anything other than plain text in the US-ASCII character set. In addition, non-MIME user agents should be upgraded if at all possible to include appropriate MIME header information in the messages they send even if nothing else in MIME is supported. This upgrade will have little, if any, effect on non-MIME recipients and will aid MIME in correctly displaying such messages. It also provides a smooth transition path to eventual adoption of other MIME capabilities. > 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. I should have known: That's the proper Gnus way to do things. I guess that makes the proposal OK. Bjørn -- I'll bet you think that random frobs are disgusting.