Hi Ivo,
>>Today, the process for new strings involves specifying both the germany >>and the english string in the spec document, and writing them into the >>.src (done by the developer). If the german string is not to be entered >>at source-level anymore, how would this work? Would only the english >>string be specified, and the german version is part of the usual >>translation process? > > Yes why not! To handle German as a usual translation language has a lot > of benefits: > ... Sure, I don't object this. Just saying that our current process requires german strings to be specified and reviewed (linguistic-wise) even before implementation starts (in theory), and that the developer is responsible for maintaining the german strings in the resource files. If german becomes another traslation language (I'd be fine with this), there are more consequences than only technical ones. Somebody needs to allocate the resources for the german translation, at least. OR, german strings are "created" as they're today, and we give developers technical means to push them into a translation database. I had hope you already solved those problems, that's why I was asking for how the solutions look like :) Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
