Question
APP: More questions
Some addiional questions have occurred to me about using APP:
- Chapter 2 of the APP Users Guide is about the APP User Interface. How is it accessed?I saved a sample XML document as a .3d file, but it opened in Arbortext Editor as ASCII text.
- Does APP have anything like the FOSI formatting pass reduction feature?
- FOSI uses cache files to speed up formatting after a document has been formatted once. Does APP have anything similar?
- Does APP have anything like the FOSI formatting faults feature?
- Are there any books out or in the works about APP?
Thinking about FOSI publishing solutions I know about, some additional questions come to mind:
- Is is true that APP does not support run-in titles? Run-in titles are required in milspec documents.
- Can APP write an external ASCII file with or without markup?
- Can APP formatArbortextuser-defined tags (UDTs)?
- Can APP test and use the value of an ACL variable? For example, a user selects a custom menu item such as File->Print->Glovebox Size, which sets $booksize=glovebox to tell the stylesheet to use different formatting specs than when $booksize=standard. (An ACL variable is used when the doctype does not have an attribute for this purpose, or it is not desirable to store the setting with the document.)
- Does APP support Arbortext pseudo-attributes? A pseudo-attribute may be used instead of the ACL variable in the above example. (A pseudo-attribute is used when the doctype does not have an attribute for this purpose, and the pseudo-attribute setting should be saved with the document.)
- Can APP detect when a warning is too deep for the column depth, and in some way change the warning to a smaller font size and leading amount, repeating the process until the warning fits or no smaller font and leading can be used? With FOSI, when the warning must be edited, a message ito that effect is displayed in the Edit window.
- When page numbering continues from one volume to the next, but the volumes are not published at the same time, is there a way to provide APP with the appropriate page number initialization when each volume is published?
- "Print/PDF Output via APP" in the Styler Users Guide describes APP limitations in Styler, which impact tables and graphics as well as other areas in Styler. For example:
"Settings made in the Minimum field for the Allow space to varyoptions are ignored - space will be stretched between thePreferred and Maximum values."Can APP source edits make a difference?What about native APP?
- According to the Styler Users guide, Sylerdoes not support security classification.What about APP source edits? Native APP?
- Accordingto the Styler Users guide,Styler does not support formatting of equations created byArbortext’s equation editor.What aboutAPPsource edits? Native APP?
- Accordingthe Styler Users Guide,Styler does not support Touchup PIs. Can Touchup PIs be supported with APP source edits? Native APP?
- It appears that Styler for APP does not support overlays? What aboutAPPsource edits? Native APP?
- Styler does not provide for a generated List of Effective Pages. Can an LEP be generated with APP source edits?Native APP?
- Can an APP-generated index be exported for additional processing and then imported for additional processing and output by the formatting engine?
- Styler says "advanced parameters" for indexing are available only with FOSI and XSL. The Styler Users Guide says to search Arbortext Editor Help for "Useparams and other customizations," which yields the extract below.Will APP source edits handle these capabilities? Native APP?
Useparams and other customizationsDepending on the content and placement of the index savetexts and various useparam settings, it is possible to customize the behavior of index entries. A useparam is set in the usetext that outputs the index string. If multiple useparams are set they should be separated by a space as in the following example. <usetext source="index.app" userule="2"<br"/> useparam="index_levels=5 mergeinhibit=-3"></usetext>
Topics covered in this section:
| | • | Specifying more than 4 levels in an entry (index_levels) |
| | • | Specifying a maximum number of page references (maxlocators) |
| | • | Controlling merging of page numbers (maxunmerge) |
| | • | Controlling merging of entries (mergeinhibit) |
| | • | Allowing empty headings in entries (allowemptyheadings) |
| | • | Allowing empty headings in entries – FOSI technique |
| | • | Specifying behavior of spaces (keep_all_space, keep_leading_space, keep_trailing_space, keep_embedded_space) |
| | • | Specifying behavior of leading punctuation (sortleadpunc) |
| | • | Specifying behavior of markup in page locators (locmarkuppriority) |
| | • | Specifying a language for sorting (language) |
| | • | Sorting by a subsequent level heading |
| | • | Specifying placement of see and see also references (seeorder) |
| | • | Allowing page numbers and/or see also references with see references (allowseenotalone) |
| | • | Renaming preliminary and final index markup |
| | • | Eliminating page numbers for upper level entries |
| | • | Eliminating page numbers for entries altogether |
| | • | Forcing page ranges using <ixstart> and <ixend> |
| | • | Generating running head1ers |
| | • | Generating “(contd.)” at column breaks in an index |
| | • | Specifying Korean_mode index options |
| | • | Specifying Chinese_mode index options |
| | • | Changing index formatting for materials published onlinez
|
I hope this is helpful! Please let me know any questions you may have.
Suzanne Napoleonwww.FOSIexpert.com"WYSIWYG is last-century technology!"
- Chapter 2 of the APP Users Guide is about the APP User Interface. How is it accessed?I saved a sample XML document as a .3d file, but it opened in Arbortext Editor as ASCII text.
- Does APP have anything like the FOSI formatting pass reduction feature?
- FOSI uses cache files to speed up formatting after a document has been formatted once. Does APP have anything similar?
- Does APP have anything like the FOSI formatting faults feature?
- Are there any books out or in the works about APP?
Thinking about FOSI publishing solutions I know about, some additional questions come to mind:
- Is is true that APP does not support run-in titles? Run-in titles are required in milspec documents.
- Can APP write an external ASCII file with or without markup?
- Can APP formatArbortextuser-defined tags (UDTs)?
- Can APP test and use the value of an ACL variable? For example, a user selects a custom menu item such as File->Print->Glovebox Size, which sets $booksize=glovebox to tell the stylesheet to use different formatting specs than when $booksize=standard. (An ACL variable is used when the doctype does not have an attribute for this purpose, or it is not desirable to store the setting with the document.)
- Does APP support Arbortext pseudo-attributes? A pseudo-attribute may be used instead of the ACL variable in the above example. (A pseudo-attribute is used when the doctype does not have an attribute for this purpose, and the pseudo-attribute setting should be saved with the document.)
- Can APP detect when a warning is too deep for the column depth, and in some way change the warning to a smaller font size and leading amount, repeating the process until the warning fits or no smaller font and leading can be used? With FOSI, when the warning must be edited, a message ito that effect is displayed in the Edit window.
- When page numbering continues from one volume to the next, but the volumes are not published at the same time, is there a way to provide APP with the appropriate page number initialization when each volume is published?
- "Print/PDF Output via APP" in the Styler Users Guide describes APP limitations in Styler, which impact tables and graphics as well as other areas in Styler. For example:
"Settings made in the Minimum field for the Allow space to varyoptions are ignored - space will be stretched between thePreferred and Maximum values."Can APP source edits make a difference?What about native APP?
- According to the Styler Users guide, Sylerdoes not support security classification.What about APP source edits? Native APP?
- Accordingto the Styler Users guide,Styler does not support formatting of equations created byArbortext’s equation editor.What aboutAPPsource edits? Native APP?
- Accordingthe Styler Users Guide,Styler does not support Touchup PIs. Can Touchup PIs be supported with APP source edits? Native APP?
- It appears that Styler for APP does not support overlays? What aboutAPPsource edits? Native APP?
- Styler does not provide for a generated List of Effective Pages. Can an LEP be generated with APP source edits?Native APP?
- Can an APP-generated index be exported for additional processing and then imported for additional processing and output by the formatting engine?
- Styler says "advanced parameters" for indexing are available only with FOSI and XSL. The Styler Users Guide says to search Arbortext Editor Help for "Useparams and other customizations," which yields the extract below.Will APP source edits handle these capabilities? Native APP?
Useparams and other customizationsDepending on the content and placement of the index savetexts and various useparam settings, it is possible to customize the behavior of index entries. A useparam is set in the usetext that outputs the index string. If multiple useparams are set they should be separated by a space as in the following example. <usetext source="index.app" userule="2"<br"/> useparam="index_levels=5 mergeinhibit=-3"></usetext>
Topics covered in this section:
| | • | Specifying more than 4 levels in an entry (index_levels) |
| | • | Specifying a maximum number of page references (maxlocators) |
| | • | Controlling merging of page numbers (maxunmerge) |
| | • | Controlling merging of entries (mergeinhibit) |
| | • | Allowing empty headings in entries (allowemptyheadings) |
| | • | Allowing empty headings in entries – FOSI technique |
| | • | Specifying behavior of spaces (keep_all_space, keep_leading_space, keep_trailing_space, keep_embedded_space) |
| | • | Specifying behavior of leading punctuation (sortleadpunc) |
| | • | Specifying behavior of markup in page locators (locmarkuppriority) |
| | • | Specifying a language for sorting (language) |
| | • | Sorting by a subsequent level heading |
| | • | Specifying placement of see and see also references (seeorder) |
| | • | Allowing page numbers and/or see also references with see references (allowseenotalone) |
| | • | Renaming preliminary and final index markup |
| | • | Eliminating page numbers for upper level entries |
| | • | Eliminating page numbers for entries altogether |
| | • | Forcing page ranges using <ixstart> and <ixend> |
| | • | Generating running head1ers |
| | • | Generating “(contd.)” at column breaks in an index |
| | • | Specifying Korean_mode index options |
| | • | Specifying Chinese_mode index options |
| | • | Changing index formatting for materials published onlinez
|
I hope this is helpful! Please let me know any questions you may have.
Suzanne Napoleonwww.FOSIexpert.com"WYSIWYG is last-century technology!"