Closed GoogleCodeExporter closed 8 years ago
Hi,
This is a very new feature. It was added in the previous version and is not
complete,
it is just a basic working implementation right now. Ultimately I plan to have
a gui
for adding new handlers as the xml is really just the protocol.
I am not sure at the moment why its failing to parse the xml file on your
machine I
will have to try it later when I get a chance. But I would look at it with hex
editor
and see if there may possibly be some hidden characters at the start of the file
possibly there is a BOM that is needs to be stripped prior to feeding it to the
parser.
Also your file is associating it self with ID_LANG_PYTHON for which there is
already
a handler for so it would be easier to just edit the settings in the Launch
configuration dialog unless you wanted to associate the handler with a
different file
type.
Original comment by CodyPrec...@gmail.com
on 1 Feb 2010 at 2:45
Hi Cody,
I dumped one of my XML files with 'hexdump', as you suggested. Attached are
jal.edxml
and resulting dumped jal.hexa. I don't see any BOM char or other weird chars.
As a workaround (which doesn't explain what's really going on), instead of
using
sax.parseString(string,handler), you can use sax.parse(filename,handler) in
synxml.py. I tried and it seems to work, so I really wonder why this utf8
decoding is
needed...
xml.__version__ says "41660". Just in case...
Cheers,
Seb
Original comment by sebastie...@gmail.com
on 5 Feb 2010 at 7:18
Attachments:
Hi,
The decoding is needed because Editra expects all internal text data to be of
Unicode
type and not of string type.
Luckily sax.parse does appear to render unicode tokens so switching to it work
just fine.
Thanks,
Cody
Original comment by CodyPrec...@gmail.com
on 5 Feb 2010 at 9:53
Original issue reported on code.google.com by
sebastie...@gmail.com
on 1 Feb 2010 at 2:22Attachments: