Discussion:
reuh deux points
(trop ancien pour répondre)
Olivier B.
2017-03-18 14:58:09 UTC
Permalink
Raw Message
On Sat, 18 Mar 2017 14:33:00 +0100, Stephane Legras-Decussy
salut,
petite interrogation de ma part, le préfixage du sujet par "re:"
est-il normalisé sur usenet ?
merci
A+
--
pas de .turlututu. avant l'@robase
joie
2017-03-18 15:24:11 UTC
Permalink
Raw Message
Post by Olivier B.
On Sat, 18 Mar 2017 14:33:00 +0100, Stephane Legras-Decussy
salut,
petite interrogation de ma part, le préfixage du sujet par "re:"
est-il normalisé sur usenet ?
merci
A+
Ah ! reuh ! ? ce n'est qu'un retour à l'enfance !
--
Plus rien à faire
Plus rien à foutre
Julien ÉLIE
2017-03-18 15:29:39 UTC
Permalink
Raw Message
Bonjour Olivier,
Post by Olivier B.
petite interrogation de ma part, le préfixage du sujet par "re:"
est-il normalisé sur usenet ?
RFC 1849 (Son-of-1036) :

https://tools.ietf.org/html/rfc1849

5.4. Subject

The Subject header's content (the "subject" of the article) is a
short phrase describing the topic of the article:

Subject-content = [ "Re: " ] nonblank-text

Encoded words MAY appear in this header.

If the article is a followup, the subject SHOULD begin with "Re: " (a
"back reference"). If the article is not a followup, the subject
MUST NOT begin with a back reference. Back references are case-
insensitive, although "Re: " is the preferred form. A followup agent
assisting a poster in preparing a followup SHOULD prepend a back
reference, UNLESS the subject already begins with one. If the poster
determines that the topic of the followup differs significantly from
what is described in the subject, a new, more descriptive subject
SHOULD be substituted (with no back reference). An article whose
subject begins with a back reference MUST have a References header
referencing the precursor.

NOTE: A back reference is FOUR characters, the fourth being a
blank. [RFC1036] was confused about this. Observe also that only
ONE back reference should be present.

NOTE: There is a semi-standard convention, often used, in which a
subject change is flagged by making the new Subject-content of the
form:

new topic (was: old topic)

possibly with "old topic" somewhat truncated. Posters wishing to
do something like this are urged to use this exact form, to
simplify automated analysis.



Cette notion est toujours présente dans USEAGE, qui n'est
malheureusement pas arrivé au stade de RFC :

https://tools.ietf.org/html/draft-ietf-usefor-useage-01
--
Julien ÉLIE

« La femme ne voit jamais ce que l'on fait pour elle ; elle ne voit
que ce que l'on ne fait pas. » (Georges Courteline)
Loading...