OJS versions and translation

Software Support
1

Hi,

When I do Weblate translation of OJS, which OJS version is in question? For example if I want to do translation for OJS 3.4 can i do that using Weblate or Weblate is used for version 3.5 (or version doesn’t matter)? I didn’t find any info about this in documentation.

Regards.

2

Hi @orcalator,

The Weblate translation tools are currently set to contribute to the stable-3_5_0 branch, which means new contributions are merged for every 3.5.0 release. I also forward-port them to main in preparation for the 3.6 release.

Back-porting new translations to older releases (3.4.0 and 3.3.0) has been an unresolved challenge. There are tools and a process for this (see GitHub - asmecher/summit-tools: Locale summiting tools for PKP software) but they are quite heavyweight to work into the development process.

Regards,
Alec Smecher
Public Knowledge Project Team

4

Hi @asmecher,

Huh, we already invested some time in translation using Weblate but this means that we can not download those translations and put them in OJS 3.4? I suppose we can only do translation locally for 3.4? Why don’t you organize translations in Weblate per OJS/OMP/… version? Also, if i’m not wrong, it seems anybody can visit Weblate and do translation, aren’t you afraid of overwriting valid translations with some garbage?

Regards.

5

Hi @orcalator,

Unfortunately a “perfect” workflow hasn’t come up for moving translations between branches. Weblate does seem to support a workflow for multiple branches, but it seems to require creating duplicate components for every branch, which would be impossible to manage, and would likely be very confusing for users.

Other projects run into the same problem, of course, and are using a variety of approaches. XWiki is experimenting with approaches in Weblate, but as you can see from the discussion, it’s not yet concluded and some additional tooling will be required. And the approach I linked above is borrowed from the KDE project, which uses another toolset.

While it is possible that someone could vandalize the project without someone catching it, I do skim and merge translations manually – they don’t automatically get into the official git branches. We’ve talked with some communities about a more formal propose-and-approve workflow, such as Spanish, but most communities are not formalized enough for that to work.

Perhaps a short-term solution: the 3.5.0 translations will, for the most part, work directly with 3.4.0 releases. You could either…

  • Just use them and correct issues as they come up,
  • Run a comparison of the English locale files between 3.4.0-x and 3.5.0-x and ensure those differences are accounted for,
  • Run the summiting tools linked above yourself to automatically account for the differences, or
  • Upgrade to 3.5.0 and not have to worry about it.

Regards,
Alec Smecher
Public Knowledge Project Team

6

Hi @asmecher ,

Thank you for reply. We will probably fix things “on the go“ while still using 3.5 translation in 3.4. Our original plan was to go for OJS 3.5 but in a test phase we found too many issues in 3.5 so we had to go back to 3.4. I hope issues will be resolved in the future, so we will do an upgrade again.

Regards.

7

Hi @orcalator,

We’re hoping to release OJS/OMP/OPS 3.5.0-2 in the near future, and those releases will fix a number of issues that you may have encountered. If there is anything else you don’t see reflected, please report it!

If the 3.5.0-2 releases go well, we may consider adding the LTS stamp to them. Otherwise it’ll probably be 3.5.0-3.

Regards,
Alec Smecher
Public Knowledge Project Team

8

This topic was automatically closed after 11 days. New replies are no longer allowed.