We now also want to migrate our web app translation management to Translatewiki.
@abi_, @Nikerabbit – we have Ajapaik dev camp going on at the moment (one more day to go) and we are also looking into the integration with Translatewiki that we have issues with (with the web app added most recently, no problems with the Android app).
Is there some online channel our developer @H2kks and also @Zache could be in contact with you? We have an open Slack workspace where we could have a dedicated channel if you could join it.
Our main question at the moment is how could we trigger pull/push in order to test some things – there are issues with whitespaces (with new lines) in some languages etc.
Short answer, it is not possible for you to trigger push, except by asking us and pull happens every few hours semi-autoamtically. We generally push translations out every Monday and Thursday.
The best way to contact us would be via IRC on mediawiki-i18n channel on Freenode.
Could you describe the issue you are having in some more detail? Maybe we could add some validations / checks on our end to avoid translators saving translations that have those issues.
Hi @abi_ ,
There are two issues happening,
The first issue is that the translations started with newline and whitespace characters. We have now edited the messages not to start with new lines and whitespaces.
When translations were added for some languages whitespace and newline character were not added. This caused the compilemessages step to fail, as both the message id (msgId) and message have to start with /n.
Other issues that we have noticed, is that in some languages there are duplicate msgId's which causes an error on compilemessages.
We think that the first issue is best fixed in source code, as having indenting and newlines in translations is error prone and can cause confusion.
Second issue is still under investigation.
Was just reviewing the translations submitted to Translatewiki.net from the Ajapaik-web project - https://translatewiki.net/wiki/Special:ManageMessageGroups/unattended
- We should not mark the source language (English) strings as fuzzy. Once you make changes to the source language, translatewiki.net will take care of marking the corresponding translations as fuzzy.
- Also please take a look at the pot file from the Dissemin project for an example on how to structure the file properly. The file I've linked to is the source language (English) file.
I've just exported the changes from Translatewiki.net - https://github.com/Ajapaik/ajapaik-web/commit/e7c3efdf65ca07f2d26619655fcdfec9d5a1a6ce
The translations were exported without merging the changes highlighted in the previous comment.
Let me know if you'd like me to run another export.
I have now removed the Fuzzy markings for english, can you please check if this can be used for syncing the changes?
I have now checked the pot file from Dissemin project. Is this something that we should include instead on english .po?
@H2kks - One more thing that I noticed is that since now your English po file no longer contains !!FUZZY!!, but your translations still do. For ex:
#: ajapaik/ajapaik/forms.py:414 #| msgid "Album created" msgid "!!FUZZY!!Album created" msgstr "Álbum criado"
Might be a good idea to remove the fuzzy from there too to make the msgid the same as in English, so that translators don't have to re-translate that string again.
Generally such key / msgid renames are handled on Translatewiki.net but since there were so many of them (FUZZY was removed from English msgid), it will be easier to do it on your end.