<!-- Generated by SpecStory, Markdown v2.1.0 -->

# 2026-03-11 13:21:00Z

<!-- VS Code Copilot IDE Session 8684bd38-5bc0-408b-ba7f-e0c3143a5e77 (2026-03-11 13:21:00Z) -->

_**User (2026-03-11 13:21:00Z)**_

I am trying to run a custom transformation in Oxygen XMLto PDF. This project codebase contains the customization files used in the transformation. The screencap shows the transformation scenario. It is currently not producing a PDF but failing the build. Here is the summary of a previous conversation:
Context

Project: Customizing a DITA‑OT XSL‑FO PDF transform inside Oxygen to add a full‑page cover image.
Issue: Cover image not showing and DITA‑OT build failed with stylesheet/template errors during PDF2 (FOP) transforms.
Key Decisions

Catalog corrected: Fixed malformed entries in catalog.xml (replaced plain text with proper <uri .../> elements).
Override placement: Moved the cover override into an attribute override (fo/attrs/custom.xsl) and used xsl:apply-imports so the original front‑matter runs after the cover.
Requirements

Customization loading: The transformation must use -Dcustomization.dir pointing at the folder containing catalog.xml, fo/, and common/.
File resolution: Catalog entries must reference actual files and image paths must resolve relative to that customization directory.
Open Items

Build output: Need the full DITA‑OT/Saxon console log when the transform runs (the Saxon “Caused by:” stack shows the exact failing file/line).
Import timing: Verify DITA‑OT imports the attrs override after the front‑matter definitions; if not, adjust import order or template names.
Next Steps

Run & capture log: Re-run the Oxygen/DITA‑OT scenario (or dita.bat) and capture the full log to share if it still fails.
I’ll analyze: After you paste the full log (or stage1.xml excerpt), I’ll pinpoint the failing stylesheet line and provide the minimal fix.

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user wants to debug a failing DITA-OT PDF transformation in Oxygen XML. Let me first look at the current state of the customization files to understand what's there.

---

_**User (2026-03-11 13:27:47Z)**_

I believe what you are looking for is: C:\Users\Kelly.Mankenberg\AppData\Local\Programs\Oxygen XML Editor 27\oxygen27.1.exe

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user is telling me where Oxygen XML Editor is installed. Let me look for the DITA-OT installation within Oxygen's directory, specifically the PDF2 plugin's front-matter XSL files.

---

_**User (2026-03-11 14:11:56Z)**_

Important: Do not modify the ditamap in the editor without approval.

Now what I am needing is to place the othermeta element values in the PDF cover page dirtectly under the tunnel image in the menner shown in the screencap. Use this order (including green horizontal rule with the exact shade of green):
division
title (use the map/title attribute value)
product-family
year.month

do you understand or have questions?

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user wants to create a custom PDF cover page that displays metadata from the DITA map's `othermeta` elements below the tunnel image. The layout should be:
1. Tunnel cover image (full width)
2. Green horizontal rule
3. Division (from othermeta)
4. Title (from map/title)
5. Product-family (from othermeta)
6. Year.month (from othermeta)

Let me first look at the ditamap to understand what `othermeta` elements are available, without modifying it.

Then I need to understand the current cover page layout and update the XSL customization.

Let me read the ditamap to understand the structure, and also look at the existing front-matter templates more carefully.

---

_**User (2026-03-11 14:17:18Z)**_

System ID: C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap
Scenario: DITA Map PDF - based on XSL-FO - WKFS
Input file: C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap
Engine name: DITA-OT
Severity: fatal
Description: Transformation failed.

System ID: C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap
Scenario: DITA Map PDF - based on XSL-FO - WKFS
Input file: C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap
Engine name: DITA-OT
Severity: error
Description: Error:  Error reported by XML parser: The string "--" is not permitted within comments.

System ID: C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap
Scenario: DITA Map PDF - based on XSL-FO - WKFS
Input file: C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap
Engine name: DITA-OT
Severity: error
Description: Error: Build failed with an exception: C:\Users\Kelly.Mankenberg\AppData\Local\Programs\Oxygen XML Editor 27\frameworks\dita\DITA-OT\plugins\org.dita.base\build.xml:28: The following error occurred while executing this line:


---

_**Agent (copilot/claude-sonnet-4.6)**_

The error is clear: `The string "--" is not permitted within comments.` This is an XML well-formedness error — you cannot have `--` inside an XML comment. 

Looking at the comment I wrote in `fo/xsl/custom.xsl`:

```
        ─────────────────────────────────────────── (green rule #83BB26)
```

Those are em-dashes/box-drawing characters... wait, let me look at what I actually wrote. In the multi-line comment in `fo/xsl/custom.xsl`, I used `──────────────────────────────────────────────` (box drawing characters) which are fine, BUT I also have `--` in the comment text:
    
Now I see the full comment block — it's documenting the branded cover layout with the visual structure, metadata sources, and how the URI resolution works for FOP to locate the image. The issue is that somewhere in this comment I've got a literal `--` sequence that's breaking the XML parsing.

Looking at the custom stylesheet, I found it: the green rule comment has a line of dashes that creates `--` in the middle of the comment, which violates XML syntax. I need to scan through all the comments in the custom stylesheets to find and fix any other instances of this pattern.

---

_**User (2026-03-11 14:33:53Z)**_

now in the PDF I need a second page to appear (directly after the cover page) that looks like the screencap. It cannot appear in the TOC, which will be the page directly following this second page. How do I inject this?

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user wants to add a "legal/copyright" page as the second page of the PDF, directly after the cover page and before the TOC, and it should NOT appear in the TOC.

Looking at the screencap, the page contains:
- A WK blue header: "Financial & Corporate Compliance"
- Body text with various legal sections:
  - "This publication was written for Product Family® Plus."
  - "Publication Information / Version" section
  - "Distributed Subject to Terms of a License or other Agreement"
  - "Do Not Reproduce or Transmit"
  - "Not a Substitute for Legal Advice"
  - "Warranty Disclaimer"
  - "Attributions and Acknowledgements"
  - "Copyright Information"

The metadata values (product family, document type, year, etc.) should come from the ditamap othermeta elements. In DITA-OT PDF2, I need to override the `createFrontMatter` template in `fo/xsl/custom.xsl` to inject this legal page after the cover but before the TOC, ensuring it doesn't get indexed.

I'm realizing the challenge here: I can't use `xsl:apply-imports` with named templates in XSLT 2.0/3.0, so I need to either completely override `createFrontMatter` or find a different extension point. Let me look more carefully at the front-matter.xsl structure to see if there's a better hook... I see that `xsl:apply-imports` won't work with named templates, so I need to copy the original `createFrontMatter` structure into my customization and then append the new legal page-sequence after it. Looking at how the original template constructs the front cover page-sequence with its static contents and flow...

Determining page master...

I need to figure out which page master to use for the legal page. Since it won't be part of the TOC (it doesn't correspond to any DITA topic), I can use the `front-matter` master or a simpler `body` variant. The TOC generation is controlled separately by the `createTOC` template, which only reads the document structure, so this custom legal page won't automatically appear in it.

Looking at the design, I need a header with "Financial & Corporate Compliance" in large bold blue text with a thick blue top border, followed by the legal disclaimer content below.

Now I'm mapping out the full structure of the legal page: it starts with publication information like the product family and date, then moves into the legal sections covering licensing terms, reproduction restrictions, legal disclaimers, warranty information, and attributions.

I need to handle the month conversion from the numeric format to the full month name in the publication date field, so I'll set up a conditional to translate "03" to "March" and format it as "March 2026".

For the legal page layout, I'm deciding between using the existing `front-matter` page master or a simpler `body` master—since the legal page is pre-TOC content like the cover, `front-matter` makes sense and is already configured, though I should verify it doesn't include headers that would be unnecessary here.

---

_**User (2026-03-11 15:16:38Z)**_

Now we need to work on the Back Cover. The back covber 
The back cover needs to look like the screencap.
Under the green horizontal rule use the ditamap variables as follows:
"Product Family" is populated by "product-family" variable
Phone number is populated by "phone-number" variable
ext value is populated by "phone-extension" variable
Email value is populated by "email" variable
The logo at the bottom of the page uses 'common\artwork\logo.png'

any questions?

_**User (2026-03-11 15:28:31Z)**_

the back page is not showing in the PDF

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user says the back page is not showing in the PDF. Let me check why.

The issue is almost certainly that `$generate-back-cover` is false/not set, so the `<xsl:if test="$generate-back-cover">` condition prevents the back cover from being output. Let me check the DITA-OT PDF2 parameter for this.

Let me look at how `$generate-back-cover` is defined in DITA-OT to understand its default value and how to ensure it's enabled.

---

_**User (2026-03-11 15:42:21Z)**_

Show me where I can modify the font styling in the second page (Copyright info)

_**User (2026-03-11 16:14:08Z)**_

I need to change the font family for all headings to Fira Sans Medium. How and where do I do that?

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user wants to change the font family for all headings on the legal/copyright page (page 2) to Fira Sans Medium. Looking at the file, all the heading `fo:block` elements in `createLegalPage` use inline `font-weight="bold"` attributes directly on the `fo:block`. 

The cleanest approach for this customization is:
1. Add named attribute sets in `fo/attrs/custom.xsl` for the legal page headings and section headings
2. Replace the inline font attributes on the heading blocks in `fo/xsl/custom.xsl` with `xsl:use-attribute-sets` references

But wait - before that, I need to think about whether Fira Sans is available to FOP. 

FOP needs the font to be registered, so I should clarify that with the user. Looking at the question again, they're asking both for guidance on where to make the changes and how to implement them. So I need to explain where to define the font-family change in the attribute sets, how to apply those attribute sets to the heading blocks, and also mention that FOP requires the font to be registered first.

Now I'm looking at what "all headings" actually refers to on the copyright page—there are division headings, section headings, and bold notices, each with their own current styling. I should create a unified attribute set for the legal headings that applies Fira Sans Medium across all of them, then reference that from the appropriate fo:blocks in the XSL. I need to implement the actual changes rather than just suggest them. I'll add the `legal.heading` attribute set to the custom attributes file, then update each heading block in the legal page template to reference that attribute set instead of having inline styling. There are several headings to update—the division heading, publication information section, and the distributed terms section. I'm creating an attribute set for the legal section headings that applies the Fira Sans Medium font family while keeping the existing formatting properties like bold weight and font size, then defining a separate one for the larger division heading.

Since I need to apply this to multiple heading blocks, I'll use the multi_replace_string_in_file approach to add the attribute set reference to each of the nine heading blocks while preserving their individual space-after values.

---

_**User (2026-03-11 16:28:23Z)**_

for the first line of text on the cover page (division name), make that font Fira Sans Medium and 16pt. Then show me where in the code you made the change.

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user wants to change the `cover.division` attribute set in `fo/attrs/custom.xsl` to use `font-family="Fira Sans"` and `font-size="16pt"`. Let me make that change.

---

_**User (2026-03-11 16:31:59Z)**_

now where can I place the fonts (Fira Sans) so that it is actually used in the transformation?

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user wants to know where to place the Fira Sans font files so FOP can use them during the DITA-OT PDF transformation. I need to find the FOP configuration file location in the Oxygen DITA-OT installation and explain what needs to be done.

Let me check the FOP configuration file location and the font directory structure in the Oxygen installation.

---

_**User (2026-03-11 16:38:24Z)**_

Can we add fonts specifically to the 'common' folder of the project and reference them there? That way we can ensure any has access to the fonts.

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user wants to copy the Fira Sans font files into the customization project's `common/` folder and reference them from there in `fop.xconf`. This way the fonts travel with the project rather than depending on system fonts.

Let me:
1. Create a `common/fonts` folder and copy the Fira Sans TTF files there
2. Add explicit `<font>` entries to `fop.xconf` using paths relative to the customization directory (or absolute paths)
3. Update the attribute sets to use `font-weight="500"` for Medium

First, let me check what's already in common/ and understand the path structure, then copy the fonts and update fop.xconf.


Now I'm mapping out the file paths—the fop.xconf is in the Oxygen installation directory, while my customization folder is separate in the DITA workspace, so I'll need to set up the fonts in `common/fonts/` and configure fop.xconf to reference them from that location. `embed-url

---

_**User (2026-03-11 16:44:33Z)**_

I have placed all the required fonts in 'common\fonts'. LEt's work with those.

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user has placed the Fira Sans fonts in `C:\DITA\WKFS_oXygen_Files\PDF-files\Customization\common\fonts\`. Now I need to:

1. Create a `cfg/fop.xconf` in the customization project that registers the fonts using paths relative to the customization directory
2. Update `fo/attrs/custom.xsl` to use `font-weight="500"` for Medium specifically
3. Tell the user how to wire `args.fo.userconfig` in the Oxygen scenario

Let me first verify what fonts are actually in that folder, then create the fop.xconf.


---

_**User (2026-03-11 16:54:34Z)**_

Executing:
"C:\Users\Kelly.Mankenberg\AppData\Local\Programs\Oxygen XML Editor 27\frameworks/dita/DITA-OT/bin/dita.bat" -v -f pdf2 -o C:\DITA\transforms\out\smartsign_plus_tagging_guide.ditamap -t C:\DITA\transforms\temp/oxygen_dita_temp -i "C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap" "-Dpdf.formatter=fop" "-Dcustomization.dir=C:\DITA\WKFS_oXygen_Files\PDF-files\Customization" "-Dxep.failOnError=true"

Initializing project

==> Validate and init input arguments
Created dir: C:\DITA\transforms\temp\oxygen_dita_temp
transtype = pdf2
tempdir = C:\DITA\transforms\temp\oxygen_dita_temp
outputdir = C:\DITA\transforms\out\smartsign_plus_tagging_guide.ditamap
DITA-OT version = 4.3.0
input = C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap

==> Merge DITAVAL files into temporary file

==> Generate file list
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/smartsign_plus_tagging_guide.ditamap
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/anchor-text.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/api-updates.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/application-behavior.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/conditional_tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/field-preparation.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/how-to-manually-tag-documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/individual-tag-specs.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/manual-tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-json-sample.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/supplemental-file-specs.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tag-types.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tagging-introduction.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tagging-method-overview.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/updating_tags_via_api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy-coordinate-considerations.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy-coordinates.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy_coordinate_json_sample.dita

==> Debug and filter input files
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-json-data-schema.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/updating_tags_via_api.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/updating_tags_via_api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/manual-tagging.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/manual-tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tagging-method-overview.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-method-overview.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/field-preparation.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/field-preparation.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/adding_redacted_tags_via_api.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/anchor-text.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/anchor-text.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/application-behavior.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/application-behavior.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-parameters-by-tag-type.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-tagging.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/how-to-manually-tag-documents.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/how-to-manually-tag-documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/smartsign_plus_tagging_guide.ditamap to file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-json-sample.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-sample.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/api-updates.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api-updates.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/api.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/conditional_tagging.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/conditional_tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy_coordinate_json_sample.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy_coordinate_json_sample.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf_form_field_using_v3_post_documents.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy-coordinate-considerations.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinate-considerations.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy-coordinates.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinates.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/supplemental-file-specs.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/supplemental-file-specs.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/individual-tag-specs.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/individual-tag-specs.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tagging-introduction.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-introduction.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tag-types.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tag-types.dita

==> Resolve mapref in ditamap
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap

==> Resolve keyref
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/mapref.xsl
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/mapref.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap

==> Resolve conref push

==> Resolve conref in input files

==> Normalize same topic fragment identifiers and table column names, and resolve coderef
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/updating_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/manual-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-method-overview.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/field-preparation.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/anchor-text.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/application-behavior.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/how-to-manually-tag-documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api-updates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/conditional_tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy_coordinate_json_sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinate-considerations.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/supplemental-file-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/individual-tag-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-introduction.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tag-types.dita

==> Move metadata entries
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap
Loading stylesheet C:\Users\Kelly.Mankenberg\AppData\Local\Programs\Oxygen XML Editor 27\frameworks\dita\DITA-OT\plugins\org.dita.base\xsl\preprocess\mappull.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap

==> Find and generate related link information

==> Pull metadata for link and xref element
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/topicpull.xsl
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/topicpull.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/updating_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/manual-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-method-overview.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/field-preparation.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/anchor-text.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/application-behavior.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/how-to-manually-tag-documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api-updates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/conditional_tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy_coordinate_json_sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinate-considerations.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/supplemental-file-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/individual-tag-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-introduction.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tag-types.dita

==> Clean ditamap
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/clean-map.xsl
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/clean-map.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap

==> Clean preprocess

==> Copy html files

==> Merge topics
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-introduction.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tag-types.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-method-overview.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/manual-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/how-to-manually-tag-documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinate-considerations.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy_coordinate_json_sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/field-preparation.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/anchor-text.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/individual-tag-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/supplemental-file-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api-updates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/application-behavior.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/updating_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/conditional_tagging.dita

==> Build FO
Copying 4 files to C:\DITA\transforms\temp\oxygen_dita_temp\Configuration\OpenTopic
Copying 2 files to C:\DITA\transforms\temp\oxygen_dita_temp\Customization\OpenTopic
Copying 12 files to C:\DITA\transforms\temp\oxygen_dita_temp\Configuration\OpenTopic\cfg\common\artwork
Using document.locale=en
Processing C:\DITA\transforms\temp\oxygen_dita_temp\smartsign_plus_tagging_guide_MERGED.xml to C:\DITA\transforms\temp\oxygen_dita_temp/stage1.xml
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.pdf2.fop/xsl/fo/topic2fo_shell_fop.xsl
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.pdf2.fop/xsl/fo/topic2fo_shell_fop.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/stage1.xml to file:/C:/DITA/transforms/temp/oxygen_dita_temp/stage2.fo
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/stage2.fo to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topic.fo
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.pdf2/xsl/fo/i18n-postprocess.xsl
<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 


==> Format PDF
[WARN] Font "Helvetica,normal,500" not found. Substituting with "Helvetica,normal,400".
[INFO] Rendered page #1.
[INFO] Rendered page #2.
[WARN] Font "SimSun,normal,700" not found. Substituting with "SimSun,normal,400".
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 8784 millipoints. (See position 75:440)
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 21143 millipoints. (See position 158:265)
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 20303 millipoints. (See position 159:265)
[WARN] The contents of fo:block line 1 exceed the available area in the inline-progression direction by 1161 millipoints. (See position 422:216)
[INFO] Rendered page #3.
[INFO] Rendered page #4.
[INFO] Rendered page #5.
[INFO] Rendered page #6.
[INFO] Rendered page #7.
[INFO] Rendered page #8.
[INFO] Rendered page #9.
[INFO] Rendered page #10.
[INFO] Rendered page #11.
[INFO] Rendered page #12.
[INFO] Rendered page #13.
[INFO] Rendered page #14.
[INFO] Rendered page #15.
[INFO] Rendered page #16.
[INFO] Rendered page #17.
[INFO] Rendered page #18.
[INFO] Rendered page #19.
[INFO] Rendered page #20.
[INFO] Rendered page #21.
[INFO] Rendered page #22.
[INFO] Rendered page #23.
[INFO] Rendered page #24.
[WARN] Content overflows the viewport of an fo:block-container in block-progression direction by 1020 millipoints. (See position 872:293)
[INFO] Rendered page #25.
C:\DITA\transforms\temp\oxygen_dita_temp\topic.fo -> C:\DITA\transforms\out\smartsign_plus_tagging_guide.ditamap\smartsign_plus_tagging_guide.pdf

==> Clean temp directory

BUILD SUCCESSFUL in 17 seconds

The process finished with exit code: 0

It is obviously not finding the fonts to use them

_**User (2026-03-11 17:04:24Z)**_

Executing:
"C:\Users\Kelly.Mankenberg\AppData\Local\Programs\Oxygen XML Editor 27\frameworks/dita/DITA-OT/bin/dita.bat" -v -f pdf2 -o C:\DITA\transforms\out\smartsign_plus_tagging_guide.ditamap -t C:\DITA\transforms\temp/oxygen_dita_temp -i "C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap" "-Dpdf.formatter=fop" "-Dargs.fo.userconfig=C:\DITA\WKFS_oXygen_Files\PDF-files\Customization\cfg\fop.xconf" "-Dcustomization.dir=C:\DITA\WKFS_oXygen_Files\PDF-files\Customization" "-Dxep.failOnError=true"

Initializing project

==> Validate and init input arguments
Created dir: C:\DITA\transforms\temp\oxygen_dita_temp
transtype = pdf2
tempdir = C:\DITA\transforms\temp\oxygen_dita_temp
outputdir = C:\DITA\transforms\out\smartsign_plus_tagging_guide.ditamap
DITA-OT version = 4.3.0
input = C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap

==> Merge DITAVAL files into temporary file

==> Generate file list
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/smartsign_plus_tagging_guide.ditamap
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/anchor-text.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/api-updates.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/application-behavior.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/conditional_tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/field-preparation.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/how-to-manually-tag-documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/individual-tag-specs.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/manual-tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-json-sample.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/supplemental-file-specs.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tag-types.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tagging-introduction.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tagging-method-overview.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/updating_tags_via_api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy-coordinate-considerations.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy-coordinates.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy_coordinate_json_sample.dita

==> Debug and filter input files
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-json-data-schema.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/updating_tags_via_api.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/updating_tags_via_api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/manual-tagging.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/manual-tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tagging-method-overview.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-method-overview.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/field-preparation.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/field-preparation.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/adding_redacted_tags_via_api.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/anchor-text.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/anchor-text.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/application-behavior.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/application-behavior.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-parameters-by-tag-type.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-tagging.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/how-to-manually-tag-documents.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/how-to-manually-tag-documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/smartsign_plus_tagging_guide.ditamap to file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-json-sample.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-sample.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/api-updates.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api-updates.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/api.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/conditional_tagging.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/conditional_tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy_coordinate_json_sample.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy_coordinate_json_sample.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf_form_field_using_v3_post_documents.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy-coordinate-considerations.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinate-considerations.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy-coordinates.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinates.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/supplemental-file-specs.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/supplemental-file-specs.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/individual-tag-specs.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/individual-tag-specs.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tagging-introduction.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-introduction.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tag-types.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tag-types.dita

==> Resolve mapref in ditamap
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap

==> Resolve keyref
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/mapref.xsl
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/mapref.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap

==> Resolve conref push

==> Resolve conref in input files

==> Normalize same topic fragment identifiers and table column names, and resolve coderef
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/updating_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/manual-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-method-overview.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/field-preparation.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/anchor-text.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/application-behavior.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/how-to-manually-tag-documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api-updates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/conditional_tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy_coordinate_json_sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinate-considerations.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/supplemental-file-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/individual-tag-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-introduction.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tag-types.dita

==> Move metadata entries
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap
Loading stylesheet C:\Users\Kelly.Mankenberg\AppData\Local\Programs\Oxygen XML Editor 27\frameworks\dita\DITA-OT\plugins\org.dita.base\xsl\preprocess\mappull.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap

==> Find and generate related link information

==> Pull metadata for link and xref element
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/topicpull.xsl
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/topicpull.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/updating_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/manual-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-method-overview.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/field-preparation.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/anchor-text.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/application-behavior.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/how-to-manually-tag-documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api-updates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/conditional_tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy_coordinate_json_sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinate-considerations.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/supplemental-file-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/individual-tag-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-introduction.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tag-types.dita

==> Clean ditamap
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/clean-map.xsl
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/clean-map.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap

==> Clean preprocess

==> Copy html files

==> Merge topics
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-introduction.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tag-types.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-method-overview.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/manual-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/how-to-manually-tag-documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinate-considerations.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy_coordinate_json_sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/field-preparation.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/anchor-text.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/individual-tag-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/supplemental-file-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api-updates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/application-behavior.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/updating_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/conditional_tagging.dita

==> Build FO
Copying 4 files to C:\DITA\transforms\temp\oxygen_dita_temp\Configuration\OpenTopic
Copying 2 files to C:\DITA\transforms\temp\oxygen_dita_temp\Customization\OpenTopic
Copying 12 files to C:\DITA\transforms\temp\oxygen_dita_temp\Configuration\OpenTopic\cfg\common\artwork
Using document.locale=en
Processing C:\DITA\transforms\temp\oxygen_dita_temp\smartsign_plus_tagging_guide_MERGED.xml to C:\DITA\transforms\temp\oxygen_dita_temp/stage1.xml
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.pdf2.fop/xsl/fo/topic2fo_shell_fop.xsl
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.pdf2.fop/xsl/fo/topic2fo_shell_fop.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/stage1.xml to file:/C:/DITA/transforms/temp/oxygen_dita_temp/stage2.fo
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/stage2.fo to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topic.fo
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.pdf2/xsl/fo/i18n-postprocess.xsl
<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 

<?error-code PDFX008W?><?level WARN?>[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'. 


==> Format PDF
[WARN] Font "Helvetica,normal,500" not found. Substituting with "Helvetica,normal,400".
[INFO] Rendered page #1.
[INFO] Rendered page #2.
[WARN] Font "SimSun,normal,700" not found. Substituting with "SimSun,normal,400".
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 8784 millipoints. (See position 75:440)
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 21143 millipoints. (See position 158:265)
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 20303 millipoints. (See position 159:265)
[WARN] The contents of fo:block line 1 exceed the available area in the inline-progression direction by 1161 millipoints. (See position 422:216)
[INFO] Rendered page #3.
[INFO] Rendered page #4.
[INFO] Rendered page #5.
[INFO] Rendered page #6.
[INFO] Rendered page #7.
[INFO] Rendered page #8.
[INFO] Rendered page #9.
[INFO] Rendered page #10.
[INFO] Rendered page #11.
[INFO] Rendered page #12.
[INFO] Rendered page #13.
[INFO] Rendered page #14.
[INFO] Rendered page #15.
[INFO] Rendered page #16.
[INFO] Rendered page #17.
[INFO] Rendered page #18.
[INFO] Rendered page #19.
[INFO] Rendered page #20.
[INFO] Rendered page #21.
[INFO] Rendered page #22.
[INFO] Rendered page #23.
[INFO] Rendered page #24.
[WARN] Content overflows the viewport of an fo:block-container in block-progression direction by 1020 millipoints. (See position 872:293)
[INFO] Rendered page #25.
C:\DITA\transforms\temp\oxygen_dita_temp\topic.fo -> C:\DITA\transforms\out\smartsign_plus_tagging_guide.ditamap\smartsign_plus_tagging_guide.pdf

==> Clean temp directory

BUILD SUCCESSFUL in 14 seconds

The process finished with exit code: 0


---

_**Agent (copilot/claude-sonnet-4.6)**_

The build log shows that `args.fo.userconfig` is now being passed correctly (visible in the screenshot of the Oxygen scenario), but FOP is still reporting `PDFX008W: Font definition not found for the logical name or alias 'Fira Sans'`. This means `cfg/fop.xconf` is being passed to FOP but FOP still can't find the font files.

The key issue: The `PDFX008W` warning comes from the **XSL-FO stage** (the i18n-postprocess.xsl step), not from FOP's font rendering stage. Looking more carefully:

The warning `[PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'` appears **before** the `==> Format PDF` section. This warning comes from the XSL-FO processor (Saxon) during the i18n-postprocess step, which checks font availability using a different mechanism than FOP.
 
Looking at the actual log output, I can see the warning is being triggered during the i18n-postprocess transformation when Saxon processes stage2.fo and outputs to topic.fo—this is happening before FOP even gets involved in the PDF rendering stage.

---

_**User (2026-03-11 17:07:23Z)**_

System ID: C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap
Scenario: DITA Map PDF - based on XSL-FO - WKFS
Input file: C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap
Engine name: DITA-OT
Severity: info
Description: [PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'.

The PDF renders it as Arial because it cannot find Fira Sans. Are we indeed pointing to the common/fonts folder for our fonts? Or is it still attempting the Windows/Fonts folder?

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user is saying the PDF is rendering as Arial (fallback font) instead of Fira Sans. They want to know if the fop.xconf is actually being read and if the font paths are correct.

Let me analyze what's happening:

The PDFX008W warning comes from DITA-OT's i18n validation step, NOT from FOP. That warning always fires because DITA-OT's `font-mappings.xml` doesn't know about Fira Sans.

But the user says Arial is being used, which means FOP itself is also not finding our fonts. In the previous build log I analyzed, I said "No warning about Fira Sans from FOP" — but let me re-read...
 
Looking at the FOP output, I see warnings about Helvetica and SimSun fonts not being found, but notably there's no warning about Fira Sans missing. That's suspicious — if FOP were actually loading Fira Sans from the configuration, it would either use it silently or warn that it can't find it. The absence of any mention suggests FOP might not be reading the fop.xconf file at all, or the font paths in that configuration are pointing to files that don't exist.

I'm wondering if the relative paths in fop.xconf are actually resolving correctly. The configuration sets a base directory and then uses relative paths like `../common/fonts/FiraSans-Medium.ttf`, which should work if the base is resolved relative to where fop.xconf lives. But there's a catch — when FOP processes files, the working directory might affect how those relative paths resolve, potentially breaking the path chain entirely.

---

_**User (2026-03-11 17:10:40Z)**_

I still get this:
System ID: C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap
Scenario: DITA Map PDF - based on XSL-FO - WKFS
Input file: C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap
Engine name: DITA-OT
Severity: info
Description: [PDFX008W]: Font definition not found for the logical name or alias 'Fira Sans'.


_**User (2026-03-11 17:18:25Z)**_

And how do I use a 'Light" font to assimilate Fira Sans Light?

---

_**Agent (copilot/gpt-5-mini)**_

**Managing the todo list**

I need to follow the instructions carefully and start with the manage_todo_list tool since the task is multi-step. It’s a small request, but I want to make sure I’m organized. I'll create a todo list with steps: 

1) Add Fira Sans Light triplet in fop.xconf (it’s already there),
2) Update attribute sets to use font-weight="300" or "Light",
3) Optionally, add an alias in font-mappings.xml for 'Fira Sans Light.'

The user wants to know how to use the 'Light' font style to apply it in XSL attribute sets, so I’ll clarify how to do that!

---

_**User (2026-03-11 17:29:17Z)**_

where is the horizontal rule above the cover.division configuired?

---

_**Agent (copilot/gpt-5-mini)**_

**Searching for configuration details**

I'm looking to answer where the horizontal rule above the cover.division is configured. The user wants to know about the cover.division attribute. I think I should search the relevant files to find this rule. It seems like the createFrontCoverContents template includes a green rule. There's mention of the rule having a specific color and thickness. I'll locate createFrontCoverContents and read the fo/xsl/custom.xsl file to provide a concise answer and appropriate file references.

---

_**User (2026-03-11 17:32:11Z)**_

and where is the blue horizontal rule at the top of the copyright info?

---

_**Agent (copilot/gpt-5-mini)**_

**Reading file for line numbers**

I'm planning to read a file again, specifically looking for the block's line number within certain ranges. First, I’ll use the function to read the entire file and count the lines to pinpoint the index. I'll look at the custom.xsl file, covering a broader range, say lines 1 to 500. After I get the full content, I’ll parse it to find the line number containing 'border-top="4pt solid #005BAC"'. I’ll need to use the appropriate reading function for that.

---

_**User (2026-03-11 17:42:26Z)**_

now all in the Copyright information - except for the major heading - needs to use the Calibri font

---

_**Agent (copilot/gpt-5-mini)**_

Applying the change to set Calibri for the copyright text blocks.

---

_**User (2026-03-11 17:44:34Z)**_

System ID: C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap
Scenario: DITA Map PDF - based on XSL-FO - WKFS
Input file: C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap
Engine name: DITA-OT
Severity: info
Description: [PDFX008W]: Font definition not found for the logical name or alias 'Calibri'.


_**User (2026-03-11 17:45:17Z)**_

yes

---

_**Agent (copilot/gpt-5-mini)**_

I'll add Calibri registrations to both 

---

_**User (2026-03-11 17:51:25Z)**_

not working. It's reverting to SimSun

---

_**Agent (copilot/gpt-5-mini)**_

**Checking font configurations**

I need to check the FOP logs for any warnings related to "Font X not found," specifically for Calibri. It might be a good idea to ask someone to run the build and capture the logs. However, it seems more effective to verify that the fop.xconf file has the Calibri registration in the right location. We previously added a font-triplet with name="Calibri," style="normal," weight="normal," and the file 'calibri.ttf'. Let’s read fop.xconf to confirm everything is set up correctly.

---

_**User (2026-03-11 17:53:42Z)**_

[INFO] Rendered page #2.
[WARN] Font "SimSun,normal,700" not found. Substituting with "SimSun,normal,400".
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 8784 millipoints. (See position 75:440)
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 21143 millipoints. (See position 158:265)
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 20303 millipoints. (See position 159:265)
[WARN] The contents of fo:block line 1 exceed the available area in the inline-progression direction by 1161 millipoints. (See position 422:216)

still not rendering Calibri

_**User (2026-03-11 17:55:04Z)**_

issue persists.

---

_**Agent (copilot/claude-sonnet-4.6)**_

Let me think carefully about this. The user is trying to use Calibri in their DITA-OT PDF output for the copyright info section. The font keeps falling back to SimSun.

Let me list the possible root causes:

1. **The `calibri.ttf` file might not actually be a valid/full Calibri font** - it might be a subset or corrupted
2. **FOP font cache** - FOP has a font cache that persists between runs. The cache needs to be cleared or FOP needs to rebuild it.
3. **The `font-family="Calibri"` reference in the XSL-FO might be correct, but FOP is using the cache** from before Calibri was registered


4. **FOP might not be picking up our fop.xconf at all** - but wait, we see Fira Sans working, so fop.xconf IS being read
5. **Java font caching** - FOP caches font metrics, and if Calibri wasn't registered when the cache was built, it may still be using old cached data

The most likely culprit is the **FOP font cache**. FOP creates a persistent cache file that stores font information between runs. When we add a new font to `fop.xconf`, FOP may not recognize it because it's still referencing the old cached data instead of re-scanning the configuration.

Looking at the actual log output more carefully: there's no warning about Calibri not being found, which suggests either FOP is successfully locating it but it's not rendering as expected, or the `font-family="Calibri"` attribute isn't even reaching FOP in the first place. The user says it's still not rendering correctly, so I need to figure out whether this is a font discovery issue or a rendering issue.

The key insight is that `font-family="Calibri"` in the XSL-FO should bypass DITA-OT's logical font system entirely and go straight to FOP—but that only works if FOP actually has Calibri registered in fop.xconf and can access it. The most likely culprit is the FOP font cache, which persists at `~/.fop` and might be serving stale data. The FOP font cache at `C:\Users\{username}\.fop\fop-fonts.cache` needs to be cleared so FOP rescans the system fonts, since `<auto-detect/>` should already be picking up Calibri from Windows Fonts but something's preventing the font-family reference from resolving correctly in the XSL-FO output.

Looking at the FOP logs more carefully, I notice there's no warning about Calibri not being found—only the SimSun substitution warning—which suggests FOP might not even be attempting to use Calibri, or the font name in the metadata doesn't match what's being requested. I'm realizing the real issue might be that the `calibri.ttf` file in the common fonts directory is a stripped-down or incomplete version compared to the full Calibri installed in Windows, which could cause FOP to fall back to SimSun when it encounters characters not present in that particular font file.

---

_**User (2026-03-11 17:58:54Z)**_

nope.
Executing:
"C:\Users\Kelly.Mankenberg\AppData\Local\Programs\Oxygen XML Editor 27\frameworks/dita/DITA-OT/bin/dita.bat" -v -f pdf2 -o C:\DITA\transforms\out\smartsign_plus_tagging_guide.ditamap -t C:\DITA\transforms\temp/oxygen_dita_temp -i "C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap" "-Dpdf.formatter=fop" "-Dargs.fo.userconfig=C:\DITA\WKFS_oXygen_Files\PDF-files\Customization\cfg\fop.xconf" "-Dcustomization.dir=C:\DITA\WKFS_oXygen_Files\PDF-files\Customization" "-Dxep.failOnError=true"

Initializing project

==> Validate and init input arguments
Created dir: C:\DITA\transforms\temp\oxygen_dita_temp
transtype = pdf2
tempdir = C:\DITA\transforms\temp\oxygen_dita_temp
outputdir = C:\DITA\transforms\out\smartsign_plus_tagging_guide.ditamap
DITA-OT version = 4.3.0
input = C:\Users\Kelly.Mankenberg\Wolters Kluwer\Technical Writing Team Site - DITA Repository\eOriginal\SmartSignPlus\TaggingDocument_XML\smartsign_plus_tagging_guide.ditamap

==> Merge DITAVAL files into temporary file

==> Generate file list
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/smartsign_plus_tagging_guide.ditamap
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/anchor-text.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/api-updates.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/application-behavior.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/conditional_tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/field-preparation.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/how-to-manually-tag-documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/individual-tag-specs.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/manual-tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-json-sample.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/supplemental-file-specs.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tag-types.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tagging-introduction.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tagging-method-overview.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/updating_tags_via_api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy-coordinate-considerations.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy-coordinates.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy_coordinate_json_sample.dita

==> Debug and filter input files
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-json-data-schema.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/updating_tags_via_api.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/updating_tags_via_api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/manual-tagging.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/manual-tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tagging-method-overview.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-method-overview.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/field-preparation.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/field-preparation.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/adding_redacted_tags_via_api.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/anchor-text.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/anchor-text.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/application-behavior.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/application-behavior.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-parameters-by-tag-type.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-tagging.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/how-to-manually-tag-documents.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/how-to-manually-tag-documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/smartsign_plus_tagging_guide.ditamap to file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf-form-field-json-sample.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-sample.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/api-updates.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api-updates.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/api.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/conditional_tagging.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/conditional_tagging.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy_coordinate_json_sample.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy_coordinate_json_sample.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/pdf_form_field_using_v3_post_documents.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy-coordinate-considerations.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinate-considerations.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/xy-coordinates.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinates.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/supplemental-file-specs.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/supplemental-file-specs.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/individual-tag-specs.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/individual-tag-specs.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tagging-introduction.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-introduction.dita
Processing file:/C:/Users/Kelly.Mankenberg/Wolters%20Kluwer/Technical%20Writing%20Team%20Site%20-%20DITA%20Repository/eOriginal/SmartSignPlus/TaggingDocument_XML/topics/tag-types.dita to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tag-types.dita

==> Resolve mapref in ditamap
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap

==> Resolve keyref
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/mapref.xsl
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/mapref.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap

==> Resolve conref push

==> Resolve conref in input files

==> Normalize same topic fragment identifiers and table column names, and resolve coderef
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/updating_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/manual-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-method-overview.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/field-preparation.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/anchor-text.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/application-behavior.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/how-to-manually-tag-documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api-updates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/conditional_tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy_coordinate_json_sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinate-considerations.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/supplemental-file-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/individual-tag-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-introduction.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tag-types.dita

==> Move metadata entries
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap
Loading stylesheet C:\Users\Kelly.Mankenberg\AppData\Local\Programs\Oxygen XML Editor 27\frameworks\dita\DITA-OT\plugins\org.dita.base\xsl\preprocess\mappull.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap

==> Find and generate related link information

==> Pull metadata for link and xref element
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/topicpull.xsl
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/topicpull.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/updating_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/manual-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-method-overview.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/field-preparation.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/anchor-text.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/application-behavior.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/how-to-manually-tag-documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api-updates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/conditional_tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy_coordinate_json_sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinate-considerations.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/supplemental-file-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/individual-tag-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-introduction.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tag-types.dita

==> Clean ditamap
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/clean-map.xsl
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.base/xsl/preprocess/clean-map.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap

==> Clean preprocess

==> Copy html files

==> Merge topics
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/smartsign_plus_tagging_guide.ditamap
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-introduction.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tag-types.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/tagging-method-overview.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/manual-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/how-to-manually-tag-documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy-coordinate-considerations.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/xy_coordinate_json_sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-tagging.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/field-preparation.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-data-schema.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-parameters-by-tag-type.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf-form-field-json-sample.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/pdf_form_field_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_documents_with_prefilled_tags_and_pdf_form_fields_using_v3_post_documents.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/anchor-text.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/individual-tag-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/supplemental-file-specs.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api-updates.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/application-behavior.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/adding_redacted_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/updating_tags_via_api.dita
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/topics/conditional_tagging.dita

==> Build FO
Copying 4 files to C:\DITA\transforms\temp\oxygen_dita_temp\Configuration\OpenTopic
Copying 2 files to C:\DITA\transforms\temp\oxygen_dita_temp\Customization\OpenTopic
Copying 12 files to C:\DITA\transforms\temp\oxygen_dita_temp\Configuration\OpenTopic\cfg\common\artwork
Using document.locale=en
Processing C:\DITA\transforms\temp\oxygen_dita_temp\smartsign_plus_tagging_guide_MERGED.xml to C:\DITA\transforms\temp\oxygen_dita_temp/stage1.xml
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.pdf2.fop/xsl/fo/topic2fo_shell_fop.xsl
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.pdf2.fop/xsl/fo/topic2fo_shell_fop.xsl
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/stage1.xml to file:/C:/DITA/transforms/temp/oxygen_dita_temp/stage2.fo
Processing file:/C:/DITA/transforms/temp/oxygen_dita_temp/stage2.fo to file:/C:/DITA/transforms/temp/oxygen_dita_temp/topic.fo
Loading stylesheet file:/C:/Users/Kelly.Mankenberg/AppData/Local/Programs/Oxygen%20XML%20Editor%2027/frameworks/dita/DITA-OT/plugins/org.dita.pdf2/xsl/fo/i18n-postprocess.xsl

==> Format PDF
[WARN] coverage set class table not yet supported
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Cambria
[INFO] Cambria Math
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Cambria <-- selected
[INFO] Cambria Math
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Cambria
[INFO] Cambria Math <-- selected
[WARN] coverage set class table not yet supported
[WARN] coverage set class table not yet supported
[INFO] This is a TrueType collection file with 3 fonts
[INFO] Containing the following fonts: 
[INFO] MingLiU-ExtB
[INFO] PMingLiU-ExtB
[INFO] MingLiU_HKSCS-ExtB
[INFO] This is a TrueType collection file with 3 fonts
[INFO] Containing the following fonts: 
[INFO] MingLiU-ExtB <-- selected
[INFO] PMingLiU-ExtB
[INFO] MingLiU_HKSCS-ExtB
[INFO] This is a TrueType collection file with 3 fonts
[INFO] Containing the following fonts: 
[INFO] MingLiU-ExtB
[INFO] PMingLiU-ExtB <-- selected
[INFO] MingLiU_HKSCS-ExtB
[INFO] This is a TrueType collection file with 3 fonts
[INFO] Containing the following fonts: 
[INFO] MingLiU-ExtB
[INFO] PMingLiU-ExtB
[INFO] MingLiU_HKSCS-ExtB <-- selected
[INFO] This is a TrueType collection file with 3 fonts
[INFO] Containing the following fonts: 
[INFO] MS Gothic
[INFO] MS UI Gothic
[INFO] MS PGothic
[INFO] This is a TrueType collection file with 3 fonts
[INFO] Containing the following fonts: 
[INFO] MS Gothic <-- selected
[INFO] MS UI Gothic
[INFO] MS PGothic
[INFO] This is a TrueType collection file with 3 fonts
[INFO] Containing the following fonts: 
[INFO] MS Gothic
[INFO] MS UI Gothic <-- selected
[INFO] MS PGothic
[INFO] This is a TrueType collection file with 3 fonts
[INFO] Containing the following fonts: 
[INFO] MS Gothic
[INFO] MS UI Gothic
[INFO] MS PGothic <-- selected
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft JhengHei
[INFO] Microsoft JhengHei UI
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft JhengHei <-- selected
[INFO] Microsoft JhengHei UI
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft JhengHei
[INFO] Microsoft JhengHei UI <-- selected
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft JhengHei Bold
[INFO] Microsoft JhengHei UI Bold
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft JhengHei Bold <-- selected
[INFO] Microsoft JhengHei UI Bold
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft JhengHei Bold
[INFO] Microsoft JhengHei UI Bold <-- selected
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft JhengHei Light
[INFO] Microsoft JhengHei UI Light
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft JhengHei Light <-- selected
[INFO] Microsoft JhengHei UI Light
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft JhengHei Light
[INFO] Microsoft JhengHei UI Light <-- selected
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft YaHei
[INFO] Microsoft YaHei UI
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft YaHei <-- selected
[INFO] Microsoft YaHei UI
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft YaHei
[INFO] Microsoft YaHei UI <-- selected
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft YaHei Bold
[INFO] Microsoft YaHei UI Bold
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft YaHei Bold <-- selected
[INFO] Microsoft YaHei UI Bold
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft YaHei Bold
[INFO] Microsoft YaHei UI Bold <-- selected
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft YaHei Light
[INFO] Microsoft YaHei UI Light
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft YaHei Light <-- selected
[INFO] Microsoft YaHei UI Light
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Microsoft YaHei Light
[INFO] Microsoft YaHei UI Light <-- selected
[WARN] coverage set class table not yet supported
[WARN] coverage set class table not yet supported
[WARN] coverage set class table not yet supported
[INFO] ignoring out of order or duplicate glyph index: 168
[INFO] ignoring out of order or duplicate glyph index: 169
[INFO] ignoring out of order or duplicate glyph index: 170
[INFO] ignoring out of order or duplicate glyph index: 171
[INFO] ignoring out of order or duplicate glyph index: 172
[INFO] ignoring out of order or duplicate glyph index: 173
[WARN] coverage set class table not yet supported
[INFO] ignoring out of order or duplicate glyph index: 168
[INFO] ignoring out of order or duplicate glyph index: 169
[INFO] ignoring out of order or duplicate glyph index: 170
[INFO] ignoring out of order or duplicate glyph index: 171
[INFO] ignoring out of order or duplicate glyph index: 172
[INFO] ignoring out of order or duplicate glyph index: 173
[WARN] coverage set class table not yet supported
[INFO] ignoring out of order or duplicate glyph index: 168
[INFO] ignoring out of order or duplicate glyph index: 169
[INFO] ignoring out of order or duplicate glyph index: 170
[INFO] ignoring out of order or duplicate glyph index: 171
[INFO] ignoring out of order or duplicate glyph index: 172
[INFO] ignoring out of order or duplicate glyph index: 173
[WARN] coverage set class table not yet supported
[INFO] ignoring out of order or duplicate glyph index: 168
[INFO] ignoring out of order or duplicate glyph index: 169
[INFO] ignoring out of order or duplicate glyph index: 170
[INFO] ignoring out of order or duplicate glyph index: 171
[INFO] ignoring out of order or duplicate glyph index: 172
[INFO] ignoring out of order or duplicate glyph index: 173
[WARN] coverage set class table not yet supported
[INFO] ignoring out of order or duplicate glyph index: 168
[INFO] ignoring out of order or duplicate glyph index: 169
[INFO] ignoring out of order or duplicate glyph index: 170
[INFO] ignoring out of order or duplicate glyph index: 171
[INFO] ignoring out of order or duplicate glyph index: 172
[INFO] ignoring out of order or duplicate glyph index: 173
[WARN] coverage set class table not yet supported
[INFO] ignoring out of order or duplicate glyph index: 168
[INFO] ignoring out of order or duplicate glyph index: 169
[INFO] ignoring out of order or duplicate glyph index: 170
[INFO] ignoring out of order or duplicate glyph index: 171
[INFO] ignoring out of order or duplicate glyph index: 172
[INFO] ignoring out of order or duplicate glyph index: 173
[WARN] coverage set class table not yet supported
[INFO] ignoring out of order or duplicate glyph index: 168
[INFO] ignoring out of order or duplicate glyph index: 169
[INFO] ignoring out of order or duplicate glyph index: 170
[INFO] ignoring out of order or duplicate glyph index: 171
[INFO] ignoring out of order or duplicate glyph index: 172
[INFO] ignoring out of order or duplicate glyph index: 173
[WARN] coverage set class table not yet supported
[INFO] ignoring out of order or duplicate glyph index: 168
[INFO] ignoring out of order or duplicate glyph index: 169
[INFO] ignoring out of order or duplicate glyph index: 170
[INFO] ignoring out of order or duplicate glyph index: 171
[INFO] ignoring out of order or duplicate glyph index: 172
[INFO] ignoring out of order or duplicate glyph index: 173
[WARN] coverage set class table not yet supported
[INFO] ignoring out of order or duplicate glyph index: 168
[INFO] ignoring out of order or duplicate glyph index: 169
[INFO] ignoring out of order or duplicate glyph index: 170
[INFO] ignoring out of order or duplicate glyph index: 171
[INFO] ignoring out of order or duplicate glyph index: 172
[INFO] ignoring out of order or duplicate glyph index: 173
[WARN] coverage set class table not yet supported
[WARN] coverage set class table not yet supported
[WARN] coverage set class table not yet supported
[WARN] coverage set class table not yet supported
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] SimSun
[INFO] NSimSun
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] SimSun <-- selected
[INFO] NSimSun
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] SimSun
[INFO] NSimSun <-- selected
[INFO] ignoring out of order or duplicate glyph index: 257
[INFO] ignoring out of order or duplicate glyph index: 257
[INFO] This is a TrueType collection file with 3 fonts
[INFO] Containing the following fonts: 
[INFO] Yu Gothic Bold
[INFO] Yu Gothic UI Bold
[INFO] Yu Gothic UI Semibold
[INFO] This is a TrueType collection file with 3 fonts
[INFO] Containing the following fonts: 
[INFO] Yu Gothic Bold <-- selected
[INFO] Yu Gothic UI Bold
[INFO] Yu Gothic UI Semibold
[INFO] This is a TrueType collection file with 3 fonts
[INFO] Containing the following fonts: 
[INFO] Yu Gothic Bold
[INFO] Yu Gothic UI Bold <-- selected
[INFO] Yu Gothic UI Semibold
[INFO] This is a TrueType collection file with 3 fonts
[INFO] Containing the following fonts: 
[INFO] Yu Gothic Bold
[INFO] Yu Gothic UI Bold
[INFO] Yu Gothic UI Semibold <-- selected
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Yu Gothic Light
[INFO] Yu Gothic UI Light
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Yu Gothic Light <-- selected
[INFO] Yu Gothic UI Light
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Yu Gothic Light
[INFO] Yu Gothic UI Light <-- selected
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Yu Gothic Medium
[INFO] Yu Gothic UI Regular
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Yu Gothic Medium <-- selected
[INFO] Yu Gothic UI Regular
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Yu Gothic Medium
[INFO] Yu Gothic UI Regular <-- selected
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Yu Gothic Regular
[INFO] Yu Gothic UI Semilight
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Yu Gothic Regular <-- selected
[INFO] Yu Gothic UI Semilight
[INFO] This is a TrueType collection file with 2 fonts
[INFO] Containing the following fonts: 
[INFO] Yu Gothic Regular
[INFO] Yu Gothic UI Semilight <-- selected
[INFO] Rendered page #1.
[INFO] Rendered page #2.
[WARN] Font "SimSun,normal,700" not found. Substituting with "SimSun,normal,400".
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 8784 millipoints. (See position 75:440)
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 21143 millipoints. (See position 158:265)
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 20303 millipoints. (See position 159:265)
[WARN] The contents of fo:block line 1 exceed the available area in the inline-progression direction by 1161 millipoints. (See position 422:216)
[INFO] Rendered page #3.
[INFO] Rendered page #4.
[INFO] Rendered page #5.
[INFO] Rendered page #6.
[INFO] Rendered page #7.
[INFO] Rendered page #8.
[INFO] Rendered page #9.
[INFO] Rendered page #10.
[INFO] Rendered page #11.
[INFO] Rendered page #12.
[INFO] Rendered page #13.
[INFO] Rendered page #14.
[INFO] Rendered page #15.
[INFO] Rendered page #16.
[INFO] Rendered page #17.
[INFO] Rendered page #18.
[INFO] Rendered page #19.
[INFO] Rendered page #20.
[INFO] Rendered page #21.
[INFO] Rendered page #22.
[INFO] Rendered page #23.
[INFO] Rendered page #24.
[WARN] Content overflows the viewport of an fo:block-container in block-progression direction by 1020 millipoints. (See position 872:293)
[INFO] Rendered page #25.
C:\DITA\transforms\temp\oxygen_dita_temp\topic.fo -> C:\DITA\transforms\out\smartsign_plus_tagging_guide.ditamap\smartsign_plus_tagging_guide.pdf

==> Clean temp directory

BUILD SUCCESSFUL in 15 seconds

The process finished with exit code: 0


_**User (2026-03-11 18:01:52Z)**_

issue persists:
Rendered page #2.
[WARN] Font "SimSun,normal,700" not found. Substituting with "SimSun,normal,400".
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 8784 millipoints. (See position 75:440)
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 21143 millipoints. (See position 158:265)
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 20303 millipoints. (See position 159:265)
[WARN] The contents of fo:block line 1 exceed the available area in the inline-progression direction by 1161 millipoints. (See position 422:216)

---

_**Agent (copilot/claude-sonnet-4.6)**_

That `SimSun,normal,700` warning is **not** the Calibri issue — it's a completely separate, pre-existing condition unrelated to your customization work.

**What it is:** FOP's `<auto-detect/>` scans all Windows system fonts and registers SimSun (a Chinese fallback font from `simsun.ttc`). Somewhere in the base DITA-OT stylesheets, a `font-weight="bold"` is inherited in a context where the font falls back to SimSun. Since Microsoft never released a SimSun Bold variant, FOP substitutes Regular — which is correct behavior and has zero visual impact (SimSun only activates for CJK characters that don't exist in your content).

**Impact:** None. Your document contains no Chinese characters, so SimSun never actually renders anything. The substitution is purely internal.

**To silence it** if you want a clean log, I can add a SimSun Bold triplet to `cfg/fop.xconf` that points to the Regular TTF — this tells FOP "Bold SimSun = Regular file" and suppresses the warning. Want me to do that?

---

_**User (2026-03-11 18:06:28Z)**_

Rendered page #2.
[WARN] Font "SimSun,normal,700" not found. Substituting with "SimSun,normal,400".
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 8784 millipoints. (See position 75:440)
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 21143 millipoints. (See position 158:265)
[WARN] The contents of fo:external-graphic line 1 exceed the available area in the inline-progression direction by 20303 millipoints. (See position 159:265)
[WARN] The contents of fo:block line 1 exceed the available area in the inline-progression direction by 1161 millipoints. (See position 422:216)
[INFO] Rendered page #3.

It is still trying to fall back on SimSun. I have taken all non-english languages out of font-mappings as they are noty necessary. Where else is this being picked up?

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user is asking about the SimSun warning. They've edited `fo/font-mappings.xml` to remove non-English language entries. But the SimSun warning comes from FOP's `<auto-detect/>` in `fop.xconf`, not from `font-mappings.xml`.

Let me read the current state of both files to understand what's happening.

The key issue: `[WARN] Font "SimSun,normal,700" not found. Substituting with "SimSun,normal,400".`

This warning comes from FOP itself during rendering. It means FOP has SimSun registered (from `<auto-detect/>`), and something in the FO content requests `SimSun` with `font-weight="bold"` (700), but FOP only has the Regular cut registered.


The SimSun request is likely coming from the base DITA-OT stylesheets, probably through the font fallback chain in `i18n-postprocess.xsl` or the font mappings configuration. I need to check both files to see where SimSun is being referenced and why it's being requested for bold text.

---

_**User (2026-03-11 18:18:28Z)**_

How can I modify the font stylings of the TOC?

---

_**Agent (copilot/gpt-5-mini)**_

**Coordinating tasks and updates**

I need to update the attribute sets/templates for TOC fonts and then run a test rebuild, which the user can do but I'll provide instructions. I’ll call manage_todo_list with a to-do list of three items and proceed to read files afterward. First, I'll set the commentary preamble before my tool calls, ensuring everything's laid out clearly. It’s essential to send concise progress updates after every 3-5 tool calls to keep everything organized and transparent.

---

_**User (2026-03-11 18:27:38Z)**_

The TOC font stylings in custom.xsl (~line 284) are not affecting the rendered TOC. Why?

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user says there are TOC font stylings in custom.xsl at around line 284. Let me read that section to see what they've added, and then I need to look at how DITA-OT PDF

---

_**User (2026-03-11 18:35:37Z)**_

now I also need chapter heading styles to use Fira Sans, use the 007ac3 color and have no bottom border

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user wants to style chapter headings (the "Tagging Introduction", "Tag Types" etc. headings visible in the screenshot) to use Fira Sans, color #007ac3, and no bottom border. I need to find the correct DITA-OT attribute-set names

---

_**User (2026-03-11 18:50:28Z)**_

now in all footers except for front and back covers I need the following:
Two rows of text containing:
Row 1:
1. Left aligned: <product family> <document type>
2. Right aligned: <page number>
Row 2:
1. Right aligned: "©<year> Wolters Kluwer N.V. and/or its subsidiaries. All rights reserved."

These should all use Calibri normal font, 9pt size and color 007ac3.
Any questions?

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user wants to customize the footer for all pages except front and back covers. Let me understand the requirements:

1. Two rows of text in the footer
2. Row 1: Left aligned product family + document type, Right aligned page number
3. Row 2: Right aligned copyright notice
4. Font: Calibri, normal weight, 9pt, color #007ac3

Before I start coding, let me check a few things:
1. The current state of custom.xsl
2. How DITA-OT PDF2 handles static content (footers/headers) - specifically the static-content templates
3. What metadata is available (product-family, doctype, year)


Now I need to examine how the current footer is structured in DITA-OT. The front matter pages use a separate page master, while body content uses different ones, and static content gets inserted through templates that reference specific regions like the footer area.

---

_**User (2026-03-11 18:57:24Z)**_

you can see how they are rending tight against the page edges. I need the footer text to stay within the margins as in the header. While we are at it, remove the header text entirely. Headers should be blank.

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user wants:
1. Footer text to stay within the page margins (not go edge-to-edge)
2. Remove header text entirely (blank headers)

Let me look at how the body region and static content are set up - I need to understand the margin/indent structure. The footer is probably running edge-to-edge because it uses the full page width rather than the body region width. I need to check the layout masters and static-content attribute sets.

Let me first read the current custom.xsl to see the footer implementation, and also look at the DITA-OT base for header templates and the layout masters for margin info.

---

_**User (2026-03-11 19:09:28Z)**_

footer is still not conforming to margins

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user is saying the footer margins are still not right. Looking at the screenshot, I can see the footer text is at the bottom. Let me analyze what I see:

- Left side: "SmartSign Plus Tagging Guide" - appears to be at the left
- Right side: "5" (page number) with the product/doctype info
- Second row: "©2026 Wolters Kluwer N.V. and/or its subsidiaries. All rights reserved." on the right

The footer looks like it's positioned correctly in terms of left-right spacing, but let me think about the margin issue more carefully.

Looking at the screenshot more carefully:
- "SmartSign Plus Tagging Guide" is flush on the left


- "5" is on the right but seems very close to the edge
- The copyright line is on the right

The real issue might be that the footer's internal padding of 10pt doesn't align with the page's 20mm margins, so I need to adjust the footer spacing to match the page margin settings.

Looking at how the regions stack: the page master sets 20mm margins around the entire physical page, which creates the page reference area. The header and footer regions sit within that reference

---

_**User (2026-03-11 19:18:53Z)**_

issue persists

---

_**Agent (copilot/claude-sonnet-4.6)**_

Looking at the screenshot, the footer text is still going to the right edge of the page. The right side ("©2026 Wolters Kluwer N.V. and/or its subsidiaries. All rights reserved.") is flush against the right page edge.

The issue is that `end-indent="0pt"` means the block extends to the full reference area width. But the region-after has no inherent indents — it spans the full page minus the page margins (20mm). So the text just goes to the right edge of the region.

Wait, let me think about this more carefully.

The `fo:region-after` has `extent` = `$page-margin-bottom` = 20mm. 

The region-after spans the full width of the reference area, which is the page width minus the left and right margins (40mm total). The static-content content area matches the region-after's width. When I set `start-indent` to the side column width and `end-indent` to 0, the block starts at that indent but still extends all the way to the right edge of the reference area.

Looking at the screenshot more carefully, I notice the page number "5" and the copyright text both appear to extend beyond where the main body text ends—they're reaching toward the right edge of the page itself, not just the body margin. This suggests the footer content might be using the full region-after width rather than being constrained by the body text margins. The copyright text spans nearly the full width, which actually makes sense since the region-after is already constrained by the page margins. So when `end-indent="0pt"`, it just means the text reaches the right margin boundary. I need to trace through what `$side-col-width` actually controls in the body region—it adds 25pt of left indentation beyond the page margin, but there's no corresponding right-side constraint, so body text extends all the way to the right margin.

Looking at the screenshot more carefully, the footer appears correct: the title aligns with the body text's left indent, the page number sits at the right margin, and the copyright line is right-aligned to that same edge. But the user says the issue persists, so I'm missing something about how the copyright text is actually positioned versus where it should be. Looking more carefully at the alignment, the left side seems fine—the footer text starts at roughly the same indent as the body content. But I'm noticing the copyright text on the right might still be extending beyond where the body text ends, so that could be what the user is seeing as the persistent issue. to roughly the same right boundary

Hmm, maybe the issue is more subtle. Actually looking very carefully at the second screenshot vs the first:
1. First screenshot: Footer clearly way too wide, going to page edges
2. Second screenshot: Footer appears much more contained

But user says "issue persists"... 

Wait, maybe I'm wrong. Let me look at the screenshot description again. In the second screenshot (the current one), the footer appears at the bottom:
- "SmartSign Plus Tagging Guide" on the left, "5" on the right  
- "©2026 Wolters Kluwer N.V. and/or its subsidiaries. All rights reserved." on the right

Comparing to the body text margins... the "5" appears to be right-aligned, and the copyright text seems to go all the way to the right edge.

Actually I think the problem might be that the `start-indent` attribute is using an XSLT variable reference with curly braces, which should work as an attribute value template to evaluate the variable at transformation time. Let me reconsider whether this syntax is actually valid in XSL-FO context.

So the real question is: does the variable actually resolve to the right value, or is there a scoping issue where `$side-col-width` isn't accessible in the custom template file?

I need to check if the custom template file properly imports or has access to the global variable definition.

Actually, let me step back and reconsider the XSL-FO geometry itself. The page has 20mm margins on all sides, and the `region-after` with `extent=20mm` sits within that reference area at the bottom. But I'm not sure I have the positioning right — let me think through how regions actually work in XSL-FO.

---

_**User (2026-03-11 19:31:50Z)**_

good. now add some space under the second row 

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user wants to add some space below the second row (copyright row) of the footer. I'll add `space-after` to the second `fo:block`.

---

_**User (2026-03-11 19:57:36Z)**_

i bimped that to space-after="12pt" and it did not make any difference\

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user bumped `space-after` to 12pt on the copyright row and it made no difference. This is because `space-after` on a block inside `fo:static-content` is typically ignored by FOP — the static content region has a fixed extent and blocks inside it don't push the region boundary. The way

---

_**User (2026-03-11 19:59:24Z)**_

now add a blue border to the top of the footer

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user wants to add a blue border to the top of the footer. The best approach is to add a `border-top` to Row 1 (the first `fo:block` in `wkfs.footer.content`), or add a separate thin rule block before Row 1. 

Adding `border-before` (or `border-top` in FO terms — actually in XSL-FO it's `border-before`) to the first block is the simplest approach. Let me use `border-top` which in XSL-FO is actually written as individual properties or shorthand. In XSL-FO the correct property is `border-before-style`, `border-before-width`, `border-before-color` or the shorthand `border-top`. Actually in FO you can use `border-top="1pt solid #007ac3"` as a shorthand attribute.


Now I'll apply the border styling to the Row 1 block.

---

_**User (2026-03-11 20:15:25Z)**_

give me 36pt padding above the selected Wolters Kluwer heading

---

_**Agent (copilot/claude-sonnet-4.6)**_

The user wants to add 36pt padding above the "Wolters Kluwer" heading in the back cover contents. The selected text is at lines 332-336. I can see it in the file content.

---

_**User (2026-03-11 20:19:34Z)**_

that had no effect

---

_**Agent (copilot/claude-sonnet-4.6)**_

<think><details><summary>Thought Process</summary>
`space-before` is discarded by FOP when it appears on the first block in a flow. Use `padding-top` instead, which is part of the block's own box and always renders.
</details></think>

_**Agent (copilot/claude-sonnet-4.6)**_

The user says `space-before` had no effect on the "Wolters Kluwer" heading. This is the first block inside `createBackCoverContents`, which is called from `createBackCover`. The `fo:flow` starts with this block, so `space-before` on the first block in a flow is suppressed by FOP (space-before on the first block in a reference area is discarded per XSL-FO spec).

The fix is to use `padding-top` or add an empty spacer block before it, or use `margin-top` instead. Actually, `margin-top` also gets suppressed on the first block. The reliable approach is to emit an empty `fo:block` with a fixed height before it, or use `padding-top` on the block itself.


The simplest solution is to apply `padding-top` directly to the heading block itself, since that will work regardless of its position in the flow.

---

_**User (2026-03-11 20:26:53Z)**_

how would I indent this block 30pt?

---

_**Agent (copilot/claude-sonnet-4.6)**_

Add `start-indent="30pt"` to the block:

```xml
<fo:block font-family="Fira Sans" font-size="16pt" font-weight="300" color="#000"
          start-indent="30pt" space-after="4pt">
```

---

_**User (2026-03-11 20:39:24Z)**_

to what git repo am I pushing these changes?

_**User (2026-03-11 20:39:32Z)**_

@agent Try Again

_**User (2026-03-11 20:39:43Z)**_

Identify the git repo that I am using?
