On Wed, Feb 13, 2013 at 09:42:42AM +0100, janI wrote: > If performance and memory footprint is a concern, we loose a lot in our > international version, > > An average set of language text takes up 1.3Mb in the code segment. > > Since we release 8 languages, it would be expected to use about 10Mb > > However, due to the way localize_sl works, we actually include all 116 > languages from extras/l10n. Meaining the footprint is about 150Mb. > > I am sure this difference affect, download time, start up time as well as > running swap space (on ubuntu 12.04. And at the same time it is something > that a simple if could correct (dont use all languages, but simply > --with-lang) > > Ps. due to the fact that it is scattered in small pieces over the code, > and at least one language is in use, it will effectively also be in main > memory. > > My conclusion is that neither AOO nor LO, is only partial optimized for > performance, especially in regard to footprint.
I don't understand what you are talking about, it looks like you are mixing what happens during building the product, with the final product. The final product, as can be downloaded from the final, in his language, contain only resource for his language. Resources are located in <BASIS_DIR>/program/resource/, there you'll only find a binary resource file per module for the language the user downloaded; for example, if I downloaded the Spanish version cuies.res dbaes.res etc. Look the contents of cuies.res with a hex editor, you'll find only Spanish strings. Even if the user installs several language packs, the application only loads the resources for the application language, selected on the Options dialog (build main/tools/source/rc/resmgr.cxx with debug, and look at the OSL_TRACE). Regards -- Ariel Constenla-Haile La Plata, Argentina
pgpO2X6c6SU2w.pgp
Description: PGP signature
