Armenian Translation

[amirzoyan]

We are going to use OJS in Armenia for several journals. But for doing so we shall need the full and stable Armenian version to be available.
We have checked out: the Armenian translation has been partly done. But there are still some components that have not been translated yet. Plus the proofreading is also waiting for its turn.
We can contribute to the translation and proofreading in order to have the fully translated and approved Armenian translation.
What is the next step to approve Armenian translation?

[primozs]

Hi @amirzoyan,

Here is the doc about the translation and how to contribute: Translating Guide for OJS, OMP, OPS, and PKP Software Documentation

Regards, Primož

[asmecher]

Hi @amirzoyan,

Here’s a message I sent by email – maybe it got spam-trapped?

All of our translations are contributed by volunteers; you can register for an account on the translation service (https://translate.pkp.sfu.ca/), find an untranslated component, and begin translating or correcting an existing translation. Make sure to agree to the Contributor License Agreement on a component before you’ll be able to work on it – unfortunately the Weblate software we use for translations doesn’t allow this to be signed once for the entire system, so it has to be done for each component you want to work on.

The translations you work on now will be released with OJS 3.4.0, which is planned for the second quarter of this year, but if you want to use the translations with an earlier release (e.g. 3.3.0) it’s possible to download the translations from Weblate and apply them to your installation of OJS. There are some instructions here:

New locale support installed manually on OMP?

Hi @open2source, (The text below talks about OJS, but it applies equally to OMP or OPS!) We add all the new language content from Weblate to each new release on our current “stable” branch (at the moment, that’s stable-3_2_1 in github). Right now, this means that any work you’ve done on Weblate will be released in OJS 3.2.1-2, when we need to make a release for some reason (e.g. a high-priority issue) or there’s enough accumulated additions/fixes to justify a release. If you want to get the l…

Thanks, and let me know if you have any questions.

Regards,
Alec Smecher
Public Knowledge Project Team

[amirzoyan]

Hi Alec,

Unfortunately, I have not received your email. I received a email from Alec Smecher via PCP Community Forum pkp@forum.pkp.sfu.ca.

@asmecher

All of our translations are contributed by volunteers; you can register for an account on the translation service (https://translate.pkp.sfu.ca/), find an untranslated component, and begin translating or correcting an existing translation. Make sure to agree to the Contributor License Agreement on a component before you’ll be able to work on it – unfortunately the Weblate software we use for translations doesn’t allow this to be signed once for the entire system, so it has to be done for each component you want to work on.

I’ve already done all this.

@asmecher

The translations you work on now will be released with OJS 3.4.0, which is planned for the second quarter of this year, but if you want to use the translations with an earlier release (e.g. 3.3.0) it’s possible to download the translations from Weblate and apply them to your installation of OJS. There are some instructions here:

Thank you for your help! We were interested in this question, because all our sites should become trilingual as soon as possible (English, Russian, Armenian).

Regards,
Artashes Mirzoyan