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 13781 - Welcome Panel does not show multibyte properly in ja_JP.UTF-8 locale
Summary: Welcome Panel does not show multibyte properly in ja_JP.UTF-8 locale
Status: CLOSED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P2 blocker (vote)
Assignee: Rostislav Levy
URL: http://Mon Dec 04 17:31:49 JST 2000su...
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2001-07-20 20:30 UTC by Ken Frank
Modified: 2008-12-23 10:30 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Welcome panel when run in ja_JP.UTF-8 locale on Solaris (13.95 KB, image/gif)
2001-07-25 19:36 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-07-20 20:30:05 UTC
In this locale, assuming the text in welcome panel has some multibyte,
which would be in case of localized product, the multibyte is not
seen or shown correctly.

This has been in bugtraq for a while as
4394603

Sometimes an exception is shown
Mon Dec 04 17:31:49 JST 2000sun.io.MalformedInputException: null
sun.io.MalformedInputException
        at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:152)
        at java.io.InputStreamReader.convertInto(InputStreamReader
.java:137)
        at java.io.InputStreamReader.fill(InputStreamReader.java:1
66)
        at java.io.InputStreamReader.read(InputStreamReader.java:2
49)
        at java.io.InputStreamReader.read(InputStreamReader.java:2
22)
        at org.netbeans.core.ui.WelcomePanel.setBrowserPage(Welcom
ePanel.java:695)
        at org.netbeans.core.ui.WelcomePanel.nextTip(WelcomePanel.
java:370)
        at org.netbeans.core.ui.WelcomePanel.restore(WelcomePanel.
java:340)        at java.awt.EventDispatchThread.pumpOneEvent(EventDispatch
Thread.java:103)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchTh
read.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.ja
va:84)

        at org.netbeans.core.ui.WelcomePanel.<init>(WelcomePanel.j
ava:118)
        at org.netbeans.core.ui.WelcomePanel.showGettingStarted(We
lcomePanel.java:728)
        at org.netbeans.core.Main$3.run(Main.java:292)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent
.java:154)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:331)
Comment 1 Jan Zajicek 2001-07-24 14:12:40 UTC
reassign to Rosta, UI owns the welcome panel
Comment 2 Ken Frank 2001-07-25 19:35:28 UTC
This happens on solaris in ja_JP.UTF-8 locale,
not ja locale, and users of localized release
will also run in this locale. And also, we have
seen that issues related to encodings and UTF-8
have been important in other parts of product.

Attached is gif of welcome window in this locale - the
messages that would show in the windows have both
English and multibyte in them.

--- Are there any other parts of product that use this browser
in this way ? We could check and see if problem is there also.
Comment 3 Ken Frank 2001-07-25 19:36:48 UTC
Created attachment 1973 [details]
Welcome panel when run in ja_JP.UTF-8 locale on Solaris
Comment 4 Ken Frank 2001-07-25 19:47:52 UTC
Additional info from original bug:

JEditorPane seems to be able to
display japanese html file which use
CONTENT="text/html;charset=EUC-JP"
(same as Japanese tips) in ja_JP.UTF-8 locale.  It looks F4J read the 
html file using InputStreamReader and fails in code conversion 
from byte to char.

tomonori.shioda@Japan 2000-12-08
Comment 5 pknakal 2001-07-26 09:52:20 UTC
I cannot reproduce this bug :-( I switched to ja_JP.UTF-8 and changed
the one HTML file in the Welcome panel to use EUC-JP encoding and then
UTF-8 encoding (for the HTML file) ... both works for me :-| Please
could you sent us the problematic HTML file (please in the zip or gzip
format ... or another archive) ???

Thank's

	Pat
Comment 6 Rostislav Levy 2001-07-31 08:07:09 UTC
It is an error in the Swing.
Patrik Knakal described in his document, that we will use coding ISO-
2022-JP, what is correct.
Comment 7 Quality Engineering 2003-07-01 16:04:00 UTC
Resolved for 3.4.x or earlier, no new info since then -> verified.

Comment 8 Quality Engineering 2003-07-01 16:30:39 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.