Thanks.  It works now.
-derek

PS: I get nightly mail about the cron job failure.  I just haven't looked
into it in a while..

On Thu, August 25, 2011 12:17 pm, Cristian Marchi wrote:
> It should be fixed now. I forgot to add the xml files for chapter 16 and
> 17.
> Thanks for noticing this problem.
>
> Cristian
>
> Il 25/08/2011 17:48, Derek Atkins ha scritto:
>> There is a bug in the docs build:
>>
>> make[2]: Entering directory
>> `/u1/home/gnucash/gnucash-docs/trunk/guide/ja_JP'
>> /bin/sh /home/gnucash/gnucash-docs/trunk/install-sh -d "gnucash-guide";
>> \
>> for file in gnucash-guide.xml; do \
>>   xsltproc -o "gnucash-guide/" --param use.id.as.filename "1" \
>>                             --stringparam chunker.output.encoding UTF-8
>> \
>>   "../../xsl/general-customization.xsl" "./$file"; \
>> done
>> warning: failed to load external entity "ch_oth_assets.xml"
>> ./gnucash-guide.xml:340: parser error : Failure to process entity
>> chapter16
>> &chapter16;
>>             ^
>> ./gnucash-guide.xml:340: parser error : Entity 'chapter16' not defined
>> &chapter16;
>>             ^
>> warning: failed to load external entity "ch_python_bindings.xml"
>> ./gnucash-guide.xml:341: parser error : Failure to process entity
>> chapter17
>> &chapter17;
>>             ^
>> ./gnucash-guide.xml:341: parser error : Entity 'chapter17' not defined
>> &chapter17;
>>             ^
>> unable to parse ./gnucash-guide.xml
>> make[2]: *** [convert-html] Error 6
>> make[2]: Leaving directory
>> `/u1/home/gnucash/gnucash-docs/trunk/guide/ja_JP'
>>
>> -derek
>>
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>


-- 
       Derek Atkins                 617-623-3745
       de...@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant

_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to