From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010725 Description of problem: While testing the groff-gxditview package, I tried to use the gxditview command to print different groff output files. The result was 100 or more blank pages in each case. When gxditview was called directly from groff (with -X option) it worked well in most cases. Because there is no docs with gxditview, I relied on a man page from the Web to find out what it was supposed to do. If only working from groff -X (and with only certain devices) is acceptable, you can close this bug and pass the package. It works well in the limited ways I describe below. How reproducible: Always Steps to Reproduce: 1.Unzip any man page (gunzip groff.1.gz) 2.Use groff to format the page (groff -man -Tps -X groff.1). The gxditview window opens and groff man page displays nicely. 3.Direct output to a file, then open in gxditview.(groff -man -Tps groff.1 > /tmp/groff.ps;gxditview /tmp/groff.ps Actual Results: gxditview opened with 159 blank pages. (At least I think they were all blank. I didn't actually check every one.) Expected Results: I expected to be able to open the file directly with gxditview so that it would work as it does using the -X option to groff. Additional info: I tried all the output devices listed on the man page I found for groff. Here are the ones that could display with gxditview (called by groff -X): ps X75 X100 lj4 html Here are the ones that couldn't: dvi ascii ascii8 utf8 cp1047 nippon lbp
We (Red Hat) should try to fix this for the next release.
This seems to work fine for me: troff -man -r.X=1 -Tps manpage.1 > manpage.ps; gxditview manpage.ps Florian La Roche
man gxditview: >DESCRIPTION > The gxditview program displays gtroff output on an X display. > It uses the standard X11 fonts, so it does not require access > to the server ... You have to use gtroff, not groff. 'gtroff -man <manpage> | gxditview -' works.