Internationalization problem

mborchorst wrote on Sunday, November 06, 2011:

When I try to install the translation to my 4.1.0 (3) installation I run into problems.
The translationsfile:
http://github.com/openemr/translations_development_openemr/raw/master/languageTranslations_utf8.sql

The file saves at 4,9 MB (4.901.922 bytes)
When i follow the instructions and go to the database upload (see linked screen shot)
I get the following error message:
‘No data was received to import. Either no file name was submitted, or the file size exceeded the maximum size permitted by your PHP configuration. See FAQ 1.16.’

Following the advice from:
http://wiki.phpmyadmin.net/pma/FAQ_1.16
moving the file to the openemr directory and running *source langua……sql does not produce any results.

I have successfully imported the translations by reducing the file size to below 2MB, but removing some 40k lines takes time.

Maybe I could suggest to split the language file into multiple files, each containing one language. Most likely most people downloads the file to use only one language anyway.

Greetings,
Morten

bradymiller wrote on Sunday, November 06, 2011:

Hi Morten,

I assume that you used these instructions:
http://open-emr.org/wiki/index.php/Install_Translations

Recommend using the following php settings for OpenEMR:
http://open-emr.org/wiki/index.php/FAQ#What_are_the_correct_PHP_settings_.28can_be_found_in_the_php.ini_file.29_.3F
(especially note the post_max_size and upload_max_filesize, which will fix your issue)

Regarding size, there are likely ways to reduce the size of this file markedly even with keeping all the translations; at some point when have time, may attack this issue. A more important project is placing an import feature within OpenEMR to get the most recent translation sets, which is described here:
http://open-emr.org/wiki/index.php/Active_Projects#Translation_database_maintenance.2Fimprovement
(in the TO DO sub-section; if we have this, then no need to have to do via the phpmyadmin way and the simple push of a button within OpenEMR would do it)(making a separate translation set file for each language would require a lot more time to set up and maintain than to set up this type of mechanism)

Also, note you can force OpenEMR to only use one of the languages if you desire at the settings at top of Administration->Globalse->Locale:
http://open-emr.org/wiki/index.php/Administration_Globals#Locale

-brady
OpenEMR Project

mborchorst wrote on Monday, November 07, 2011:

THKS

Correction of php.ini solved the problem indeed

In the globals section 2 danish entries exists: one called Dansk (login with that one gives an English interface) or one called Danish (giving the danish interface).

If splitting the data into each language is more difficult I agree keeping things as is is satifying for now.

Greetings,

Morten

bradymiller wrote on Tuesday, November 08, 2011:

Hi Morten,

Good to hear php.ini mod worked. You report of the separate Dansk/Danish entries is odd. If I login in with Danish translation in both demos, I only see dansk (which give Danish translations) option (don’t see a Danish option):
http://open-emr.org/wiki/index.php/Development_Demo
http://open-emr.org/wiki/index.php/OpenEMR_Version_4.1.0_Demo

-brady

mborchorst wrote on Wednesday, November 09, 2011:

I guess I added “Danish” via Administration - Other - Language - Add Language before the language was available through importing the tables, and therefore creating a null language named “Danish”. The official one is called “danish”.

Just thoughts though.

/Morten

bradymiller wrote on Thursday, November 10, 2011:

Hi Morten,

I think I sorted out your issue. The official language (in English) should be ‘Danish’. In the official 4.1.0 release Danish translation set it also is ‘Danish’ (likely doesn’t have a translation entered yet there), however in the most current development translation that you downloaded, the ‘Danish’ gets translated to ‘dansk’.

So, the official Danish language for you should be “Danish” in english and “dansk” in Danish. The other one is likely something you added.

-brady
OpenEMR Project