Hi everyone,
When I last checked the Arabic translation for “manager file of OJS”, I found it missing hundreds of pre-translated keys! That lead me to return to OJS project on Github to see what happened there.
Arabic translation there was present and intact, but there is a commit moving some language’s locale keys into pkp-lib.
Do I have to re-translate all missing keys again, or this is a routine development process and things would be solved soon in Weblate?
Thanks
Hi @vormia, this should be a routine development process and I think that things in Weblate should be resolved soon. But I’ll ping @asmecher who knows better how the integration with Weblate works.
Thanks for staying on top of the translations!
Hi @vormia,
I’ve just synced the Weblate translations against git main
to see if that clears things up. Do you have an example of a locale key that appears to want translation in Weblate in the OJS “manager” component, but has been moved to pkp-lib?
Regards,
Alec Smecher
Public Knowledge Project Team
Hi @vormia,
Ah, that helps – I’ve tracked this down to a syntax error in the .po file. See https://github.com/pkp/ojs/commit/dd8afd3db2d18ee8107aa10f73ccd6bbb5b7e3fc#r50830561 for details. It’s fixed for now but I’ve also filed a feature request adding validation to .po files during automated testing so these can be captured earlier and automatically. That’s here: Introduce PO file validation in validation testing · Issue #7063 · pkp/pkp-lib · GitHub
Weblate should pick up the missing content shortly.
Thanks,
Alec Smecher
Public Knowledge Project Team
Thanks @asmecher,
What you just did was very helpful.
1 Like
This topic was automatically closed after 6 days. New replies are no longer allowed.