copying this to forrest-dev for feeback.
Thanks :-)
Victor Mote wrote:
Keiron Liddle wrote:
I wouldn't recommend putting the dtd's in our cvs, one version is
better.
In principle I agree. I think the best solution is for Forrest to make them
available in a small download.
The are some p
Keiron Liddle wrote:
> I wouldn't recommend putting the dtd's in our cvs, one version is
> better.
In principle I agree. I think the best solution is for Forrest to make them
available in a small download.
> The are some pages describing the dtd but I presume you mean for
> editing. I think it w
Christian Geisert wrote:
> Hmm .. if you are working on the documention you'll need forrest anyway
> to render the pages.
I don't really want to render the pages, just work on the content.
> > could suggest to the forrest group that they make these items directly
> > available on their web-site
Hi Victor,
I wouldn't recommend putting the dtd's in our cvs, one version is
better.
The are some pages describing the dtd but I presume you mean for
editing. I think it would be useful to make them downloadable separately
just for editing.
You still need forrest to do the verifying and generation
Victor Mote wrote:
Keiron:
It looks like most of the documents in src/documentation/contents/xdocs use
Public IDs for their DTD declarations. The forrest web site indicates that
it has a catalog that maps these Public IDs. However, it looks like one has
to download forrest to get either the catal
Keiron:
It looks like most of the documents in src/documentation/contents/xdocs use
Public IDs for their DTD declarations. The forrest web site indicates that
it has a catalog that maps these Public IDs. However, it looks like one has
to download forrest to get either the catalog or the DTDs. Do y
