I don't think you want to remove the distinction between en_GB and en_US. Where the term is the same in both, the en would apply. If the term specifies en_GB or en_US it should mean that there is a different term in the other locale.
I would love to have someone smarter than I go over the issues with localization. It seems that there should be an automatic failover... if there is a term with a specified locale (en_GB) it should be used, but if there isn't, then a term with the more generic locale (en) should be used. I am not sure why metadata sharing should care about allowable locales. The inbound concept should come over with its appropriate locale. I don't think we want to change these during the import. Andy -------------------- Andrew S. Kanter, MD MPH - Director of Health Information Systems/Medical Informatics Millennium Villages Project, Earth Institute, Columbia University - Asst. Prof. of Clinical Biomedical Informatics and Clinical Epidemiology Columbia University Email: [email protected] Mobile: +1 (646) 469-2421 Office: +1 (212) 305-4842 Skype: akanter-ippnw Yahoo: andy_kanter >________________________________ >From: Wyclif Luyima <[email protected]> >To: [email protected] >Sent: Wednesday, August 3, 2011 5:23 PM >Subject: Re: [OPENMRS-DEV] Locale on concept_name > > >Technically 'en' is considered to be different from 'en_GB' and 'en_US', there >are few sections of the application that might loosen on this, i can't seem to >recall any right now. > > >It should be fine if you updated all 'en_GB' and 'en_US' occurrences to 'en' >in the 'concept_name.locale' column and probably update 'en_GB' and 'en_US' >values to 'en' for locale.allowed.list. > > > >Wyclif > > >On Wed, Aug 3, 2011 at 4:43 PM, Ellen Ball <[email protected]> wrote: > >Is there a default standard for concept_name.locale? Should we use 'en', >>'en_US' or 'en_GB'? I've landed on a problem with metadata sharing of >>concepts, and believe the problem is that one system is using >>locale.allowed.list = 'en_GB,fr', and the other system has >>locale.allowed.list = >>'en,fr,rw' (META-112). (I'm not sure if the bug is related to the locale.) >> >>I am aware that there are reasons to use en_US or en_GB for 'hemorrhage' or >>'haemorrhage'. However we normally use the American spellings. Should we >>use plain 'en'? >> >>We are using various locales when we mean the same thing (en, en_US and >>en_GB). If I change from 'en_GB' to 'en', what else would be affected? Will >>this change how dates are handled? How should this work with metadata >>sharing? If I import a concept with the same uuid, will it change the >>concept_name.locale on the importing server? >> >>Perhaps this has previously been discussed, so apologies if this is >>repetitive. If >>this is clear to someone, I'd be grateful if it was documented on the OpenMRS >>wiki. >> >>Regards, >> >>Ellen Ball >>Partners In Health >> >>_________________________________________ >> >>To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to >>[email protected] with "SIGNOFF openmrs-devel-l" in the body (not >>the subject) of your e-mail. >> >>[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l] >> > >________________________________ > Click here to unsubscribe from OpenMRS Developers' mailing list > > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
