cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@indexgeo.com.au>
Subject entity resolution for documentation builds
Date Thu, 25 Oct 2001 09:00:34 GMT
Now that entity catalogs and the entity resolver are properly
implemented, the next step is to apply them to the documentation
build. I already have this functioning correctly in my local
working copy. Also the document xdocs/catalog-test.xml
is already proving that it works.

However, i do not want to just spring it on you by cvs commit.
Here is the plan ...

1) Add new entries for each DTD that is used by xdocs into
the catalog at webapp/resources/entities/catalog

2) Copy the DTDs from documentation/xdocs/dtd/
to webapp/resources/entities/
Leave the original DTDs in place at documentation/xdocs/dtd/
until we are completely satisfied.

3) Commit all of that.

4) Watch the output from "build docs". You will see messages
from the entity resolver as it finds the relevant DTDs, etc.
The parser is using the entity resolver to find the relevant
centralised DTD rather than following a hard-coded path to
a relative location.

5) Ensure that all xdocs/*.xml have the proper Document Type
Declaration.

6) Fix validation errors with some xdocs that currently have
their Document Type Declaration commented-out.

If there are no objections, then i will proceed with that
tomorrow. Steps 5 and 6 can follow in due course.

--David


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message