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 65557 - I18N - can't profile project that has mbyte as part of project name
Summary: I18N - can't profile project that has mbyte as part of project name
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: Sun All
: P2 blocker (vote)
Assignee: Jiri Sedlacek
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2005-09-30 20:32 UTC by Ken Frank
Modified: 2007-02-20 18:08 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
image (4.42 KB, image/gif)
2005-09-30 20:35 UTC, Ken Frank 		Details
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 Ken Frank 2005-09-30 20:32:18 UTC 
created java project in which mbyte part of project name - it can run
ok, as is case for other types of projects

but when go to profile the project, get 
error in output window

multibyte in header of outputwindow tab that indicates project name
does not look like correct mbyte

-- see attached gif for both

my guess is that encoding is not being handled correctly - either utf8 being
used when enc of locale should be or visa versa

PS - java program with mbyte in its name/contents was able to be profiled
when proj name did not have mbyte, and the function name with mbyte did
seem to show ok in profiler windows.
Comment 1 Ken Frank 2005-09-30 20:35:52 UTC 
Created attachment 25376 [details]
image
Comment 2 iformanek 2005-10-03 16:40:14 UTC 
Assigning to Jirka for M10
Comment 3 Jiri Sedlacek 2005-10-10 11:12:45 UTC 
Could you please give me a hint how to reproduce this - I mean how to setup my 
English Windows XP & NB to be able to reproduce and fix the mbyte problem? I've 
tested Czech locale/special signs and everything worked fine for me.
Comment 4 Jiri Sedlacek 2005-10-11 14:17:00 UTC 
Default encoding was used for processing build.xml, but this file uses UTF-8.

Fixed for M10.
Comment 5 Ken Frank 2005-11-17 04:41:58 UTC 
verified

ken.frank@sun.com
Comment 6 Alexander Kouznetsov 2007-02-20 10:19:29 UTC 
Closing old issues
Comment 7 Alexander Kouznetsov 2007-02-20 18:08:43 UTC 
Reverting to original Target Milestone value changed by mistake. Sorry for
inconvenience.