[pve-devel] [PATCH manager] ui: mark strings translatable

Thomas Lamprecht t.lamprecht at proxmox.com
Tue Nov 28 16:44:10 CET 2023

Am 28/11/2023 um 16:29 schrieb Dietmar Maurer:
>> I'm taking on a lot of contributions to translations and the common complaint
>> I hear is that not all can be translated correctly due to such tricks (or just
>> missing gettext), most translators care much more about a correct translation
>> than some over-optimized ones than then break depending on context or target
>> language.
>> Also, changing this now results in only a few new strings to be translated for
>> those languages we get common contributions for, so not really much effort to
>> catch up again.
>>> So what languages are the problem exactly? Please can you
>>> give me an example?
>> Any right-to-left languages could be broken.
> If its only right-to-left languages, we could just add another helper
> to assemble lists in the correct order?

Those I'm rather sure of, but I'd not bet anything that they are the
only ones..

But as said, IMO such special helpers and optimizations are not really
worth the hassle, as most translators do not care and are happier if they
have more context and that the end result is OK, not that they have a
dozen strings, or so, less to translate..

I think the 

Ext.String.format(gettext('Default ({0})'), gettext('Free')) 

is really the biggest reuse one would get, and it needs no special new
helpers and  we have that pattern quite a few time, so IMO worth it.

btw. @Maximiliano: "Free" is rather a bad original text for the
component in question anyway, should be probably rather "Unrestricted".

More information about the pve-devel mailing list