Thanks, Mark. So much for using oXygen to check the docbook markup (although
it does find silly typos quite well). 
Will check as you suggest.
Atb,
Oliver
 

  _____  

From: Mark Miesfeld [mailto:miesf...@gmail.com] 
Sent: 15 August 2011 13:42
To: Open Object Rexx Users
Subject: [Oorexx-users] oodguide compile errors


Hi Oliver,
 
Now you get to enter into the fun part of compiling the doc. <grin>
 
If you look at the build output from last night on the build machine, you
will see that no oodguide.pdf exists.  This signals that the build for that
doc failed.  The next step is to open up the docs-buildrpt.txt file.
 
If you search for oodguide, you will find the section where it is being
compiled.  You can then locate the errors:
 
jade -t xml -d ../shared/oorexx.html.dsl -V html-index oodguide.xml
jade:Chapter04.xml:335:86:E: end tag for "LINK" omitted, but OMITTAG NO was
specified
jade:Chapter04.xml:334:38: start tag was here
jade:Chapter04.xml:500:61:E: document type does not allow element
"PROGRAMLISTING" here; assuming missing "FOOTNOTE" start-tag
jade:Chapter04.xml:512:23:E: character data is not allowed here
jade:Chapter04.xml:512:64:E: document type does not allow element
"COMPUTEROUTPUT" here; missing one of "SYNOPSIS", "LITERALLAYOUT",
"PROGRAMLISTING", "SCREEN", "PARA", "SIMPARA" start-tag
jade:Chapter04.xml:512:88:E: character data is not allowed here
jade:Chapter04.xml:513:28:E: document type does not allow element
"COMPUTEROUTPUT" here; missing one of "SYNOPSIS", "LITERALLAYOUT",
"PROGRAMLISTING", "SCREEN", "PARA", "SIMPARA" start-tag
jade:Chapter04.xml:513:52:E: character data is not allowed here
jade:Chapter04.xml:515:27:E: document type does not allow element
"COMPUTEROUTPUT" here; missing one of "SYNOPSIS", "LITERALLAYOUT",
"PROGRAMLISTING", "SCREEN", "PARA", "SIMPARA" start-tag
jade:Chapter04.xml:515:61:E: character data is not allowed here
jade:Chapter04.xml:522:18:E: character data is not allowed here
jade:Chapter04.xml:524:27:E: document type does not allow element
"COMPUTEROUTPUT" here; missing one of "SYNOPSIS", "LITERALLAYOUT",
"PROGRAMLISTING", "SCREEN", "PARA", "SIMPARA" start-tag
jade:Chapter04.xml:524:58:E: character data is not allowed here
jade:Chapter04.xml:527:50:E: end tag for "FOOTNOTE" omitted, but OMITTAG NO
was specified
jade:Chapter04.xml:500:46: start tag was here
jade:Chapter04.xml:527:50:E: end tag for "LINK" omitted, but OMITTAG NO was
specified
jade:Chapter04.xml:496:88: start tag was here

 
Usually the tag errors, which occur frequently when you are doing a lot of
editing, are relatively easy to fix. The numbers following the file names
are the line and character position of the error.
 
If you have problems fixing the tags, let us know and we'll give you some
help.  David is actually the expert, but most of the time the error is
pretty straight forward.
 
--
Mark Miesfeld
------------------------------------------------------------------------------
uberSVN's rich system and user administration capabilities and model 
configuration take the hassle out of deploying and managing Subversion and 
the tools developers use with it. Learn more about uberSVN and get a free 
download at:  http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users

Reply via email to