You know ... as long as we're on this subject. I see that there is no longer any difference between the %(tws) and %(pretty) escape, since David Levine removed the backend code that differentiated this in commit 0c926c599d9def7f70. Because it didn't work (it would return the local timezone symbolic name always, rather than the timezone of the specified date). So that makes me wonder if we should still try to bother to generate a symbolic timezone name. It looks like the only portable way to do this is to have an internal list of timezone names. A large part of me says to not bother. What do others think?
This would ONLY be for user display; dates generated in email headers would continue to use a numeric timezone offset. --Ken _______________________________________________ Nmh-workers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/nmh-workers
