Re: XML Catalog entries for docbook-xml
Jor-el <jorel@austin.rr.com> writes:
> The docbook-xml package bundles the dtd's from four different
> versions - 4.2, 4.1, 4.0 and 3.1.7 . The public id strings of the DTDs are
> very similar. Here are two examples :
>
> dbhierx.mod from 4.0 :
> "-//Norman Walsh//ENTITIES DocBk XML Document Hierarchy V4.0//EN"
> dbhierx.mod from 4.1 :
> "-//Norman Walsh//ENTITIES DocBk XML Document Hierarchy
> V4.1.2//EN"
>
> Since the public ids are _almost_ the same, delegating the lookups
> to a second level catalog from the root catalog isnt very efficient
> (though its technically feasible).
I'm just going to have to deal with it. I can't change these FPIs
without breaking lots of stuff for others.
> Here is another problem :
>
> soextblx.dtd from 4.2.cr1 :
> "-//OASIS/DTD XML Exchange Table Model 19990315//EN"
> soextblx.dtd from 4.1 :
> "-//OASIS/DTD XML Exchange Table Model 19990315//EN"
>
> There is no point in having two versions of the same file if there
> is no way the catalog heirarchy can distinguish between the two.
Already fixed in the latest. But I did do some grepping and find it's
also referenced by docbook 4.0 and not commented out. Will be fixed
in the next upload.
> So here is what I propose : the root catalog chain will only point
> to the most recent versions of DTDs when a package provides multiple
> versions. If this is not reasonable, please let me know at the earliest.
In the case of this file, it's very reasonable and what I've already
done in the latest docbook=xml. As for the DocBook DTDs, I have opted
to provide multiple versions of the DTDs to support people with
documents using the earlier version.
--
...Adam Di Carlo..<adam@onshore-devel.com>...<URL:http://www.onshored.com/>
Reply to: