This script upload translation templates (pot files) to KDE SVN and download translations
(po files) from KDE SVN.
Run ./l10n_sync.sh daily. It is fully automatic.
guoyunhe |
Krita: Manual |
This script upload translation templates (pot files) to KDE SVN and download translations
(po files) from KDE SVN.
Run ./l10n_sync.sh daily. It is fully automatic.
No Linters Available |
No Unit Test Coverage |
Buildable 1139 | |
Build 1152: arc lint + arc unit |
What worries me a bit is that this checks out the entire svn tree which is huge. Couldn't we make a list of languages that have manual translations, and only checkout out what we need?
Even if checkout several language, the size is still huge. Better solution is to checkout only folder <language_code>/docmessages/extragear-graphics. This folder mainly contains doc of digiKam and Krita. Not all languages have these files, so checkout all languages doesn't waste much space. I will make an update later today.
You should define a StaticMessages.sh script and let scripty handle the synchronization.
Sorry, I totally forgot that we already discussed this and that StaticMessages.sh only create one file for repository.
The other solution would be helping us to extend the code which calls StaticMessages.sh to support more po files.
digiKam has many pot files in docmessages. If they can do it, I can just borrow their code / idea. I need to do some further study.
@ltoscano Do you know where is the script that handles StaticMessages.sh? I want to try if the script can be modified to support multiple pot files.
Here is another solution using Crowdin platform https://phabricator.kde.org/D14992
I have tested it and it works nicely.
If we cannot solve the file structure problem, Crowdin is a better option.
StaticMessages.sh is not a solution, because it's targeted for messages, not documentation.
The documentation works differently, and it requires some changes.
Lines 422-425 are dealing with the docbook translations:
https://websvn.kde.org/trunk/l10n-kf5/scripts/update_translations?revision=1522690&view=markup
Another block of code could be added there to extract sphinx stuff.
Please don't fork the translator community again with yet another platform. We may need a site like that, but on kde.org.