
XPP Automatic Looseleaf and XyDiff Publishing Overview
- XPP Automatic Looseleaf Overview
- Life Cycle of a Looseleaf Document
- Looseleaf Manifest
- List of Effective Pages (LOEP)
- XyDiff Differencing Engine Overview
- XyDiff Configuration File
- Significant Macro/Tag Control File
- Alias Control File
- Creating a Baseline Division
XPP Automatic Looseleaf Overview
XPP Looseleaf Publishing software provides comprehensive tools for streamlining the update of pages in frequently-revised publications and significantly reduces the time and cost of updating pages and maintaining looseleaf publications. The goal of publishing documents in looseleaf format is to generate and issue as few new pages as possible with each document update.
Once users define their preferences, the software automatically composes and paginates with the goal of creating the minimum number of change pages while following their preferences. Automatic looseleaf composes only the edited pages. Additionally, the same page numbers that were in effect before composition remain in effect after automatic composition. With Automatic Looseleaf composition, users first set up a looseleaf style sheet in which they can define:
- How deleted pages are treated during the update
- Whether automatically generated page-deletion statements are generated
- How full-page graphics, tables, and other page elements are treated
- Whether right pages are filled, where possible, before left pages
- How to resolve text overflow on edited pages
Life Cycle of a Looseleaf Document
Generally, issuing an update does not necessitate reprinting the entire document. You only print and distribute the pages that have changed. However, after a series of updates, you usually incorporate all updates into the document, print the entire document, and then reissue the entire document to your customers. The reissue replaces the current version of the document. The following illustrate the life cycle of a Looseleaf document:
Initial release
The Looseleaf document life cycle begins with an initial release. An initial release is the first printing of an entire document. A release can be either a new document or a document that is being reissued in its entirety. In an initial release:
- All information is current
- Pages are numbered sequentially
- The entire document is composed, paginated, and printed
Updates (also known as revisions or supplements)
Between releases, you often revise sections of a Looseleaf document. The revisions between releases are called updates. Lengthy publications tend to have long life spans, but require frequent updates. Because updates are ongoing, the update process is often described as a cycle within the life cycle of a Looseleaf document. Updates are:
- Created in the form of changed pages or insert pages. XPP allows up to two levels of insert pages and numbers.
- Designed to fit into the existing publication
- Contained to as few pages as possible to help reduce costs
Reissues (also known as subsequent release)
A reissue is similar to the first release because the entire document is recomposed, repaginated, and reprinted. Think of a reissued document as a new release. When and why you create a reissue depends on the guidelines established by your company. For a reissue, Looseleaf composition:
- Integrates all pages, both updated and unchanged, into the document
- Composes and renumbers all pages
- Makes all page numbering sequential once again
- Flows text and graphics freely across page boundaries
- Eliminates all insert pages and backup filler pages
.
Looseleaf Manifest
The Looseleaf manifest is a database that stores and tracks the information for producing updates and releases, maintains an edit history of a Looseleaf document, and provides the information for generating a list of effective pages.
When you compose a Looseleaf document, XPP automatically stores information about each page in the manifest. You can display, view, and edit the information in the manifest.
List of Effective Pages (LOEP)
With Looseleaf documents, it is important to track pages changed through the life of a document. To track page revisions, you can create a list of effective pages (LOEP) when a document is printed. The LOEP defines the current status of a document.
With the LOEP, you can determine precisely what pages you need to have the most current version of the document. The LOEP contains information about each page of a document, including a change number for each page. The change number is the actual number associated with an update.

XyDiff Differencing Engine Overview
Once you have an initial release or baseline division in XPP, updates are created using the XyDiff Differencing Engine. XyDiff is an XPP utility that compares the XML version of an existing XML baseline division with an updated XML file, then outputs the differences to a file with trace elements to show where changes occurred.
XyDiff is typically used in an XPP automatic Looseleaf environment. In an automated looseleaf environment, XyDiff is called by an application interface or shell script. However, XyDiff can also be run manually from a command line.
XyDiff compares the contents of two files and generates a page-delimited output file that consists of pages with differences. This output file is suitable as input for the import program. XyDiff does not output pages that have no traced differences unless you explicitly request them. You can use XyDiff in the following ways:
- To compare two divisions and produce a total count of pages that are different, which is useful for billing purposes.
- To revise non-Loose-leaf documents with edit trace marks for changed text/data.
- In an automatic Loose-leaf environment, to produce divisions containing only those pages that are different. You can recompose this division separately and issue it as a “changed pages” packet.
XyDiff Configuration File
The XyDiff configuration file contains rules for hanuling editorial changes. Rules in the configuration file tell XyDiff whether or not to trace textual differences between the two input files. Traces appear in the updated “working baseline” division as change bars or deletion deltas. An example of using this file is for special characters, spaces, tabs and text strings that you want XyDiff to ignore. The XyDiff configuration file is used to:
- To differentiate between content changes and editorial changes
- To determine whether or not to trace specific changes.
- To override the standard behavior of any given differencing result.
Significant Macro/Tag Control File
The Significant Macro/Tag control file lists tags and XyMacros that you want XyDiff to trace different from the default behavior and update the pages. All tags/macros not listed in this file will not be traced, but will be included in the page in the final XyDiff output file. An example of using this file is when you do not want XyDiff to trace or include the page in the final output file when an XML element has changed.
Alias Control File
The Alias control file allows you to define aliases for the default pickup <pick> and footnotes <foot> XyMacros. An example of using this file is for XML element names that need to be hanuled as pickup and footnote callouts.
Creating a Baseline Division
If you have a document that was previously published without using XPP Looseleaf and now you want to produce the document using XPP Looseleaf and XyDiff, you must first rebuild the publication history of the document – the baseline.
The goal is to rebuild the release and update history of the existing publication and to preserve the integrity of that document history. You can then create future releases and updates using Xyvision Loose-leaf, which will track added, deleted, and changed pages.
To rebuild the publication history of a document, you must:
- Define page and block breaks in the input XML document so that each page of a converted document matches exactly the same on XPP as it does on the hard copy.
- Set up the style specs so that the converted document matches the original document style as closely as possible. If the style specs of the converted document do not match the original document style, it may not be possible to re-create the baseline
- Compose the document. The most important concept to remember when composing a converted document is that each page of a converted document must look exactly the same on XPP as it does on the hard copy. Therefore, you will probably compose each page separately with forced page and block breaks.
- Modify the Page manifest. You must manually update each
page in the Looseleaf manifest to reflect the applicable information on the
page, such as correct page number, change number, added/deleted status, filler
status, and right/left page sequencing. You must modify any fields in the
manifest that are incorrect.
- Generate an up-to-date LOEP
- Create a new LOEP spec with the new manifest information
- Edit the LOEP spec to reflect added/deleted pages. Create new rules for any page history that is missing.
- Update the list of effective pages by running LOEP
- Register pages that were deleted in previous releases and updates
![]()
Note: Fully integrating XPP Looseleaf and XyDiff with Contenta or another content management system requires customisation due to the numerous content management and publish requirements.