typograph-editor-documentation
    Preparing search index...

    Release Notes - Version 1.0.0-20260903

    • Text frames that InDesign threads together arrive as one flow. InDesign lets a story run on through several frames — a column continuing onto the next, an article carrying across a spread — and that threading was read and thrown away on every import. Each frame in the chain was handed the whole story instead, so a document that had one article running through four boxes arrived as four boxes each holding the entire article and each overflowing. They now arrive linked, with the text running from one into the next as it did in InDesign.
    • Only the first frame of a flow holds its text; the frames after it are filled with whatever did not fit in the one before. That is how a flow already worked for frames linked by hand in the editor, and converted documents now join the same arrangement rather than a parallel one.
    • Text that flows from one frame into another is filled in when a document is opened. A flow is held by its first frame — the frames after it are given whatever did not fit in the one before — and nothing did that filling at opening time. A document kept whatever its frames were last saved holding, which was right often enough that it went unnoticed, and a flow that arrived from anywhere else showed everything in the first frame and nothing in the rest.
    • A flow whose later frames were empty to begin with stopped after the first of them. The frames after that stayed blank however much text there was, and the one before them reported that it had room to spare while holding several times what it could show. A frame that starts out empty has no line spacing of its own, and it was never given the spacing of the text it received; every measurement it then made was meaningless. Frames in a flow now take their line spacing from the frame the text started in, as they already take hyphenation and language from it.
    • Images from InDesign arrived in the wrong place and at the wrong size. A photo placed larger than its frame — cropped, so that the frame shows a part of it — came through shrunk until it fitted inside the frame and centred there, which is a different picture from the one that was designed. Only images cropped by their frame looked wrong; one already sitting neatly inside its frame was unaffected, which is why it read as occasional rather than as every image.
    • The position and size were read correctly on import all along. They were then overruled by a second instruction, written beside them, that said to fit the image to its frame — so the reading was right and the picture still moved.
    • A group could lose its place in a flow when a document was opened. Groups can sit in a flow just as frames can, and one of the two ways a document is read asked for the link under a name nothing writes, so it found none and the group came back unlinked. Frames were never affected.
    • The fill runs over every flow at load, unconditionally, rather than only over those that look empty: "empty" would have to be a judgement about a flow whose text genuinely ends in its first frame, and reflow is not expensive enough to buy that risk. It runs after fonts are loaded and after text wrap has recomposed, because it measures text, and before the document-opened event, so a host never sees a half-filled flow.
    • A flow is resolved within one spread. Frames on different pages of the same spread work, because a spread is one lookup scope; frames on different spreads do not, and nothing can author such a flow today. reflow_chain now takes the spread that owns the flow, defaulting to the active one, because during loading there is not yet an active spread.
    • The import reads PreviousTextFrame and NextTextFrame, and gives the story only to the frame at the head of the chain. It is a single pass: an element's identifier is derived from its InDesign one, so the frame that says it continues into another can record that link before the other frame has been read.
    • A frame naming a continuation that is not in the document leaves a link to nothing. The flow stops there rather than failing, so such a document loses the tail of its text instead of refusing to open. Reporting it as a conversion error needs a whole-document check and is not in this release.
    • The image fix is in the converter, not the editor: the placement is read from the InDesign document and was being overridden by a fitting mode written onto the same element. An image whose placement is known now arrives with no fitting mode at all, so nothing recomputes it. A frame that genuinely asks to fit its content still says so.
    • Both halves of this ship together — the editor fills the flows, the converter reads them — so a document converted before this release still arrives with each frame holding the whole story until it is converted again.