From: "Jonas Fonseca" <jonas.fonseca@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Teemu Likonen" <tlikonen@iki.fi>, git@vger.kernel.org
Subject: Re: A typesetting problem with git man pages
Date: Wed, 29 Oct 2008 21:14:35 +0100 [thread overview]
Message-ID: <2c6b72b30810291314n75154276ma226cccc1ea07504@mail.gmail.com> (raw)
In-Reply-To: <20081029193958.GA12856@sigill.intra.peff.net>
On Wed, Oct 29, 2008 at 20:39, Jeff King <peff@peff.net> wrote:
> so the problem is the extra \&. But I don't know why that is being
> generated. It _should_ be part of the character entity, I thought, but
> xmlto seems to be rendering it as the newline character entity _plus_
> the ampersand.
>
> So it seems like a bug to me in the XML parser, but it is more likely
> that I'm somehow clueless about XML.
The way I understand it is that the DocBook XSL (stylesheet) doing the
conversion from xml to the manpage ensures that possible problematic
characters that could break the manpage are escaped. A dot in the
start of a line is problematic since it could be interpreted as markup
by the manpage viewer and in the mentioned case, the code was not
generated by the stylesheet, thus it must be escaped. So IMO, the
stylesheet is hardly to blame, the problem is that the asciidoc.conf
file defines a macro for literallayout, in which it expects manpage
code to be passed through unescaped.
--
Jonas Fonseca
prev parent reply other threads:[~2008-10-29 20:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 19:16 A typesetting problem with git man pages Teemu Likonen
2008-10-29 19:35 ` Jonas Fonseca
2008-10-29 22:22 ` Teemu Likonen
2008-10-30 10:45 ` [PATCH] asciidoc: add minor workaround to add an empty line after code blocks Jonas Fonseca
2008-10-30 12:56 ` Teemu Likonen
2008-11-01 22:48 ` Junio C Hamano
2008-11-01 23:42 ` Thomas Adam
2008-11-03 0:12 ` Kalle Olavi Niemitalo
2008-10-31 7:37 ` A typesetting problem with git man pages Teemu Likonen
2008-10-31 8:37 ` Teemu Likonen
2008-10-29 19:39 ` Jeff King
2008-10-29 20:14 ` 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=2c6b72b30810291314n75154276ma226cccc1ea07504@mail.gmail.com \
--to=jonas.fonseca@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=tlikonen@iki.fi \
/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).