On Thursday, 13. September 2001 13:41, Vadim Plessky wrote: > On Wednesday 12 September 2001 19:36, Nicolas Goutte wrote: > | On Tuesday, 11. September 2001 14:45, Vadim Plessky wrote: > | > I was wondering for some time why HTML exported by KWord, always was > | > using
...
for every paragraph. > | > | Because a paragraph is aelement in HTML! > > For sure :-) > And support for it is some kind of *legacy support*. I am sorry, but I DO care about legacy! I am sure that somebody will one day put on the Internet a HTML file created by KWord's HTML export filter. And I would like that visitors of that site would be able to read at least the text, whatever user agent they use, not just if they use the lastest browsers around. And who tells you that the user agent will be a visual one. KWord's HTML export filter cannot give information for non-visual user agents, as KWord itself is visual-centered. So any reader (rendering to speech), braille display and so on can only rely on HTML tags. Using
in their specifications (I mean in the HTML files themselves.) And if I follow someone, it is the people who makes the (X)HTML specifications, not Mozilla. > > IMO DIV is much more modern technics than *old* P and tables. > Note that you can even have scrollbar in fixed-size DIV element if context > doesn't fit completely into it! :)) > // not sure wether Konq supports it, though. > > Major disadvantage of using P is that P *always* breaks line, and starts > new block. So, if you want to have two paragraphs following each other - > there is no, basically, a way to do this with P tag (except overriding CSS > style with !importnat instruction and disbaling breaking) From what I know, KWord always have a line break between paragraphs, so where is the problem? And if KWord would support something like suppressing the line break, then it is special case, that could be handle through CSS. We are here creating a (X)HTML + CSS2 file, not a (generic) XML + CSS2 file. > With SPAN, you can do it easily. > > Another problem is putting image. > There is no problem to put an image inside DIV, but it's not very clear > *how*
will behave if you placed picture inside. > Sorry it may sound a little bit OT for KWord/KPresenter itself, it's more > KHTML/Konq related, but it seems there is some kind of misunderstanding > what should be
used for.
I am sorry, but I think that you do not have understood the concept of
document structure, for what SGML was created (and from which HTML is
derived.) HTML gives the structure, CSS how to display. *Both* are important!
>
> IMPORTANT NOTE:
> anyway, when you export image to HTML (either as IMG or as OBJECT of Image
> MIMEtype), you need to place it in some *bounding* structure.
> If you placed just in , for every
> | > paragraph.
> |
> | The HTM 4.01 Specification defines (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."
>
> I think default settings of KWord should be exported.
> There is default setting for before and after paragraph space, right?
> So you can export them in 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.
>
> No-no, I care!...
> Sorry I was not very active on list recently, August was rather mixed for
> me and I decided to make some break, but I follow the list ...
> Hope to participate more actively soon!
>
> | Have a nice day/evening/night!
>
> Take care!
Have a nice day/evening/night!
_______________________________________________
Koffice-devel mailing list
Koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel
, a non-visual user agent knows that a table is coming and can
handle it correctly (for example for a reader with a different speech for
column titles.)
>
> // oh, eys, you can use IFRAME as well, and insert IMG into complimentary
> frame (html), but is seems to me a little bit overhead.
>
> | > 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