Yes! On 2/26/19 10:59 AM, Martin Burnicki wrote:
Phake Nick wrote:
I don't think localizing the identifier would solve much of the problem like user at Hanoi would most probably not know they need to select Asia/Bangkok to be the right timezone for them even if you localize the identifier. Sorry, you misunderstood what I wrote.
As I already wrote in another reply I just meant that the names presented in the user interface should be localized. Obviously this is sometimes the case, sometimes not, and sometimes in a different way, and it would be good to make it easier or more obvious to show consistent information to a user.
For example, people living in Liberland may not appreciate very much that they have to select a timezone Europe/Belgrade just because Liberland is located at the same longitude, and happens to use the same DST settings as Europe/Belgrade.
So it would be sufficient to add Liberland to CLDR or whatever provides a mapping, so that Liberland can be selected for the time zone settings, and this is the label that should be localized.
Martin