On 6/22/18 13:30, Lester Caine wrote:
On 22/06/18 17:18, Paul Eggert wrote:
If I were designing the terminology from scratch, I wouldn't specify two nearly-identical phrases "time zone" and "timezone" to mean such different things. However, the phrases do have the advantage of existing practice (common English usage and POSIX, respectively).
tzdist specified that the 'time zone' format would be used throughout but there are places with the space is problematic and needs replacing in some way ...
And if you want another one how about the inconsistent use in class names: TimeZone for java - implies space before Z timezone in python - wouldn't it be time_zone if a space was implied? That aside - most documentation and names seem to assume 2 words rather than 1. Even google offers you Did you mean: */time zone/* <https://www.google.com/search?client=firefox-b-1&q=time+zone+classes&spell=1...>