drbowen wrote on Wednesday, September 17, 2008:
In general I agree with your thoughts.
We should have to have in each record (both at DB level as in the csv file )
- name of the object / field , english term, spanish (or target language) term
I would prefer, if possible, to also include a column with the path to the file to make it easier for others to translate other languages. So what I would like to see would be:
Path to the file, field name in the file, language name, english term or phrase, translation
For me it would be more intuitive for non programmers to be able to help with these translations. I am a non-programmer but I have access to German, Russian, French, Romanian, Ukrainian and probably others in my community. Currently, the translation process is sopmewhat arcane and difficult to figure out.
Also, we already had a Swedish translation but it got lost in one of the upgrades. Having individual CSV files will help insure against this loss.
lang_languages=(lang_id, lang_code, lang_description)
The constant_name is the english term
OEMR should have the possibility of exporting the language table into a csv - encoded file, so we can edit it.
oemr already has this capability in the MyPHPAdmin. This can export CSV values that are in Excel spreadsheet format.
We also should have the way of importing the specific language from the csv file (either from console/OS or from the the admin menu).
I should not be too hard to write a script that can be executed from the "admin" area to import CSV files.
This will make the language table smaller, since only English will be initially loaded. Then, we can import as many extra languages as we wish, but it will be optional.
2) Create a directory i18n with the different translation files, with the ISO code for each language / country :*****
Agreed. This would be my preference but some of the other developers have insisted that we not worry about this.
Sam, regarding having a single language flavor, "plain" Spanish is hard. Spanish from Argentina varies significantly from Spanish from Spain. The system should be localized to the specific country. This method should take care of it. *****
I know there is no "plain Spanish". My reference was to "Standard Spanish" such as that used on CNN. Most Spanish speakers understand this even if it is not there usual dialect.
If it is easier to have country specific Spanish dialects I am all for it.
Sam Bowen, MD