The project types and some special modules need an update to use FileEncodingQuery.
The project should provide the FileEncodingQueryImplementation in its Lookup and
the javac target in the build-impl.xml should use -encoding argument (see
The most of DataObject should work as they are when they are derived from
DataEditorSupport, but if the project encoding shouldn't be used or the editor
is derived from CloneableEditorSupport the DataObject need an update (see
Some special modules which directly read|write the FileObject content should be
updated to use the correct encoding, for example search module.
should projects of enterprise, scripting, uml and other types of projects
or file types not covered by issues filed under this issue (see depends on issues) -
should their be tasks filed by developers of those projects ?
Since its one nb6 now ?
If so, I can write the iteams of those areas if someone can tell me the wording
of what to say and ptrs to applicable issues and perhaps contact person they
can ask about it.
Every project type should provide the FileEncodingQueryImplementation. There is
already an issue for j2ee project (enterprise). The scripting/schliemann should
be fine. The scripting/ruby has it's own project type I've added new issue: #99344.
The uml/project: #99345. If you know about some other project type not covered
by dependent issues create a task for it.
With state of this one as resolved, does it mean all depends on bugs are now
PS I created 100178 and 100312 on enterprise and visualweb; I'll create one
on identity in case something needs to be done with that.
The issue is not yet resolved, it contains opened dependent issues. This issue
will be resolved when all the dependent issues will be resolved.
added 67340 on css files and feq
moving opened issues from TM <= 6.1 to TM=Dev
Change of default owner.
The opened issues are from visualweb and uml. Probably fixed.
#97867 partially fixed by open|save in encoding (contrib/encoding).
Close enough; no reason to have this open.