From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/26121 Path: main.gmane.org!not-for-mail From: Hrvoje Niksic Newsgroups: gmane.emacs.gnus.general Subject: Re: charset="Windows-1252" Date: 02 Nov 1999 12:14:27 +0100 Sender: owner-ding@hpc.uh.edu Message-ID: <9t9puxtb0x8.fsf@mraz.iskon.hr> References: <9t9u2n5b4o7.fsf@mraz.iskon.hr> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035163388 17711 80.91.224.250 (21 Oct 2002 01:23:08 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 01:23:08 +0000 (UTC) Return-Path: Original-Received: from lisa.math.uh.edu (lisa.math.uh.edu [129.7.128.49]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id GAA10400 for ; Tue, 2 Nov 1999 06:15:25 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by lisa.math.uh.edu (8.9.1/8.9.1) with ESMTP id FAB15755; Tue, 2 Nov 1999 05:15:23 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Tue, 02 Nov 1999 05:15:24 -0600 (CST) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id FAA00079 for ; Tue, 2 Nov 1999 05:15:13 -0600 (CST) Original-Received: from mraz.iskon.hr (mail@mraz.iskon.hr [195.29.170.8]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id GAA10384 for ; Tue, 2 Nov 1999 06:14:36 -0500 (EST) Original-Received: from hniksic by mraz.iskon.hr with local (Exim 3.03 #1 (Debian)) id 11ibtT-0008DJ-00 for ; Tue, 02 Nov 1999 12:14:27 +0100 Original-To: ding@gnus.org X-Attribution: Hrvoje X-Face: &{dT~)Pu6V<0y?>3p$;@vh\`C7xB~A0T-J%Og)J,@-1%q6Q+, gs<-9M#&`I8cJp2b1{vPE|~+JE+gx;a7%BG{}nY^ehK1"q#rG O,Rn1A_Cy%t]V=Brv7h writes: > >>>>> Hrvoje Niksic : > > > Steinar Bang writes: > >> That would be the correct solution. AFAIK "Windows-1252" isn't a > >> legal charset parameter to text/plain. > > > Why not? > > Because of this statement from section 4.1.2 (not 4.1.1 as I said > earlier. Sorry!) of RFC2046. at the bottom of page 9: > > The defined charset values are: > > (1) US-ASCII -- as defined in ANSI X3.4-1986 [US-ASCII]. > > (2) ISO-8859-X -- where "X" is to be replaced, as > necessary, for the parts of ISO-8859 [ISO-8859]. Note > that the ISO 646 character sets have deliberately been > omitted in favor of their 8859 replacements, which are > the designated character sets for Internet mail. As of > the publication of this document, the legitimate values > for "X" are the digits 1 through 10. You missed the rest. The character sets specified above are the ones that were relatively uncontroversial during the drafting of MIME. This document does not endorse the use of any particular character set other than US-ASCII, and recognizes that the future evolution of world character sets remains unclear. Note that the character set used, if anything other than US- ASCII, must always be explicitly specified in the Content-Type field. No character set name other than those defined above may be used in Internet mail without the publication of a formal specification and its registration with IANA, or by private agreement, in which case the character set name must begin with "X-". The Windows things are registered.