FlowTagging Class

Definition

How Render(PdfDocument) tags what it lays out: a structure tree built while the flow is drawn, one element per block and part, in construction order, with the page content of each tied to it by MCID and everything else (page backgrounds, watermarks, headers and footers, table rules and backgrounds, repeated table headers, underlines) marked as artifacts.

public sealed class FlowTagging

Remarks

ISO 32000-2 §14.8 (tagged PDF), §14.7 (structure tree), §14.8.2.2 (artifacts), §14.8.4 (standard structure types), §14.8.5.7 (table attributes), §14.9.2 (natural language), §14.3.3 (title). The tree is Document, then a Sect per StartSection(PageTemplate), then each block's StructureType: paragraphs (P, H1...), lists (L / LI / Lbl / LBody), tables (Table / THead / TBody / TR / TH / TD with RowSpan, ColSpan, Scope and Headers), figures with Alt, links (Link with the annotation's object reference) and inline spans that carry a language. A paragraph with the type Caption next to a figure or a table becomes that element's caption. A block or part that continues on the next page stays one element.

A structure type that is not standard in the chosen namespace is written in the default namespace and role-mapped (§14.8.6.2) to the type given with WithRoleMapping(String, String), or else to the type the element would have had (a paragraph to P, an image to Figure, a list to L, a table to Table, a run to Span or Link). Instances are immutable.

Tip: use kind:method, kind:property, kind:ctor. Press Esc to clear.

Properties (5)

Methods (4)