I may be misunderstanding you, Rich, but print composers do (eg,
Arbortext to PDF). It uses the relationships to autonumber TOCs,
references to work packages, steps, figures, etc. See 40051-B/C xrefs.
It has the nasty side effect that even in very large manuals, the
contents all have to be in a single file so when the page count gets
about say 1200 pages, a compose cycle can be fifteen or twenty
minutes. Tough when testing.
len
Quoting Richard Salz <>:
>> So, why can't XML documents have loops (cycles)? Why doesn't an XML
>> parser have to worry about falling into an infinite loop?
>
> Because an XML parser does not follow ID/IDREF's. What standard tools do?
>
>
> --
> STSM, WebSphere Appliance Architect
> https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe:
> subscribe:
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>
