4.2 in the new repo, yes. It doesn't fail. I happend to notice the severe message as it ran by
mobile biligual spell checker used Op 4 okt. 2013 16:22 schreef "David Nalley" <da...@gnsa.us>: > Bah - I hit send without dealing with the second question. > > On Fri, Oct 4, 2013 at 9:15 AM, Daan Hoogland <daan.hoogl...@gmail.com> > wrote: > > H, > > > > I started building the docs of the 4.2 tree, using the cfg > publican-all.cfg > > I fails. Is there a defined set of targets that must/should build in the > > docs? > > > > > > Processing file tmp/en-US/xml_tmp/zone-add.xml -> > > tmp/en-US/xml/zone-add.xml > > Beginning work on en-US > > Validation failed: > > hypervisor-support-for-primarystorage.xml:6: validity error : ID > > hypervisor-support-for-primarystorage already defined > > add-remove-nic.xml:31: validity error : ID prereq-addnic already defined > > api-throttling.xml:6: validity error : ID api-throttling already defined > > api-throttling.xml:30: validity error : ID api-throttling-configure > already > > defined > > api-throttling.xml:61: validity error : ID api-throttling-limitations > > already defined > > globally-configured-limits.xml:6: validity error : ID > > globally-configured-limits already defined > > configure-package-repository.xml:28: validity error : IDREF attribute > > linkend references an unknown ID "sect-source-buildrpm" > > management-server-install-multi-node.xml:30: validity error : IDREF > > attribute linkend references an unknown ID "sect-source-buildrpm" > > using-netscaler-load-balancers.xml:41: validity error : IDREF attribute > > linkend references an unknown ID "external-guest-lb-integration" > > configure-package-repository.xml:28: validity error : IDREF attribute > > linkend references an unknown ID "sect-source-builddebs" > > management-server-install-multi-node.xml:30: validity error : IDREF > > attribute linkend references an unknown ID "sect-source-builddebs" > > > > also the other targets flash by the following > > > > Oct 4, 2013 3:12:03 PM org.apache.fop.hyphenation.Hyphenator > > getHyphenationTree > > SEVERE: Couldn't find hyphenation pattern en > > > > I read I should ignore warnings and this one says severe. How important > is > > hyphenation in english? > > > > thanks, > > Daan > > > You are doing this in the new cloudstack-docs repo on the 4.2 branch? > I have been building admin and install guides, so I know they aren't > broken and don't have validity errors. If it's only publican-all that > is broken I am happy to git rm that file :) > > Re FOP warnings, if it builds, ignore them, FOP complains loudly about > lots of things that might matter to people doing magazine layout, but > not to tech manuals. >