from discussions, it seems there will be langpacks for nb6, rather than ml builds,
with user given choice of what language translation(s) will be installed; unlike
ml builds, not all translations will be installed by default.
I think there are 2 big parts to this as relates to i18n readiness
1. nbi part - setting up ui and code to process users choice and to install the
chosen languages for the components the user has chosen.
2. RE part (I can file separate issue - let me know - which relates to building
of the langpacks; for example, for each component zip build and delivered to nbi,
there might be a localized component zip per translated locale.
For testing this , perhaps we can start with a separate branch or setup so that
I can provide pseudo localized zips to perhaps emulate what a localized component
zip per locale would look like, and then let test installers with the new ui and code,
build them into the installer and then can exercise the choices on the installer web page
and make sure that:
- only the chosen language jars are installed
- that there is a 1/1 match for each en jar per localized jar per locale
(this part we have checked in the past with ml builds)
A proposal wrt language packs and possible way to install them has been made in late May. The decision as far as I see
it should be made by Trung and his team. CC-ing him and marking this issue as incomplete.
would need as part of this the process to test it much before real localized packs would
a. would need to provide RE with some dummy localized files so that they could
be built into some 1 file per component per locale as is laid out in the spec for langpacks.
(and to know about proper file naming for these langpacks)
b. how to special enabling of showing the langpacks choices in ui would be needed if its not part
of the en installer itself - that is, if there are no langpacks to install, the ui is there but choices
but for testing using items in a above, some flag would be needed to activate this ui
since the items mentioned in a. could be inserted in the correct place in the regular installer
jar as part of testing, without needing to have current installers do that.
b1. would need to know where in the installer jar these files would go.
c. or perhaps separate ml langpack installers would be needed in any case ? since l10n work
wants to start at beta2, and that they need installers to check their work.
More a task than a defect.
there would be no language packs for 6.0
so resolving as later.
please reopen it when the decision to make langpacks is positive again.
do you want a separate issue filed on what is needed to be done given that
there will be one ml zip or zips with all translations ?
that is, i think some tasks mentioned below will still need to be done.