KvE> We are talking about software that was developed, when code pages KvE> were the norm and UTF-8 only on the horizon.
Hm. If certain 'historians' bothered to do some fact checking they might have been aware that utf-8 has been around since 1992. However I think there might have been a few changes since back then and I also believe usage was somewhat limited back then. Speaking for myself I only started using it a couple years ago but was aware of it as well as the fact that it is a variable byte encoding where things like what I believe the limit parameter was meant to address will fail since it isn't a fixed byte encoding such as utf-16 for example. That is why I state, and will continue to state, the CHRS kludge for utf-8 is in error. It cannot be cheated that way which makes it perfect imho.
KvE> I am not shure that I can disable the use of the timezone kludge
It would have made a great fix for the obsoleted datetime stamp in MSG headers if it actually followed real world standards for utc offsets. The '+' character is a must for real world apps where applicable even for clocks set to utc (ie +0000 and NOT just 0000). Since I have a choice I decided to turn mine off rather than send a bogus one. My times are really utc by the way just in case you're curious. The clock on the wall here is set to Pacific Standard Time which for the record would be -0800 for it's TZUTC if indeed my computers were set to PST which they aren't. They are set to UTC which is proper networking etiquette and has been since long before Fidonet and in that case the proper and correct offset is +0000.
It is just that simple and all the arguing in the world will not alter it's correctness, with or without kludges.
Life is good, Maurice
--- GNU bash, version 4.2.45(2)-release (x86_64-unknown-linux-gnu) * Origin: Pointy Stick Society - Ladysmith BC, Canada (1:153/7001.0)
