From koffice-devel  Wed Sep 12 19:36:57 2001
From: Nicolas Goutte <nicog () snafu ! de>
Date: Wed, 12 Sep 2001 19:36:57 +0000
To: koffice-devel
Subject: Re: [RFC] filter redesign
X-MARC-Message: https://marc.info/?l=koffice-devel&m=100032406005574

On Tuesday, 11. September 2001 14:45, Vadim Plessky wrote:
> On Monday 10 September 2001 21:02, Nicolas Goutte wrote:
> |   On Monday, 10. September 2001 21:08, Thomas Zander wrote:
>
> [...]
>
> |   > > 	virtual buildFooter(...);
> |   > > 	virtual buildParagraph(...);
> |   > > 	virtual buildTable(...);
> |   >
> |   >     don't forget that this method needs a created paragraph as an
> |   > argument. (actually an ID, see below)
> |
> |   You cannot have this! <TABLE> cannot be a child of <P> according to
> | strict DTD of HTML 4.01.
>
> I was wondering for some time why HTML exported by KWord, always was using
> <P> ... </P> for every paragraph.

Because a paragraph is a <p> element in HTML!

> While at a first glance it seems logical, almost for every paragraph you
> redefine style (font size, color, font name, etc.)
> It's much more convinient to use DIV, instead of <P>, for every paragraph.

The HTM 4.01 Specification defines <div> as "generic language/style 
container", that is not a paragraph!

> Then you don't have such limitations.
>
> At a moment, you just can't have nested paragraphs :-((

Since when does KWord support nested paragraphs? Or do I have missed 
something?

> It's a real limitation for page layouting, IMO.
> Changing P to DIV allows to fix it.
>
> As KWord uses XML internally, I do not think that implementing such changes
> will be difficult.
>
> BTW: I found serious inconsistance when view exported from KWord HTML in
> different browsers.
> Reason: KHTML uses to much space *before* and *after* <P> (about 1em in
> each case), while Mozilla - only half of it.

That will change when the space before and after the paragraph will be 
exported as CSS too. But then I am sure that I will have complaints like: 
"But why there is no space between paragraphs in exported HTML."

> So IMO it's not good to count *default* behavior/style for P tag, it's
> better to define it each time (or to have extra option for this)

Sure, that is called style in KWord and class in CSS but I was trying to make 
a library for KWord export filters before finsih it. But however, I have the 
feeling that nobody cares anymore that I write this library when I read this 
thread.

Have a nice day/evening/night!
_______________________________________________
Koffice-devel mailing list
Koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel