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.
Steps: 1. Install ml build 200712131200 2. Launch NetBeans IDE on Chinese platform. 3. Create a Visual Web project 4. Drag drop a table, or check box group, or radio box group from Palette -> Basic or Standard Result: The default items are in English, ie. "Row1_Column1", "Item 1", "item 1", etc. * We localized visualweb/webui/runtime/library/src/com/sun/rave/web/ui/model/Bundle.properties and visualweb/jsfsupport/runtime/library/src/com/sun/rave/faces/data/Bundle.properties in l10n kit. However, webui- jsf_<locale>.jar and jsfcl_<locale>.jar are not installed in the target ".../visualweb1/modules/ext/locale". ** Please also check, now there're only two l10ned jars in the target place ".../visualweb1/modules/ext/locale": webui-jsf-dt_<locale>.jar webui-jsf-suntheme_<locale>.jar Shouldn't some others be there? like: dataprovider_<locale>.jar defaulttheme_<locale>.jar defaulttheme-gray_<locale>.jar defaulttheme-green_<locale>.jar designtime_<locale>.jar designtime-base_<locale>.jar errorhandler_<locale>.jar sqlx_<locale>.jar tidy-mod_<locale>.jar
There are 2 parts to this issue; we need to separate perhaps; Ming can you provide some more information ? 1. the part about Row_Column, etc - some items will not appear as translated since these are items expected to be changed by user; issues have been filed about this before and that was decision by vwp team. a. but it could be that if this applies to all things of all components, that the translations of the component messages/labels might not be done by the translation team who has provided to us those jars, since some of these msgs come from another sun team, and their translations do also. - Are all such labels of components not from translated files ? b. or it could be that the needed jars for nb for zh are not being built, as could be case for the other jars you mention - are the comparable ones for ja and pt_BR being built ? have all the translations from your team related to visualweb been put back, that were in the nb product l10n kit ? Answers to these questions will help see where the problem might be. ken.frank@sun.com
Created attachment 54289 [details] To demostrate the answer to Ken's query 1.
Created attachment 54290 [details] To demostrate the answer to Ken's query 1.
To respond to Ken's query on 2007/12/14 17:22:12 +0000 [Ken] 1. the part about Row_Column, etc - some items will not appear as translated since these are items expected to be changed by user; issues have been filed about this before and that was decision by vwp team. [Ming] No matter those default items are localized or not, they can always be changed by editing text properties.(refer to attached images.) "Item 1" for checkbox group/radiobutton group/.. can be changed from "Configure Default Options" in contextual menu. I may not understand your query, but does it have anything to do with l10ned jar missing? [Ken] a. but it could be that if this applies to all things of all components, that the translations of the component messages/labels might not be done by the translation team who has provided to us those jars, since some of these msgs come from another sun team, and their translations do also. - Are all such labels of components not from translated files ? [Ming] Please refer to comments in the bug report. We localized visualweb/webui/runtime/library/src/com/sun/rave/web/ui/model/Bundle.properties and visualweb/jsfsupport/runtime/library/src/com/sun/rave/faces/data/Bundle.properties in l10n kit. "Row1_Column1", "Item 1", "item 1" are in these files. My furthur concern is that seems some other l10n jars are missing. (refer to bug report) [Ken] b. or it could be that the needed jars for nb for zh are not being built, as could be case for the other jars you mention - are the comparable ones for ja and pt_BR being built ? [Ming] No, there aren't for ja or pt_BR either. [Ken] have all the translations from your team related to visualweb been put back, that were in the nb product l10n kit ? Answers to these questions will help see where the problem might be. [Ming] I double-checked, in branch release60, visualweb properties files for ja and zh match the latest l10n kit at http://ministop.japan.sun.com/products/devtools/netbeans60/delivery/l10n-kit/. ("Match" means each properties files in l10n kit has a corresponding l10ned one in branch release60, with the same patch while file name changed to xxx_<locale>.properties.)
Ming, thanks for the explanation and gifs. I think it is case of only missing localized jar files in ext dir. but one more question - in your gifs, I don't see any other parts of the ide as being translated but I think the zh files have been put back to translated files; were you using that build or in other locale ? I will pursue this will the build itself, but also leave this open in case it also that some of the woodstock localized files are missing and its because they were not gotten yet by nb team, since that would apply to this category. Thanks - Ken
To respond to Ken's query on 2007/12/15 17:13:39 +0000 [Ken] but one more question - in your gifs, I don't see any other parts of the ide as being translated but I think the zh files have been put back to translated files; were you using that build or in other locale ? [Ming] I took screenshots on English locale (so people can easily read). No difference on localized UI. [Ken] I will pursue this will the build itself, but also leave this open in case it also that some of the woodstock localized files are missing and its because they were not gotten yet by nb team, since that would apply to this category. [Ming] Just for your information, woodstock team only localized webui-jsf-dt_<locale>.jar. For the paticular case of English "Row1_Column1", "Item 1" and "item 1", after I copied webui-jsf_zh_CN.jar and jsfcl_zh_CN.jar from NB5.5.1 to NB6, the labels turned to Chinese. And again, please also investigate if other l10n jars missing, as some existing in NB551 don't appear in NB6, while the corresponding English ones do. Thanks.
if the webui-jsf-dt jars are from woodstock, there is another one, the webui-jsf-suntheme jars in modules/ext/locale. thus as far as I know, ws team has delivered 2 separate jars; in any case, the visualweb team works directly with ws team, not with the ws translation team per se. but am leaving this issue open in case any problem with those jars; otherwise, the problem here is related to ml build itself, not visualweb per se, and we are working on that outside of this issue. ken.frank@sun.com
Dongmei, Is this the same issue we discussed today in the email thread ? If so, we may need to close this as will not fix. In any case, please evaluate, thanks.
For non woodstock jars that are from visualweb itself and live in visualweb1/modules/ext, having the localized versions of these to be built for ml builds is being done in separate process and will be finished early next week. ken.frank@sun.com
> ------- Additional comments from jayashri Fri Jan 4 03:35:18 +0000 2008 ------- > > Dongmei, > Is this the same issue we discussed today in the email thread ? If so, we may need to close this as will not fix. In > any case, please evaluate, thanks. No. A different issue.
Ken, Thanks for the update. I will re assign the issue to you and once ML build issue is resolved, please mark the issue as fixed.
For vwp developers: I'll be glad to close this one when other part is fixed, but first need to know if all woodstock localized jars have been delivered to vwp team and are now part of ml builds; please confirm about that. ml builds can be obtained at http://bits.netbeans.org/download/6.0.1/ml/nightly/latest look in visualweb/modules/ext/locale ken.frank@sun.com
yes, it has been delivered
closing this issue since its confirmed that woodstock localized jars are in product, and the other missing jars are being taken care of as part of a different issue. ken.frank@sun.com