Bug#471305: "Asia/Saigon" (Vietnam) should be changed to "Asia/Hanoi"
On Sun, Mar 23, 2008 at 03:35:19PM +0700, Jean Christophe André wrote:
> Ok. In fact I better understand the tzdata idea now so I will suggest
> another way:
> 1) change "Asian/Saigon" to "Asian/Ho_Chi_Minh" (without "_City" to
> respect POSIX constraints) ;
I believe this is scheduled to happen upstream tomorrow.
> 2) in the user interface, so in the debconf question, propose "Ho Chi
> Minh City, Hanoi" instead of "Ho_Chi_Minh".
The way things work with the current setup is that for each language,
there is a pair like this:
msgid "Saigon"
msgstr "Saïgon"
The msgid represents the upstream name and the msgstr represents the
translation in the relevant language (French in this case).
After the change, translators will be prompted to translate
"Ho_Chi_Minh", not "Ho Chi Minh City" or "Ho Chi Minh City, Hanoi"
So we could make the English translation "Ho Chi Minh City, Hanoi",
but the translation teams would have no indication that they were
expected to do likewise. Note that the Vietnamese translator could
have translated "Saigon" as "Thành phố Hồ Chí Minh", but went for
a more literal "Sài Gòn" instead.
> As for 2), would it be feasible/reasonable ? And should we continue in
> this bug report or close this one as soon as tzdata maintainers have
> made the change and open a new one about proposing multiple city names
> for each time zone?
I think it would be appropriate to close this one once Asia/Saigon is
renamed to Asia/Ho_Chi_Minh, and for you to open up a new one to discuss
your multiple city idea and handling the translation issue I described
above.
Perhaps there is a better way to do timezone selection.
Reply to: