Re: [PATCH] Force listingblocks to be monospaced in manpages

From: Julian Phillips <julian@quantumfyre.co.uk>
Date: Jul 19, 2007, 11:44 UTC
Message-ID: <Pine.LNX.4.64.0707191239050.32611@reaper.quantumfyre.co.uk>
In-Reply-To: <20070719113743.GA27553@diku.dk>

On Thu, 19 Jul 2007, Jonas Fonseca wrote:

Show 24 quoted lines

> 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 addition, also add an empty line after all verbatim blocks.
>
> Signed-off-by: Jonas Fonseca <fonseca@diku.dk>
> ---
>
>  Julian Phillips <julian@quantumfyre.co.uk> wrote Thu, Jul 19, 2007:
>  > On Wed, 18 Jul 2007, Junio C Hamano wrote:
>  >
>  > >I tried with your patch, both with asciidoc7 and asciidoc8.  Did
>  > >you really mean "&#x2302;" above?  Replacing them with "."  gave
>  > >me a series of these changes (diff between output before and
>  > >after your patch with the "s/\&#x2302;/./g" fixup):
>  >
>  > I did mean it.  I originally just had .ft, but I was getting \&.ft in the
>  > manpage, which then just came out as .ft in the console.
>
>  This is because AsciiDoc does the escaping. I think it would be cleaner
>  to do this thing when converting from DocBook to roff like we already
>  do for other things.

No. Docbook does the escaping (as it says here: http://docbook.sourceforge.net/release/xsl/current/RELEASE-NOTES.html#V1.72.0 ). I tried your approach first, but 1) I idn't want to copy that much from the docbook xsl, as then we won't get updates/changes/fixes etc, 2) I still had to use ⌂ _anyway_.

Just compare the chunk that you have copied from the docbook xsl to the version from 1.72.0 and you will find that all the '.'s have become ⌂s ...

-- 
Julian

  ---
"It's when they say 2 + 2 = 5 that I begin to argue."
-- Eric Pepke