[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] groff output bug
Regarding the stuck font change: if groff is like other troffs, then it doesn't maintain a font change stack, just a single "previous" font. It is possible that nested elements are causing nested font changes, leaving the "previous" font as bold instead of normal. For example, a bold font change nested inside an italic font change would do this: This is \fI italic stuff \fB now bold \fP now back to italic \fP now back to bold for the rest of the text. I'm not familiar enough with the stylesheet to tell you where that is happening, though. Regarding the olinks inserting Unicode characters, I have to say that I never tried to do olinks with plain text output. You may run into other Unicode character references being inserted into the manpage output. The Unicode characters come from the gentext templates, so you could work around it by customizing those to remove all such special character references. Then when you process your file set the 'use.local.olink.style' parameter to 1 to use your gentext templates instead of the original ones that created the olink database. That's about all the help I can give at this point. Bob Stayton Sagehill Enterprises DocBook Consulting bobs@sagehill.net ----- Original Message ----- From: "Sam Steingold" <sds@gnu.org> To: "Bob Stayton" <bobs@sagehill.net> Cc: <docbook-apps@lists.oasis-open.org> Sent: Sunday, May 16, 2004 7:46 AM Subject: Re: [docbook-apps] groff output bug > > * Bob Stayton <obof@fntruvyy.arg> [2004-05-15 23:30:53 -0700]: > > > > Are you are using the manpages/docbook.xsl stylesheet in the 1.65.1 > > XSL stylesheet distribution to generate roff man page code from > > refentry elements? > > yes. > > > If so, that stylesheet does not even have a template for <emphasis>, > > and it gets no markup in my testing. > > OK, sorry, the specific elements which result in bold runs are > (see clisp/doc/clisp.xml.in in the CLISP CVS) > <ulink><function>READ</function></ulink> > <ulink><command>CLISP</command></ulink> > <command>clisp</command> > <command>base</command> > <envar>LANG</envar> > <option><link>-ansi</link></option> > <term><option>-C</option></term> > <command>#!</command> > > Note also that > <olink targetdoc="impnotes" targetptr="dffi"/> > is rendered as > Section 30.3, > “Extensions-2.3. The Foreign Function Call Facili- > ty” > > I don't think that "“" and "”" are appropriate here. > > you can find all my files and complete setup here: > <http://cvs.sourceforge.net/viewcvs.py/clisp/clisp/doc/> > > -- > Sam Steingold (http://www.podval.org/~sds) running w2k > <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> > <http://www.mideasttruth.com/> <http://www.honestreporting.com> > Sufficiently advanced stupidity is indistinguishable from malice. > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]