Translation process

Nico Düsing nico.duesing at gmx.de
Tue Apr 15 22:32:48 BST 2025


Hi,

as I'm a newcomer here who has never contributed to translations before 
the process looks very complicated and is not well documented. But from 
different sources I think I understood it.

So correct me if I'm wrong, but the process for translations is the 
following?
1. I check if a translation already exists. So I (just) have to know 
that I need this link:
https://l10n.kde.org/stats/gui/trunk-kf5/team/de/websites-endof10-org/
2. It tells me that no translation exists, so I need to find the po file 
of the thing I want to translate (here End of 10 website) in SVN and 
download it.
3. I need to install Lokalize on my computer.
4. I have to configure Lokalize, so it works correctly with the KDE setup.
5. I do the translations
6. I have to create a diff file with the command line with SVN (so I 
have to install that as well?)
7. I visit another website called https://phabricator.kde.org/ and log 
in there.
8. I upload the po diff file there.
9. After the review process someone is copying the file into SVG.

And after that I would maybe be surprised that someone else was already 
working on that there. So instead I would maybe add steps in that 
process like ask a mailing list I need to know somehow and wait for a 
day before starting? So I need to know 4 different tools:
- l10n.kde.org
- websvn.kde.org / SVN
- Lokalize
- phabricator.kde.org

Is that really a good process? Why do I need to install a tool on my 
computer? That could be a website. Why do I need SVN? Why diff files? 
Wouldn't it be better to have a tool like Pontoon? There the process is:

1. I log in
2. I open the project
3. I add the translations
4. Others approve the change.

I can even see how other languages translated the same text, so if I 
speak English, German, Spanish and French, I can look into the Spanish 
and French translations as well, when I do the German translation. You 
always see the newest translations, can approve new translations, see 
terms and a history of older translations and comments, etc.

Here is a link to how it looks like:
https://pontoon.mozilla.org/de/firefox-profiler/app.ftl/?string=224494

Or couldn't we at least have a git repo, where I just can
1. checkout the repo
2. I need to install Lokalize on my computer.
3. I have to configure Lokalize, so it works correctly with the KDE setup.
4. I do the translations
5. commit and push the changes to a new branch
6. create a Merge Request
7. someone else merges the Merge Request
Not as simple or comfortable as Pontoon, but at least simpler than the 
current process.

Regards,
Nico


More information about the kde-i18n-doc mailing list