On Jul 28, 2004, at 11:47 AM, Simon Pepping wrote:
On Sun, Jul 25, 2004 at 12:46:03PM -0700, Clay Leeds wrote:
(More comments inline)

On Jul 25, 2004, at 11:41 AM, Simon Pepping wrote:
I have tried to build the site with forrest, without much success. I
had a few problems:

1. Validation error. I solved this problem by creating an OASIS
catalog.

I solved this by essentially replacing the xml-fop/.../sitemap.xmap file with a 'clean' version from forrest. I then added the ==== FOP ADDITIONS ==== section.

When online, validation succeeds because the system ids point to the CVS. Offline, most validation succeeds due to forrest's catalog, which points to local copies of the DTDs. This does not work for compliance.xml, which uses its own DTD. There is an SGML Open Catalog for it, but apparently that is not used. I added an OASIS XML catalog, and now the local copy of the DTD in my CVS working directory is used.

I'd like to figure out how to do that. I'm using eclipse for much of my editing...


2. Files in build/webapps/content are missing. These problems can be
solved
  by copying src/documentation/content into webapps, or by replacing
  in sitemap-0.5.xmap all source references to content/ with
  {project:content}, whatever that may mean.

I don't recall why a sitemap-0.5.xmap was created, but I removed it completely.

It is still in our CVS repository. And it is the sitemap which forrest uses in my local build.

True. I didn't remove it from CVS. I removed it from my local copy at the request of the forrest-dev folks who were helping me. In fact, I eradicated both sitemap*.xmap files from my local directory.


My plan (when I get Forrest building successfully!) is to replace all forrest-related files (forrest.properties, site.xml, sitemap.xmap, etc.) and eradicate those which are not needed (sitemap-0.5.xmap, as well as all of those book.xml files--these are all replaced by site.xml--unless there's a compelling reason for them).

Regards, Simon

Thanks for the message. I'm looking forward to getting the forrest stuff *&* your documentation files in xml-fop!


Web Maestro Clay



Reply via email to