A long-playing task, which is unlikely to be attainable in early milestones.
Keeping it open, but moving out of M04 scope.

please consider the following as part of the i18n:

1. marking #NOI18N comments on applicable key/values in bundle files

2. deciding if the way localized messages will be found -
either with localized in the same en jar

or

separate localized jars.

IS required that they be in same files, like for assembly.dat
but since nbi is java, they could follow our usual model of
having separate localized jars and since there are many of the
components/*.jar, each with a bundle file, besides those in 
nbi-engine.jar, it might be cleaner to have separate localized jars.

3. setting up l10n.list and having kits built; and a specific location
for the kits -- this assumes that they should be on a usual public
server like smetiste.czech, where other nb based builds are, or
on balui or clue.

4. creating translatedfiles/src/nbi

5. setting up for the build of ml installer
a. first step is the parts that have localized files built into it,
following model discussed in item 1.

b. 2nd part is to have the localized things to be installed in it;
I guess this is really not needed early on, since the localized of some
product/pack/GF comes later in the cycle, and replaces the en one,
but the messages in components/*.jar will be the same.

6.resizing - I noticed that nbi window does not resize; if that will be true
then it means the same problem as was with IS, that layout and sizing of 
items in a given panel will need to be customized rather than using layout
manager and other java api to let the entire panel window resize dynamically.

already in some early testing using pseudo localized I saw some resize
situations that not an entrie string showed.

Thus if there can be dynamic resizing it will really help.

Also suggest to allow user to run nbi with a chosen font size.


ken.frank@sun.com

-> M12

-> M15

Unfortunately, moving I18N to post M9.

-> TBD

Assigned to new owner.