Re: [OT] Funny Sig

On Sun, 07 Aug 2005 11:50:24 +0200, Patrick Lamaizière wrote:

> Robert Spanjaard écrivait :
>
>>>> 1036 doesn't even contain the strings "us-ascii" or "english".
>>>
>>> It is implicit.
>>
>> Then show me the pieceof text you got it from.
>
> RFC 822
> «
> 3.1. GENERAL DESCRIPTION
>
> A message consists of header fields and, optionally, a body.
> The body is simply a sequence of lines containing ASCII charac-
> ters. It is separated from the headers by a null line (i.e., a
> line with nothing preceding the CRLF).
> »
>
> ASCII characters.

Already answered:

>>>> 822 was obsoleted in 2001 by 2822, which clearly mentiones the
>>>> MIME-RFCs 2045-2049. None of them state that only us-ascii should be
>>>> used in english groups.

---8<------8<------8<------8<------8<------8<------8<------8<------8<---
2.3. Body

The body of a message is simply lines of US-ASCII characters. The
only two limitations on the body are as follows:

- CR and LF MUST only occur together as CRLF; they MUST NOT appear
independently in the body.

- Lines of characters in the body MUST be limited to 998 characters,
and SHOULD be limited to 78 characters, excluding the CRLF.

Note: As was stated earlier, there are other standards documents,
specifically the MIME documents [RFC2045, RFC2046, RFC2048, RFC2049]
that extend this standard to allow for different sorts of message
bodies. Again, these mechanisms are beyond the scope of this
document.
---8<------8<------8<------8<------8<------8<------8<------8<------8<---

Still, nothing about english groups.

>>> This is for mail not for usenet articles.
>>
>> No, it's for mail _and_ usenet articles.
>
> No, if it is for mail and usenet articles i don't think Usefor would
> spend some time on drafts about the format of usenet articles ...

RFC 1036 --8<------8<------8<------8<------8<------8<------8<------8<---
2. Message Format

The primary consideration in choosing a message format is that it
fit in with existing tools as well as possible. Existing tools
include implementations of both mail and news. (The notesfiles
system from the University of Illinois is considered a news
implementation.) A standard format for mail messages has existed
for many years on the Internet, and this format meets most of the
needs of USENET. Since the Internet format is extensible,
extensions to meet the additional needs of USENET are easily made
within the Internet standard. Therefore, the rule is adopted that
all USENET news messages must be formatted as valid Internet mail
messages, according to the Internet standard RFC-822. The USENET
News standard is more restrictive than the Internet standard,
---8<------8<------8<------8<------8<------8<------8<------8<------8<---

RFC 2822 --8<------8<------8<------8<------8<------8<------8<------8<---
Abstract

This standard specifies a syntax for text messages that are sent
between computer users, within the framework of "electronic mail"
messages. This standard supersedes the one specified in Request For
Comments (RFC) 822, "Standard for the Format of ARPA Internet Text
Messages", updating it to reflect current practice and incorporating
incremental changes that were specified in other RFCs.
---8<------8<------8<------8<------8<------8<------8<------8<------8<---

>
> There was several drafts from Usefor. Previous drafts used UTF-8 as
> default character sets in headers (This is not allowed by the RFC
> 822/2822)
>
> See the old draft :

Now you start using _old_ drafts? Great.

> <EOT>

Al least we agree on one point.

--
Regards, Robert http://www.arumes.com

All the power of an MS-compatible office suite without the high price tag:
http://www.openoffice.org
.

Relevant Pages

  • Re: Village idiot
    ... network News messages among USENET hosts. ... It does not specify an Internet standard. ... Please note that it states "It does not specify an Internet standard." ... Interchange of USENET Messages" - very confusing but your point is well ...
    (rec.woodworking)
  • Re: Village idiot
    ... network News messages among USENET hosts. ... It does not specify an Internet standard. ... Please note that it states "It does not specify an Internet standard." ... Interchange of USENET Messages" - very confusing but your point is well ...
    (rec.woodworking)
  • Re: ES format
    ... >> runtime format, even a runtime format that is trivially constant, not. ... You aren't allowed by Standard C to define any _external_ linkage ... In particular you certainly can define a 'static' function printf(), ... but otherwise it is part of the language and the compiler ...
    (comp.lang.fortran)
  • Re: VISTA
    ... One of the most powerful aspects of open source software is that you cannot make a change like the one you are suggesting - if Sun tried to change to a new closed format, the project would be quickly forked and backing companies, developers, and users would switch to the fork. ... A slightly incompatible version of this format was fast-tracked by ECMA through ISO. ... Although Open Office now supports importing these files, the standard format for Open Office is still the single *real* standard format, namely Open Document Format. ... OASIS is an independent standards group with a solid reputation, thus keeping ODF separate from any one implementation and ensuring it can be freely used by anyone. ...
    (comp.arch.embedded)
  • Re: cobol data format!!! urgent!!!
    ... misunderstood what "conformance to a standard" means. ... Cobol people 'know' binary floating-point is ... The quotation above is from IEEE 754. ... same as the IBM System/390 format which isn't the same as the Unisys MCP ...
    (comp.lang.cobol)
Loading