Due to difference in layout of nbi built installer from IS ones,
and that it also allows running in browser, and that the components
also have messages shown to user, besides nbi own --
for doing the i18n testing, what is needed is an initial
kind of l10n kit as well as a special build set up
to build the resulting pseudo localized files that would
be returned after using that kit.
For the IS installers, I was able to do all this myself,
but nbi is more complex.
This is not for real translations, but for i18n testing now,
since m8 or m9 is build that is supposed to have most of the
i18n implemented in it, as far as I know.
I have looked at and browsed the nbi directory on nephrite
first to analyze about this.
Also, at the moment, nbi executables, code, etc is on
other machine, so it would mean I'd need to copy
all things to my own machine to modify, and thats
a lot of copying and time needed.
And also, if the individual components pseudo localized
msgs can be part of this "pseudo ml nbi", then
it means separate actions wont be needed to pseudo them
once an installer is created when using the web interface.
I18N is not a requirement for preview. -> TBD
can we start to discuss this ?
should it be part of nb l10n kit or separate kit ?
approach to nb kit now is different - there is a global l10n.list and a way for
dev to specify files not covered by those patterns and to exclude files; there is not a top
level l10n.list per nb cvs module; the special l10n.list files would live further down;
Rudolf can provide more information.
even though beta is not localized, it will help to get this setup by then, since translation
work starts then.
BTW, in prototype/early new l10n kit, there is not a subkit for nbi so RE would need to
add that if nbi kit would be in the nb l10n kit.
here's what is needed for this flow
a. nbi engine and components in product or special kit via l10n.lists
(or if in product kit, might be covered by global patterns, see BE mail/docs)
b. I'll get the special kit, pseudo localize the msgs; put back to translatedfiles
or return to installer team to emulate that part.
c. have special installer built using the pseudo files; even though i can add them myself to en jar;
this part allows installer to set this up for real future builds and it what is really needed to test.
d. then it can be tested running in the other locale.
Note - this does not need to wait for implementation of langpacks ui or logic
since this is about nbi/component msgs in general.
based on conversation with Kirill, there needs to be a separate l10n kit for installer.
I will file issue in nbbuild to have this kit setup.
1. BE has new process for doing product kits; I dont know if this can apply to installer kit -
ie there is a global l10n.list maintained by BE that has most common patterns and paths
and then indiv modules can include or exclude other files
if not, then perhaps the traditional l10n.list process can be used.
2. please clarify - in the installer kit will be translatable files of
a. nbi engine itself
b. bundle files of all compoonents that might be installed
c. the installer web page where user chooses which bld to download
d. the bundle files from the logic,1.jar of each langpack per locale that is based on the langpack zip
delivered from BE, and that has had the logic,1.jar, etc added by installer team.
110470 was filed in nbbuild to setup the separate installer l10n kit and to ask to let installer team know
if they need to do the usual l10n.list in their cvs.
More a task than a real defect.
BE issue 110470 is done; build is setup
to build separate installer l10n kit.
The kit is now empty since installer cvs needs
custom l10n.list files in it as per solving
of this issue, since the global l10n.list patterns
do not apply to nbi cvs.
Also, in the new installer l10n kit is a sub kit for
the msgs of previous installers - are these still needed ?
are there still bundles or releases using these previous IS based installers ?
I`ve modified installer and nbi l10n.list today. So wait for the next build and check if contains the required files.
in current installer l10n kit are 2 tar files, yet they seem to both have an nbi section ?
are both needed ?
can they be combined and placed into just one tar file ?
since there is just one nb6 installer.
(I realize for mac there might need to be another tar file for its installer kit)
As Dmitry mentioned in other mail, we might need to have the 2 separate installer kit tar files
for nb6 and there might be some duplicate files, but I think that can be ok since its late in
cycle and its more important now to have ml installer, since dont think there are that many duplicate
What is needed now is for team to compare the kit to the installer itself and make sure that:
each file in kit is needed; there are no files that should not be there
there are no files missing from kit that are in installer (that are translatable kind of files)
--> this is part of nb schedule milestone of installer l10n kit complete for 10/29.
Thanks - Ken
kit will also need files for the installer web page; will that be
properties kind of file or html file ?
translation and can lead to syntax errors.
there is task about setting up for the web page as to i18n and that translated
items are found.
I hope that it is completely done now (kit is availiable, builds are available).