diff options
| author | Tassilo Horn <tsdh@gnu.org> | 2021-08-26 12:51:08 +0200 |
|---|---|---|
| committer | Tassilo Horn <tsdh@gnu.org> | 2021-08-26 12:51:08 +0200 |
| commit | fbf2933e6907c1344c0b543c3f05cb3cfcc0ebc3 (patch) | |
| tree | b9b3937844b45e5877fb1a1419c34026b5f8a282 | |
| parent | d54ffa25bd297f9bc57918ca65db714beade7473 (diff) | |
| download | emacs-fbf2933e6907c1344c0b543c3f05cb3cfcc0ebc3.tar.gz emacs-fbf2933e6907c1344c0b543c3f05cb3cfcc0ebc3.tar.bz2 emacs-fbf2933e6907c1344c0b543c3f05cb3cfcc0ebc3.zip | |
Fix docs about the meaning of the Re: in the subject
* doc/misc/message.texi (Message Headers): Clarify that it comes from
the Latin "res" meaning "in the matter of" rather than "in response
to" as claimed previously (see RFC-2822).
| -rw-r--r-- | doc/misc/message.texi | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/doc/misc/message.texi b/doc/misc/message.texi index c0e3dfae12d..4136ad859f7 100644 --- a/doc/misc/message.texi +++ b/doc/misc/message.texi @@ -1699,14 +1699,15 @@ result is inserted. @cindex Sv @cindex Re Responses to messages have subjects that start with @samp{Re: }. This -is @emph{not} an abbreviation of the English word ``response'', but is -Latin, and means ``in response to''. Some illiterate nincompoops have -failed to grasp this fact, and have ``internationalized'' their software -to use abominations like @samp{Aw: } (``antwort'') or @samp{Sv: } -(``svar'') instead, which is meaningless and evil. However, you may -have to deal with users that use these evil tools, in which case you may -set this variable to a regexp that matches these prefixes. Myself, I -just throw away non-compliant mail. +is @emph{not} an abbreviation of the English word ``response'', but it +comes from the Latin ``res'', and means ``in the matter of''. Some +illiterate nincompoops have failed to grasp this fact, and have +``internationalized'' their software to use abominations like +@samp{Aw: } (``antwort'') or @samp{Sv: } (``svar'') instead, which is +meaningless and evil. However, you may have to deal with users that +use these evil tools, in which case you may set this variable to a +regexp that matches these prefixes. Myself, I just throw away +non-compliant mail. Here's an example of a value to deal with these headers when responding to a message: |