qppscanlog.txt records the DTP plugin’s scan of a template.
It can show whether expected text and tokens were found, which objects were processed, and which fonts, styles, strokes, or colors were discovered. The supplied examples are from InDesign; exact messages depend on the plugin and version.
This log describes the scanned template. It does not establish which dates were loaded for a subsequent diary or prove that a particular output page used this template. First confirm that the scan corresponds to the template and revision being investigated.
Section / message |
Diagnostic use |
Application/plugin header |
Identify the InDesign or QuarkXPress release and plugin build. |
Input file opened / Number of pages |
Confirm that scanning reached an open document and its reported page count. |
Adding slugs |
Lists object IDs, DTP UIDs, and item types used while preparing the scan. |
IN GeneratePCode / Scanning object |
Locate the source page/object being inspected. |
Box Text |
Inspect the text and token strings extracted for that object. An empty value is different from a missing object entry. |
Template contains / total objects |
Read summary counts together with any skipped-object messages. |
Template Global Attributes |
Check page-side and other template-level observations recorded by the plugin. |
missing fonts |
Identify font resources reported as unavailable during the scan. |
ExtractStyleDashStripeInfo / ExtractColourInfo |
Inspect resource names, descriptions, identifiers, and scan activity. |
ExtractHeaderInfo / Closing scanned file |
Establish whether the scan reached its concluding stages. |
IN GeneratePCode Box UID = 00000153 in page 1
Extracting info for objectID 4
Scanning object 4 of page 1
Box Text: [1d]
This excerpt shows that the scan logged the text [1d] for object 4 on source page 1, associated with UID 00000153. It supports the presence of that token in that scanned object. It does not prove that the token was used by a later script or determine its resulting date.
A scan object ID, a DTP UID, a generation object ID, a template ID, and a printed page number are different identifiers. Do not join the scan and generation logs solely because an object number happens to be equal. Use the template and page-copy information, token text, and the appropriate mapping.
If an Expected Token Is Missing
1. Confirm the correct template and a sufficiently recent scan. Search for the exact token and for nearby distinctive text, allowing for the way line breaks or paragraph markers appear in the log.
2. Inspect the relevant object entry and surrounding messages. Determine whether the object was scanned with different text, was explicitly skipped, or cannot be identified from the available excerpt.
3. Compare with the template and its scanning messages in Q++Studio. Do not infer that an object was absent from the document merely because a search of an incomplete log returned no match.
4. If the token is present in the scan, continue with the script’s template selection and the generation p-code. The scan alone does not explain a missing holiday result.
Resources and Diagnostic Messages
The example reports 105 objects and 105 text frames, with zero skipped inline objects. These are counts for that scan, not general limits or guarantees about other object types.
It also reports five missing fonts. The generation-log example reports a different list of missing fonts. Keep resource findings attached to the operation that reported them; do not merge the two lists as though they necessarily describe one document.
Style and swatch names help check native-formatting commands. Internal resource values require their proper representation: a raw color-component tuple is not automatically a set of percentages, and a resource UID is not a portable name.
The sample line “ColourBox discrepancy: 24 created but only 0 logged-back” should be retained with its surrounding scan activity. By itself it does not establish that the diary lost 24 colors. Check the scanned resource list and the actual symptom before assigning a cause.
“Reading BLOBS.zip containing 0 instructions” occurs in the successful example scan. It does not mean the template was empty: the object extraction and summary later in the same log provide the relevant evidence.
Identify the specific template token, object, or resource under investigation; cite the relevant scan excerpt and explain what it establishes. Keep missing resources distinct from fatal scan errors, and distinguish source-template evidence from subsequent generation evidence.
Related documentation: Scanning diagnostics; qpplog.txt; diagnostic-files overview.
Topic 189930, last updated on 22-Oct-2026
