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

List:       koffice-devel
Subject:    Fwd: KWord File Format
From:       David Faure <faure () kde ! org>
Date:       2002-04-23 16:23:11
[Download RAW message or body]

This sounds like a valid point...
although it would certainly make the "grep '<text>'" idea more difficult again.
Does anyone know if this would break compatibility? I think reading a text
node is done the same way, with and without CDATA in the XML.

----------  Forwarded Message  ----------

Subject: KWord File Format
Date: 23/04/2002 19:30
From: kogs@kogsman.demon.co.uk
To: dfaure@kde.org

I was playing around with KWord maindoc.xml files with a view to making an external 
mail merge processor using a Kylix XML parser of my own devising.  My XML document 
object has a text property which returns the document as a string containing the 
document with lots of TABS to make it pretty.

When I loaded maindoc.xml into my parser and the wrote the text property back out to 
maindoc.xml (and then tarred maindoc.xml and documentinfo.xml) and opened it in 
KWord, the xml formating TABS were displayed.

May I suggest, therefore, that the contents of <TEXT> elements of maindoc.xml 
bracketed by <![CDATA[...]]> so that meaningful whitespace is distinguished from xml 
formating whitespace which should not show up in KWord.  This would greatly assist 
external processing of KWord documents.

Best regards

Stuart



-------------------------------------------------------

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://people.mandrakesoft.com/~david/
Contributing to: http://www.konqueror.org/, http://www.koffice.org/
KDE, Making The Future of Computing Available Today


_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]