Re: TRichView vs WPTools

Author

Message

Sergey Tkachenko

Posted: 12/19/2003 20:05:50

I just passed a file saved by actiontest demo through W3C HTML validator.

It found the following incompatibilities:

1) There is no magic line

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

at the beginning of document

2) Charset is not defined (TRichView saves charset in HTML only if the 0-th

text style's charset is not a DEFAULT_CHARSET)

3) <img> misses alt tag (TRichView saves alt only if it is not empty; in any

case, you can provide it in OnWriteHyperlink event)

4) In tables, validator says that color values (like #FFFFFF) must be in

double quotes

5) Validator does not understand that tables are contained in <P>. I tested

in browsers, well, it seems that only Internet Explorer understands it, so

this is really an incompatibility.

What's all. Do you really think these issues are really make HTML unusable?

In any case, thank you for pointing to this problem, I'll fix them in the

next update (1, 4, 5 and I'll think about 3)

"Simplified" HTML generates more warnings, but it was designed to be

compatible with old browsers. For example, it includes some tag attributes

specially for Netscape Navigator, and these attibutes produces validator's

error.

But this HTML was specially created for compatibility with old HTML readers,

not with HTML validator.

Please send follow-ups in the new "What does it mean?" thread.

> For me, the key thing is Unicode support. Anyone developing a text-based

> application who is ignoring Unicode at this point won't have much of a

> future.

> The HTML output from TRichView is one of my least-favourite features; it

> produces code that doesn't validate on the W3C validator, and doesn't

> even specify what DTD it's supposed to conform to. I'll be really happy

> when we can get proper XHTML output that validates. An application I use

> regularly, FastHelp, is based around TRichView, and its HTML output is

> unusable.

> Cheers,

> Martin