Closed yakushabb closed 3 months ago
Thanks a lot for this PR! Marking descriptions as untranslatable and adding translator-credits
are both really good ideas. I'll add credits for other translations and publish all that in v2.4.7 tomorrow :)
I have a few nitpicks like using // TRANSLATORS:
instead of // TR:
and the accidental removal of %AUTHOR%, %YEAR%
but that's nothing I can't fix myself after merging this ;)
By the way, do you think the way Spedread handles translations is good or do you have things you think should change? I've never gotten any feedback on this ^^'
Generally, FOSS projects manage translations in several ways.
Translations for KDE are managed via SVN.
Translations for GNOME are managed through Damned Lies. I can say that a relatively more controlled translation process is in place.
Some projects prefer translating through Weblate. Generally, translation via Weblate is easier for shorter translations. However, since everyone can translate without supervision, it is prone to low-quality translations.
There are also websites like POEditor.com and transifex.com that perform the same function as Weblate. I find Transifex a bit more challenging to use.
Translating directly from code requires a bit more expertise.
If we were to rank them, I would probably prioritize Damned Lies > Code-based translation > Weblate and similar services > SVN.
I see thank you! I'll keep the code-based translation approach for now then :)
appdata: Mark release descriptions as untranslatable
GNOME automatically excludes release descriptions on Damned Lies (GNOME Translation Platform). It's a good practice to follow the GNOME way.
This can streamline the translation process, allowing translators to focus their efforts on more critical and user-facing aspects of the application.
data: Add translator-credits
Add translator-credits tag to show translator information.
https://wiki.gnome.org/TranslationProject/DevGuidelines/Add%20translator%20credits
i18n: Add Turkish translation