C parser and deeply nested DTDs

Question

Your C parser is VERY fast :-),
but I am having trouble with deeply nested DTDs.
I can do DTD validation for an internal DTD and a single external DTD file.
My problem is with a DTD which includes other DTDs to a depth of 5 levels.
I am using the C XML parser v2.0.7 on Solaris 2.6.
My XML docs & their DTD are for an OAG Purchase Order (056_add_po_003.dtd or 056_add_po_006.dtd).
As these are OAG 'standards based' XML I cannot change the XML or DTD nesting.
The screen dump & error message I get was:
The error code after calling xmlinit() was >0<
startDocument
In line 20 of 056_add_po_006.xml:
In line 31 of 056_add_po_006.dtd:
In line 19 of oagis_resources.dtd [parameter entity RESOURCES]:
In line 57 of oagis_segments.dtd [parameter entity SEGMENTS]:
In line 4 of oagis_fields.dtd [parameter entity FIELDS]:
LPX-00252: invalid entity replacement-text nesting
The error code after calling xmlparse() was >252<
=================
Line 4 was:
<!ELEMENT ACCTPERIOD %STRDOM;>
The error is always at the same line of the oagis_fields.dtd dtd independent of whether I delete or move the 'ACCTPERIOD ELEMENT' that was at line 4.
The sample OAG PO XML and its DTDs were:
056_add_po_006.xml
056_add_po_006.dtd
oagis_domains.dtd
oagis_extensions.dtd
oagis_fields.dtd
oagis_resources.dtd
oagis_segments.dtd
are available from OAG: http://www.openapplications.org/xml/loadform.htm
You need to register to get the OAG docs but it is free.
Thanks for your Help
Doug.

Answer 1

The error message file lpxus.msg has a detailed explanation:
00252, 00000, "invalid entity replacement-text nesting"
// *Cause: Markup included from an entity must nest/group properly, that
// is, open/close markup must occur within the same entity.
// For example,
// <!DOCTYPE doc [ <!ENTITY e "</foo><foo>"> ]>
// <doc><foo>&e;</foo></doc>
// Is invalid since foo's start-tag occurs in the top-level
// document, but the close-tag is provided by the "e" entity.
// Both start and end must be provided by the same source.
// *Action: Stay away from tricky nonsense such as the above, it's
// not permitted.
null