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 64023 - I18N - plugin module project - top component xml file does not show multibyte ok
Summary: I18N - plugin module project - top component xml file does not show multibyte ok
Status: CLOSED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Templates (show other bugs)
Version: 5.x
Hardware: Sun All
: P2 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords: I18N
: 74212 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-09-10 04:27 UTC by Ken Frank
Modified: 2007-07-06 20:45 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
gif (37.54 KB, image/gif)
2005-09-10 04:28 UTC, Ken Frank
Details
Screenshot (68.71 KB, image/gif)
2006-01-26 09:40 UTC, Marek Grummich
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Frank 2005-09-10 04:27:56 UTC
I don't know which subcat this goes in;please transfer it.

Create a new netbeans plugin module - module project and use mbyte in its name

then choose file -> and choose netbeans module component -> windows component

and a java and 2 xml files are created with name seeded as TopComponent

in the xml file, the mbyte that is part of the module project name path
does not show correctly. see gif for xml file and on left in file explorer,
the project name with mbyte showing ok.

this might be that encoding is being read as utf8 when should be that of
system locale or visa versa.

Can you check other plugin project types and file->new types
java, xml or html files also to make sure encoding is ok ?
Comment 1 Ken Frank 2005-09-10 04:28:43 UTC
Created attachment 24672 [details]
gif
Comment 2 Jesse Glick 2005-09-11 16:41:03 UTC
I see a place where platform default encoding is used. Probably every XML file
touched by module development should use UTF-8. I will try to fix but Ken you
will need to verify.

Note that, as usual, if you just set your platform default encoding to UTF-8 you
should not have such problems.
Comment 3 Jesse Glick 2005-09-12 22:18:06 UTC
Ken please verify:

committed   * Up-To-Date  1.16       
apisupport/project/src/org/netbeans/modules/apisupport/project/CreatedModifiedFilesFactory.java
committed   * Up-To-Date  1.2        
apisupport/project/src/org/netbeans/modules/apisupport/project/ui/wizard/winsys/templateSettings.xml
Comment 4 Tomas Danek 2005-12-12 12:10:26 UTC
please verify..thanks
Comment 5 Tomas Danek 2005-12-14 12:49:12 UTC
x - sorry, wrong mark
Comment 6 Tomas Danek 2005-12-14 12:50:03 UTC
waiting to verify.
Comment 7 Marek Grummich 2006-01-26 09:39:16 UTC
Ken ask me to verify this issue, but if I repeate steps above, I have not
correct character in xml file also. Please, look at the attachment. (Windows,
Japanese)
Comment 8 Marek Grummich 2006-01-26 09:40:41 UTC
Created attachment 28604 [details]
Screenshot
Comment 9 Jesse Glick 2006-01-26 18:18:25 UTC
Probably best to verify with some less problematic character set like Cyrillic
that you can be sure the glyphs are available for but which is not in either
ISO-8859-1 or (if not UTF-8) the platform default encoding.
Comment 10 Ken Frank 2006-03-30 22:35:57 UTC
*** Issue 74212 has been marked as a duplicate of this issue. ***
Comment 11 Ken Frank 2006-03-30 22:36:21 UTC
*** Issue 74212 has been marked as a duplicate of this issue. ***
Comment 12 Ken Frank 2007-05-27 03:09:22 UTC
reopening - happens in latest nb6 - same description and as per attachment.

am in, as before, solaris euc jp (ja) locale 

will try running ide in ja utf8 locale and see what happens and add info here.

ken.frank@sun.com
Comment 13 Ken Frank 2007-05-27 03:23:58 UTC
I think situations described here is same as 101076, which is still open and applies
to nb6 - so if that is true, please let me know and I'll
close this one since it was on nb5.
Comment 14 Jesse Glick 2007-06-01 01:26:52 UTC
Probably issue 101076.