Thanks for those opening that errant XML file of mine.
I never could get it to open without having to abort OOo. So, I created a brand-new empty XML file with the same filename in its place and copy-and-pasted the contents with oXygen from the original. So, now it works fine.
Whatever was wrong with that file, I'll never know. It could easily open with three other XML editors, but it always choked (locked up) on OOo Writer, so that it then had to be aborted via the Windows Task Manager.
I'm in the process of converting the OOoAuthors Writer Guide small book back into its constituent chapters, then into XML for its DocBook structure and then create a stylesheet for Writer's formatting afterwards. Also, I will develop FrameMaker 8 EDD files for them using standard DocBook 4.1.2, 4.5, and 5. But first, it'll have to work faithfully with DB 4.1.2.
Chapter 1 was done manually so I could get a feel for what Writer came up with its XML rendition. oXygen was nice and easy to work with, so that application was the ML editor used for chapter 1. Then, I'll probably develop a conversion table using the DOC version of the other Writer Guide chapters and then use FM 8 to build the XML files for them. That's seems to be one way to go.
Perhaps, Writer has a similar capability to convert a conventional ODF into XML along the same lines as FrameMaker does to FM or DOC files. I want something that minimizes my workload in producing the XML conversion.
The chapter 1 file still needs its character styles added in DocBook structure. More later...
I periodically post some of what I'm doing on the resurrected OOoAuthors forum (set up about a week ago) (http://technicaleditor.freeforums.org/) which will eventually have more OOoAuthors content matter added to it. Anybody can post there about OOoAuthors matters if they want. Or about other editing areas.
Gary -- Gary Schnabl 2775 Honorah Detroit MI 48209 (734) 245-3324
