Difference between revisions of "Internationalization"
Peterbodtke (talk | contribs) (→Client Support for Spanish) |
Peterbodtke (talk | contribs) (→Automated Tools) |
||
| (12 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
INTERNATIONALIZATION of VISTA | INTERNATIONALIZATION of VISTA | ||
| − | The goal of this page is to collect information and resources | + | The goal of this page is to collect information, plans and resources about internationalization of VistA and clients in one place. 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 == | == Client Support for Spanish == | ||
| − | There have been two translation effort for CPRS. David Fonseca | + | There have been two translation effort for CPRS. In 2007, David Fonseca (University of Costa Rica) completed a manual Spanish translation of the field labels (the version of CPRS indeed quickly became outdated.) In 2008, Dr. Kevin Toppenberg's used a plug-in that copied and replaced the field labels with markers. The field label values 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. These translation projects did not address the significant translation development effort that remains within the VistA server. |
A demonstration of enhancements delivered in TMG CPRS can be watched here: | A demonstration of enhancements delivered in TMG CPRS can be watched here: | ||
| Line 14: | Line 14: | ||
Kevin used the DKLang Localization Package to edit the language file: | Kevin used the DKLang Localization Package to edit the language file: | ||
http://www.dk-soft.org/products/dklang/index.php?lang=en | http://www.dk-soft.org/products/dklang/index.php?lang=en | ||
| − | + | Through the use of a language editor tool provided by the DKLang package (http://www.dk-soft.org/products/dklang/index.php?product=dktraned&action=viewinfo#dktraned), it is possible to use this TMG CPRS to support *any* language. This tool creates language translation files, which are then pulled into CPRS for run-time translation. There is a caveat, the version of CPRS that Kevin enhanced is now one version old. There are many additional features that Kevin added to TMG CPRS that you will hopefully enjoy and find useful. | |
== Medsphere's CIS == | == Medsphere's CIS == | ||
| Line 20: | Line 20: | ||
Links describing Medsphere's work: | Links describing Medsphere's work: | ||
| − | |||
| − | |||
| − | |||
| − | 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. | + | Internationalization (i18n) and Localization (L10n) |
| + | http://medsphere.org/community/project/openvista-cis/blog/tags/translate | ||
| + | |||
| + | OpenVista CIS Features and Functions | ||
| + | http://medsphere.org/docs/DOC-1202 | ||
| + | |||
| + | 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 Translation Effort == | ||
| Line 32: | Line 35: | ||
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. | 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. | ||
[http://www.hardhats.org/fileman/MSC.html] (updated 8/2009) | [http://www.hardhats.org/fileman/MSC.html] (updated 8/2009) | ||
| + | |||
| + | MSC FileMan release documentation related to internationalization:<br> | ||
| + | <blockquote> | ||
| + | -Many new DIALOGs handle all end-user interactions<br> | ||
| + | -FILE NAMES, FIELD LABELS, SET VALUES, and HELP MESSAGES can be entered into the ^DD schema for any of the languages listed in File .85.<br> | ||
| + | To enter Spanish, DO SPANISH^DIALOGZ<br> | ||
| + | -Formatting of date output is now consistently done throughout all the end-user routines. Changing the global node ^DD("DD") will change the way all FileMan dates are output. Re-running ^DINIT will not change this node.<br> | ||
| + | -Upper/lowercase translations is consistently handled | ||
| + | </blockquote> | ||
== Automated Tools == | == Automated Tools == | ||
| − | Chris Richardson developed a tool which automates the selection and replacement of strings for translation purposes in VistA. | + | Chris Richardson developed a tool which automates the selection and replacement of strings for translation purposes in VistA. Richardson's code will parse all of the VistA routines and populate the DIALOG file. Once this is accomplished, then the problem is generating spreadsheets that can be used to make the parallel translations possible. That code exists as well. Basically, the process identifies literal strings in English and makes sure that they are in the DIALOG file. Then the literal is replaced in parallel, generated instrumented code. The selection of the languages seen is selected by the user. |
| + | |||
| + | Rick Marshall has commented that the tool is useful, but significant additional development is required to complete the work. | ||
| + | |||
| + | Richardson's routines and sample spreadsheets were released as open source protected intellectual property. The work was posted to the WorldVistA Trac server on 11/15/2008: https://trac.opensourcevista.net/browser/internationalization/trunk | ||
== Interested Parties == | == Interested Parties == | ||
| − | '''Mexico''' - two point of interest: IMSS experienced issues integrating translated catalogues and they leveraged middleware to support Spanish | + | '''Mexico''' - two point of interest: IMSS experienced issues integrating translated catalogues and they leveraged middleware to support Spanish |
'''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. | '''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. | ||
| Line 43: | Line 59: | ||
'''OHUM''' - has a long term objective to complete a translation effort, but it is not on their immediate schedule. | '''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 | + | '''Jordan''' - has a goal to support Arabic in a limited number of user interfaces |
| + | |||
| + | Central American Universities that have shown interest in VistA: | ||
| + | '''Universidad de Costa Rica''' (San Jose, Costa Rica) | ||
| + | '''Instituto Tecnológico de Costa Rica''' (Cartago, Costa Rica) | ||
| + | '''CONARE''' (San Jose, Costa Rica) | ||
| + | '''Universidad Technologica de Panama''' (Panama City, Panama) | ||
| + | '''Universidad del Valle de Guatemalla''' (Guatemalla City, Guatemalla) | ||
| + | '''Universidad Centroamericana''' "Jose Simon Canas" (San Salvador, El Salvador) | ||
== Related Resources == | == Related Resources == | ||
Google Group "VistA Latino" http://groups.google.com/group/vista-latino?lnk=srg&hl=es This group is dedicated to discussing issues related to VistA in Latin America. Topics of interest include supporting Spanish and Portuguese in VistA. | Google Group "VistA Latino" http://groups.google.com/group/vista-latino?lnk=srg&hl=es This group is dedicated to discussing issues related to VistA in Latin America. Topics of interest include supporting Spanish and Portuguese in VistA. | ||
| + | |||
| + | Discussion thread regarding translation on Hardhats in November 2008: http://groups.google.com/group/hardhats/browse_thread/thread/48cad1527ad0e9f5 | ||
Latest revision as of 19:43, 18 November 2009
INTERNATIONALIZATION of VISTA
The goal of this page is to collect information, plans and resources about internationalization of VistA and clients in one place. 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.
Contents
Client Support for Spanish
There have been two translation effort for CPRS. In 2007, David Fonseca (University of Costa Rica) completed a manual Spanish translation of the field labels (the version of CPRS indeed quickly became outdated.) In 2008, Dr. Kevin Toppenberg's used a plug-in that copied and replaced the field labels with markers. The field label values 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. These translation projects did not address the significant translation development effort that remains within the VistA server.
A demonstration of enhancements delivered in TMG CPRS can be watched here: http://www.youtube.com/watch?v=ojcIoIy7HC4
The Astronaut WorldVistA and TMG CPRS installer can be downloaded here: http://sourceforge.net/projects/worldvistaautoi/files/
Kevin used the DKLang Localization Package to edit the language file: http://www.dk-soft.org/products/dklang/index.php?lang=en Through the use of a language editor tool provided by the DKLang package (http://www.dk-soft.org/products/dklang/index.php?product=dktraned&action=viewinfo#dktraned), it is possible to use this TMG CPRS to support *any* language. This tool creates language translation files, which are then pulled into CPRS for run-time translation. There is a caveat, the version of CPRS that Kevin enhanced is now one version old. There are many additional features that Kevin added to TMG CPRS that you will hopefully enjoy and find useful.
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:
Internationalization (i18n) and Localization (L10n) http://medsphere.org/community/project/openvista-cis/blog/tags/translate
OpenVista CIS Features and Functions http://medsphere.org/docs/DOC-1202
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. [1] (updated 8/2009)
MSC FileMan release documentation related to internationalization:
-Many new DIALOGs handle all end-user interactions
-FILE NAMES, FIELD LABELS, SET VALUES, and HELP MESSAGES can be entered into the ^DD schema for any of the languages listed in File .85.
To enter Spanish, DO SPANISH^DIALOGZ
-Formatting of date output is now consistently done throughout all the end-user routines. Changing the global node ^DD("DD") will change the way all FileMan dates are output. Re-running ^DINIT will not change this node.
-Upper/lowercase translations is consistently handled
Automated Tools
Chris Richardson developed a tool which automates the selection and replacement of strings for translation purposes in VistA. Richardson's code will parse all of the VistA routines and populate the DIALOG file. Once this is accomplished, then the problem is generating spreadsheets that can be used to make the parallel translations possible. That code exists as well. Basically, the process identifies literal strings in English and makes sure that they are in the DIALOG file. Then the literal is replaced in parallel, generated instrumented code. The selection of the languages seen is selected by the user.
Rick Marshall has commented that the tool is useful, but significant additional development is required to complete the work.
Richardson's routines and sample spreadsheets were released as open source protected intellectual property. The work was posted to the WorldVistA Trac server on 11/15/2008: https://trac.opensourcevista.net/browser/internationalization/trunk
Interested Parties
Mexico - two point of interest: IMSS experienced issues integrating translated catalogues and they leveraged middleware to support Spanish
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 a limited number of user interfaces
Central American Universities that have shown interest in VistA: Universidad de Costa Rica (San Jose, Costa Rica) Instituto Tecnológico de Costa Rica (Cartago, Costa Rica) CONARE (San Jose, Costa Rica) Universidad Technologica de Panama (Panama City, Panama) Universidad del Valle de Guatemalla (Guatemalla City, Guatemalla) Universidad Centroamericana "Jose Simon Canas" (San Salvador, El Salvador)
Related Resources
Google Group "VistA Latino" http://groups.google.com/group/vista-latino?lnk=srg&hl=es This group is dedicated to discussing issues related to VistA in Latin America. Topics of interest include supporting Spanish and Portuguese in VistA.
Discussion thread regarding translation on Hardhats in November 2008: http://groups.google.com/group/hardhats/browse_thread/thread/48cad1527ad0e9f5
