| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Sunday 11 August 2002 22:58, Justin T. wrote: |
| 5 |
> Good good. With CVS compiled from today they work perfectly. |
| 6 |
> I can make a screenshot if anyone is interested. Looks like |
| 7 |
> there won't be a problem then when KDE 3.1 comes out. |
| 8 |
|
| 9 |
no, it's not ok, no matter how well khtml from cvs might render |
| 10 |
the pages. |
| 11 |
|
| 12 |
it's the opposite way round: there are official w3c {x}html |
| 13 |
recommendations. now people need to write valid pages and |
| 14 |
programmers need to write correct parsers/renderers for the w3c |
| 15 |
recommendations. you can't expect from hackers to write |
| 16 |
parsers/renderers for all these invalid "{x}html" pages out |
| 17 |
there, that's the point. |
| 18 |
|
| 19 |
thus, the important thing here is that the pages are valid |
| 20 |
{x}html pages. obviously they aren't :\ (pipe some gentoo doc |
| 21 |
web pages through http://validator.w3.org/ and see for |
| 22 |
yourself). astonishing. the pages are all transformed from valid |
| 23 |
xml, aren't they? somebody from gentoo-doc should take a look at |
| 24 |
this. |
| 25 |
|
| 26 |
regards |
| 27 |
|
| 28 |
dan |
| 29 |
|
| 30 |
- -- |
| 31 |
...::: Daniel Mettler | http://www.numlock.ch :::.... |
| 32 |
|
| 33 |
-----BEGIN PGP SIGNATURE----- |
| 34 |
Version: GnuPG v1.0.7 (GNU/Linux) |
| 35 |
|
| 36 |
iD8DBQE9VujTSLYjgrGjnWQRAp50AKC+1NQ0XUCxFB3ccpU8yCYLO/ITrgCbBWWK |
| 37 |
9btSqQGimsue4VaPOqOK4fE= |
| 38 |
=idGw |
| 39 |
-----END PGP SIGNATURE----- |
Archives