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 19467 - I18N-Bean Shell does not display multibyte characters
Summary: I18N-Bean Shell does not display multibyte characters
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: languages (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P3 blocker (vote)
Assignee: Milos Kleint
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2002-01-16 00:48 UTC by gautham mudra
Modified: 2008-08-01 15:44 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description gautham mudra 2002-01-16 00:48:44 UTC 
The Bean Shell does not display multibyte characters.

Steps to reproduce the bug:
Locale:	Ja_jp.UTF8
1. go to view->Scripting Console
2. Choose the "Bean Shell" as the scripting language.
3. give a print statement that prints a multibyte character.
4. press "execute"

The english characters are printed properly but the multibyte characters
are not printed.
I am attaching a snapshot to give a better understanding
Comment 1 Milos Kleint 2002-01-17 14:55:41 UTC 
do the other  scripting types display the japanese characters correctly?

If so, then the problem might be within the BeanShell which is not
part of netbeans.
Comment 2 gautham mudra 2002-02-04 20:50:14 UTC 
The multibytes are not properly displayed in both Bean Shell and 
Dynamic Java.So what should be the action item to rectify this bug.
Comment 3 Milos Kleint 2002-03-12 10:22:23 UTC 
update: I've figured the problem comes from the fact that both djava
and bshell require a ASCII only stream, any non-ascii characters need
to be converted to unicode escaped sequences..
Comment 4 Milos Kleint 2002-03-12 15:44:27 UTC 
I believe I fixed the problem (*fingers crossed*). In dev build on
13/Mar/2002 and later.

Can you please verify the fix? thanks a lot..
Comment 5 gautham mudra 2002-08-01 17:46:02 UTC 
verified on RC1 build.closing the issue.
Comment 6 Jesse Glick 2002-12-23 16:47:57 UTC 
Consistent use of the I18N keyword.