docbook-apps

  • 1.  manpages output: \n not escaped to \\n?

    Posted 12-04-2006 19:07
    I'm finding in manpage output that text such as \t
    is output as \\t (correct), but \n is output as \n
    (that is, unchanged, and incorrect).

    I look in manpages/params.xsl, where I find this:



    <substitution oldstring="\\fB" newstring="\fB"/>
    <substitution oldstring="\\fI" newstring="\fI"/>
    <substitution oldstring="\\fR" newstring="\fR"/>
    <substitution oldstring="\\n" newstring="\n"/>

    If I remove that last line, the output comes out
    correctly as far as I can see (that is, \n is output
    as \\n). Comparing the old and new output for several
    manpages, I can't find other effect. But perhaps there is
    a better fix for the problem?



  • 2.  Re: [docbook-apps] manpages output: \n not escaped to \\n?

    Posted 12-05-2006 14:50
    Paul DuBois <paul@kitebird.com>, 2006-12-04 13:06 -0600:

    > I'm finding in manpage output that text such as \t
    > is output as \\t (correct), but \n is output as \n
    > (that is, unchanged, and incorrect).
    >
    > I look in manpages/params.xsl, where I find this:
    >
    >
    >
    > <substitution oldstring="\\fB" newstring="\fB"/>
    > <substitution oldstring="\\fI" newstring="\fI"/>
    > <substitution oldstring="\\fR" newstring="\fR"/>
    > <substitution oldstring="\\n" newstring="\n"/>
    >
    > If I remove that last line, the output comes out
    > correctly as far as I can see (that is, \n is output
    > as \\n). Comparing the old and new output for several
    > manpages, I can't find other effect. But perhaps there is
    > a better fix for the problem?

    I guess I put that substition in there for some reason, but I
    don't remember why now. I'll have to go back through the commit
    logs and see. Anyway, there probably is some better fix. The
    substition thing in the params.xsl file is just a hack to
    workaround some cases I couldn't otherwise deal with in the
    main part of manpages stylesheet.

    --Mike