String Freeze for Krita 5
Alvin Wong
alvin at alvinhc.com
Tue Jul 13 14:10:31 BST 2021
Hi Luigi,
I don't oppose to the idea of split these messages into a separate
catalog, but I am not familiar enough with the i18n infrastructure to
know what effects it will have and what changes will need to be
implemented. Can you please give a bit of detail?
Another thing to note is that, although most of the relevant messages
are new, there are 68 of them that has been translatable for some time.
If we want to split these messages into their own catalog, ideally we
should have them copied over from the existing translated krita.po catalogs.
Best Regards,
Alvin Wong
Luigi Toscano 於 13/7/2021 20:18 寫道:
> Alvin Wong ha scritto:
>> Hi translation teams,
>>
>> We have just merged two changes to both master and stable which makes some
>> existing but previously untranslated strings to be translatable. Let me
>> explain a bit:
>>
>> * A simple message i18nc("Name of automatically created background
>> color fill layer", "Background Fill") has been added to translate
>> the automatically created fill layer when creating a new document,
>> which has been in used for a long time but left untranslatable.
>> https://invent.kde.org/graphics/krita/-/merge_requests/954
>> * A large number of messages (about 900 of them) has been added to
>> translate the built-in resource names, including brush presets,
>> brush tips, textures, workspaces, etc. These messages use the
>> resource file path as the context. They should be at the top of the
>> POT template and easily recognizable.
>> Please note that it is not necessary to translate them all. At this
>> moment the translated resource names only serves as an additional
>> comment displayed on tooltips alongside with their English names. If
>> you feel that they are difficult to translate, that's because they
>> *are*, as the original names often have very abstract meanings, some
>> that the Krita developers may not even be able to explain. You may
>> consider leaving them to be the original English name.
>> https://invent.kde.org/graphics/krita/-/merge_requests/939
> I think we partially discussed about this, but would it make sense to split
> those files to their own translations catalog and use it explicitly? It would
> be easier to distinguish the messages that must be translated from the
> optional ones, and make the krita file easier to handle.
>
> Ciao
More information about the kde-i18n-doc
mailing list