Manpage rendering faults

I often read manpages using a `man -t whatever | ggv -' command, since
I like how it is rendered in PostScript. However, it turns out that
some things in the Git manpages don't really render very well using
that method. For example, in the git-rebase manpage, there are two
history graphs that look like this when reading the manpages normally
in a terminal:

      A---B---C topic
     /
D---E---F---G master

and then

              A'--B'--C' topic
             /
D---E---F---G master

However, in the PostScript rendering, they look rather like this:

  A---B---C topic
 /
D---E---F---G master

and then

      A'--B'--C' topic
     /
D---E---F---G master

It took me quite a while to figure out that the rendering was
wrong. Before that, I just couldn't figure out why git-rebase would do
that. :)

Unfortunately, I can't say that I have a fix available -- particularly
as I don't really know anything at all about asciidoc. I thought I'd
at least let you know, though.

Fredrik Tolf

On Wed, 18 Jul 2007, Fredrik Tolf wrote:

I often read manpages using a `man -t whatever | ggv -' command, since
I like how it is rendered in PostScript. However, it turns out that
some things in the Git manpages don't really render very well using
that method. For example, in the git-rebase manpage, there are two
history graphs that look like this when reading the manpages normally
in a terminal:

It's a proportional font issue ...

Running "groff -Tps -f C -man $(man -w git-rebase) | ggv -" should display 
it correctly.  (The "-f C" being the part the man doesn't do)

No idea how to make it use that font by default though ... not even sure 
if you can put that kind of information into a man page?

-- 
Julian

  ---
Dinner suggestion #302 (Hacker's De-lite):
 	1 tin imported Brisling sardines in tomato sauce
 	1 pouch Chocolate Malt Carnation Instant Breakfast
 	1 carton milk

Julian Phillips [off-list ref] writes:

On Wed, 18 Jul 2007, Fredrik Tolf wrote:

quoted

I often read manpages using a `man -t whatever | ggv -' command, since
I like how it is rendered in PostScript. However, it turns out that
some things in the Git manpages don't really render very well using
that method. For example, in the git-rebase manpage, there are two
history graphs that look like this when reading the manpages normally
in a terminal:

It's a proportional font issue ...

Running "groff -Tps -f C -man $(man -w git-rebase) | ggv -" should
display it correctly.  (The "-f C" being the part the man doesn't do)

No idea how to make it use that font by default though ... not even
sure if you can put that kind of information into a man page?

Well, if it were a "pure" manpage, I'd try to use pic(1) to do it for
the PS version, but I don't suspect asciidoc has a similar feature. I
don't actually know, though -- again, I know virtually nothing about
asciidoc.

Fredrik Tolf

For the html output we can use a stylesheet to make sure that the
listingblocks are presented in a monospaced font.  For the manpages do
it manually by inserting a ".ft C" before and ".ft" after the block in
question.

In order for these roff commands to get through to the manpage they
have to be element encoded to prevent quoting.

Signed-off-by: Julian Phillips <redacted>
---

On Wed, 18 Jul 2007, Fredrik Tolf wrote:

Julian Phillips [off-list ref] writes:

quoted

On Wed, 18 Jul 2007, Fredrik Tolf wrote:

quoted

I often read manpages using a `man -t whatever | ggv -' command, since
I like how it is rendered in PostScript. However, it turns out that
some things in the Git manpages don't really render very well using
that method. For example, in the git-rebase manpage, there are two
history graphs that look like this when reading the manpages normally
in a terminal:

It's a proportional font issue ...

Running "groff -Tps -f C -man $(man -w git-rebase) | ggv -" should
display it correctly.  (The "-f C" being the part the man doesn't do)

No idea how to make it use that font by default though ... not even
sure if you can put that kind of information into a man page?

Well, if it were a "pure" manpage, I'd try to use pic(1) to do it for
the PS version, but I don't suspect asciidoc has a similar feature. I
don't actually know, though -- again, I know virtually nothing about
asciidoc.

How about this?

Seems to work for me - but I'm not an asciidoc/docbook/roff expert ...

 Documentation/asciidoc.conf |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/Documentation/asciidoc.conf b/Documentation/asciidoc.conf
index 6b6220d..d54fe29 100644
--- a/Documentation/asciidoc.conf
+++ b/Documentation/asciidoc.conf

@@ -27,7 +27,13 @@ ifdef::backend-docbook[]
 [listingblock]
 <example><title>{title}</title>
 <literallayout>
+ifdef::doctype-manpage[]
+&#10;&#x2302;ft C&#10;
+endif::doctype-manpage[]
 |
+ifdef::doctype-manpage[]
+&#10;&#x2302;ft&#10;
+endif::doctype-manpage[]
 </literallayout>
 {title#}</example>
 endif::backend-docbook[]

-- 
1.5.2.2