Many thanks! That pointed me to the right solution...in my old environment, I was defining an entity for each chapter, then invoking it. Because they were basically cut/paste into the base document, I couldn't have headers on the files.
I tested with adding an appropriate header and switching to Xinclude, and it seems to understand that the chapters are actually DocBook documents, and...at least so far...doesn't seem to mess with formatting inside screen elements. Thanks! On Fri, Sep 21, 2012 at 3:19 AM, Hussein Shafie <[email protected]> wrote: > On 09/21/2012 01:55 AM, Mike Vevea wrote: > >> I've just started working with xxe. I originally thought that this was >> just related to the spell checker, but it appears to be worse than that. >> >> I work in DocBook, with frequent use of the <screen> element. >> >> I've found that for some reason, my screen elements are periodically >> reformatted, losing the (very critical) appearance. >> >> For example, I have a section which originally said: >> <screen width='75'> >> neustar.biz <http://neustar.biz>. 60 IN A 156.154.164.103 >> neustar.biz <http://neustar.biz>. 1800 IN NS pdns1.ultradns.net >> <http://pdns1.ultradns.net>. >> neustar.biz <http://neustar.biz>. 1800 IN NS pdns2.ultradns.net >> <http://pdns2.ultradns.net>. >> neustar.biz <http://neustar.biz>. 1800 IN NS pdns3.ultradns.org >> <http://pdns3.ultradns.org>. >> neustar.biz <http://neustar.biz>. 1800 IN NS pdns4.ultradns.org >> <http://pdns4.ultradns.org>. >> neustar.biz <http://neustar.biz>. 1800 IN NS pdns5.ultradns.info >> <http://pdns5.ultradns.info>. >> neustar.biz <http://neustar.biz>. 1800 IN NS pdns6.ultradns.co.uk >> <http://pdns6.ultradns.co.uk>. >> neustar.biz <http://neustar.biz>. 1800 IN SOA pdns1.ultradns.net >> <http://pdns1.ultradns.net>. >> sec_grp.neustar.com <http://sec_grp.neustar.com>. 1311620677 10800 3600 >> 604800 600 >> neustar.biz <http://neustar.biz>. 43200 IN MX 2 ns6.neustar.com >> <http://ns6.neustar.com>. >> neustar.biz <http://neustar.biz>. 43200 IN MX 2 ns7.neustar.com >> <http://ns7.neustar.com>. >> neustar.biz <http://neustar.biz>. 1800 IN TXT >> "google-site-verification= >> 7V6yaWsW0q7fh3JYXAuYOnpyE4BF8J**A2RCawOaSrUCs" >> neustar.biz <http://neustar.biz>. 1800 IN AAAA 2610:a0:16:4::1 >> >> </screen> >> >> but which was turned into: >> <screen >> width="75"> neustar.biz <http://neustar.biz>. 60 IN A >> 156.154.164.103 neustar.biz <http://neustar.biz>. 1800 IN NS >> pdns1.ultradns.net <http://pdns1.ultradns.net>. neustar.biz >> <http://neustar.biz>. 1800 IN NS pdns2.ultradns.net >> <http://pdns2.ultradns.net>. >> neustar.biz <http://neustar.biz>. 1800 IN NS pdns3.ultradns.org >> <http://pdns3.ultradns.org>. neustar.biz <http://neustar.biz>. 1800 IN NS >> pdns4.ultradns.org <http://pdns4.ultradns.org>. neustar.biz >> <http://neustar.biz>. 1800 IN NS pdns5.ultradns.info >> <http://pdns5.ultradns.info>. >> neustar.biz <http://neustar.biz>. 1800 IN NS pdns6.ultradns.co.uk >> <http://pdns6.ultradns.co.uk>. neustar.biz <http://neustar.biz>. 1800 IN >> SOA >> pdns1.ultradns.net <http://pdns1.ultradns.net>. sec_grp.neustar.com >> <http://sec_grp.neustar.com>. 1311620677 10800 3600 604800 600 >> neustar.biz <http://neustar.biz>. 43200 IN MX 2 ns6.neustar.com >> <http://ns6.neustar.com>. neustar.biz <http://neustar.biz>. 43200 IN MX 2 >> ns7.neustar.com <http://ns7.neustar.com>. neustar.biz >> <http://neustar.biz>. 1800 IN TXT "google-site-verification= >> 7V6yaWsW0q7fh3JYXAuYOnpyE4BF8J**A2RCawOaSrUCs" neustar.biz >> <http://neustar.biz>. 1800 IN AAAA >> >> 2610:a0:16:4::1 </screen> >> >> Given the purpose of the screen element, which is to present data as it >> would appear on the screen, this clearly is a bad thing! >> >> Even worse, once it has happened, the only way I've been able to fix it >> is to open that section of the document with another editor, and clean >> it up. I don't seem to be able to find a way to edit the data within the >> screen element. (I can add text within the element, but "enter" doesn't >> cause a line break.) >> >> I'm not sure what I'm doing which causes this. >> >> Is there a way to prevent it? >> >> And is there a way to reformat the blocks within xxe, or do I really >> have to use a different editor to fix it? >> > > The problem you describe indeed makes XXE completely useless for editing > DocBook documents. This being said: > > [a] Most XXE users use our product to edit DocBook documents. > [b] No other XXE user has this problem. > [c] We have no way to reproduce this problem here at XMLmind. > > So what could cause this problem? > > --> First idea: XXE does not recognize your document as being a DocBook 4 > or DocBook 5 one. > > Move your mouse over the document tab to display tooltip info about your > document. If you see "DocBook" like in the attached screenshot, then forget > about this idea. > > --> Second idea: your document is structurally invalid. (Example: a table > element does not start with a title child element.) > > Do you see a red icon at the botton/left of XXE's main window (see other > attached screenshot)? If this is the case, then please fix all validation > errors. > > After doing that, please use XXE normally (e.g. never use "Force > Deletion", "Force Removal"), as XXE makes it impossible to create > structurally invalid documents. > > If you don't know how (or, for any reason, don't want) to fix the > structure of your document, then I confirm that, unfortunately for us, > you'll have to use another XML editor. >
-- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
