git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Force listingblocks to be monospaced in manpages

From
Julian Phillips <julian@quantumfyre.co.uk>
Date
Jul 18, 2007, 21:33 UTC
Message-ID
<20070718213725.31383.50523.julian@quantumfyre.co.uk>
In-Reply-To
<m3k5sxiiib.fsf@pc7.dolda2000.com>

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 <julian@quantumfyre.co.uk>
---
On Wed, 18 Jul 2007, Fredrik Tolf wrote:
Show 23 quoted lines
> Julian Phillips <julian@quantumfyre.co.uk> writes:
>
>> 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?
>
> 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
Previous: Fredrik TolfNext: Junio C Hamano
Message 4 of 16 in “Manpage rendering faults”
  1. Fredrik TolfJul 18, 2007
  2. Julian PhillipsJul 18, 2007
  3. Fredrik TolfJul 18, 2007
  4. Force listingblocks to be monospaced in manpagesJulian Phillips, Jul 18, 2007
  5. Junio C HamanoJul 18, 2007
  6. Julian PhillipsJul 19, 2007
  7. Force listingblocks to be monospaced in manpagesJulian Phillips, Jul 18, 2007
  8. Junio C HamanoJul 20, 2007
  9. Julian PhillipsJul 20, 2007
  10. Update listingblock monospace fix to support all docbook versionsJulian Phillips, Jul 20, 2007
  11. Junio C HamanoJul 20, 2007
  12. Brian GernhardtJul 20, 2007
  13. Julian PhillipsJul 20, 2007
  14. Force listingblocks to be monospaced in manpagesJonas Fonseca, Jul 19, 2007
  15. Julian PhillipsJul 19, 2007
  16. Jonas FonsecaJul 19, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.