Community
Participate
Working Groups
As per bug 189353, xml file types need to be treated differently from files that are considered "binary" or "text". For known XML file types, RSE, always downloads as binary and then determines encoding via inspection of the text. However there are some file types (for example WSDL and XSD) that are XML yet RSE is not aware of that and therefore is unable to treat appropriately unless there's a means to indicating that. I think the best way to resolve this is to use the remoteFileTypes extension point to include an "xml" file type.
Created attachment 141223 [details] patch with changes for xml file type enhancement Here is a patch to show the code changes needed. Due to the api changes, I'm not sure which version this could go into - so I've left out the @since tags and left the manifest files unchanged.
Technically, the changes to ISystemFileTypes are API breaking, because you are adding methods to an interface and the interface is not marked @noimplement. From my reading of the source, though, it looks like nobody could ever meaningfully implement ISystemFileTypes, so not marking the interface @noimplement was probably an oversight. I filed bug 304170 for discussing this and tracking it. If I am right, then please have bug 304170 fixed -- then the version number may remain at 3.2 and the @since tags may remain as they are now.
I've committed the changes to cvs.