Hi Hussein Thanks for the info - I couldn't see anything relevant when I checked through the archives (but then you have to know what you're looking for...).
In the end it turned out that I needed to check both Option boxes in order to get the correct layout (you're right - it does offend my sense of good taste :) but then I'm used to an evironment where a closing bracket for a tag precedes the end-of-line marker instead of the other way about). I was having problems (still am) in getting reliable output to PDF using a set of tools developed internally in the company here. Setting certain text to <emphasis> under Simplified DocBook was sometimes emphasizing and sometimes not, and the only culprit I could see was the unfamiliar file format, hence my question. One thing I haven't found is a way to set the baseline directory for FO Converter (it constantly complains about not being able to find graphics (media)objects despite their presence in the same directory as the .xml file that references them - so no path should be necessary). If I use absolute references (the full path, including the drive letter) then all is OK - but then that prevents the book from being relocatable... I looked around to see if there was a reference source for that but haven't so far been able to locate one... Thanks for your feedback though - I'll be interested to see the next update while I continue to evaluate the product. Best, Peter -----Original Message----- From: Hussein Shafie [mailto:[email protected]] Sent: Monday, September 02, 2002 12:57 AM To: Peter Brooks Cc: xmleditor-support at xmlmind.com Subject: Re: File format problem Peter Brooks wrote: > > I've been using the evaluation copy of 1.3p3 XXE for about five weeks now > and I seem to have a problem with the .xml file format that is reproducible > despite uninstalling and reinstalling the product (the Windows > self-installer version with Java bundled file name xxe-m13p3-setup.exe). > > What happens is that the .xml file is being apparently corrupted in a > systematic way. A CR/LF is being inserted before the closing bracket of a > tag (>) instead of after it, yielding the following file structure: > > <book > ><bookinfo > ><title > >Venice Administrator</title > ><subtitle > >User Guide For:</subtitle > ><subtitle > > I have checked against a previously created .xml file that doesn't have this > problem and if I load it in, then SAVE AS, I get the same corruption. What you see is the unindented output. It is perfectly well-formed XML (i.e. not corrupted in any way), even if, as a human reader, it hurts your good taste. If you want to get a nice indented output, simply check the "Indent when DTD" toggle in the "Save" tab of the "Options" dialog box (in menu "Options"). You'll have to do that once for all because settings are automatically saved to a preference file. Of course, you'll have to repeat this setting each time you install XXE on a new machine, as it is not the default setting. > Is this a known problem, and is there anything I can do to resolve it, > please? This is a FAQ. PS: in the product which will be released tomorrow, indented output is the default setting.
