I have some experience wrangling DocBook for the FreeBSD project; if
you'd be happy to tar up a copy of your workspace and email it over I'd
be glad to take a look if it will help.

Ceri

On Sun, Feb 17, 2008 at 12:45:08PM -0700, Rainer Heilke wrote:
> Greetings.
> 
> Well, the new sources didn't help. I checked the script, and it already 
> accounted for $BOOK.xml and $BOOK.book, so that was OK.
> 
> I updated the script to use common/xsolbook.dtd if there was no local dtd.
> 
> The script continues spewing parse errors faster than a dog scratching 
> fleas. Here's a (very) small sample after a ^C:
> 
> sparcpackagelist-sxde.xml:3242: parser error : Entity 'check' not defined
> </entry><entry><para>&check;</para>
>                              ^
> sparcpackagelist-sxde.xml:3243: parser error : Entity 'check' not defined
> </entry><entry><para>&check;</para>
>                              ^
> sparcpackagelist-sxde.xml:3250: parser error : Entity 'check' not defined
> </entry><entry><para>&check;</para>
>                              ^
> sparcpackagelist-sxde.xml:3251: parser error : Entity 'check' not defined
> </entry><entry><para>&check;</para>
>                              ^
> sparcpackagelist-sxde.xml:3252: parser error : Entity 'check' not defined
> </entry><entry><para>&check;</para>
>                              ^
> ...and so on for every page. I also saw the same for 'nbsp', 'ndash', 
> and others.
> 
> Each book seems to end with something like:
> 
> zfstrouble.xml:713: parser error : chunk is not well balanced
> </chapter>
>            ^
> ZFSADMIN.book:53: parser error : Failure to process entity zfstrouble
> differences;&zfspools;&zfsfs;&zfssnaps;&zfsacls;&zfsdeladm;&advanced;&zfstrouble
>  
>          ^
> ZFSADMIN.book:53: parser error : Entity 'zfstrouble' not defined
> differences;&zfspools;&zfsfs;&zfssnaps;&zfsacls;&zfsdeladm;&advanced;&zfstrouble
>  
>          ^
> unable to parse ZFSADMIN.book
> /work/DocTools/fop-0.94/fop: IFS=^J: is not an identifier
> 
> This last line indicates there may be a problem with the FOP tool (and a 
> look at the relevant line in the fop script bears this out), but I think 
> this is (as yet) irrelevant. Looking at the interim .fo files being 
> generated, they're all 0 bytes. If I have time, I'll do some more hunting.
> 
> So, no new PDFs yet. :-(
> 
> >> OK, I'll work on updating the script for the changes you mentioned 
> >> probably Saturday. So, with luck and the fixed source, maybe I can 
> >> have the PDF tarball up sometime Sunday PM.
> >>
> >>> OK, we found an offending parameter entity reference which is 
> >>> probably the cause of the parser errors.  I will push again tomorrow 
> >>> and let you know when new sources are available, thanks as always for 
> >>> your time to run the script and for reporting this.
> 
> Rainer
> -- 
> Mind the gap.
> _______________________________________________
> docs-discuss mailing list
> docs-discuss at opensolaris.org

-- 
That must be wonderful!  I don't understand it at all.
                                                  -- Moliere
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: 
<http://mail.opensolaris.org/pipermail/docs-discuss/attachments/20080217/b190f579/attachment.bin>

Reply via email to