On 22 Sep 1998, Karl M. Hegbloom wrote: > >>>>> "Anthony" == Anthony C Zboralski <[EMAIL PROTECTED]> writes: > > Anthony> On Fri, Sep 11, 1998 at 05:18:18PM +0200, Anthony > Anthony> C. Zboralski wrote: > >> hey is there an easy way to print info manuals? > > Anthony> No. In order to have acceptable quality output, you have > Anthony> to use the TeXinfo source files. > > >> for manuals like libg++ i am not going to print everypages > >> manually; maybe i am stupid and there is an easier way to do > >> this but when i need to print a texinfo manual, i have to grab > >> the package source, run configure and make dvi. > > Anthony> You could try getting policy extended to have .texi > Anthony> sources (in a form suitable for texi2dvi) included in the > Anthony> package (or in a separate documentation package) - > Anthony> propose it on debian-policy@lists.debian.org > > I think that the .texi source belongs in the package source. Why > make yet another package out of things when it's already there? > Perhaps there ought to be (ie, suggested by, but not required by > policy) a "debian/rules" target for creating the .dvi or .ps, whenif > the upstream Makefile doesn't perform that task adequately.
oh well, it is normal to have to download 11Megs of source code to create the dvi files for egcs, libg++ and more.. info files are okay but they are not printable. I work a lot and i save some time by reading docs in the subway or in my bed when my girlfriend is asleep.
