Re: adding a language on a private build

Hi Etienne,

Etienne de Boissezon wrote:
> hi
> 
> assuming I translated all my oo-2.0-xx-GSI.sdf file...
> And I want to make a private build, with all files patched for adding my 
> language
> There's one more step: dispatch all strings in all localize.sdf files. 
> Am I wrong?

No! You can merge those string using the localize script:

localize -m -l xx -f oo-2.0-xx-GSI.sdf

> Where to find doc on this?

localize --help

www.khmeros.info/tools

> 
> I allmost finished building the O2beta src...
> if I patch files for adding a language, should I rebuild all?

Better rebuild the whole tree if unsure.

> I read: "Note that you can only build the language packs *after* you 
> have build the complete office with all selected languages."
> ALL selected languages????

If you want to build a languagepack for en-US,fr,xy-zz you have to set 
the WITH_LANG variable to "en-US fr xy-zz" and rebuild. There is no need 
to build _all_ selected languages if you don't need _all_!

> 
> info: I build on linux, with an old P2 (6 days to build!)

The variable L10N_framework="en-US" is usefull for you, only resource 
targets are builded -> faster

> 
> how to manage dependencies (ex how to build "until transex3") ?

cd into transex3 and "build --all"

build --help

> Read the project_dependencies.png and empty unxlngi4.pro dirs to have 
> them build?

?

> 
> thanks

Please send ascii mails to this mailing list, those yellow background 
bites a bit.

Thanks,
Ivo