Add Arabic interface langauge locale error "Could not load language 'ar_JO'"

karkarii

I'm attempting to integrate Arabic (Jordan) language into the interface, but I keep encountering an error message stating 'Could not load language 'ar_JO'' consistently, resulting in the system failing to load. Here's the process I followed to add the Arabic Jordan file:

I initiated the addition of the Arabic locale through the interface (Administration->Locale), providing all necessary information.
I duplicated the en_US file, renamed it to ar_JO, and proceeded to edit the messages.po file using Poedit, translating it into Arabic. Subsequently, I compiled the messages.po file into a messages.mo file and placed it in the ar_JO folder.
I ensured that the newly created folder had appropriate permissions, mirroring those of the English locale file.
To test, I modified the default locale in the setup.php file to ar_JO.
I deleted the contents of the tmp folder within the app directory.

Despite reloading the Apache server and clearing the cache, the issue persists. Each attempt results in the recurring error message 'Could not load language 'ar_JO'', halting system functionality until I rename the ar_JO folder to something else.

Thanks

karkarii

@seth can you help in this please

darrigan

Hi karkarii,

Creating a new language in Administration > Locale allows you to add a new language when entering metadata, but this is independent of choosing a display language for the user interface. (As far as I understand CollectiveAccess!) So your step 1 is one thing, and it's OK.

Your steps 2, 3 allows you to add a new language for the user interface.
Just to be sure, at step 3, also both files messages.mo & .po have right permissions? (not only the folder)
Is there a message about this error in app/log?
First, I would have tried the following: just copy "en_US" folder and just change it to "ar_JO" without replacing any string with arabic alphabet, to check if it's accepted or not. And only then, try to replace some strings with arabic alphabet... 🤔

karkarii

darrigan Thanks dear @darrigan, to answer your question regarding the permissions, yes sure I have checked all permissions and they are ok and they are exactly the same as en_US file, regarding your last suggestion and I have tested this before aslo and I got the same error, I have copied the en_US folder and renamed it withar_JO and I got the same error.

also, there is nothing about this app/log also, I have tested all possible solutions and nothing works until now

monica

Hi Karkarii,

Make sure you have read through the documentation on creating a translation.

https://manual.collectiveaccess.org/providence/developer/translation.html

darrigan

karkarii Which version of Providence do you use?
Would you like me to try installing your file on my system, to see if I get the same error message? (My email is my username arobase univ-pau dot fr)

darrigan

karkarii In addition to the setup.php file, have you thought or tried to put in the app.conf file the line? (It's for the "pawtucket" part, but maybe will work in "providence"?)
ui_locales = [en_US,ar_JO]
(Inside [...] you can add more codes. Check if this line already exists.)

karkarii

darrigan Many Thanks I'm working on Version 1.8, do you have any Arabic file that I can test on my side ? sure I can share the file with you to test on your side

karkarii

darrigan I'm working on providence only on this version and I tested this before, aslo I have tested adding Arabic locale to providence before on other versions and it works! but on this version, it doesn't work ! even with a simple trick just by copying and renaming the en_US folder to ar_JO or another Arabic language, the error appears immediately

darrigan

karkarii No, I have no arabic file.

OK then I'm sorry, it's a subtle error that is beyond me! 🫤 (I work with 1.7.17)

monica

@karkarii If you believe this might be a bug on your version, please go and log it on github. This forum isn't always monitored by the developers, so best to log any bugs there.

ccyen

Perhaps what you're missing is the time parser:

The next step is to localize the date/time parser. To do so copy the English language date/time parser settings file in app/lib/Parsers/TimeExpressionParser/en_US.lang to a file with your locale in the name in app/lib/Parsers/TimeExpressionParser and edit to suit. The file includes comments describing the meaning and format of various settings.