Difference between revisions of "Internationalization"

Revision as of 20:15, 15 September 2009

INTERNATIONALIZATION of VISTA

The goal of this page is to collect information and resources in one place regarding the internationalization of VistA and clients. Feel free to add details to the descriptions below, insert links, note new stakeholders, share opinions, or anything you believe will advance the effort to support multiple languages in VistA.

Client Support for Spanish

There have been two translation effort for CPRS. David Fonseca's manual translation of the field labels (the version of CPRS indeed quickly became outdated) and Kevin Toppenberg's work which leveraged a plug-in that copied and replaced the field labels with markers. The field label were translated and made available in database, along with the original English labels. The language displayed in the field labels depends on a user selection. I believe many of the bugs were resolved in TMG CPRS. These translation projects did not address the larger development effort that remains to be done on the VistA server.

Medsphere's CIS

For web enabled interfaces a similar approach was taken by Medsphere. Their product, CIS, uses the open source development framework, Mono. Demonstration work has been done leverage Gettext routines to support display of multiple languages. It is not clear to me if the development work is limited to the CIS interface code with some changes to the OpenVistA or if the enhancements that support internationalization were extensively made to the OpenVistA server. I suspect the former.

Links describing Medsphere's work: [1] [2] [3]

Again, as far as I know, the translation process is only just starting with CPRS or CIS, as much more work needs to be done on the server side.

DSS Translation Effort

DSS attempted a full system translation into Spanish and Portuguese. The project was reported to have been put on the back burner by the winter of 2008.

MSC FileMan

George Timson's MSC FileMan (a.k.a. FileMan 23?) has internationalization capabilities which leverage the DIALOG files. It is assumed that an effort to fully leveraging MSC FileMan's internationalization potential would require considerable effort and resources, for integration coding, translation and quality assurance. Rick Marshall commented that such an effort would create fork like no other in VistA. I suspect that the extent of code modification would reach far beyond the realm of KIDS patches, but others would need to comment on this point. Integrating MSC FileMan would be very attractive as it would support additional languages for all of the 'roll-and-scroll' applications and display text parsed by GUI applications. [4] (updated 8/2009)

Automated Tools

Chris Richardson developed a tool which automates the selection and replacement of strings for translation purposes in VistA. Chris can provide the best description of his work. Rick Marshall has commented that the tool is useful, but significant additional development is required to complete the work. I'm not sure if Richardson's tool was ever released to Sourceforge or TRAC. I believe it was shared internally with some of the leadership, but I have lost track of it status.

Interested Parties

Mexico - two point of interest: IMSS experienced issues integrating translated catalogues and they leveraged middleware to support Spanish Central America, South America and Spain - yes, there are many interested parties (government ministries, educational, and commercial), but none that have shared or indicated a commitment to developing VistA for use in these regions. OHUM - has a long term objective to complete a translation effort, but it is not on their immediate schedule. Jordan - has a goal to support Arabic in some interfaces