BOM is killing me

[bom]

"Could not associate XSD! Content is not allowed in prolog".

I am trying to associate a schema with a document. The above message is the result. From much googling, I gather that the schema (and possibly the doc) have a hidden first character, namely, a BOM. And in fact I've looked at the schema with a hex-editor, and discovered the dreaded ef bb bf. Changing the encoding to UTF-16 or iso-8859-1 doesn't fix it. If I remove the offending bytes in the hex editor, I just get gibberish. Same result from using a script to do same.

What to do? And could this have anything to do with the fact that I'm running on XP, editing files that reside on a Solaris box via sftp?

Any and all suggestions appreciated.

Thanks,
bom

[bom]

It appears to be a network thing - everything works fine if I run Oxygen on the Solaris box. And in fact the extra bytes show up. However, XWindows is prohibitively slow - surely someone has encountered this when editing remotely?

[bom]

after more investigation, it seems to be the fault of my sftp program. We need to use secure ftp, which Oxygen doesn't support. I found what seemed a nifty solution, a program that lets one mount an sftp connection like a network drive; it seems to be the culprit, adding bytes (including BOM) along the way.

Sorry for the alarm. If anyone has a suggestion as to how to securely (i.e. over SSL) edit remote files, please chime in.

Thanks,
BOM

[sorin_ristache]

Hello,

In the current version (7.2) you can use WebDAV over HTTPS. The next version of oXygen will add SFTP support.

Regards,
Sorin