Re: more verbosity in forrest validate

[Dave Brondsema <da...@brondsema.net>]

Joao Miguel Ferreira wrote:
> Hello all,
> 
> is it possible for "forrest validate" to output some more verbose
> explanations about what went wrong ?
> 

The goal of "forrest validate" is just to make sure that the input is 
good enough for forrest to process.  You should use a DTD validator when 
editing XML files; it will provide much better error messages an often 
have useful interfaces to help you build the document.  See 
http://forrest.apache.org/docs/catalog.html for instructions on setting 
up editors to use the Forrest DTD catalog.


-- 
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal

Re: more verbosity in forrest validate

[David Crossley <cr...@apache.org>]

Dave Brondsema wrote:
> Joao Miguel Ferreira wrote:
> > Hello all,
> > 
> > is it possible for "forrest validate" to output some more verbose
> > explanations about what went wrong ?
> 
> The goal of "forrest validate" is just to make sure that the input is 
> good enough for forrest to process.  You should use a DTD validator when 
> editing XML files; it will provide much better error messages an often 
> have useful interfaces to help you build the document.  See 
> http://forrest.apache.org/docs/catalog.html for instructions on setting 
> up editors to use the Forrest DTD catalog.

Yes, i use the command-line 'xmllint' from the
libxml2 package. It has reasonable error messages.

However, the normal 'forrest validate' should give you
better error messages that just "Could not validate document".
So there must be something seriously wrong with your
xml files.

Anyway, doing 'forrest -v validate' provides more
verbose output.

-- 
David Crossley