It's done it's done... Sebastien helped us nailed it down the issue. Doc is building, finally !
Who is treating Sebastien ? -----Original Message----- From: Sebastien Goasguen [mailto:run...@gmail.com] Sent: Monday, November 25, 2013 4:29 PM To: dev@cloudstack.apache.org Subject: Re: [Doc] Validation Issue in Release Notes On Nov 25, 2013, at 5:40 AM, Abhinandan Prateek <abhinandan.prat...@citrix.com> wrote: > There are some issues with the 4.2/master docs. 4.2 is a priority. > > Anyone who fixes the build gets a special mention in the release notes ! > Now can we have someone fix this. > I can't even locate: en-US/Revision_History.xml > -abhi > > On 23/11/13 4:20 pm, "Radhika Puthiyetath" > <radhika.puthiyet...@citrix.com> wrote: > >> Hi, >> >> Sorry for cross-posting. >> >> While validating the Release Notes by using publican, there is a >> validity issue which I am not able to resolve. >> >> The command used is: >> >> >> Publican build -format=test -langs=en-us -config=publican.cfg. >> >> >> The error I am getting is the following: >> >> Release_Notes.xml:3509: validity error : Element listitem content >> does not follow the DTD, expecting (calloutlist | glosslist | >> bibliolist | itemizedlist | orderedlist | segmentedlist | simplelist >> | v ariablelist | caution | important | note | tip | warning | >> literallayout >> | programlisting | programl >> istingco | screen | screenco | screenshot | synopsis | cmdsynopsis | >> funcsynopsis | classsynopsis | fieldsynopsis | constructorsynopsis | >> destructorsynopsis | methodsynopsis >> | formalpara | para | simp >> ara | address | blockquote | graphic | graphicco | mediaobject | >> mediaobjectco | informalequation | informalexample | informalfigure | >> informaltable | equation | example | figure | table | msgset | pr >> ocedure | sidebar | qandaset | task | anchor | bridgehead | remark | >> highlights | abstract | authorb lurb | epigraph | indexterm | >> beginpage)+, got (para programlisting CDATA) >> >> The issue is that the CDATA cannot be located in the file. If it is >> removed, we can successfully build the file. The issue persists on >> both Master and 4.2 >> >> Thanks in advance >> >> -Radhika >