
Scribus Scripter's getFrameText() returns the text visible in one frame, whereas getAllText() returns text from the linked story. An active text selection can narrow either result. If an extraction unexpectedly contains only a passage, inspect scope, selection and layout freshness before treating the remainder as lost content.
The Handling Text Frames API reference in Release 1.6.6 defines these contracts. This is an in-Scribus API workflow, not a claim that importing a similarly named Python package outside Scribus supplies the same functions.
Choose visible-frame text or the linked story
For a hypothetical three-frame article, name the frames distinctly and identify which extraction is needed. A page-level label audit may need visible text from one frame. A copy completeness audit may instead need the story containing all linked text.
Use an explicit frame name in the call rather than relying on whichever object happens to be selected. The API permits an omitted name, but that makes the current item part of the script's input state.
A returned string with the expected beginning is insufficient evidence of full-story extraction. Check a recognizable sentence near the story's ending as well.
Inspect text selection before interpreting a short result
The reference says that selected text is returned when the frame has a text selection. Therefore, requesting the whole story by function name does not remove this separate state condition.
Establish a known selection state in a disposable test document. Record whether the intended query is for selected text or unselected story content. Do not silently clear a user's working selection in a production editing session without accounting for that state change.
Refresh layout before visible-frame queries
getFrameText() depends on current text layout. The documented layoutText() refreshes one frame, while layoutTextChain() refreshes the linked chain.
For a proposed chain check, relayout the named chain and then compare visible-frame extraction with all-story extraction:
scribus.layoutTextChain("BodyA")
visible = scribus.getFrameText("BodyA")
story = scribus.getAllText("BodyA")
This schematic has not been executed. Replace the frame name and confirm the selection state before interpreting its results. Relayout can change what fits visibly; it does not manufacture missing text.
Verify the intended extraction contract
Compare the result with a known marker inside the first frame and another later in the chain. Also inspect the actual layout for overflow if completeness matters.
The missing-ending guide explains why a complete story and a complete exported page are different checks. This procedure distinguishes API query scope; it does not certify a PDF or save a text-extraction file.
Related tasks
- Why Does My Photoshop Batch Action Save Files Under the Same Name?
- Apply Data Set or Export Data Sets as Files? Preserve Your Photoshop Template
- Why Does My Artwork Package Work Here but Fail on the Recipient’s File Path?
Sources and scope
- Handling Text Frames: getFrameText returns visible text in one frame and requires current layout; getAllText includes linked frames, while an existing text selection changes returned scope.
This guide follows the official Scribus documentation retained in Release 1.6.6, consulted on October 23, 2026 (Asia/Shanghai). Historical interface illustrations and optional viewer behavior require confirmation in the actual installation. The proposed procedures and code have not been executed for this article.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Paparazzi Ratzfatzzi / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.