Re: trouble of gxditview with man bash

[Werner LEMBERG]

[bash 2.05b.0]

> `gxditview' has some trouble with the man page of `bash'.  From page
> 54 up to the end, it produces only trash output, while the display
> of `xditview' is alright.  `xditview' just remarks an error `Unknown
> command d', although `groff' produces its intermediate output
> without such a command and does not produce any error.

groff and gxditview both work correctly.  It's a typo in bash.1:


--- bash.1~     2005-06-23 06:49:20.940238576 +0200
+++ bash.1      2005-06-23 06:49:20.942238272 +0200
@@ -7093,7 +7093,7 @@
 This option has no effect if \fBread\fP is not reading input from the
 terminal or a pipe.
 .TP
-.B \-u \fIfd\FP
+.B \-u \fIfd\fP
 Read input from file descriptor \fIfd\fP.
 .PD
 .PP


Using \F instead of \f makes groff use font family `P' (palatino)
instead of the default `T' (times roman).

The above problem only shows up with groff's -X option: The document
is processed with -Tps (which has font family `P') but displayed with
gxditview (which doesn't have family `P').

`xditview' works better because it has extended code (in function
MapDviNameToXName) which maps unknown fonts to a default one, while
gxditview decides to display nothing.  I wonder whether similar code
should be added to gxditview.  Volunteers?

Personally, I very much dislike option -X: Using (g)xditview for
previewing groff's PS output is ugly, and gv or any other decent PS
previewer do a much better job today.  Good looking output for
gxditview can be produced with -TX75 or -TX100 (or its variants
-TX75-12 and -TX100-12).


    Werner