The openemr v3 language code isn’t working. If you going into interface\globals.php and change it from option 1 (english) to option 3 (spanish) it doesn’t work.
the language department has done a huge job in translation changes. For now, you should ask Brady Miller for a recent SQL.file to import all three needed and connected language tables. Or you have to change all wanted translations one by one through ADMIN => Languages => ADD definitions…
I did not have any problems since version 2.8.2 and up with the Language module, if you want I can give you step by step instructions …
We’re utilizing a Collaborative Google docs spreadheet for our translators at this point, and now have following languages:
Total number of english constants: 2196
Total number of definitions: 4780
Chinese: 4% (77 definitions)
Dutch: 77% (1688 definitions)
German: 1% (23 definitions)
Norwegian: 41% (903 definitions)
Russian: 2% (40 definitions)
Spanish: 45% (981 definitions)
Swedish: 49% (1068 definitions)
Here’s our current (unstable) development version of openemr if you want a demonstration of the improvements: http://opensourceemr.com:2089/openemr user:admin pass:pass
For version 3.0.1 even with the current translation table, things are not very ideal. If you want, you can insert the current language tables into your current version of openemr, however this will delete whatever you have there now (if you installed 3.0.1, you have nothing anyways). Here are the instructions to do this:
1. Download the current currentLanguage_utf8.sql dumpfile to your computer: http://openemr.cvs.sourceforge.net/viewvc/openemr/openemr/contrib/util/language_translations/currentLanguage_utf8.sql?revision=1.3
2. Then in OpenEMR go to
admin -> Database -> Databases -> openemr -> SQL and click ‘Browse’
button at the ‘Or location of the textfile:’ field. Select the currentLanguage.sql
file you downloaded to your computer, then click ‘Go’ button.
Edit the openemr/interface/globals.php file at the translations entry. Put 3 if you want spanish, after changing setting remember to logout then login back into OpenEMR.
To ensure your database upgrades easier with the next release of openemr, I’d place the following at top of your openemr/interface/globals.php file (note, only do this if you have not yet entered any special non-us characters into your database):
ini_set(‘default_charset’, ‘iso-8859-1’);
If you need help translating the rest of the spanish definitions I am more than willing to donate my assistants time towards translating the rest of the definitions for Spanish.
Please send me the directions on to help and if it would be possible for corporate recognition for such donated time.
Thanks for the offer. Could always use more translators. The spanish translators current strategy is to use Neutral and if run into a problem then use RAE (Real Academia Española).
Send me your email address(and your assistants) to brady@sparmy.com, and I’ll send you all invitations to our Google Docs spreadsheet and instructions on using the translation spreadsheet. We’ll also further discuss a mechanism for the corporate recognition.