Bug 149405 - I18N - visual designer component project does not have encoding property
I18N - visual designer component project does not have encoding property
Status: RESOLVED WONTFIX
Product: javame
Classification: Unclassified
Component: Visual Designer
6.x
Sun All
: P2 (vote)
: 6.x
Assigned To: Karol Harezlak
issues@mobility
: I18N
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-07 19:17 UTC by Ken Frank
Modified: 2008-10-08 10:24 UTC (History)
0 users

See Also:
Issue Type: DEFECT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Frank 2008-10-07 19:17:10 UTC
there is no project encoding property for the visual designer custom component project type

if this is similar to netbeans module project, and its hardcoded to utf-8 project encoding then it can be closed since
that has been decided to be ok for those kinds of projects.
(am assuming the needed parts of feq are implemented within that context ?)

PS I used non ascii in name of the project and in explorer, the asian characters
did not show correctly, but if this is like rule for other mobility projects,
its not an issue since non ascii is not allowed in project name or path for mobility,
due to limitations of wtk (is this still a limitation of it ?)
Comment 1 Karol Harezlak 2008-10-08 10:24:11 UTC
Basically MobilityCustom Component Support project is Netbeans Module Project with few additional wizards and
pre-generated classes. It is based on the Netbeans Module Project and same rule applies to it.

As far I know there is no change over WTK, we still using 2.5.2 version so  "non ascii in name of the project and in
explorer" problem persists. Things may change with release of the new Java ME SDK 3.0 but It's hard to say it right now.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo