OpenOfficeLangPacks

Revision 1 as of 2006-06-23 15:27:49

Clear message

Summary

Build the OOo l10n and help packs in less CPU time, and without duplicating the OOo source in the archive.

Rationale

Currently the archive hosts two (identical) 450MB OOo source packages to be able to build the l10n and help packages independently from the OOo packages containing the binaries. Get rid of the duplicated source. The time required to build the language packages exceeds the time to build the binary packages.

Use cases

  • A translation team wants to test the current state of an OOo translation. The translation needs to be exported from Rosetta, converted to the GSI format and built (which currently requires bandwidth and a huge amount of build time).
  • An export from Rosetta should be checked for correctness (using the OOo lang tools)
  • The time to introduce a new OOo version into the distribution should be shortened.

Scope

Design

From the build (when the OOo binaries are built), build an OOo-l10n-dev package, containing

  • all the localize.sdf files
  • language tools (localize, transex3, ...)
  • the sources for OOo/solenv

  • the HelpLinker binary

  • other files required

Modify the build system (dmake) to be able to build the resource files for translations in all 32 subdirectories containing .sdf files independently from the binaries, lowering the build time for the language and help packs.

Implementation

Code

Data preservation and migration

Outstanding issues

BoF agenda and discussion

CategorySpec