Overview
This guide outlines the cause of errors generated when VML (Vector Markup Language) tags are included in HTML callback RTF fields within Repertoire Designer report templates. VML is proprietary to Microsoft Office applications and is not supported by the HTML callback element in Repertoire. As a result, VML‑tagged content cannot be processed and generates “not recognized” warnings in the logs.
Step 1: Issue Identification
Errors are logged whenever VML tags such as <v:shapetype>, <v:stroke>, <v:formulas>, or <v:f> are present in pasted content.
Example log messages:
WARN HTMLToAttributedString - line: 217 col: 55 <v:shapetype> is not recognized!
WARN HTMLToAttributedString - line: 218 col: 11 <v:stroke> is not recognized!
WARN HTMLToAttributedString - line: 219 col: 11 <v:formulas> is not recognized!
WARN HTMLToAttributedString - line: 220 col: 12 <v:f> is not recognized!
Step 2: Root Cause
- VML tags are proprietary to Microsoft products and are not part of standard HTML.
- The HTML callback element in Repertoire relies on Java’s HTML compatibility, which does not support VML.
- Rendering of VML‑tagged content is therefore outside the scope of the Repertoire engine.
Step 3: Acknowledge Design Limitation
HTML callback elements are intended for basic HTML content (e.g., single, HTML‑formatted paragraphs). They are not designed to handle:
- Proprietary markup languages such as VML.
- Large, multi‑page HTML outputs.
Step 4: Recommended Actions
- Avoid pasting content containing VML tags into RTF fields.
- Convert or clean source content to standard HTML before pasting.
- Use supported HTML formatting for reliable rendering.
- For complex content, consider alternative design approaches that do not rely on the HTML callback element.
What This Clarification Achieves
- Provides a clear explanation of why VML tags trigger errors.
- Highlights the design limitation of the HTML callback element.
- Offers practical guidance to ensure successful rendering in Repertoire.