Most of the openemr database uses MyISAM engine with UTF8 encoding. Is there a reason why the following openemr tables are not encoded in UTF8 in the database.sql script:
automatic_notification (explicit latin1)
notification_log (explicit latin1)
notification_settings (explicit latin1)
chart_tracker
ar_session
ar_activity
Shouldn’t we try to keep it all in UTF8 if possible? This would then allow many more translation options. Also, at some point will likely need to convert the phpgacl table from latin1 to utf8.
Hoping to get other developers input here regarding our incomplete UTF8 status, which will be important as we increase our language translation capabilities.
So would it be ok to change these above tables to UTF8 to match the rest? To deal with phpgacl will likely have to make a dumpfile and modify that to UTF8 since the current XML mysql schema bugs out because it’s using keys that are too large in UTF8.
The issue will be how to deal with all the forms which I assume are not in UTF8, and also how to deal with the sql upgrade scripts from now on, which don’t specify UTF8 when adding tables or rows. My worry is that older users will be getting tables with some UTF and some latin1; is this bad?? (Considering OpenEMR works now works with its current variety of latin1/UTF8 I’m guessing its ok as long as your using english)
the trick with FireFox and Western is great for Spanish and Chineese (Don’t know about Swedish and Norway). Just for the fun of it, can you do an update of lang_languages and lang_definitions and include Chineese in the opening pages?
I might have some medical students who are interested in Chinese and French translations. Just to show them that there is a free medical package that has WORLD POWER aspirations might give it some extra International exposure.
I will give anybody willing to add translations their own spraedsheet can use other languages as example for with locked cells for other languages, but they will have other languages for comparisson.
Check out the cvs demo, just uploaded the most recent tables. Substituted a entries in left frame with a chines phrase. Pretty cool. Note that I’m now officially encoding characters in UTF8, so it works in Firefox by default, but now in windows explorer you’ll need to change from western to UTF8 (at some point have to get openemr to tell all browsers to use utf8 via meta tags). I’m gonna commit this database for the week with the proof of concept chinese characters.
hey,
The Patient/Client, Name and Birthday are all the same phrase. Just copied it from the “has been created” definition. It’s just a proof of concept.
-brady
I thought so! I just tried one Internet connection with Chinese and another in Dutch on the same IP address/same OpenEMR and both work flawless in their own language!
As soon as we have the official translations OK-ed we make a great new start. Just login, in your own language and let everybody in the Clinic do the same, on their own computer!
Now I need to find someone to translate into Papiamentu… ;-(
Portuguese, French, Patois, Afganistan, Chinese Hong Kong, Chinese Peking, AND why is Germany not yet activated?
