On Wed, Oct 29, 2008 at 20:39, Jeff King <peff@xxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
