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 86346 - I18N - Concurrent.properties cannot display Japanese characters
Summary: I18N - Concurrent.properties cannot display Japanese characters
Status: RESOLVED DUPLICATE of bug 90863
Alias: None
Product: utilities
Classification: Unclassified
Component: Properties (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@utilities
URL:
Keywords:
: 88207 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-10-03 00:13 UTC by naokoh
Modified: 2007-01-15 09:04 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Entering some multi-byte characters (108.07 KB, image/jpeg)
2006-10-03 00:18 UTC, naokoh
Details
Multi-byte chars garbled in Concurrent.properties (107.09 KB, image/jpeg)
2006-10-03 00:19 UTC, naokoh
Details

Note You need to log in before you can comment on or make changes to this bug.
Description naokoh 2006-10-03 00:13:50 UTC
Concurrent.properties cannot display any multi-byte characters.

Steps to Reproduce:

1.  Create a test case.
2.  Go to "Files" tab.
3.  Select Concurrent.properties -> Add Locale.
4.  Select ja_JP.
5.  View Concurrent.properties for ja_JP.
6.  Modify description by entering some multi-byte characters.
    --> See attached image mbyte_concurrent.jpg.
7.  Save it.
8.  View the same file again.
9.  Note that the characters are garbled.
    --> See attached image mbyte_concurrent_garbled.jpg.

Build used: 060929.
Comment 1 naokoh 2006-10-03 00:18:25 UTC
Created attachment 34778 [details]
Entering some multi-byte characters
Comment 2 naokoh 2006-10-03 00:19:03 UTC
Created attachment 34779 [details]
Multi-byte chars garbled in Concurrent.properties
Comment 3 naokoh 2006-10-03 21:51:25 UTC
Note from Jun:
==========================================================
This "feature" comes from NetBeans platform and is definately
not welcome here, at least we are not supporting it for now.

We need to see if there is a way to turn this "feature" off.

-----Original Message-----
I noticed that there is a "Add Locale" feature for
Concurrent.properties.

I have a question regarding this feature.
What is this for?  Does this work just like the bundle files
in Java?  How does the system detect which Concurrent.properties
file to use?
==========================================================

This also happens for the default locale, so it still needs to be
fixed.  Changed the summary to be less specific.
Comment 4 Jun Qian 2006-10-05 09:22:14 UTC
This problem is actually in NetBeans IDE. Try the same steps on any property
file (project.properties, for example), and you get the same behaviour.

For the localized Concurrent.properties, I don't think it's very useful. But if
you really want it to work like the bundle file in Java, please file a separate
enhancement request.
Comment 5 naokoh 2006-10-06 00:27:06 UTC
I agree and I don't think localized Concurrent.properties are necessary.  This
unwanted "feature" should be taken out to avoid confusions.  I will file a new
bug to address that.
Comment 6 naokoh 2006-10-06 00:34:37 UTC
Issue 86623 is created to address the unwanted localize Concurrent.properties
feature.

http://www.netbeans.org/issues/show_bug.cgi?id=86623
Comment 7 Jiri Prox 2006-10-30 09:38:13 UTC
*** Issue 88207 has been marked as a duplicate of this issue. ***
Comment 8 Marian Petras 2007-01-15 09:04:38 UTC
The problem is that the text editor for bundle files saves all files in encoding
ISO-8859-1 and all characters that cannot be saved with this encoding (i.e. all
non-Latin characters) are replaced with question marks when the file is saved.

This can be split into several basic problems:
1) There is such a limitation.
2) The user is not informed about the limitation.
3) There is no mechanism that would warn the user about possible loss of data.

The limitation should be mostly removed in the upcoming NetBeans 6.0 - see issue
#75906. There are several sub-issues reported covering the about described
problems - see issue #90863, issue #92514, issue #92515

*** This issue has been marked as a duplicate of 90863 ***