asciidoc + docbook problems on slackware64-current

Ron Parker · 07-17-2009, 11:32 AM

A couple years ago, I was able to fix my docbook2... problems on Slackware-12.0, but I have not been able to do so on slackware64, yet.

Even with a simple test.txt:

Title
=====
Hello

asciidoc -a numbered -b docbook test.txt
db2rtf test.xml

produces

Using catalogs: /usr/share/sgml/docbook/dsssl-stylesheets-1.79/dtds/html/catalog, /usr/share/sgml/docbook/dsssl-stylesheets-1.79/print/catalog, /usr/share/sgml/docbook/dsssl-stylesheets-1.79/common/catalog, /usr/share/sgml/docbook/dsssl-stylesheets-1.79/catalog, /usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/catalog, /usr/share/sgml/docbook/sgml-dtd-4.5/catalog, /usr/share/sgml/docbook/sgml-dtd-3.1/catalog, /usr/share/sgml/openjade-1.3.2/catalog, /usr/share/sgml/sgml-iso-entities-8879.1986/catalog
Using stylesheet: /usr/share/sgml/docbook/utils-0.6.14/docbook-utils.dsl#print
Working on: .../test.xml
jade:<URL>http://www.oasis-open.org/docbook/xm...4.ent:42:30:E: "1D6C2" is not a character number in the document character set
jade:<URL>http://www.oasis-open.org/docbook/xm...4.ent:43:30:E: "1D6C3" is not a character number in the document character set
...

This seems to happen for all the db2... that I have tried. Any ideas?

drmozes · 07-17-2009, 01:04 PM

Quote:

Originally Posted by Ron Parker

A couple years ago, I was able to fix my docbook2... problems on Slackware-12.0, but I have not been able to do so on slackware64, yet.

Even with a simple test.txt:

Title
=====
Hello

asciidoc -a numbered -b docbook test.txt
db2rtf test.xml

Please can you send the test file & method to mozes at slackware.com and I'll have a look at it.

Did you try this on 32bit Slackware?

drmozes · 07-17-2009, 01:29 PM

Quote:

Originally Posted by drmozes

Please can you send the test file & method to mozes at slackware.com and I'll have a look at it.

Did you try this on 32bit Slackware?

I got this working with the older version of asciidoc that was bundled with linuxdoc-tools 0.9.21 build, but I get the same problem.

I'll look into it. It probably needs an update of some catalogues or something.