Hi Hugh, On Thu, 2009-04-30 at 10:23 +1000, Hugh Leslie wrote: > I agree Tim that this is an issue. One of the possible ways forward > is allowing a user to select which translations they want in the > archetype before downloading it from the repository. This would be > something that would be relatively easy to do in CKM - this means you > only get the languages that you need.
This would be a good option at this point. As it was raised with me from a potential user about get several languages that they would never need and the potential impact on applications having to manage all those. But my real argument is that we should adopt industry standards in this area as we have in other areas. It is not only efficient but it makes people feel more comfortable. If the CKM has (can have) that export capability. I wonder how difficult it would be for you (?????) to add collaborative translation ability like Launchpad has? See: https://translations.launchpad.net/oship/trunk/+pots/oship You can upload new templates as need and download .po (or already compiled .mo) files that use all of the standard tools and application framework mechanisms. As my CR is a major change I would like to ask the Jira admins to open up a target ADL version 2.0. There is already an ADL 2.0 draft specification. I envision that this is a long term project. Especially since ADL is now an ISO spec. I would like to target this for 2.0 (not even on the roadmap yet. Also, based on the openEHR mantra of "implementation,implementation,implementation"... volunteer the OSHIP project to experiment with not only using this approach but to build a tool that can extract the languages and create the .po files. Thoughts? --Tim -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090430/7ac22420/attachment.asc>
