Gav.... wrote: > Back again, > > > From: Gav.... > > > > A wee bit further now then but I reckon I am stuck at this point, > > > > I Commented out these > > > > <!ELEMENT acronym (%content.mix;)*> > > <!ATTLIST acronym %common.att;> > > > > And it all validates fine, can not test if acronym tags still work yet > > because I now get a build error :- > > > > Cannot find catalogManager.properties > > > > I have seen this before and generally does not fail a build, but this one > > :-
It is not an error. You can supply one if you want (see FAQ). I often wonder if we should add a default file just to shut that warning up. > > X [0] index.html BROKEN: > > org.apache.cocoon.acting.sourcetype,SourceTypeAction > > > > Is a new one on me, it may be something needs updating but I have no clue > > at > > the moment. > > > > Ideas? > > Well I have one of my own and it goes like this:- > > In input.xmap we have : > > <map:actions> > <map:action logger="sitemap.action.sourcetype" name="sourcetype" > src="org.apache.cocoon.acting.sourcetype.SourceTypeAction"> > <sourcetype name="glossary-v10"> > <document-declaration public-id="-//SAAFE//DTD Glossary V1.0//EN" > /> > </sourcetype> > </map:action> > </map:actions> > > The document-declaration points to I guess saafe.org and on this page [1] > A well know RDG :) says The SourceTypeAction doesn't "point to" anything. That <document-declaration> is declaring the Public Identifier to match in the input xml instances. See: SourceTypeAction (content aware pipelines) http://forrest.apache.org/docs/dev/cap.html We should be using an Apache public identifier. Follow some of the other Forrest DTDs for example syntax. I glanced at the Glossary DTDs and they already do. I reckon that you need to change the document type declaration in your xml instance to use those Apache IDs. Ditto in the SourceTypeAction above. > <quote>Fixme ( rdg ) > We should also support the public entity descriptor ("-//SAAFE/DTD Public > Document//EN") above.</quote> > > Not quite the same, anyhow, maybe this document-declaration should be > pointing somewhere else. Don't know what that means. Leave it until later. -David > I think I will have to wait on an answer here, in the meantime I can carry > on and start to populate the glossary.xml file. > > [1] - > http://www.saafe.org/documentation/rt/matchingInputAndOutputFormats.html > > Gav... > >
