On Wed, Oct 7, 2009 at 7:04 PM, Matt Wilkie map...@gmail.com wrote:
there is an open source
library for binary xml which might help with perfofmance on large
filse:
Thanks for this link. Most of my .leo files have nothing but @thin nodes in
them, so the actual .leo file is small. I'll
On Tue, Oct 6, 2009 at 3:41 PM, Ville M. Vainio vivai...@gmail.com wrote:
That document had some text I imported from a report file that had
form feed characters in each header. I had to delete the Ctrl-L
characters and it was then okay.
New versions of leo should strip those characters
On Wed, Oct 7, 2009 at 11:20 AM, Edward K. Ream edream...@gmail.com wrote:
OTOH, it would seem feasible to attempt error recovery in when
parse_leo_file when xml.sax.SAXParseException is thrown. We could strip
ctrl characters from the input, then pass the cleaned text back to sax.
I'll
New versions of leo should strip those characters on write, it was
probably saved with old version of leo.
Cases like this make me lose my faith in xml bit by bit.
I have some preliminary sketches in my head for using either sqlite or
zip files as tnode storage. This would also help small
On Tue, Oct 6, 2009 at 1:52 PM, Casey (kc) kccol...@gmail.com wrote:
In another post I described how I reverted back to 4.5.1 in order to
get Leo to run again.
Now I'm having issues that seem peculiar.
SAXParseException saying not well-formed (invalid token).
See:
May they all be this easy.
This is one of those RTFM situations where I'm going to have to
contribute all my pocket change to the kitty.
That document had some text I imported from a report file that had
form feed characters in each header. I had to delete the Ctrl-L
characters and it was then
