Pullouts can have a "type" field. Possible values include "tosumup" (To Sum Up). The pullout type attribute was not getting renamed, leading to undefined content element errors on ingestion.
In legacy, the type label is printed in bold followed by ellipses ("To Sum Up...") as a prefix to the pullout content, so this PR implements a version of that.
There are other divergences from legacy pullout behavior that are not addressed:
In legacy, typed pullouts are formatted differently than untyped (untyped render entirely in italics);
legacy merges type label as prefix into first pullout block (title or text content) rather than as header; and
legacy pullouts are indented like block quotes (torus issue #3659) -- this is what makes them 'pullouts' - while migration tool just turns them into paragraphs aligned with the preceding and following paragraphs so they are not set off.
But this gets past the error-causing handling of the type field and gets the pullout content w/label on the page in readable form.
Pullouts can have a "type" field. Possible values include "tosumup" (To Sum Up). The pullout type attribute was not getting renamed, leading to undefined content element errors on ingestion.
In legacy, the type label is printed in bold followed by ellipses ("To Sum Up...") as a prefix to the pullout content, so this PR implements a version of that.
There are other divergences from legacy pullout behavior that are not addressed:
But this gets past the error-causing handling of the type field and gets the pullout content w/label on the page in readable form.