This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 126764 - I18N - setup l10n kits to be built for 6.1
Summary: I18N - setup l10n kits to be built for 6.1
Status: RESOLVED FIXED
Alias: None
Product: www
Classification: Unclassified
Component: Builds & Repositories (show other bugs)
Version: 6.x
Hardware: Sun All
: P2 blocker (vote)
Assignee: nbbuild-issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-05 20:55 UTC by Ken Frank
Modified: 2009-07-03 12:10 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Frank 2008-02-05 20:55:47 UTC 
I think move to hg might impact this.

Its for setting up of kits to be built for product, installer
and uc kits for 6.1.

am assuming dev will still be able to rely on the global l10n.list
and also do their custom l10n.lists ?

I guess the custom lists might need changing as to paths wrt 
move to hg and different top level dir names/layout besides
the usual changes dev will need to make.

If BE can provide some guidance/doc to dev about this if so
it can really help.

schedule date for when dev need to have kits accurate is about
4/3 thus I think infrastructure and kits being built to begin
with needs to happen before that.
Comment 1 Ken Frank 2008-02-22 18:03:58 UTC 
this request is for product, installer, update center, web docs and blueprints kits.

I realize web docs might still be using cvs vs hg for 6.1.

blueprints kit is still needed since it will be on 6.1 uc; do providers of this
need to do anything different than now in providing it due to our hg move ?

PS let me know if separate issue/task needed for each kit.

ken.frank@sun.com
Comment 2 Ken Frank 2008-03-10 03:42:33 UTC 
2 questions:


1. in a meeting it was mentioned that there will be no need for l10n.lists,
that kit built from the product or binary --

what about 

a. translatable kind of file names that should not be translated ?
ie some Bundle.properties, some html files.

b. files that are not usual kind of translatable files but special cases
like some xml files and some others ?

both of these cases have existed in past.

How will these be skipped or added to the kit, since no l10n.list ?

if dev does need to do special include/exclude lists, seems that they should
know about it now so can start, since 3/26 is date for internal kit complete.


2. 

internal date for kit completion is 3/26, with final release of accurate kit to translation on 4/2 -
this gives a few days for BE to verify the kit is accurate (or for dev to fix things
if they do need to do special l10n.lists ?

ken.frank@sun.com
Comment 3 Michal Zlamal 2009-07-03 12:10:47 UTC 
This was resolved long time ago.