CC'ing the mailing list again.
Am 05/09/2023 um 08:01 schrieb Maximiliano Sandoval:
> On 9/4/23 18:26, Thomas Lamprecht wrote:
>> Am 28/08/2023 um 17:54 schrieb Maximiliano Sandoval:
>>> - title: Ext.String.format(gettext('Manage {0}'), 'Global OSD Flags'),
>>> + // TRANSLATORS: This will read 'Manage Global OSD Flags'.
>>> + title: Ext.String.format(gettext('Manage Global {0} Flags'), 'OSD'),
>> Hmm, not sure how often this will be reused where {0} will be replaced with
>> something else. I'd rather prefer one of:
>>
>> - Ext.String.format(gettext('Manage {0}'), gettext('Global OSD Flags')),
>> "Manage XYZ" is relatively common, so we might have more reuse potential.
>>
>> - gettext('Manage Global OSD Flags')
>> Fine too, as IMO this is rather specific anyway and unlikely that we have
>> many others where a parametrized msgstr is really reducing translation
>> effort.
>>
>> what do you think?
>
> I don't think that re-usability should very high in the priority list when it
> comes
> to translations, the first example for example could potentially make a
> satisfactory translation to certain languages impossible.
Re-usability sure is important for us, one shouldn't have to bend backwards just
for that, like it felt you did with the "'Manage Global {0} Flags'), 'OSD'" one,
but certainly good to use a harmonised set of terminology.
FWIW: avoiding to much churn is definitively also high on the priority list, as
that doesn't makes life of translators easier.
>
> I don't see any problem with the second suggested approach, which as it
> happens
> is the contents of v1 of the patch.
>
Yeah, I'd rather like the full thing here, as said it's specialized enough to
not
bother with re-usability here until we'd actual require it (maybe if there are
global monitor or MDS flags), as future-proofing for translations is especially
hard. That would then also allow us to drop the comment due it becoming
superfluous.
ps. Please don't top post, that's making this harder and rather irritating to
read
and follow.
_______________________________________________
pve-devel mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
