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 122330 - I18N - encoding choice in wizard of freeform from ant not seen in project encoding property
Summary: I18N - encoding choice in wizard of freeform from ant not seen in project enc...
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Freeform (show other bugs)
Version: 6.x
Hardware: Sun All
: P3 blocker (vote)
Assignee: Tomas Zezula
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2007-11-19 20:23 UTC by Ken Frank
Modified: 2011-04-06 14:50 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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-11-19 20:23:34 UTC 
1. I noticed that create project from existing source with ant script has, in a wizard
panel, a choice to set the encoding or, I assume, to accept the encoding value there
which is  that of the current active project encoding.

for a java project with existing ant:

But if change the value or don't change it, after the project is created, the
project encoding property says <No Encoding>, which seems to mean user needs
to change it again, which could be confusing for them, or that they will not even
look at the project encoding property since they assumed, as part of using the wizard,
that the encoding they accepted as default or changed to is the one to be used.

for a web project with existing ant

if change the encoding in the wizard, the new encoding is shown in project properties
but if not change it, it shows as <No Encoding> in project properties.


Also, in wizards for create freeform project with existing source (not the existing ant
script), there is no panel for choosing encoding and newly created project uses global
project encoding value at the time of its creation.

- should the encoding choice be part of this wizard, or is it that the wizard of the
existing source with ant should not have the encoding choice part ?
Comment 1 Ken Frank 2007-11-19 20:24:51 UTC 
added relnote keyword; please provide some text for release note/workaround here
soon.

ken.frank@sun.com
Comment 2 Jesse Glick 2007-11-19 20:30:46 UTC 
"wizards for create freeform project with existing source (not the existing ant script)" is an oxymoron; this would be a
regular project, not a freeform project. I don't know if that should have an encoding choice in the wizard, but that
would be a separate RFE if so. Actually I was not aware that the freeform creation wizard was supposed to let you set
encoding - this may be a mistake.
Comment 3 Ken Frank 2007-11-19 20:45:05 UTC 
thanks for clarifying about that its only the ones with existing ant script that are
considered as freeform.

should a separate issue be filed on web also due to behavior of the web project as mentioned below ?
"for a web project with existing ant
if change the encoding in the wizard, the new encoding is shown in project properties
but if not change it, it shows as <No Encoding> in project properties."


as to the choice in the wizard for encoding, I had thought that was provided as a
service to the user at that point, rather than need to go to project properties
and change it there after project creation (which is why I thought perhaps the
project with existing sources wizard might want to have it also)

ken.frank@sun.com
Comment 4 Milan Kubec 2007-11-20 07:46:53 UTC 
Please provide *exact* steps to reproduce, because I'm not able to reproduce this behavior except one situation and that
is when you don't select any source folder when creating a project by wizard. Which is kind of very special situation
when user create a project and don't assign any sources for it (such a project doesn't make any sense). After that when
user finally selects a source folder in project properties he also needs to select encoding, but that's IMO minor UI
problem. 

If this is the original problem of this issue it's not P2 priority IMO.

What is the problem with setting up encoding of the project in creation wizard? Especially for freeform project.
Comment 5 Ken Frank 2007-11-20 16:15:01 UTC 
steps, using web -> web application with existing ant script

1. new wizard appears
2. name and location panel - fill in location of the existing project
3. other sections of that wizard page is filled in
4. build and run panel - accept defaults

5. web sources panel - accept defaults
6. source package folders panel

a. source package folder is prechosen already

b. encoding value is that of the current global project encoding; I dont change it

7. next 2 panels - accept defaults and finish

8. project is created - encoding value of project properties states <No Encoding> as originally
reported.

9. HOWEVER, if in source panel, one adds another src folder, which for this project there is
another src folder at top level of the project, and then complete the wizard,
then the encoding shown in project properties is valid.


9. the case for java project is not valid, since at least for the java project I am using,
the sources panel is not seeded with anything, so it means I do need to choose a src folder,
which avoids the problem mentioned above for web project.

ken.frank@sun.com
Comment 6 Milan Kubec 2007-11-21 15:55:44 UTC 
In such case it should be probably fixed in web/freeform. I don't think that this issue needs to be mentioned in Release
notes, since web/freeform project is used by minority of users and there is really easy workaround.
Comment 7 Milan Kubec 2008-01-04 09:00:57 UTC 
Removing RELNOTE kw and lowering priority.
Comment 8 Ken Frank 2008-01-10 20:10:07 UTC 
based on last comments - should this be changed to web/freeform ?

or file new issue there and leave this one ?

(we want to see if this can be fixed for 6.1)

ken.frank@sun.com
Comment 9 Lukas Hasik 2008-04-10 21:36:47 UTC 
moving opened issues from TM <= 6.1 to TM=Dev
Comment 10 Ken Frank 2008-04-14 22:18:51 UTC 
moving to web category as suggested is issue comments.

ken.frank@sun.com
Comment 11 Milan Kubec 2008-06-20 12:32:54 UTC 
Please evaluate. Thanks.
Comment 12 David Konecny 2008-06-22 22:23:33 UTC 
Why was this passed to web? Encoding is managed by java part of freeform.
Comment 13 Sergey Petrov 2009-04-15 13:09:03 UTC 
reproducible for java freeform project, select encoding in wizard and got "no encoding" in properties. 6.7m3
Comment 14 Antonin Nebuzelsky 2010-01-11 04:28:59 UTC 
Changing the default component owner to tzezula.
Comment 15 Tomas Zezula 2011-04-06 14:49:54 UTC 
Works for me.

When encoding is not changed in the Wizard (the wizard offers native OS encoding) no encoding element is stored in the project.xml and the project properties correctly displays OS native encoding (MacRoman in my case).

When encoding is changed in the Wizard the encoding element is stored in the project.xml and the project properties correctly displays the chosen encoding.
Comment 16 Tomas Zezula 2011-04-06 14:50:27 UTC 
Tested both with j2se and web.