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

List:       koffice-devel
Subject:    Re: Fwd: Bug#19405: KHTML Kpart for Kword
From:       Nicolas GOUTTE <nicog () snafu ! de>
Date:       2001-01-31 14:21:12
[Download RAW message or body]

Having a KHtml KPart would be perhaps a nice idea but it has also drawbacks
and does *not* replace a correctly working HTML / XHTML filter for KWord.

There are a few comments I have about it (good or bad):

1. KHtml does not provide a HTML / XHTML editor, just a HTML / XHTML viewer.

Okay, may be it is sufficient for some applications!

2. How do you export your file in another format?

Think when in future versions KWord has an RTF exporter and you want to
convert HTML to RTF. How do you that with a separate KPart?
New filters? Good! Who will write them? Nobody...

3. KHtml is at the front of the "browser wars".

KHtml tries hard to be able to display all HTML pages seen on the WWW, even
those who cannot be considered HTML 4.01 or XHTML 1.0.
This work is still in progress, as many bug reports at http://bugs.kde.org are of
the type: "I cannot display this site ..."
Therefore the non-KHtml code must *not* deal with the HTML / XHTML document,
it should just be the basis for KHtml to work in the KOffice environment. Therefore
transforming KHtml into a HTML / XHTML editor will break this advantage.

4. Scripts in the HTML / XHTML document (SECURITY)

The HTML / XHTML document may contain script. It *must* be ensured that this
script language cannot execute KOffice/KScript scripts. Otherwise, you have the
door wide open to Trojan Horse Attacks. (e.g. Mellisa, I Love You...)
The mailer is one point, the scripting-able application the next most important one!

5. Keep in old format

One advantage of having a KHtml KPart is that the code may be kept in original
form (i.e. in HTML / XHTML) in a KoStore. With a working filter for KWord, it would
be stored as a KWord document!

6. What is HTML?

At the origin, HTML was to store scientific documents. For me, writing scientifc
documents is KWord's job in KOffice.
Today HTML / XHTML are basicly text documents with embedded objects.
Kword can do this too. So I do not see why we need another KPart to do it.

*My Point Of View*

I think the best would be to have a correctly working filter for HTML / XHTML
to replace the current useless one (import as ASCII text, export is forgetting
"half" of the text!)

May be KHtml can be our help, as it defines a complete HTML DOM implementation.
Someone should look at KHtml in general and see how to use it for a KWord's filter.
KHtml will be always up-to-date and the HTML DOM implementation should be able to
screen us from crazy HTML web pages (I mean "crazy" in the HTML description of
them, not how they look like on a screen!)

>----------  Forwarded Message  ----------
>Subject: Bug#19405: KHTML Kpart for Kword
>Date: 30 Jan 2001 13:06:05 -0000
>From: cap@capsi.com
>To: submit@bugs.kde.org
>
>
>Package: kword
>Version: cvs, 2001-01-29
>Severity: wishlist
>
>Hello,
>
>it would be cool/handy if you coul embed HTML in Kword.
>(Create HTML frame perhaps, just like KChart etc).
>Perhaps a KHTML Kpart could do the trick?
>
>Hm, might have to look into this myself once I've finished
>the KDE 2.0 Development book and have my skills up to
>decent level.
>
>Rob Kaper <cap@capsi.com>
>--------------------------------------------------

_______________________________________________
Koffice-devel mailing list
Koffice-devel@master.kde.org
http://master.kde.org/mailman/listinfo/koffice-devel

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