From: SourceForge.net <no...@so...> - 2007-10-23 02:20:32
|
Bugs item #1809119, was opened at 2007-10-07 13:09 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1809119&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: XSL Group: output: manpages >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Ori Avtalion (salty-horse) Assigned to: Michael(tm) Smith (xmldoc) Summary: man: macros inside <literallayout> are prepended with \& Initial Comment: Using docbook 4.5 When trying to use a roff macro in <literallayout>, docbook automatically prepends a \& char to it, preventing it from being parsed. Example: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> <refentry> <refnamediv> <refname>foo</refname> <refpurpose>bar</refpurpose> </refnamediv> <refsect1> <literallayout> .ft C foo bar .ft </literallayout> </refsect1> </refentry> $ xsltproc -o foo.1 docbook.xsl foo.xml Produces: [...] .nf \&.ft C foo bar \&.ft .fi [...] ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2007-10-22 19:20 Message: Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Ori Avtalion (salty-horse) Date: 2007-10-08 13:08 Message: Logged In: YES user_id=854801 Originator: YES An option (element, attribute) for controlling the font is just it, but I don't think it should be limited to <literallayout> elements. I'll file a feature request. Thanks! ---------------------------------------------------------------------- Comment By: Ori Avtalion (salty-horse) Date: 2007-10-08 13:02 Message: Logged In: YES user_id=854801 Originator: YES An option (element, attribute) for controlling the font is just it, but I don't think it should be limited to <literallayout> elements. I'll file a feature request. Thanks! ---------------------------------------------------------------------- Comment By: Michael(tm) Smith (xmldoc) Date: 2007-10-07 18:54 Message: Logged In: YES user_id=118135 Originator: NO Ovi, First off, thanks very much for using the manpages stylesheet and filing this report. What you describe in the report is not actually a bug; it's expected behavior. DocBook markup is neutral with regard to output formats, so the manpages stylesheet, by design, intentially does not support any mechanism for processing/evaluating raw groff markup in DocBook source; instead it gets output literally, just as you're seeing here. Otherwise, if you were, say, to be writing a guide to groff and wanted to include some program listings with groff markup in them, and have them output as-is without them getting processed or evaluated by groff in man-page output, you would not be able to do that. And if you took the example you included in this report and generated HTML or PDF output from it, the raw ".ft C" and ".ft" stuff would show up in your HTML and PDF output, which I doubt it what you'd want. Anyway, it seems to me that what you really want is to have an option for controlling what font is used for output of literallayout elements. Is that correct? If so, I'd like to ask that you instead file a feature request: http://docbook.sf.net/tracker/submit/request ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1809119&group_id=21935 |