Text 6659, 43 rader
Skriven 2013-02-19 21:32:03 av Michiel van der Vlist (2:280/5555)
     Kommentar till en text av Kees van Eeten (2:280/5003.4)
Ärende: LOL!
============
Hello Kees,

On Monday February 18 2013 19:34, you wrote to Sergey Dorofeev:

 KE>  The solution is not the problem, there are even more people who can
 KE> think of one, as there are that are able to solve them.

 KE>  The main problem is a flawless transition, that is not organised as a
 KE>  big BANG.

As ASCII is a subset of UTF-8, there is no transtion problem when moving from
ASCII to UTF-8. Anyone wanting to use pure ASCII only can continue to do so
forever.

 SD>> I can say only one thing: please use the same charset as in body
 SD>> (specified by CHRS) or use only ASCII letters. Anything other
 SD>> renders automatic message processing impossible.

 KE>  As others have recounted, the header should be in the default
 KE> characterset of the network.

That is not what FTS-0001 says...

 SD>> And, I want to add. There is TZUTC kludge that is used to
 SD>> correctly determine sender's local time. It goes after header
 SD>> (that contains considered datetime field), but are there any
 SD>> doubts that it should be applied to the field?

 KE>  I think that is up to what the software developer wants to present to
 KE>  the user. However I would not change anything in the original
 KE> message.

To sort the message by time, you need to read the TZUTC kludge.

Another error from the founding fathers. Time in the message header should have
been in UTC, instead of local time. To correct that error, we are saddled with
yet anoter kludge.


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
 * Origin: http://www.vlist.org (2:280/5555)