fix(pptx): take the face from the decoration for standard-14 names (#450)

* docs: bring the release-facing surfaces up to 2.1

The three pages a visitor reaches before any code still described an
earlier release.

README's stable-release banner and the security policy's supported-
versions table both name the current line; the table had stayed on 1.9.x
across two majors while the policy above it already said fixes go to the
latest minor.

The showcase site never mentioned PowerPoint at all, though its gallery
has been serving decks since the twin examples landed. It also told
visitors to call BusinessTheme.modern(), which ships only in the
unpublished examples module — the README has said that type is gone since
2.0, so the two public faces disagreed. Preset counts were three short in
one place and claimed fourteen entries over a list of five in another,
and the test-count claim is replaced with the gate it stands for so it
cannot go stale again.

* fix(pptx): take the face from the decoration for standard-14 names

A span naming a standard-14 style variant travelled to PowerPoint as a
bold or italic run flag, taken from the font name string. Those names are
family aliases: FontLibrary resolves Helvetica-Bold to the Helvetica
family and Font.fontType picks the real face from the decoration, so a
span that names one without a decoration is measured with the regular
metrics.

The viewer honoured the flag and drew a face roughly 6% wider than the
frame the engine had sized, so text overran its slot — a chip label
crossed its card border, and two words of a rich-text heading closed the
gap between their separately placed frames until they read as one word.
The PDF backend was unaffected because it selects the face the same way
it measures it.

Run flags now follow the decoration for the nine standard-14 variants.
A binary family keeps its own name and is measured as itself, so its
suffix still carries the face.

Author: DemchaAV

CHANGELOG.md

@@ -121,6 +121,15 @@ shade), while others lose something the format cannot carry — see Known limita
 
 ### Fixed
 
+- **PPTX text no longer overruns the frame the engine measured for it.** A span that
+  named a standard-14 style variant — `Helvetica-Bold`, `Times-Italic` and their
+  siblings — travelled to PowerPoint as a bold or italic run flag. Those names are
+  family aliases: the engine resolves each to its regular base and takes the real face
+  from the span's decoration, so the layout had measured the regular metrics. The viewer
+  then drew a face about 6% wider than its slot, which pushed a chip label past its card
+  and closed the gap between two words of a rich-text heading until they read as one.
+  Run flags now follow the decoration for those families, so a deck renders the same
+  face the PDF does; a binary family still carries its face in its own name.
 - **A large clipped region in a PPTX deck is no longer downscaled.** The raster scale
   was capped only from above, so a clip box wider than 2048 pt rasterized *below*
   native size — an A0-scale composite landed near 44 DPI and read as visibly blurry,

README.md

@@ -19,7 +19,7 @@
 </p>
 
 > **Release status** &mdash;
-> 🟢 **Latest stable**: [v2.0.0](https://github.com/DemchaAV/GraphCompose/releases/tag/v2.0.0) &mdash; the **module-first** release: the engine is now a lean `graph-compose-core` with opt-in `render-pdf` / `render-docx` backends, while `graph-compose` stays a drop-in for PDF. **[Migrating to 2.0 &darr;](docs/migration/v2.0.0-modules.md)**
+> 🟢 **Latest stable**: [v2.1.0](https://github.com/DemchaAV/GraphCompose/releases/tag/v2.1.0) &mdash; the **PowerPoint** release: `graph-compose-render-pptx` turns the same resolved layout into an editable deck &mdash; one page per slide, geometry-identical to the PDF, text and panels as native shapes. Ships as `@Beta`. **[What each backend supports &darr;](docs/architecture/backend-capability-matrix.md)**
 
 > &nbsp;·&nbsp; ⬆️ **Upgrading from 1.x?** `graph-compose` stays a drop-in for PDF with no code change; see the [2.0 modules migration guide](./docs/migration/v2.0.0-modules.md)
 > &nbsp;·&nbsp; See [API stability policy](./docs/api-stability.md) for tier definitions.

SECURITY.md

@@ -8,8 +8,8 @@ Security fixes are issued for the latest minor release. Older minors do not rece
 
 | Version | Supported |
 |---------|-----------|
-| 1.9.x   | Yes — actively patched |
-| < 1.9   | No — upgrade required (see [CHANGELOG.md](CHANGELOG.md) for per-version migration notes) |
+| 2.1.x   | Yes — actively patched |
+| < 2.1   | No — upgrade required (see [CHANGELOG.md](CHANGELOG.md) for per-version migration notes, and the [2.0 modules migration guide](docs/migration/v2.0.0-modules.md) for the 1.x → 2.x step) |
 
 ## Reporting a vulnerability
 

render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxFontMapping.java

@@ -98,8 +98,7 @@ public static boolean isBold(TextStyle style) {
         if (decoration == TextDecoration.BOLD || decoration == TextDecoration.BOLD_ITALIC) {
             return true;
         }
-        return style.fontName() != null
-                && style.fontName().name().toLowerCase(Locale.ROOT).contains("bold");
+        return nameCarriesStyle(style.fontName(), "bold");
     }
 
     /** Returns whether the run selects an italic face. */
@@ -108,8 +107,32 @@ public static boolean isItalic(TextStyle style) {
         if (decoration == TextDecoration.ITALIC || decoration == TextDecoration.BOLD_ITALIC) {
             return true;
         }
-        String name = style.fontName() == null ? "" : style.fontName().name().toLowerCase(Locale.ROOT);
-        return name.contains("italic") || name.contains("oblique");
+        return nameCarriesStyle(style.fontName(), "italic")
+                || nameCarriesStyle(style.fontName(), "oblique");
+    }
+
+    /**
+     * Reports whether a font name's own style suffix should become a run flag.
+     *
+     * <p>Only binary families carry their face in the name. The standard-14
+     * PostScript variants — {@code Helvetica-Bold}, {@code Times-Italic},
+     * {@code Courier-BoldOblique} and their siblings — are <em>family
+     * aliases</em>: the engine resolves each to its regular base family and
+     * then picks the real face from the span's {@link TextDecoration}, so a
+     * span that names one of them without a decoration is measured with the
+     * regular metrics. Turning the suffix into a run flag would ask the viewer
+     * for a bold or italic face the layout never measured, and the placed text
+     * would render wider than the frame the engine sized for it.</p>
+     *
+     * @param fontName logical document font, may be {@code null}
+     * @param token lowercase style token to look for
+     * @return {@code true} when the name may contribute the flag
+     */
+    private static boolean nameCarriesStyle(FontName fontName, String token) {
+        if (fontName == null || standardReplacementFor(fontName) != null) {
+            return false;
+        }
+        return fontName.name().toLowerCase(Locale.ROOT).contains(token);
     }
 
     static boolean isUnderline(TextStyle style) {

render-pptx/src/test/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxFontMappingTest.java

@@ -36,15 +36,46 @@ void mapsStandardFamiliesToMetricCompatibleViewerFonts() {
     }
 
     @Test
-    void combinesDecorationWithFaceSuffixes() {
-        TextStyle boldFace = new TextStyle(FontName.HELVETICA_BOLD, 12,
-                TextDecoration.DEFAULT, Color.BLACK);
+    void decorationDrivesTheFace() {
         TextStyle decorated = new TextStyle(FontName.HELVETICA, 12,
                 TextDecoration.BOLD_ITALIC, Color.BLACK);
 
-        assertThat(PptxFontMapping.isBold(boldFace)).isTrue();
-        assertThat(PptxFontMapping.isItalic(boldFace)).isFalse();
         assertThat(PptxFontMapping.isBold(decorated)).isTrue();
         assertThat(PptxFontMapping.isItalic(decorated)).isTrue();
     }
+
+    /**
+     * The standard-14 style variants are family aliases: the engine resolves
+     * {@code Helvetica-Bold} to the Helvetica family and takes the face from
+     * the decoration, so a span naming one without a decoration is measured
+     * with the regular metrics. Claiming the flag here would make the viewer
+     * draw a wider face than the frame was sized for.
+     */
+    @Test
+    void standard14FaceSuffixDoesNotBecomeARunFlag() {
+        TextStyle aliasedBold = new TextStyle(FontName.HELVETICA_BOLD, 12,
+                TextDecoration.DEFAULT, Color.BLACK);
+        TextStyle aliasedOblique = new TextStyle(FontName.COURIER_BOLD_OBLIQUE, 12,
+                TextDecoration.DEFAULT, Color.BLACK);
+
+        assertThat(PptxFontMapping.isBold(aliasedBold)).isFalse();
+        assertThat(PptxFontMapping.isItalic(aliasedBold)).isFalse();
+        assertThat(PptxFontMapping.isBold(aliasedOblique)).isFalse();
+        assertThat(PptxFontMapping.isItalic(aliasedOblique)).isFalse();
+    }
+
+    /**
+     * A binary family keeps its own name and is measured as itself, so its
+     * suffix is the only signal of the face and must still travel as a flag.
+     */
+    @Test
+    void binaryFamilySuffixStillCarriesTheFace() {
+        TextStyle bold = new TextStyle(FontName.of("Acme-Sans-Bold"), 12,
+                TextDecoration.DEFAULT, Color.BLACK);
+        TextStyle italic = new TextStyle(FontName.of("Acme-Sans-Italic"), 12,
+                TextDecoration.DEFAULT, Color.BLACK);
+
+        assertThat(PptxFontMapping.isBold(bold)).isTrue();
+        assertThat(PptxFontMapping.isItalic(italic)).isTrue();
+    }
 }

web/index.html

@@ -76,11 +76,11 @@
         "featureList": [
           "Semantic node tree DSL (ParagraphNode, TableNode, SectionNode, LayerStackNode, CanvasLayerNode)",
           "Atomic pagination with row-by-row table splitting",
-          "14 CV presets and 14 letter pairs out of the box",
-          "Theme tokens via BusinessTheme.modern() / classic() / executive()",
+          "16 CV presets and 15 matching cover letters out of the box",
+          "Theme tokens via BrandTheme.modernProfessional() / executive() / boxedClassic()",
           "Markdown-aware bodies (bold, italic) in every paragraph and list block",
-          "PDFBox-backed render pipeline plus a DOCX backend for editable output",
-          "819-test verify gate with layout snapshots and pixel-diff visual parity"
+          "PDFBox-backed render pipeline, an editable PowerPoint backend geometry-identical to the PDF, and a semantic DOCX backend",
+          "Full-reactor verify gate with layout snapshots and pixel-diff visual parity"
         ]
       },
       {
@@ -172,6 +172,7 @@
         <h1 id="hero-title">Java PDF layout engine for structured business documents.</h1>
         <p class="hero-lead">Describe documents. Render polished PDFs. A semantic layout engine for Java services that need <b>structured, paginated, theme-driven</b> output &mdash; CVs, invoices, proposals, reports.</p>
         <p class="hero-text">No drawing API. No pixel arithmetic. You compose <code>ParagraphNode</code>, <code>TableNode</code>, <code>SectionNode</code>; GraphCompose handles measurement, pagination, fonts, and PDFBox rendering.</p>
+        <p class="hero-text">The same resolved layout also renders to an <b>editable PowerPoint deck</b> &mdash; one page per slide, geometry-identical to the PDF, text and panels as native shapes. Opt in with <code>graph-compose-render-pptx</code> (<code>@Beta</code>).</p>
         <div class="hero-actions">
           <a class="button button-primary" href="#showcase">Browse Examples</a>
           <a class="button button-secondary" href="https://github.com/DemchaAV/GraphCompose">Source on GitHub</a>
@@ -212,12 +213,12 @@ <h3>Atomic pagination</h3>
           <p>Tables split row-by-row, rows are atomic, layer stacks atomic. No manual page math.</p>
         </div>
         <div>
-          <h3>14 CV presets, 14 letter pairs</h3>
-          <p>Every preset is one final class with a one-liner <code>create(BusinessTheme)</code> factory.</p>
+          <h3>16 CV presets, 15 matching letters</h3>
+          <p>Every preset is one final class with a one-liner <code>create(BrandTheme)</code> factory.</p>
         </div>
         <div>
           <h3>Tested at every layer</h3>
-          <p>819 green tests, layout snapshots per preset, pixel-diff visual parity gate, public-API leak guards.</p>
+          <p>A full-reactor verify gate on every push: layout snapshots per preset, pixel-diff visual parity, public-API leak guards.</p>
         </div>
       </div>
     </section>
@@ -286,7 +287,7 @@ <h2 id="showcase-title">50+ generated PDFs you can inspect.</h2>
 
           <h3 id="templates-section">Templates</h3>
 
-          <h4>CV (14 presets)</h4>
+          <h4>CV</h4>
           <ul>
             <li><a href="showcase/pdf/templates/cv/cv-modern-professional-v2.pdf">Modern Professional CV</a></li>
             <li><a href="showcase/pdf/templates/cv/cv-nordic-clean-v2.pdf">Nordic Clean CV</a></li>
@@ -304,7 +305,7 @@ <h4>CV (14 presets)</h4>
             <li><a href="showcase/pdf/templates/cv/cv-monogram-sidebar-v2.pdf">Monogram Sidebar CV</a></li>
           </ul>
 
-          <h4>Cover Letter (14 paired layouts)</h4>
+          <h4>Cover Letter</h4>
           <ul>
             <li><a href="showcase/pdf/templates/coverletter/cover-letter-modern-professional-v2.pdf">Cover Letter (canonical)</a></li>
             <li><a href="showcase/pdf/templates/coverletter/cover-letter-modern-professional-v2.pdf">Modern Professional letter</a></li>
@@ -359,7 +360,7 @@ <h2 id="architecture-title">Author intent stays separate from PDF rendering.</h2
       <ol class="pipeline" aria-label="Document pipeline">
         <li><strong>Semantic DSL.</strong> You build a tree of <code>ParagraphNode</code>, <code>TableNode</code>, <code>SectionNode</code>, <code>LayerStackNode</code>, <code>CanvasLayerNode</code>.</li>
         <li><strong>Layout pass.</strong> The engine resolves measurements, pagination, decoration, overlays. Output is a <code>LayoutGraph</code> &mdash; geometry only, no draw calls.</li>
-        <li><strong>Render backend.</strong> The <code>FixedLayoutBackend</code> consumes placed fragments. Default: <code>PdfFixedLayoutBackend</code> via PDFBox. DOCX backend exists for editable output.</li>
+        <li><strong>Render backend.</strong> The <code>FixedLayoutBackend</code> consumes placed fragments. Default: <code>PdfFixedLayoutBackend</code> via PDFBox. <code>PptxFixedLayoutBackend</code> consumes the same fragments, so a deck is geometry-identical to the PDF by construction. A semantic DOCX backend maps the node tree instead, with much narrower coverage.</li>
       </ol>
     </section>
 
@@ -379,7 +380,7 @@ <h3>Snapshot-tested layouts</h3>
         </article>
         <article class="feature-card">
           <h3>Theme tokens, not magic numbers</h3>
-          <p><code>BusinessTheme.modern()</code> / <code>.classic()</code> / <code>.executive()</code> set palette, typography, table styles. Override one or all.</p>
+          <p><code>BrandTheme.modernProfessional()</code> / <code>.executive()</code> / <code>.boxedClassic()</code> set palette, typography, table styles. Override one or all. Ships in <code>graph-compose-templates</code>.</p>
         </article>
         <article class="feature-card">
           <h3>Markdown-aware bodies</h3>