[Source] Xj3D Internationalisation drive

[Justin Couch]

During this week I copied in the latest version of the j3d.org and AV3D 
libraries. Both of these have now been fully internationalised. Now is 
the time to start looking at internationalising Xj3D.

This is going to be a _huge_ task. There's in the order of 10,000 files 
to work through individually and change over all the string management 
to a separate external set of files with each of the text labels. In 
many cases, the structure of the error messages have to be rewritten to 
work well with internationalised error messages etc.

If anyone is interested in helping out, please modify the file(s) and 
put the modified version and the additional lines for the xj3dResources 
file in as an enhancement request and add that bug number as a 
dependency to bug 141

http://bugzilla.xj3d.org/show_bug.cgi?id=141

I'll roll these in as I get a chance.

Sun has a great guide to internationalisation here:

http://java.sun.com/docs/books/tutorial/i18n/intro/checklist.html
http://java.sun.com/docs/books/tutorial/i18n/format/messageintro.html

Note that, at this stage, I only want to internationalise messages. We 
cannot internationalise the formatting of numbers and dates because the 
X3D spec,  when dealing with numbers only allows for US english 
conventions.  As for language translations of existing Xj3D messages, 
feel free to start, but I'd like to concentrate on getting the english 
one robust first and then pull in other languages a bit later.

Finally, to see the formatting that I like to see in code, have a look 
at exactly what I will be shortly checking in to the class 
org.web3d.vrml.renderer.common.nodes.AbstractNode

-- 
Justin