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

List:       koffice-devel
Subject:    Re: [PATCH] KWord's DTD
From:       Nicolas Goutte <nicog () snafu ! de>
Date:       2001-12-06 21:19:15
[Download RAW message or body]

On Thursday 06 December 2001 00:42, David Faure wrote:
> On Wednesday 05 December 2001 23:45, Nicolas Goutte wrote:
> > The attached patch is for the file kword/kword.dtd
> >
> > Dash sequences:
> > I have replaced the dash sequences, as in SGML, two dashes end (or start)
> > a comment and three dashes are a parsing error. A DTD is a SGML file.
> >
> > newFrameBehavior:
> > This attribute was recently renamed from British English to American
> > English, however the documenation has only half followed.
> >
> > xml:space="preserve"
> > I have added this attribute, as we are using it implictely. In <TEXT>,
> > the spaces are important, as <FORMAT> tags depend on them.
> > Note: I have done this changes according to the specification of XML. I
> > have not verified that it works with any XML tool.
>
> Looks good, except that it's DEPRECATED, not DEPRECIATED.
> Both words exist in English, but not with the same meaning.

Well, we could argue about this.

However, I have looked into the "American Heritage College Dictionnary". It 
tells me that in American English the word "deprecated" is taking over the 
sense of "depreciated". (And sense 1 of one is the sense 2 of the other and 
vice-versa!)

So for project in American English (like KDE) I will start to use 
"deprecated" as everybody.

>
> I'm not too sure about the preserve space thing. QDom isn't always
> preserving our spaces (e.g. you can't have <TEXT>   </TEXT> - more than one
> space, if there's nothing else in the text, is always reduced to a single
> one, IIRC.) Anyway that atllist doesn't influence validating from the dtd
> in any way, so this doesn't matter much.

That is much more serious than the deprecated/depreciated stuff.

Here were are talking about what a XML tool is allowed to do with a KWord XML 
file. Whitout "preserve", you are telling the tool that it can add or remove 
white space (nearly) wherever it want. Do this and you will be (very) 
surprised by the result when KWord loads the modified file, if the file has 
any character formatting (<FORMAT>.)

I also want that an external developer is able to see in the DTD that spaces 
matter in <TEXT> and that he should be careful when manipulating <TEXT>.

I am not talking about QDomDocument::setContent, which is a non-validating 
parser. It does not look after the DTD and we could only complain to Qt Bug, 
if we would add xml:space="preserve" explicitely in each <TEXT> opening tag.

Have a nice day/evening/night!
_______________________________________________
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]