Christoph M. Becker
8/26/2014 11:25:00 AM
Evertjan. wrote:
> "Christoph M. Becker" <cmbecker69@arcor.de> wrote on 26 aug 2014 in
> comp.lang.javascript:
>
>> schrieb Evertjan. wrote:
>>
>>> =?UTF-8?B?5ZCz5pme5rWp?= <shwu.cs98@gmail.com> wrote on 26 aug 2014 in
>>> comp.lang.javascript:
>>>
>>> Could you please ad a signature or at least a nickname,
>>> discussing with a nobody who seems to be named
>>> =?UTF-8?B?5ZCz5pme5rWp?= is rather combersome
>>> and we would, be it slowly, come to know
>>> whether you are a strong or weak type of programmer.
>>
>> It seems your newsreader can't properly handle encoded-words[1]. The OP
>> has posted as å³æÂ?Â?浩 <shwu.cs98@gmail.com>, which is perfectly fine.
>
> I don't think ³æ��浩 is perfectly fine, usenet stipulates using ASCII for
> addresslines, so much for your "properly".
It seems you are referring to RFC 1036 section 2.1.1. However, RFC 1036
is obsoleted by RFC 5536 and 5537, and RFC 5536 section 3.1.2 specifies:
| The From header field is the same as that specified in Section 3.6.2
| of [RFC5322], with the added restrictions detailed above in
| Section 2.2.
I have not been able to find any restriction on ASCII characters,
besides that non ASCII characters have to be encoded, what they have
been in the OP.
However, if you post to Usenet, you should be aware that the default
Content-Type is
Content-type: text/plain; charset=us-ascii
So if you are using non ASCII characters, you should configure your
newsreader to add an appropriate Content-Type header field.
> However, dear Christoph, even having a fine addressline, quod non, does not
> in the least diminish the value of my request for a signature or at least a
> nickname.
Well, the name has been already given in the "addressline"--there is no
*need* to duplicate it.
--
Christoph M. Becker