Re: Gzipped .dvi files?
-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 29 Jan 1998 Marcus.Brinkmann@ruhr-uni-bochum.de wrote:
> No. All documentation, that is not short, has to
> be gzipped. This is requested by policy and was discussed often and
> thoroughly (sp?). dvi files tend to be rather long, and not everyone needs
> them. They are no pain in the ass, because you can quite easily do
> zcat <file>.dvi.gz /tmp/<file>.dvi
> and then point your favourite dvi viewer to this location.
> If you have time to volunteer, try to fix the dvi viewer's to accept
> gzipped files - start with dvisvga, it is my favourite one ;)
The easiest way that I have found to do this under a libc5 system is
to install zlibc, the latest version being 0.9f. I couldn't find a .deb
for it, but it wouldn't be very hard for me to build one if anyone thinks
it would be worth it (I'd probably need some help getting the policy stuff
straight, so I'd be bugging you again...)
In any case, once it's been installed, you simply pretend that the .gz
extension doesn't exist when passing arguments to xdvi or whatever. I
don't use dvisvga, but I do know that neither xdvi nor gv are bothered by
.gz files with zlibc installed.
Incidentally, I couldn't find anything in the documentation on this...
What's the etiquitte for replies sent to the list in terms of what should
go into "To" or "Cc" fields? Should the individual names be stripped, and
just the debian-devel address left (those people are going to get two
copies, after all...), or more like I have left it (by automated
Zed Pobre <firstname.lastname@example.org> | PGP key on servers, fingerprint on finger
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to email@example.com .