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.
Tried on solaris and windows 1. Create a new class that has multibyte as part of class name, variable name and method name. 2. From editor menu tools->generate javadoc 3. A popup appears asking if you want to now view the javadoc in browser, answer yes 4. The javadoc appears in external chosen browser and multibyte appears ok. 5. Go to the javadoc tab on explorer and click on the javadoc item for this class, say index.html. The javadoc appears in browser (either external browser or in browser below javadoc index search window) - the multibyte does not appear correctly but usually as ?????, sometimes as small boxes. 6. When viewing in the browser part of the javadoc search window, in the case when the multibyte appears correctly, or from doing a search and clicking on a result, there is still part of the document that the part at the bottom with word API (see attachment), that shows small boxes. In the external browser that shows multibyte ok, this section is all Japanese, and so assume it is from either a jdk file that has a Japanese version of these messages or from one of the non FFJ jars in lib/ext, since I'm not using a localized FFJ or JDK. 7. I noticed that the url used when the popup appears (after generating javadoc menu is chosen) is of the form file://localhost//path/javadoc/indexall.html whereas the url used when javadoc tab on explorer is used is http://ultralion:8082/resource/nbfs%3AQBpathQBpartpathirQBjavadoc/indexall.html 8. I varied the search engines to use both Japanese one and regular one. Also varied encoding, charset and locale in various javadoc and doclet project and options settings, but no effect; it seems this should work as default in users locale without needing to set these anyway. 9. Attachments: a. jdoc.searchwin.gif - javadoc index search window showubg in lower browser pane the correct multibyte and the part not correct. earch.browser.gif - the javadoc index search window and also external browser showing the same parts in each where multibyte is displayed correctly in ext browser and not in browser part of search window c. jdoc.viewfromjdoctab.explorer.gif - what the inaccurate multibyte looks like when javadoc is invoked from the javadoc tab on explorer. d. jdoc.viewfromedmenu.gif - what ok looking multibyte looks like when javadoc is invokded from eiditor menu show javadoc, or from popup shown after choosing editor menu tools->generate javadoc.
Created attachment 2264 [details] javadoc shown in browser part of javadoc search window
Created attachment 2265 [details] javadoc output in javadoc search window and from external browser
Created attachment 2266 [details] javadoc multibyte based on using javadoc tab on explorer
Created attachment 2267 [details] javadoc with multibyte shown in browser as invoked from editor menu
Divide problem to two parts. 1) Changes in Doclet can take no effect util restart, now known bug, path was send to RE. 2) if you go to FS a try to look to documentation, there is used NB filesystem -> please, on which locale your NB runs? Threre could be bad interaction bettwen US (or other) and Japanese locales. Petr
As to the two parts, I have further questions: 1. How does this other bug affect what we see in this bug ? 2. I'm not sure I understand about FS mentioned or where docs about NB filesystem are - can you point me there ? I was running in,on Solaris, the ja locale. On windows was using Japanese Windows 2000. And am using FFJ Pilsen FCS builds.
1)If you make some change in doclet as mentioned in poit 8, they can take no effect until restart. 2)There is probably some problem beetwen FS, HTTPserver and browser, javadoc only points to place, which have to be shown ( setURl(..) method )
Please could you test this issue for NB 3.3 dev trunk? Use tomorow build 10/8/2001.
I just have tested it for czech locale, it looks ok for both external and swing browser
If javadoc has correctly set encoding and you use direct path to file, javadoc is shown correctly. If you go via nbfs and http server, file is corrupted. Reassigned to HTTP server
Now it should be correctly passed to external browser too.
verified
Fixed in pilsenfixes
Resolved for 3.3.x or earlier, no new info since then -> closing.