Hi Keith, BrailleBlaster uses the xom package for handling xml. That is much easier than using a sax parser directly. Look at the method walkTree in DocumentManager. Keeping track of changes and reflecting them back to the xml document is indeed a hard problem. I am thinking of using customized StyledTextContent classes. See the various abstract classes in the wordprocessing package. I don't understand the error lmessage. Is there any other information? There is certainly a lot to do in displaying and editing documents. I think we will be using xsl stylesheets to format the display properly. Thanks, John On Thu, May 03, 2012 at 09:45:29AM -0400, Keith Creasy wrote: > John, first I'm dealing with the problem of how to save changes as I know you > are and here is the approach I plan to use. I think we are going to try just > keeping a map by ID of elements that have been changed. Then, when saving, we > are actually going to read the original document using a SAX parser but when > we hit an element that is changed we'll write out the changed element rather > than the original one. This is all done in a temporary file. We'll use temp > files anyway because I want to work with the NIMAS archive directly without > the user having to unpack it. > > Secondly, I got LibLouis and LibLouisUTDML to build but when I run Braille > Blaster I get a "major/minor revision conflict". I think the version it sites > is 50.1 but I could be mistaken. > > Thanks. > > Keith > > > -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities