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 41998 - I18N - startup messages in terminal window look garbage
Summary: I18N - startup messages in terminal window look garbage
Status: VERIFIED FIXED
Alias: None
Product: installer
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P2 blocker (vote)
Assignee: mslama
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2004-04-15 03:21 UTC by ohsumi
Modified: 2006-01-04 15:48 UTC (History)
1 user (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 ohsumi 2004-04-15 03:21:24 UTC 
Tested build is NB3.6 ML build 200404121736.

When running installer, there are some
platforms/locales that startup messages in a
terminal window look garbages.

		ja	    ja_JP.PCK	  ja_JP.UTF-8
--------------------------------------------------------	
Sol9 SPARC	OK (Ja)	    OK (En)	  OK (En)
Sol8 SPARC	OK (Ja)	    OK (En)	  OK (En)
Sol9 x86	OK (Ja)	    NG (garbage)  NG (garbage)
linux RH9	OK (Ja)	    -- 		  --
JDS QS		OK (Ja)     --            NG (garbage)


This is IS bug, but installers in the past
releases had a workaround.

Also, system default locale of JDS QS is
ja_JP.UTF-8, so users can always see
garbage characters.

For three parts of "NG (garbage)", is it possible
that installer will be updated that English
startup messages appear like Solaris SPARC?
Comment 1 ohsumi 2004-04-15 03:27:55 UTC 
I hope that this problem will be fixed by ML RC1 build on 4/16.
Could you please evaluate asap if we can have a workaround?
Comment 2 George Hernandez 2004-04-15 21:57:34 UTC 
This is an InstallShield issue. There is a patch for the solaris-x86
platform that I gave to RE. They have installed it and are now using
it. This problem should now be fixed for this platform. For the JDS
platform, there is no patch. InstallShield asks for 30 days in order
to create a patch so getting something for the ml release is not
realistic. I've talked with Ming who thinks we can waive this as long
as the solaris-x86 patch is working.
Comment 3 _ ttran 2004-07-27 17:41:21 UTC 
can someone check if the new 4.0 installer works better?  We migrated
to  InstallShield Multiplatform 5
Comment 4 _ ttran 2004-08-02 16:51:49 UTC 
just verified that the new installer for NB 4.0 works OK on JDS
Quicksilver ja_JP.UTF-8.  So it seems they fixed the bug in ISMP 5
Comment 5 Michal Mocnak 2005-07-12 10:38:32 UTC 
Verified