[
Lists Home |
Date Index |
Thread Index
]
Norman Walsh wrote:
> I've been exchanging some documents with an author using XML Spy. It
> really appears to me that XML Spy is mangling the mixed content. In
> particular, it turns:
>
> <p><termdef>blah blah</termdef> de blah blah blah</p>
>
> into
>
> <p>
> <termdef>blah blah</termdef> de blah blah blah</p>
Looks like result of XML Spy's pretty-printing.
> Anyway, I'm hoping someone out there can satisfy my curiosity. If XML
> Spy loads the DTD and sees that there's mixed content, please tell me
> that it doesn't introduce random *significant* white space into my
> document.
It does instroduce \n\t after <p> start tag in the above document when
pretty-printing the document, even if p is defined as
<!ELEMENT p (#PCDATA | termdef)*>
> Failing that, tell me there's a setting I can have my
> co-author frob so that it doesn't mangle this particular document.
Well, to forget about pretty-print button and XML grid view (latter
could be difficult, because it's default view for XML documents, he must
switch default view to Text View). In effect that means using XML Spy as
regular text editor :)
--
Oleg Tkachenko
http://www.tkachenko.com/blog
Multiconn Technologies, Israel
|
