97854 was on implementing feq for new project encoding property
for freeform projects
for a new java project from existing source with ant script,
the wizard shows the global encoding value
(in this case its been changed by a previous project to not be utf-8)
the encoding choice in the wizard is not changed.
but after the project is created and opened, the encoding properties
shows "no encoding" rather than the encoding that is the current
global value and that was not changed when doing the wizard.
this does not happen for a new java project with existing sources.
Other question - for web and enterprise and other projects that have choices for create a project using existing sources
with or without ant scripts -
- is the implementation and use of global encoding property the same code in the same module as for the java ones, or
is it implemented separately by each project ?
When creating the project - did you select any source package folder? Because encoding is bound with package folder and
if the project doesn't have any package folder there is no encoding. Please verify that. I'm not able to reproduce when
selecting some folder as package root.
Yes, when selecting src folders for the project, the global encoding is shown ok.
If its the typical use that src folders would be chosen then this issue can be closed.
Yes, it's required to select any folder to actually safe project encoding, because the encoding is bound to folder.
Closing as invalid.
To your question - each project type implements its own file encoding handling.