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.
Don't know if this subcat covers the actual configuring for and building the product. Please let me know if not. For the base team (not l10n team) milestone of having ml localized nb (and ME/prof) built and accurate before l10n work starts, I have been getting l10n kit, pseudo localizing the files, and put back to nb cvs. Attached are some things seen when examining installed ml build as to some missing localized jars and other files.
Created attachment 27074 [details] list of the missing files/jars
In addition to any missing localized jars or files mentioned in attachment, if there are any other nb jars or files (new or otherwise) that do have files to be localized, can rules/specs for building localized of these be added ? ken.frank@sun.com
Additional questions of where in translatedfiles/src, the files from the special l10n kit that has persistence should go - the location should be one that will be best for RE to make rules to build the localized persistence jar and also the localized persistence help that actually lives in the nb AS plugin help jar. Here are details: or nb4, the special AS plugin and persistence put back to translatedfiles/src/appsrv-plugin/... and the persistence went to appsrv-plugin/external/tolocalize/... for nb5, as mentioned in other mail, only persistence files there in kit as persistence/* which includes persistence/mapping/core/javahelp/com/sun/jdo/modules/persistence/ docs for the javahelp. --> So should the localized go to translatedfiles/src/persistence/..... as per kit path ? so that you can then create rule for building the localized enterprise2/modules/ext/locale/persistence-tools-support_locale.jar and for building the localized javahelp that is part of enterprise2/modules/docs/org-netbeans-modules-j2ee-sun-appsrv81.jar (which also has AS plugin help which is from nb cvs.) *** For the other part of special l10n kit, the blueprints, the process is clear and same as it was for nb4. ken.frank@sun.com
Created attachment 27460 [details] Patch for translatedfiles/build.xml
I've prepared a patch for translatedfiles/build.xml to fix the most of issues described in very first attachment to this issue. Please note that: - the patch was not tested yet - the patch contains a lot of untested code backported from release41 branch - enterprise2/modules/ext/jsp-parser-ext.jar (web/jspparser/extsrc) is not localized - missing translation files (files seem to be incorrectly checked-in under web/jspparser/src) - I don't know how to handle localization of enterprise2/docs/syntaxref20.zip - haven't found any familiar data looking like translation of this file
Are the ml builds now using the fixes or still need to be tested by you before that ? (dont want to examine a ml build unless fixes are in ) Also, dummy pseudo files have been put back to blueprints cvs, and Yuta has done his steps; so these are ready to be part of localized blueprints jar; we sent separate mail about this to RE. ken.frank@sun.com
The changes are in. I'm still working on some fixes, but those should not affect your goals.
update as of 12/15 ml daily build: 1. installer msgs now are from locale files in nb cvs 2. these files had been in ml builds, and had been put back before release50 branch, yet not in current ml build nb5.0/shortcuts_zh_CN.pdf nb5.0/docs/*_zh_CN.html ken.frank@sun.com
ml build of 1218 still has the missing localized files as mentioned in previous comment; real l10n putbacks start today so thats why bringing this up again. ken.frank@sun.com
Marking RESOLVED FIXED. Please reopen if you think otherwise. The remaining issues have been fixed for issue 70801, which I fixed today. Next NB 5.0 build (#200501022030) should get this fix.
agree, am verifying this as fixed, since the other issues are covered by the recenly fixed other issue. ken.frank@sun.com