[oXygen-user] "content is not allowed in prolog" using Oxygen for MXML files

[George Cristian Bina]

Hi Joshua,

If you open your message from the list archive
http://www.oxygenxml.com/pipermail/oxygen-user/2006-June/000804.html
in oXygen for instance, you can see that the line you entered as the 
beginning of your document starts with a character encoded as a 
character reference with the code 65279

& #65279;<?xml version="1.0" encoding="utf-8"?>

(one space added after the first & to avoid having the character 
reference replaced with the actual character by some email clients)

65279 is in hexa FEFF, that is the BOM for UTF-16 Big Endian encoding. 
Your document specifies UTF-8 as encoding thus the UTF-16 BOM is not 
ignored when opening the document and ends up as an invisible character 
before the XML header.

Best Regards,
George
---------------------------------------------------------------------
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com


Joshua Noble wrote:
> 
> 
> I'm trying to use Oxygen to edit MXML files (Macromedia Flex). 
> Everything works fine except that this error always appears: content is 
> not allowed in prolog. What's up with this? Here's the line it chokes on:
> 
> <?xml version="1.0" encoding="utf-8"?>
> 
> This is the way all Flex files start and there don't seem to be any 
> problems there. Anybody know what's up?
> 
>