is there a script/macro to register them in a postinstall hook or similiar? 
 
 

Karl, can you please help out here? Note that the file the bug report refers 
to is just a copy of the docbook DTD, which we can easily symlink (not for 
10.0 though). But kdelibs3-doc still installs other catalog files not 
registered (.../customization/catalog) 

stupid web interface. Karl, please look above  

docbookx.dtd version 4.2 also comes with docbook_4.  With docbook_4 installed
arbitrary DTD aware parsers are able to validate KDE documentation.  The report
looks invalid to me.

as I said in #2, the report itself is bogus, yes.  
 
But KDE docbook looks like this: 
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" 
"dtd/kdex.dtd" 

Could you explain how the report is invalid?

The problem isn't that there is no dtd installed that will allow the document to
be parsed.  The problem is that there's no way for a standard parser to find the
dtd based on the doctype declaration as quoted above.  dtd/kdex.dtd isn't a
proper uri, so we can't search based on that.  The standard way to turn the
string "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" into a DTD is to
look in /etc/xml/catalog, but it's not in there anywhere.

How is an arbitrary xml parser supposed to find the DTD?

Okay, dtd/kdex.dtd is a different story.

I will write a recipe.

for 10.1 - I hope that's okay with you.

see comment #7 and comment #8

-------------------------------------------------------------------
Wed Sep 21 23:01:32 CEST 2005 - ke@suse.de

- Add KDE docbook customizations to the SGML resp. XML catalog system [#
  113080].

-------------------------------------------------------------------

untested.

Also check SGML catalog and make use of toms converter script.

Issue was already fixed with the patch applied on 2005-09-21.  In case of trouble, please reopen and provide a test case.