> For the complete documentation index, see [llms.txt](https://docs.pd4ml.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pd4ml.com/features/dynamic-page-format-changes-within-a-document.md). # Dynamic Page Format Changes Within a Document A single page format and `htmlWidth` chosen for an entire document doesn't always suit every section of it equally well -- the textbook case is a wide table sitting among otherwise ordinary-width text. Scaling the whole document down by lowering `htmlWidth` is always an option, but it comes at a real cost: it shrinks *everything*, not just the section that actually needed the room, and it disproportionately lengthens ordinary text lines that have no block-level width constraint of their own, hurting readability throughout the document rather than only where the problem actually was. `` offers a more targeted set of escape hatches instead, each suited to a different degree of "how much wider does this content actually need to be" -- from a simple orientation flip up to switching to an outright larger page format, applied only to the section that needs it and reset immediately afterward. {% hint style="warning" %} The `pageFormat` and `htmlWidth` attributes on `` shown below are part of the **pre-v4 feature set**. As already noted on the [Usage Examples](/usage-examples.md) page's Apply Page Breaks entry, versions of PD4ML prior to v4 gave `` several extra capabilities -- rotating the following page, adjusting the HTML-to-PDF scale factor, conditional breaks -- that hadn't yet been ported to v4 as of that writing. Confirm against the Javadoc/changelog for the PD4ML version actually in use before relying on this tag-attribute syntax under v4; the CSS-based and `setPageSize(...)`/`setPageMargins(...)` scope-string approaches covered in the [Programmer's Manual](/pd4ml-manual.md) (§7) are the current, version-independent way to vary page geometry across a document. {% endhint %} ## 1. Rotate to landscape, then reset The least invasive fix is a dynamic switch from portrait to landscape for just the wide section: it leaves the HTML-to-PDF scale factor completely untouched everywhere else in the document, since the extra horizontal room comes from the page's own reorientation rather than from scaling anything down. Once the wide content ends, a second `` resets the format back to what it was. ```html ... main content ... ... wide data ... ... main content (continued) ... ``` ![Portrait section followed by a landscape-rotated wide table, then back to portrait](https://367318506-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcjbNvevStmXi1uYduM7U%2Fuploads%2FjCoyRAVHs5es9SJcAXw4%2Fscreenshot004-tiny.png?alt=media) ## 2. Rotate, plus a temporary htmlWidth increase Sometimes the wide content is only a little wider than landscape orientation alone can accommodate. Temporarily raising `htmlWidth` just for that section adds a small additional scale-down on top of the rotation -- a modest, localized trade-off, rather than compromising the legibility of the whole document to fit one wide table. `htmlWidth="reset"` on the closing `` restores the original value along with the page format. ```html ... main content, htmlWidth is 600 ... ... wide data ... ... main content (continued) ... ``` ![The same wide table with a slightly increased htmlWidth applied on top of the rotation](https://367318506-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcjbNvevStmXi1uYduM7U%2Fuploads%2FfG0crWaqKRKaeZRsE1dw%2Fscreenshot005-tiny.png?alt=media) ## 3. Switch to an outright larger page format When the wide content is significantly wider than the main document layout -- wide enough that rotation and a modest `htmlWidth` bump both fall short -- the better fix is usually to reconsider how that content and data are organized in the first place, rather than continuing to chase it with page-geometry tricks. Where a larger page genuinely is the right answer, `pageFormat` accepts either a named larger format (`A3`, for instance) or explicit custom dimensions given in typographical points: ```html ... ... ``` ## Finding the right combination In practice, arriving at a layout that reads well on screen and still prints legibly is usually a matter of experimenting with `pageFormat` and `htmlWidth` together for the specific section giving trouble, rather than expecting one fixed combination to work for every wide-content case a document might contain. ## See also * [PD4ML page format output basics](https://old.pd4ml.com/cookbook/pdf_page_formatting.htm) -- background on page format conversion parameters referenced above. * [Usage Examples](/usage-examples.md) -- the Apply Page Breaks entry covers the v3/v4 status of ``'s extended attributes in more detail. * [PD4ML Programmer's Manual](/pd4ml-manual.md) -- §7 covers the current, scope-string-based way to vary page size and margins across a document (`setPageSize(...)`/`setPageMargins(...)` with a `"1"`, `"2+"`, ... scope). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pd4ml.com/features/dynamic-page-format-changes-within-a-document.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.