Hi Tim I am keen, as some others have said, that CKM manages this with users being able to get as many translations as they need when they download the archetype. The advantage with the approach is that you do not need the source language to translate using the archetype so you do not need to keep languages not used locally.
It does rely on CKM but allows full language archetypes for repositories whenever they are sought. Sebastian has already got to a point in CKM where languages are stored separately and languages can be added, reviewed and approved independently. Cheers, Sam > -----Original Message----- > From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- > bounces at openehr.org] On Behalf Of Tim Cook > Sent: Wednesday, 29 April 2009 6:23 AM > To: For openEHR technical discussions; For openEHR implementation > discussions > Subject: [Fwd: [JIRA] Created: (SPEC-302) Translations embedded in the > ADL are not efficient and should instead use 'gettext' catalogs.] > > Hi All, > > I raised the below CR and I wanted to open up discussion on this issue. > Actually I brought it up a few years ago but I don't have a record of > where/when; now. > > I know that this have a major impact on implementers but I think the > current way we handle translations in ADL is a monster that is only > going to get worse. > > Thoughts? > > --Tim > > > -------- Forwarded Message -------- > From: Tim Cook (JIRA) <jira-admin at openehr.org> > To: timothywayne.cook at gmail.com > Subject: [JIRA] Created: (SPEC-302) Translations embedded in the ADL > are not efficient and should instead use 'gettext' catalogs. > Date: Tue, 28 Apr 2009 21:47:02 +0100 (BST) > > Translations embedded in the ADL are not efficient and should instead > use 'gettext' catalogs. > ----------------------------------------------------------------------- > ----------------------- > > Key: SPEC-302 > URL: http://www.openehr.org/issues/browse/SPEC-302 > Project: Specification > Issue Type: Change Request > Reporter: Tim Cook > > > Archetypes like openEHR-EHR-OBSERVATION.blood_pressure.v1 with four > translations are huge and tedious to process the languages. > openEHR should adopt the standard use internationalization (i18n) and > localization (i10n) tools that use gettext catalogs. This is the > industry standard approach to performing translations. Tools like > POEdit are open source and cross platform http://www.poedit.net/ > > More info about gettext is here: > http://www.gnu.org/software/gettext/manual/gettext.html though it is > about the GNU set of tools there are others. > > What will openEHR-EHR-OBSERVATION.blood_pressure.v1 look like with 10, > 15, 100 translations? > > > -- > Timothy Cook, MSc > Health Informatics Research & Development Services LinkedIn > Profile:http://www.linkedin.com/in/timothywaynecook > Skype ID == timothy.cook > ************************************************************** > *You may get my Public GPG key from popular keyservers or * > *from this link http://timothywayne.cook.googlepages.com/home* > **************************************************************
