usefor-article-12 November 2003

[< Prev] [TOC] [ Next >]
4.4.1.  Character Sets within Article Headers

   The character set for headers is US-ASCII.  Where the use of non-
   ASCII characters is required, they MUST be encoded using the MIME
   mechanisms defined in [RFC 2047] and [RFC 2231].

   Examples:
      Organization: Technische =?iso-8859-1?Q?Universit=E4t_M=FCnchen?=
      Approved: =?iso-8859-1?Q?Fran=E7ois_Faur=E9?= <ff@modsite.example>
         (=?iso-8859-1?Q*fr?Mod=E9rateur_autoris=E9?=)
      Archive: yes; filename*=iso-8859-1'es'ma=F1ana.txt

        NOTE: The raw use of non-ASCII character sets or of encodings
        other than those described above is not compliant with this
        standard, even though such usage has been seen in some
        hierarchies (with no indication of which character set has been
        used beyond the user's ability to guess based upon other clues
        in the article, or custom within the newsgroup). Future
        extensions to this standard may make provision for other
        character sets, hence the requirement that octets beyond the
        US-ASCII range be transported without error.
[< Prev] [TOC] [ Next >]
#Diff to first older
NewerOlder
News Article Format and Transmission May 2004
News Article Format June 2003
News Article Format April 2003
News Article Format February 2003
News Article Format August 2002
News Article Format May 2002
News Article Format November 2001
News Article Format July 2001
News Article Format April 2001
News Article Format February 2000

--- ../usefor-article-11/Character_Sets_within_Article_Headers.out          June 2003
+++ ../usefor-article-12/Character_Sets_within_Article_Headers.out          November 2003
@@ -1,8 +1,8 @@
 4.4.1.  Character Sets within Article Headers
 
-   Where the use of non-ASCII characters is required, they MUST be
-   encoded using the MIME mechanisms defined in [RFC 2047] and [RFC
-   2231].
+   The character set for headers is US-ASCII.  Where the use of non-
+   ASCII characters is required, they MUST be encoded using the MIME
+   mechanisms defined in [RFC 2047] and [RFC 2231].
 
    Examples:
       Organization: Technische =?iso-8859-1?Q?Universit=E4t_M=FCnchen?=


Documents were processed to this format by Forrest J. Cavalier III