UseJunior Book a Demo

ECMA-376 edition 5, Part 1 § 17.16.18

w:fldChar five-part complex-field emission

Product posture and evidence for this normative section. The ECMA publication is the authority; this page reports only the pinned Safe DOCX projection.

ECMA publication ↗

Safe DOCX posture

targeted

w:fldChar five-part complex-field emission

Every generated field is a complete five-run sequence — fldChar begin, preserved-space w:instrText, fldChar separate, a cached-result run, fldChar end — and w:dirty is never set. The cached result is a required spec property, making the no-recovery-dialog guarantee unrepresentable-by-omission; the structural validator runs a begin → separate → end state machine over every story part. The comparison path keeps these field-state markers outside the w:del payload wrappers shown by the Part 1 complex-field and deleted-field-code syntax. The runtime ancillary predicate adds fail-closed stack diagnostics without changing the Lean-pinned predicate or protocol.

Registry identity: ECMA-PART1-17-16-18

Schema declarations

Bounded evidence