Hi, On 2025-01-22 23:14, Holger Wansing wrote: > Hi, > > Am 22. Januar 2025 00:01:09 MEZ schrieb Aurelien Jarno <aure...@debian.org>: > >Hi, > > > >On 2025-01-21 23:13, Holger Wansing wrote: > >> Oooh, how I wish people could think more about the impact on translations, > >> when > >> changing templates these days, where trixie's development cycle is nearly > >> over ... > >> > >> Can this be reverted please? > > > >Have you actually checked the changes at the translation level? This is > >basically three changes to match actual timezone changes: > > Only now. > But that's not that important anyway. > AFAICS all translations now show the "This translation is not > complete, do you want > to proceed?" warning (or similar; don't have the exact text at hand). > It doesn't matter, if there's only three or twenty new strings, we are > dropped > from 25 fully translated to 0 now.
Ok, I wasn't aware of that. > >- Truk => Chuuk > >- Godthab => Nuuk > >- Enderbury => Kanton > > > >In the case of Truk and Godthab, I manually fixed the translation that > >were already translating Truk as Chuuk and Godthab as Nuuk. > > I think this will not work, when you add the translations into > the po files directly in the package. > Translations have to be put into the po files in the "d-i" repo > (sublevelX/<lang>.po). > d-i packages are different compared to "normal" packages. And I wasn't aware of that either. > >Also please note that all the Cyprus changes were already shipped in > >tzsetup templates, just not offered in the po files, as all the previous > >uploaders never committed the po changes from the automatically > >generated templates... > > I don't get your point here... I mean that the templates are automatically generated by gen-templates. That script was issuing a: warning: autogenerated template for CY should be manually reviewed warning: autogenerated template for CY should be manually reviewed At the end it means that the templates file in the tzsetup-udeb package contains the Cyprus strings untranslated, and not visible from the translators. I only reviewed the changes and made them available for translators. > >I am fine reverting the 3 changes above. But at the end is do we want to > >provide correct translation of the wrong timezone or the correct > >untranslated timezone. > > We could indeed have both - if there was more time until the release... > > I saw this already frequently with previous releases: when the freeze > is in sight, development work starts for d-i. Well in my case, I got pointed about #1055541 from someone testing the Alpha 1 release. This bug might even needs to get its severity increased. For some countries like USA and Mexico, selecting a timezone doesn't work, it always ends up into Etc/UTC. And then I just got attracted by the warnings... > Anyway, we will see, how that goes. > Before the next alpha/beta, I will insert the English text into the > translated strings as well, at least for the above mentioned languages, > when translators don't act until then. At least for Chuuk and Nuuk, it's very likely the correct translation for languages with latin characters. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
