>> There was some resistance to nominating this for 3.0 because ChristianL >> wanted to re-do the translation work to use Java Properties instead of >> the new transex tool we wrote that translated complete XML files >> per-lang. > > This is bogus, I discussed with Jan that in my opinion it is a cleaner > solution to use the Java Properties file for translation as I think the > current way of doing it does not fit with the OOo translation database > and tooling.
Other than than, having one one XML file per language sounds pretty wasteful to me. *Maintaining* different versions of the same dialog for different languages is certainly a no-go, since they would soon get out-of-sync. And if we automatically "create" (by whatever means) different-language versions from one "master XML file", then I don't see a reason why this should/could not be done at runtime, instead of compile time. Which implies we need to separate the UI description from the translation - and here Java Properties files are an established concept which has proven to work, and even already has an implementation in OOo. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
