Internationalization - Revision history

Peterbodtke: /* Automated Tools */

2009-11-18T19:43:51Z

Automated Tools

← Older revision		Revision as of 19:43, 18 November 2009
Line 50:		Line 50:
	Rick Marshall has commented that the tool is useful, but significant additional development is required to complete the work.		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 posted on the WorldVistA Trac server on 11/15/2008: https://trac.opensourcevista.net/browser/internationalization/trunk		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 ==

Peterbodtke: /* Automated Tools */ link to Trac server and decription

2009-11-18T19:42:10Z

Automated Tools: link to Trac server and decription

← Older revision		Revision as of 19:42, 18 November 2009
Line 48:		Line 48:
	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.		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. ~~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~~.		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 posted on the WorldVistA Trac server on 11/15/2008: https://trac.opensourcevista.net/browser/internationalization/trunk

	== Interested Parties ==		== Interested Parties ==

Peterbodtke: /* Related Resources */

2009-11-18T19:38:37Z

Related Resources

← Older revision		Revision as of 19:38, 18 November 2009
Line 69:		Line 69:
	== 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

Kdtop: /* Client Support for Spanish */

2009-10-08T15:23:12Z

Client Support for Spanish

← Older revision		Revision as of 15:23, 8 October 2009
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
	~~I believe Kevin also used another~~ tool to ~~automatically copy the field labels and insert code that would~~ support ~~the display manipulation~~. 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.		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 ==

Peterbodtke: MSC FileMan release notes

2009-10-04T22:43:52Z

MSC FileMan release notes

← Older revision		Revision as of 22:43, 4 October 2009
Line 35:		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 ==

Peterbodtke: /* Interested Parties */

2009-09-29T16:38:07Z

Interested Parties

← Older revision		Revision as of 16:38, 29 September 2009
Line 42:		Line 42:

	== Interested Parties ==		== Interested Parties ==
	'''Mexico''' - two point of interest: IMSS experienced issues integrating translated catalogues and they leveraged middleware to support Spanish ~~Central~~		'''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.

Peterbodtke: /* Interested Parties */

2009-09-29T16:37:22Z

Interested Parties

← Older revision		Revision as of 16:37, 29 September 2009
Line 48:		Line 48:
	'''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 ~~some~~ interfaces		'''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.

Peterbodtke: /* Automated Tools */

2009-09-29T15:10:43Z

Automated Tools

← Older revision		Revision as of 15:10, 29 September 2009
Line 37:		Line 37:

	== Automated Tools ==		== 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.		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. 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 ==		== Interested Parties ==

Peterbodtke: /* Client Support for Spanish */

2009-09-16T14:44:21Z

Client Support for Spanish

← Older revision		Revision as of 14:44, 16 September 2009
Line 4:		Line 4:

	== Client Support for Spanish ==		== 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.		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:

Peterbodtke at 14:40, 16 September 2009

2009-09-16T14:40:16Z

← Older revision		Revision as of 14:40, 16 September 2009
Line 1:		Line 1:
	INTERNATIONALIZATION of VISTA		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.		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 ==