[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Interesting QDomDocument::setContent variant
From:       David Faure <faure () kde ! org>
Date:       2004-06-07 19:22:40
Message-ID: 200406072122.40333.faure () kde ! org
[Download RAW message or body]

On Monday 07 June 2004 20:36, David Faure wrote:
> > I doubt that; its hard work to create nicely indented XML files; my guess 
> > is that they were just lazy :)
> I disagree. It really makes the (computer-) parsing simpler.

To confirm this: there's the other case where indenting complicates things.

   <text:p text:style-name="P1"> <text:span text:style-name="T1">bold</text:span>
    <text:span text:style-name="T2"> </text:span>
    <text:span text:style-name="T3">italic</text:span>
   </text:p>

After activating the whitespace-reporting feature of QXmlSimpleReader, you get
the space in the second span (as intended), but you also get newlines between the spans,
and "\n   " in character data means a space (inside text:p we are in "whitespace collapse" mode,
says the spec). So at least within text:p, there should be no indentation at all,
since it introduces wrong spaces into the text.

If there is no indentation within text:p and indentation in the rest of the XML it will
look rather strange, won't it?

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]