Exporting

The Export menu in the toolbar offers four outputs.

TEI-XML

The complete document: header, lemmas, annotations, entity references and the MENOTA levels if the template enables them.

This is the archival and interchange format. It validates against TEI P5 or MENOTA P5 depending on the template, and it is what other tools in a digital-edition workflow expect.

HTML

The document transformed by the stylesheet chosen in Settings, as a single file with its styles and the Junicode font embedded. It needs no network connection and no other files, so it can be emailed, deposited or opened from a USB stick.

PDF

The same output, set in A4 pages with margins and page numbers, using Vivliostyle and CSS Paged Media. The built-in layout avoids headings and single lines stranded at a page edge, and embeds Junicode so MUFI characters print even where the font is not installed.

• On Linux and Windows, PDF export saves directly to the file you choose.
• On macOS, the system print dialog opens; choose Save as PDF to create the file.

Dictionary JSON

Your confirmed word forms with their lemmas, analyses and normalized forms, for backup or analysis.

This is not a TEI format. It is a flat export of the scholarship attached to the words, useful for checking consistency, building a glossary, or moving lemmas into another tool.

Errors and exports

Exports are refused while the shorthand contains errors. A failed compile would produce an incomplete or malformed document, so Saga-Scribe stops rather than write one.

HTML and PDF export run behind a progress overlay showing the current step, with a Cancel button. Exporting a large manuscript can take a little while; the editor stays responsive.

Note

The preview and the export use the same stylesheet, but exports apply it to the whole document. If your stylesheet uses the page-by-page declaration, check an export before relying on the preview alone — see Faster previews.