Skip to content

v0.3.13 — W9 and the submit and reset docs

Choose a tag to compare

@thatsme thatsme released this 02 Nov 08:12
· 176 commits to main since this release

Text in an embedded font that the font cannot draw was drawn as blanks,
silently.
A character the font has no glyph for was written as glyph 0,
the font's placeholder, and drawn as a blank. This affected every release
from 0.1.0 to 0.3.12, and a validator does not name it: veraPDF's PDF/A-2b
profile passed one such file, and failed another only on a glyph width
(clause 6.2.11.5). 0.3.13 warns, naming each such character, and 0.4.0 will
refuse it. No output byte changes.

The release also corrects the documentation of the reset action, and
documents what a submit action sends.

The veraPDF 1.30.2 reports for this release are attached below, produced by CI against the tagged commit. Eight reports, for five documents, every one isCompliant="true".

Deprecated

This warns now and raises in 0.4.0:

  • Text in an embedded font that has no glyph for one of its characters.
    Every function that draws text warns once per call, naming each such
    character and its code point: font "Sans" has no glyph for "✓" (U+2713), which is drawn as a blank. text_paragraph/6 and the Tincture.Layout
    functions, which draw word by word, warn once for the whole call. A
    default-ignorable code point (Unicode's Default_Ignorable_Code_Point, such
    as a variation selector, a zero-width joiner or space, or a soft hyphen) is
    not counted: it has no visible glyph of its own. The standard 14 fonts are
    not checked.
    Migration: register a font that covers the character, or remove it.

Documentation

  • :reset restores each field's initial value. push_button/7
    documented it as clearing every field. A reset sets each field to its
    default value, and Tincture writes a field's initial value as its default,
    so a field created with :value gets that value back, and only a field
    created without one is emptied.
  • What a submit sends. push_button/7 gains a section on
    {:submit, url}: an HTTP POST in HTML form format, with each field's name
    and value, leaving out fields with no value, push buttons and fields
    created with no_export: true. It records what Acrobat Reader 26.2 was
    observed to do: it asks before connecting to an untrusted host, it reports
    an HTML reply as an error, and it sends a value outside ASCII in a Windows
    code page with no charset. PDFgear 2.1.16 runs no form actions.