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.

Bug 14652 - I18N - viewing javadoc from explorer does not show multibyte propertly in browser
Summary: I18N - viewing javadoc from explorer does not show multibyte propertly in bro...
Status: CLOSED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: Internal Server (show other bugs)
Version: -FFJ-
Hardware: Sun Windows ME/2000
: P2 blocker (vote)
Assignee: _ rkubacki
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2001-08-21 21:55 UTC by Ken Frank
Modified: 2003-07-01 09:34 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
javadoc shown in browser part of javadoc search window (12.52 KB, image/gif)
2001-08-21 22:09 UTC, Ken Frank
Details
javadoc output in javadoc search window and from external browser (6.07 KB, image/gif)
2001-08-21 22:11 UTC, Ken Frank
Details
javadoc multibyte based on using javadoc tab on explorer (11.99 KB, image/gif)
2001-08-21 22:13 UTC, Ken Frank
Details
javadoc with multibyte shown in browser as invoked from editor menu (9.62 KB, image/gif)
2001-08-21 22:14 UTC, Ken Frank
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Frank 2001-08-21 21:55:29 UTC
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.
Comment 1 Ken Frank 2001-08-21 22:09:24 UTC
Created attachment 2264 [details]
javadoc shown in browser part of javadoc search window
Comment 2 Ken Frank 2001-08-21 22:11:25 UTC
Created attachment 2265 [details]
javadoc output in javadoc search window and from external browser
Comment 3 Ken Frank 2001-08-21 22:13:24 UTC
Created attachment 2266 [details]
javadoc multibyte based on using javadoc tab on explorer
Comment 4 Ken Frank 2001-08-21 22:14:37 UTC
Created attachment 2267 [details]
javadoc with multibyte shown in browser as invoked from editor menu
Comment 5 Petr Suchomel 2001-08-22 09:53:34 UTC
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
Comment 6 Ken Frank 2001-08-22 16:56:38 UTC
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.
Comment 7 Petr Suchomel 2001-08-22 17:08:23 UTC
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 )
Comment 8 Petr Suchomel 2001-10-08 15:15:06 UTC
Please could you test this issue for NB 3.3 dev trunk? Use tomorow 
build 10/8/2001.
Comment 9 Petr Suchomel 2001-10-08 17:51:55 UTC
I just have tested it for czech locale, it looks ok for both external 
and swing browser
Comment 10 Petr Suchomel 2001-10-17 10:39:49 UTC
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
Comment 11 _ rkubacki 2001-10-17 15:14:00 UTC
Now it should be correctly passed to external browser too. 
Comment 12 gautham mudra 2001-11-08 04:07:31 UTC
verified
Comment 13 Petr Pisl 2001-11-29 08:49:14 UTC
Fixed in pilsenfixes
Comment 14 Quality Engineering 2003-07-01 09:33:51 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 15 Quality Engineering 2003-07-01 09:34:52 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.