Bug#41352: compressed HTML/dhelp
Ron wrote:
Hi Ron!
> FWIW, I agree with Joel - IMHO one of the best things about Debian's
> documentation is that it doesn't waste (often precious) disk space with
> uncompressed plaintext.
A unreadable documentation is a waste of space, IMHO.
> The *only* valid justification I have seen so far for storing html
> uncompressed on a Debian system is in the case where a document
One simply question: do you know any web pages in the internet
sending compressed html to their users? I don´t know one.
> uncompressed filenames. Even in this case I would prefer to see a
> script run over them to tack .gz onto the relevant links and then
> have them packaged compressed too.
Where does the HTML standard describe compressed HTML files?
HTML is defined as an uncompressed format.
> If you really need to browse these docs on a legacy system that does
> not support automatically uncompressing them then it is a relatively
> simple matter to configure a httpd to uncompress them on the fly for
Really? How can I do this as a *user*?
> If dhelp & friends do not support compressed docs then the correct
> thing to do would be fix dhelp.
dhelp has got no problems with any kinds of files, because it don´t
use them. It simply creates URLs. But there´re several version of
netscape having problems mit a gzip transfer encoding, even on
linux systems!
> *Every* time we increase the required space of some existing package
> or function, someone somewhere has a machine on which they must start
> deleting things just to maintain the functions they most need. Yes, to
> some extent this inevitable, but when the increase is gratuitous rather
> than functional, the quality of Debian as a whole for that person is
> likewise reduced.
????
cu, Marco
--
-- Linux HOWTOs: Die besten Lösungen der Linuxgemeinde --
ISBN 3-8266-0498-9
Uni: Budde@tu-harburg.de Fido: 2:240/6298.5
Mailbox: mbudde@sms.antar.com http://www.tu-harburg.de/~semb2204/
Reply to: