Browse Prior Art Database

A method of source code Globalization Disclosure Number: IPCOM000014484D
Original Publication Date: 2002-Feb-01
Included in the Prior Art Database: 2003-Jun-19
Document File: 2 page(s) / 74K

Publishing Venue




This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 58% of the total text.

Page 1 of 2

A method of source code Globalization


Much of the current code does not under development use the concept of Globalization (G11N). Retrofitting G11N into current code is a time consuming process. It is however fairly mechanical.


My idea is to automate the process as much as possible, which would save time, and standardize the resulting code.

Current Automated Methods

Current methods replace language text with keys. These keys are placed into a text file which will then contain the keys and the original text. Translators create a language specific file using the same keys, but with text suitable to the target language.

The problem with this approach is that most code does not output only language text. The text is usually interspersed with values. For instance, to display the number of bytes in a file a possible code fragment (In Java) could look like:

System.out.println( "The number of bytes in file " + filename + " is " + byteCount );

Current techniques would replace the two strings (in bold) with keys: key1 = The number of bytes in file
key2 = is

However the grammar in another language might require that the value byteCount be placed before the filename, or even require words after the last value

System.out.println( "The number of bytes in file " + filename + " is " + byteCount + " long." );

This problem has been identified and solved, however the programmer must manually create the code to use it (in Java):

Object[] parms = new Object[2]; parms...