From: Fredrik Tolf <fredrik@dolda2000.com>
To: git@vger.kernel.org
Subject: Manpage rendering faults
Date: Wed, 18 Jul 2007 20:47:37 +0200 [thread overview]
Message-ID: <m3odi9im5y.fsf@pc7.dolda2000.com> (raw)
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
next reply other threads:[~2007-07-18 18:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 18:47 Fredrik Tolf [this message]
2007-07-18 19:29 ` Manpage rendering faults Julian Phillips
2007-07-18 20:06 ` Fredrik Tolf
2007-07-18 21:33 ` [PATCH] Force listingblocks to be monospaced in manpages Julian Phillips
2007-07-18 23:56 ` Junio C Hamano
2007-07-19 1:21 ` Julian Phillips
2007-07-18 21:33 ` Julian Phillips
2007-07-20 7:00 ` Junio C Hamano
2007-07-20 7:09 ` Julian Phillips
2007-07-20 12:06 ` [PATCH] Update listingblock monospace fix to support all docbook versions Julian Phillips
2007-07-20 16:42 ` Junio C Hamano
2007-07-20 19:32 ` Brian Gernhardt
2007-07-20 22:14 ` Julian Phillips
2007-07-19 11:37 ` [PATCH] Force listingblocks to be monospaced in manpages Jonas Fonseca
2007-07-19 11:44 ` Julian Phillips
2007-07-19 12:25 ` Jonas Fonseca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3odi9im5y.fsf@pc7.dolda2000.com \
--to=fredrik@dolda2000.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).