> For the complete documentation index, see [llms.txt](https://docs.santacruzsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.santacruzsoftware.com/printui/guides/text-styles-and-tables.md).

# Work with Text, Styles and Tables

## Text frames

Editable text should use rectangular text frames where possible. Non-rectangular text frames are converted to rectangles for editing.

Use the single-line composer in InDesign when line breaks must closely match the editor. InDesign's paragraph composer can create different line breaks than the PrintUI editor.

## Styles palette

Use the styles palette when users must choose from approved paragraph and character styles. This is useful for brand-controlled templates and table editing.

Define every style users may need, even if no live text currently uses that style. Name styles clearly for non-designers.

## Fonts palette

Use the normal text palette when users may choose fonts, sizes, colors, and other text attributes more freely. The available font list comes from base fonts and fonts used in the template.

To include extra template-specific fonts in the editor menu, add off-page text on a foreground or background layer using each desired font.

## Fit text frames

Use Fill Text Frame for frames where text should shrink or grow to fit. Set minimum and maximum font sizes so the result remains readable and on brand.

## Tables

Tables can be edited in PrintUI when created in InDesign. Users may add or remove rows and columns and style cells when the styles palette is available.

Important restrictions:

* Column width is fixed in the editor.
* Table structure and formatting require the styles palette.
* Cell styling should be done through cell styles.
* Merged cells can span columns but not rows.
* Tables with merged cells cannot have columns added or removed.
* Users cannot add entirely new tables in the editor.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.santacruzsoftware.com/printui/guides/text-styles-and-tables.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.