From: Jonas Fonseca <fonseca@diku.dk>
To: Julian Phillips <julian@quantumfyre.co.uk>
Cc: Junio C Hamano <gitster@pobox.com>,
Fredrik Tolf <fredrik@dolda2000.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Force listingblocks to be monospaced in manpages
Date: Thu, 19 Jul 2007 14:25:41 +0200 [thread overview]
Message-ID: <20070719122541.GA28414@diku.dk> (raw)
In-Reply-To: <Pine.LNX.4.64.0707191239050.32611@reaper.quantumfyre.co.uk>
Julian Phillips <julian@quantumfyre.co.uk> wrote Thu, Jul 19, 2007:
> On Thu, 19 Jul 2007, Jonas Fonseca wrote:
> > 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
> ).
Oops, yes, you are right.
> 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_.
OK, I didn't think you tried it. Nevermind then.
--
Jonas Fonseca
prev parent reply other threads:[~2007-07-19 12:25 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
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 [this message]
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=20070719122541.GA28414@diku.dk \
--to=fonseca@diku.dk \
--cc=fredrik@dolda2000.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=julian@quantumfyre.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.