On Tue, 07 Jan 2014, Maurice Kinal wrote to Kees van Eeten:
MK> I can say the same about the lack of the '+' character in your MK> TZUTC kludge. Try sending that to date in the appropriate position MK> as is. I'm willing to bet it fails without the '+' character.
TZUTC is not meant to be fed to 'date'... but if that's what you want to do with it, then you need to ensure that you add the '+' if it is required ;)
MK> I'd suggest you ditch that kludge as it is most definetly broken MK> for half the world.
TZUTC works perfectly for all who use it...
MK> West of prime meridian is okay though since the '-' character is MK> there but given your location that isn't doable. Same with clocks MK> set to UTC such as mine. Real standards (not FTSC) call for it to MK> be expressed as +0000 which is why I decided it was best to turn MK> my TZUTC kludge off rather than argue the point with silly FTSC MK> people with blinders on.
when in rome, do as the romans do... fidonet has its own standards created and maintained for its own needs... if one is going to try to meld between two worlds, it is up to them to add/remove the little bits where necessary for their processing... the goal is to not violate the standards with one's emissions... if the fidonet standard for TZUTC doesn't allow the '+' then leave it out...
KvE> My default is probably some IBM font
MK> I doubt it.
it was LATIN-1 2 as easily seen in his CHRS line...
