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 101076 - I18N - multibyte in file contents of some module project file->new items do not show correctly in some asian locales
Summary: I18N - multibyte in file contents of some module project file->new items do n...
Status: VERIFIED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords: I18N
Depends on: 99232
Blocks: 97852
  Show dependency tree
 
Reported: 2007-04-15 17:39 UTC by Ken Frank
Modified: 2007-10-30 04:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
image (52.27 KB, image/gif)
2007-04-15 17:50 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 2007-04-15 17:39:00 UTC 
scenario is running in solaris ja locale, whose default encoding is euc.

create a module project that has multibyte in its name, and with code name base
and display name with multibyte (I dont know if later 2 are important here)

then choose file-new and create an installer and the package name used has the
multibyte in it since based on the project name.

look at installer.java and see that in the java file, the package name does not
show the
multibyte properly.

-- then run in solaris ja_JP.UTF-8 locale and do same actions -
the package name in the java file does look correct.

many users still use solaris ja euc locale or windows japanese
locale, whose encoding is based on shift jis 


this happens for the generated java files when creating 
also wizard, file type, installer, options panel, template and perhaps
some others from file->new of  netbeans module development.

I dont know about code inserted into the java progam once it is generated.

see attached gif - explorer shows the mulibyte correctly whereas in editor
its incorrect at package, class and component name.

.
Comment 1 Ken Frank 2007-04-15 17:50:13 UTC 
Created attachment 40933 [details]
image
Comment 2 Jesse Glick 2007-04-15 18:14:00 UTC 
CreatedModifiedFilesFactory.copyAndSubstituteTokens needs to use FEQ. Strange, I
could have sworn this was filed separately already, but I cannot find it.
Comment 3 Jesse Glick 2007-04-15 18:15:24 UTC 
BTW as I said already, this should affect only apisupport-specific templates,
not generic templates like empty Java files.
Comment 4 Ken Frank 2007-10-01 20:50:55 UTC 
update - still seen in current builds in module or library projects.

can/should this be fixed for nb6 ?

ken.frank@sun.com
Comment 5 Ken Frank 2007-10-10 19:20:48 UTC 
note to myself that once fix is done for this to make sure firefox can find generated javadoc
as per issue with other projects like 118174

ken.frank@sun.com
Comment 6 Jesse Glick 2007-10-10 21:36:29 UTC 
Can probably be handled as part of usage of FreeMarker for templates.
Comment 7 Jesse Glick 2007-10-23 21:10:44 UTC 
Ought to have been fixed as part of issue #99232, though I can hardly verify myself since I use Ubuntu with UTF-8 and
this sort of thing is never broken to begin with.
Comment 8 Ken Frank 2007-10-30 04:21:25 UTC 
verifying - the multibyte looks ok.

will open separate issue for the record on javadoc not being found on solaris
by firefox if there is mbyte in the project name/path and in pkg
name when user in euc vs utf8 ja locale, or even if mbyte is in just path to project or project name and not
in pkg name, perhaps since utf8 is being used for apisupport modules ?

for other projects that have this problem, it usually when there is some conflict
in how browser is viewing encoding of the path to project and paths/filenames within
project that has 
some parts and euc for other parts of the path, but browser can handle just
one encoding. see 118174 on this for j2se project.

But if this problem for apisupport, for the case of just mbyte in project path,
for example, and nowhere else in path or file name, shouldnt that at
least work ?

will file separate issue
am verifying this one.

ken.frank@sun.com