- From: Alexander Biron <biron@ifh.de>
- Date: Tue, 21 Dec 1999 15:55:37 +0100 (MET)
- To: Bob Bagwill <robert.bagwill@nist.gov>
- cc: html-tidy@w3.org
On Tue, 21 Dec 1999, Bob Bagwill wrote: > IMHO Tidy-master Raggett shouldn't put any more > development effort into the slide feature. It's > cute but doing it right (IMHO again) would be a waste of time. > > An XML/XSL slide package would be more appropriate > but slides are so presentational (no pun intended) > that they almost always need to be hand-tweaked, > which is sort-of anti-SGML. I fully agree. And anyway one might find a few other problems with the output of the -slides option: - It converts HTML4.0 pages (with Doctype declaration) to HTML3.2 and inserts the <center> element (which is deprecated in HTML 4.0 - It's output does not follow the recommondation that every page's topmost heading should be a <h1> heading - It links the slide*.html files with <a href="slide1.html"> tags - even if there is a <base href=""> in the header which sets the default directory to something else Actually the last point is a real bug, which Ionly just discovered. The bad thing: It might not be easy to fix. Suppose the following domainstructure: URL filesystem http://www.foo.com/ /home/user/www/ http://www.foo.com/bar1.html /home/user/www/pub/bar1.html http://www.foo.com/protected/bar2.html /home/user/www/protected/bar2.html And suppose you set a <base href="http://www.foo.com/"> in both files. Tidy might be able to find out where the files are located within the system filestructure. But how should it know how the server is set up, i.e. how this translates to the URL structure? Removing the <base href=""> is also no option since then other links within the page won't work any more. Merry X-mas Alexander Biron -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
Received on Tuesday, 21 December 1999 09:55:43 UTC