OJS 3: What is the correct procedure of the locale updating

Hi @mtub,

Would you please recommend a robust procedure of updating the locale ? Assuming we cannot upgrade it using the git repository.

E.g. I can remove the locale in the Admin settings and then install it again. Would it be safe? Would it be updated? :slight_smile:

Or would the replacement of certain folders in our installation folder be the only option in our case? Thanks!

Hi @Ph_We,

I am not sure I understand exactly. Are we talking about

a) updating your local OJS installation, or
b) updating the Russian locale of OJS?

Hi @mtub,

Sorry, I’m talking about our local OJS installation (a).

updating locale files (by removing and adding a newer version of a xml file)

You should be aware that if you add locale files from a newer version of OJS to your not updated local installation, you may end up with unexpected errors. The locale files are part of the OJS releases, and you might see results like

  • in the newer locale file we removed translations that your older installation still needs (because you only updated locale files, but not the actual code that uses the translations)

So I would always advise to update your OJS installation regularly and thus getting all the local updates.

local modifications to your installation

If you want to change the existing translation, e.g. because you want to see a different language in certain UI elements, you can modify the files. Please note that the next upgrade probably will overwrite your changes.

stuck with older OJS version

If you are stuck with an older OJS version and cannot upgrade, but want to profit from translation updates, you could identify missing keys (e.g. by using the translator plugin or by spotting untranslated text in the UI) and search the most recent XML files (from GitHub) for these keys to then add them locally.

Hi @mtub,

Thank you! So now we stuck with OJS 3.0.1 and we cannot do a git pull.
We planned to just replace these folders in our local ojs 3.0.1 installation folder (with those in the main branch): \locale and \lib\pkp\locale. We tried to do that on our test platform and it seemed to work fine.

But you would not recommend this, since we might get some unexpected errors. And those may not go away even after our upgrading to 3.0.2. Is that right?

Regarding “going away” of your local updates: If you update locally and run an upgrade later, this should be okay (assuming that the changes you apply locally are committed to PKP’s repositories).

1 Like

@mtub, Thank you! That was really helpful.