From: Julian Phillips <julian@quantumfyre.co.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: Fredrik Tolf <fredrik@dolda2000.com>, git@vger.kernel.org
Subject: Re: [PATCH] Force listingblocks to be monospaced in manpages
Date: Fri, 20 Jul 2007 08:09:49 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707200806540.20056@beast.quantumfyre.co.uk> (raw)
In-Reply-To: <7v3azj1rva.fsf@assigned-by-dhcp.cox.net>
On Fri, 20 Jul 2007, Junio C Hamano wrote:
> Julian Phillips <julian@quantumfyre.co.uk> writes:
>
>> In order for these roff commands to get through to the manpage they
>> have to be element encoded to prevent quoting. In particular with
>> docbook xsl 1.72.0 and newer we have to use U+2302 instead of . to
>> prevent the roff command being escaped. We also add a small perl
>> script for docbook < 1.72.0.
>
> This does not work at all for docbook 1.71. I get "^<TAB>ft C"
> as output from xmlto.
Oh, well ... that's handy? :S
I've just checked, and I do have a machine with docbook < 1.72, so I'll
see if I can get something working on both. Probably early next week
since I'm away this weekend.
--
Julian
---
Words are the voice of the heart.
next prev parent reply other threads:[~2007-07-20 7:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 18:47 Manpage rendering faults Fredrik Tolf
2007-07-18 19:29 ` 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 [this message]
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=Pine.LNX.4.64.0707200806540.20056@beast.quantumfyre.co.uk \
--to=julian@quantumfyre.co.uk \
--cc=fredrik@dolda2000.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).