I don't have a system with plain nroff to test this on, so I'm not clear on
what exactly the problem is or how to fix it.

Do you know if the issue is the use of macro
names longer than two characters, or the use of built-in groff instructions
that don't work with plain nroff?  If it is the former, then it could be
easily fixed by renaming defined macros, but if it is the latter,
then it will be harder.

If you manage to get a new 'define.macros' working, you could submit it for
inclusion and we could add it to the stylesheet with an option parameter to
turn it on.

Bob Stayton
Sagehill Enterprises
[email protected]


----- Original Message ----- From: "Ralph Böhme" <[email protected]>
To: <[email protected]>
Sent: Tuesday, February 03, 2009 2:47 AM
Subject: [docbook-apps] manpage/docbook.xsl generated code broken for nroff


Hello list,

I'm facing another problem with the manpage generation from Docbook
source:
I'm using `xsltproc` with the 1.74.0 XSL manpage/docbook.xsl stylesheet.

So far the manpages look allright on platforms that are using groff  for
formatting (linux, OS X), but on plattform where nroff is used  (Solaris,
Opensolaris) _all_ manpages come out bad, only header and  footer are
shown.

I've isolated the problematic code: it's coming from the template
"define.macros" in manpages/other.xsl. If I remove the following  macros,
nroff processes the manpages ok: toupper, SH-xref, SH, SS.

The unedited generated manpage is attached. Source:
http://netatalk.cvs.sourceforge.net/viewvc/netatalk/netatalk-docs/manual/man/man1/achfile.1.xml?revision=1.4&view=markup

Imo the XSL stylesheet should be fixed to also support other *roff
implementations than groff. Until then I guess I'll have to somehow
inject my own "define.macros" stylesheet.

-Ralph

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to