Administration > Environment Variables > APTFRAGCX — Ignoring the Context String During e-i-c Matching
  
APTFRAGCX — Ignoring the Context String During e-i-c Matching
The APTFRAGCX environment variable controls how Arbortext Editor performs FOSI e-i-c matching when you edit a fragment as a standalone document. By default, Arbortext Editor matches each e-i-c in a fragment based on the fragment's position in its parent document. Setting the APTFRAGCX environment variable to none will instruct Arbortext Editor to ignore the fragment's position in its parent document.
When a fragment of a larger SGML document is saved as a separate file entity or document object, Arbortext Editor normally stores a context string in the fragment to indicate the fragment's context within the larger document. In file entities, the context string is stored with the Pub CX processing instruction. In document objects, the context string is stored as a metadata entry in the document management system.
However, when a fragment of a larger XML document is saved, Arbortext Editor normally does not store a context string. If you are editing a fragment that does not have a context string stored in it, Arbortext Editor interprets APTFRAGCX as none. Because XML files normally do not contain the context string PI, context checking interprets APTFRAGCX as none. To supply more context for eic matching in an XML document, you can add the context string PI to an XML file using a text editor. Arbortext Editor preserves the context string PI when the file is saved.
For example, the following fragment has a Pub CX PI:
<!-- Fragment document type declaration subset:
PTC Inc., 1988-1999, v.4002
<!DOCTYPE SET PUBLIC "-//Davenport//DTD Docbook V4.0//EN">
-->
<?Pub CX set(book(article(artheader()>
<programlisting>
This is a test.
This is only a test.
</programlisting>
Assume that the FOSI includes the following e-i-c's for programlisting:
<e-i-c gi="programlisting" context="article">
<e-i-c gi="programlisting">
By default, Arbortext Editor would examine the context string (that is, the line starting with <?Pub CX), determine that the programlisting element occurs within article, and display the element using the first e-i-c entry. If you had set the APTFRAGCX to none, Arbortext Editor would ignore the context string and display the element using the second e-i-c entry.
An example of this practice would be to create a FOSI that would format a chapter differently based on whether it was being edited or printed as a part of a book, or as a standalone document.