profiler code will move to nb cvs (some of it in nb cvs already)
this issue is to make sure that BE is aware that profiler kit needs to be in nb product l10n kit
(the part of it in kit now is just from the part in nb cvs - some docs)
Also, if some custom l10n.list files are needed in profiler cvs, this issue covers doing that
(with new BE approach to having global l10n.list managed by BE, its possible no l10n.list is needed
in addition - see BE docs on this new approach.)
This is a TASK, not DEFECT. It could turn into DEFECT once the profiler is moved to nb cvs and l10n.list is missing
I think also that the current l10n kits, which have the profiler separate docs that are in the nb cvs,
are not correct now, since have 5.5 docs and also a zh_CN subdirerectory, but translatedfiles do not
go into l10n kit.
ALSO, the date for l10n kits accurate is mid october, but also early in october is milestone
related to building of localized zip files, that will be delivered to installer.
for that to happen, profiler needs to be in nb cvs, since l10n kit is built based on being in nb cvs,
and then kit is gotten and files put back to translatedfiles, so the ml zip files can be built
(these are not real translated, but test translations so we can verify the ml zips.
--> will profiler code be in nb cvs by about 10/1/2007 ?
Target milestone cleanup.
Milestone cleanup: future->next