forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clay Leeds <>
Subject Re: DocBook and numeric entity declaration
Date Fri, 22 Oct 2004 15:35:06 GMT
On Oct 21, 2004, at 10:45 PM, David Crossley wrote:
> Clay Leeds wrote:
>> Changing &rarr; to &#x2192; is an acceptable solution. The xml-fop
>> /forrest/ build does not error out when it tries to validate
>> 'properties.xml'. I made the change and checked it in.
>> I'd also like to resolve the error in Forrest if possible, so the rest
>> of this POST deals with that.
> I do not see any such problem. I have a test seed site
> that includes a couple of Full DocBook examples using the
> DocBook XSL and also processes them via Forrest's default
> docbook2document XSL. I can add an example character entity
> to them &rarr; and everything works perfectly:
> 'forrest validate' is fine
> and with 'forrest run' i see the entity rendered as "->"
> as expected.

Is it:
- just /forrest/ which doesn't render it?
- did you render xml-fop/ yesterday (after I changed it to its numeric 
entity: &#x2192;)?
- is this your own example which you added an example character entity?

> This is my document type declaration.
> <!DOCTYPE article
>   PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
>   "">
> Forrest resolves all the DTDs and *.ent properly.
> More below ...
>> I suspect the problem is related to the fact that properties.xml
>> references a dtd like this:
>> <!--
>> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
>>                            "docbookx.dtd">
>> -->
>> A couple of things I note here:
>> 1. It's commented out
> I don't understand. How can it ever work if it is commented out?

I suspected this may be the problem, but wasn't sure. However, even if 
it's not commented out, the docbookx.dtd file doesn't exist in that 
directory, so I'm thinking it would still fail.

> Remember, if you suspect issues with the catalog entity resolver
> then raise the verbosity level in src/core/context/WEB-INF/cocoon.xconf
> for the <entity-resolver> component. Then watch the messages
> when Cocoon starts and during 'forrest run'. You should see stacks
> of messages and then "Resolved public: ..." when the forrest catalog
> finds each DTD and *.ent file.
> --David

Actually, I didn't remember. Glad you brought that up. BTW, perhaps 
forrest could be improved with a note in the output/BUILD FAILED 
indicating this tip.

Web Maestro Clay
Clay Leeds - <>
Webmaster/Developer - Medata, Inc. - <>
PGP Public Key: <>

View raw message