Frank Schönheit - Sun Microsystems Germany wrote: > Hi Ivo, > >>> I guess that for building a language pack the OOo source tree would not >>> be needed anymore, except maybe a few modules, is still a wish for the >>> far future? >> >> MBA had the idea to move also all resource source files into a own >> module but we first need to discuss this a bit further .... > > Don't think this would be a good idea. I'd hate to deal with / build Yet > Another 100MB monster if I just want to change a resource string in a > project of mine.
This is a misunderstanding due to the very "reduced" version of my idea. We have to balance two requirements: developers working on e.g. a dialog may want to keep the english resources in their code module (you just have proven that ;-)). OTOH developers building language packs would welcome to get rid of the source trees. There is a possible and clean way to fulfil both requirements, but it would require some coding work: we could keep the resouces in the source tree, but change the resource system in a way that the localizations don't contain complete resources but only the strings. At runtime the code then will always load the english resources and merges in all localized strings. Another potential benefit: we could get rid of the sdf format here and move to e.g. po files (or any other format that the localization community might prefer). So all code developers can work as they did before, localization developers get rid of the source trees and - IMHO even more important - of the RSC compiler and use a much easier processing. The price to pay is a little bit coding work in tools/vcl and a few more CPU cycles to burn when a dialog resource is loaded. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[email protected]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
