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 74212 - I18N - mbyte does not show ok in some created xmll files
Summary: I18N - mbyte does not show ok in some created xmll files
Status: CLOSED DUPLICATE of bug 64023
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: Sun All
: P2 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2006-03-30 19:43 UTC by Ken Frank
Modified: 2006-03-30 22:37 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
incorrect mbyte (37.31 KB, image/gif)
2006-03-30 19:44 UTC, Ken Frank
Details
showing ok mbyte (43.67 KB, image/gif)
2006-03-30 19:45 UTC, Ken Frank
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Frank 2006-03-30 19:43:32 UTC
seems like we had seen this in 5.0 but I dont see it under apisupport past i18n
issues but if filed then maybeit was really moved to other category; please let
me know if more general problem than just module project

steps
in ja locale 
module project with mbyte in name and new window component type with mbyte
in name

files created include TopComponentSettings and Wstcref xml
files

the mbyte in those files is not correct and thats why in gif
it also shows not correct in xml navigator

see other gif with comparison of a layer,xml
file created in module project that does show
the mbyte ok.

gifs are attached.

I don't know if other module project file-> new areas have this
situation when they create xml or other files.
Comment 1 Ken Frank 2006-03-30 19:44:31 UTC
Created attachment 29513 [details]
incorrect mbyte
Comment 2 Ken Frank 2006-03-30 19:45:15 UTC
Created attachment 29514 [details]
showing ok mbyte
Comment 3 Jesse Glick 2006-03-30 22:06:03 UTC
Ken please do not test apisupport with 5.5. The 5.5 release is focussed on J2EE
development, and apisupport is on a separate development track entirely. Test
either with 5.0 FCS, or with 5.0 FCS plus the soon-to-be-released 5.0u1
apisupport update.

Is this somehow related to issue #64023? Did you ever test the fix of that issue
in 5.0?

I doubt I would be able to reproduce myself (very likely Windows-specific) so I
would appreciate if someone from QA could attempt to do so.
Comment 4 Ken Frank 2006-03-30 22:35:58 UTC
Sorry, this indeed is dup of 64023; and will verify that one in nb5
as Jesse mentions, so am closing this as dup.

ken.frank@sun.com

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