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.
3 html files at org/netbeans/docs/startup bundled in core.jar file can't be i18ned. Environment ----------- FFJ, EE V.3.0 (Build 010512) Solaris 8, u2 Locale ja_JP.eucJP JDK 1.3.0 How to reproduce ---------------- 1. Rename the html files: info-NewTemplateAction.html --> info-NewTemplateAction_ja.html info-ProxySettingsAction.html --> info-ProxySettingsAction_ja.html info.html --> info_ja.html 2. Psuedo translate the renamed files. See the attachment, which are included a multi-byte character (a multi-byte bracket "{"). 3. Create core_ja.jar from core.jar. core_ja.jar is contained the 3 html files above with psuedo translated Bundle_ja.properties files and tip??_ja.html files at org/netbeans/docs/tips. 4. Put core_ja.jar to <IDE_ROOT>/lib/locale directory. 5. Start IDE and check startup window. tip??_ja.html files showed in the lower pane of startup window can be i18ned. In other word, a multi-byte character inputed in tip??_ja.html files can be found. However I can't see it in 3 html files at the upper pane of starup window. I guess that IDE doesn't refer psuedo localized html files or IDE actually refer other html files included in other module's jar files.
Created attachment 1386 [details] Psuedo translated core.jar
Works for me (3.2 release): I put your core_ja.jar in lib/locale/ and started it with -locale ja:JP (after inserting more obvious comments like "JAPANESE" into e.g. info-NewTemplateAction_ja.html) and I saw them. If you are having problems with getting the 16-bit characters to display correctly, maybe you need a character encoding in an HTML <META> tag.
Switching to INVALID...
Now I see the problem (and why I could not reproduce with NetBeans)--this is an error on the part of the translators. In an FFJ build, there are FFJ-branded variants of some of these HTML files, but not others. Currently branding takes priority over locale when there is not a branded localized version of the resource. Thus e.g. info_f4j.html is being used in preference to info_ja.html. Refer to the URL above, info_ja.html represents Japanese translations of a NetBeans tip, whereas a translated Forte tip would be e.g. info_f4j_ja.html and would live in lib/locale/core_f4j_ja.jar.
I verified that the 2 html files are included in <FFJ_HOME>/lib/locale/core_f4j.jar. But the rest of 1 file is not match with the view of the startup window. I can verified that the correct info_f4j.html and info-NewTemplateAction_f4j.html are included in core_f4j.jar and they can be displayed in the startup window if they are translated to info_f4j_ja.html and info-NewTemplateAction_f4j_ja.html and packed in <FFJ_HOME>/lib/locale/core_f4j_ja.jar. But info-UpdateAction_f4j.html in core_f4j.jar can't be displayed in the startup window.
There is in info-UpdateAction.html in core.jar, it is in autoupdate.jar I guess, so info-UpdateAction_f4j.html belongs in modules/locale/autoupdate_f4j.jar.
Consistent use of the I18N keyword.
Resolved for 3.4.x or earlier, no new info since then -> closing.