On Sun, Jan 4, 2009 at 8:29 PM, mdb <[email protected]> wrote:
> I am a new user of leo and find it most powerful and useful. I did run > into a XML parsing problem that was able to track down and figure out > and I thought to post what I found. > > The problem came from pasting in a block of text from a PDF file into > a a node text window and the text happened to have an 'unprintable' > character. After saving the .leo file and reading back the file the > next day, in the whole outline and file became unusable until I > manually tracked down and deleted the bad character in the XML file. > > SAXParseException: <unknown>:51:55: not well-formed (invalid token) Thanks for this report. There is a FAQ entry that discusses old versions of Leo that write invalid xml files, but your report indicates there is a new way to get this message. BTW, where you using the qt gui? If so, the paste logic may be suspect. And the problem could be called a python SAX xmlreader problem, and I am not > sure if it is possible to fix in leo code... Surely, a better error message would help, but the more important problem is that present version of Leo can write an invalid xml file. I would have thought the low-level write code would be solid. Presumably a new guard is required. Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
