docbook-apps

If I convert the attached Docbook 4 file via e.g.

xsltproc /usr/share/xml/docbook/stylesheet/docbook5/db4-upgrade.xsl db4.xml > db5.xml

the resulting Docbook 5 file drops the

Hi Jon,

Am Samstag, 2. November 2013, 03:08:33 schrieb Jon Leech:
> [...]
> the resulting Docbook 5 file drops the

On 11/02/2013 04:53 AM, Thomas Schraitle wrote:
> Hi Jon,
>
> Am Samstag, 2. November 2013, 03:08:33 schrieb Jon Leech:
>> [...]
>> the resulting Docbook 5 file drops the

Hi Jon,

I could be wrong (I'm away from my desk and writing this on my phone), but I think the reason is that parameter may not be legal inside term in 5.0.

Dick Hamilton



On Nov 3, 2013, at 17:34, Jon Leech <jon@alumni.caltech.edu> wrote:

> On 11/02/2013 04:53 AM, Thomas Schraitle wrote:
>> Hi Jon,
>>
>> Am Samstag, 2. November 2013, 03:08:33 schrieb Jon Leech:
>>> [...]
>>> the resulting Docbook 5 file drops the

Hi Dick,

Am Sonntag, 3. November 2013, 19:26:36 schrieb XML Press:
>
> I could be wrong (I'm away from my desk and writing this on my phone), but I
> think the reason is that parameter may not be legal inside term in 5.0.

I've checked the reference of parameter[1]: term allows the parameter element
(version 4 and 5).


[1] http://www.docbook.org/tdg5/en/html/parameter.html


--
Gruß/Regards
Thomas Schraitle

Hi Jon,

Am Sonntag, 3. November 2013, 01:34:03 schrieb Jon Leech:
> [...]
> > If I try your document with version 9783 it works.
>
> Thank you. That does help with this particular problem but introduces
> a new one: <varlistentry> elements containing e.g.
> <term><parameter>x</parameter></term>
> in the DB4 source are converted to
> <term>x</term>

I can confirm your analysis.


> The changes between the revs 7660 and 9783 of db4-upgrade.xsl were
> large and it's not easy to figure out why this behavior change
> occurred, given my limited understanding of XSL. I suspect I'll be
> better off accepting the issues from one or the other version and
> fixing them up after the translation.

The DocBook schema allows these elements inside term. So if the stylesheet
doesn't handle these elements correctly, it's a bug.

Could you add the following 3 lines into the latest db4-upgrade.xsl stylesheet
and try it again?

-------------
<xsl:template match="*" mode="clean-terms">
<xsl:apply-templates select="." mode="copy"/>
</xsl:template>
-------------

(You can add it below the <xsl:template match="glossterm|term"> template
rule).

The above template rule just copies any element inside term unless it is a
classsynopsis, cmdsynopsis, or any other "special" element. These are handled
differently.

If it works for you, I can update the stylesheet in the SVN repository.


--
Gruß/Regards
Thomas Schraitle

On 11/03/2013 04:56 AM, Thomas Schraitle wrote:
> Could you add the following 3 lines into the latest db4-upgrade.xsl stylesheet
> and try it again?
>
> -------------
> <xsl:template match="*" mode="clean-terms">
> <xsl:apply-templates select="." mode="copy"/>
> </xsl:template>
> -------------
>
> (You can add it below the <xsl:template match="glossterm|term"> template
> rule).
>
> The above template rule just copies any element inside term unless it is a
> classsynopsis, cmdsynopsis, or any other "special" element. These are handled
> differently.
>
> If it works for you, I can update the stylesheet in the SVN repository.

Thank you, Thomas! That lets through the various legal elements within
<term> and so seems to solve all the issues I've encountered to date with
the conversion. I did ask the Debian docbook5-xml package maintainers to
sync up with the Docbook top-of-trunk release, so hopefully the prepackaged
version will eventually get up to date as well.
Jon Leech

Hi Jon,

Am Sonntag, 3. November 2013, 13:11:25 schrieb Jon Leech:
> [...]
> > If it works for you, I can update the stylesheet in the SVN repository.
>
> Thank you, Thomas! That lets through the various legal elements within
> <term> and so seems to solve all the issues I've encountered to date with
> the conversion. I did ask the Debian docbook5-xml package maintainers to
> sync up with the Docbook top-of-trunk release, so hopefully the prepackaged
> version will eventually get up to date as well.

Ok, thanks for your test.

I've committed the patch[1] to the DocBook SVN repository now, it's in
revision 9828.


[1] http://sourceforge.net/p/docbook/code/9828

--
Gruß/Regards
Thomas Schraitle