Documents

Translate full documents with structured content and HTML round-tripping.

What Is Document Localization?

While strings handle short pieces of text like button labels and error messages, document localization is for longer-form content that needs to be translated as a whole. This includes:

Help articles — Step-by-step guides and support documentation
Legal pages — Terms of service, privacy policies, and compliance documents
Marketing copy — Landing pages, feature descriptions, and promotional content
Release notes — Product update announcements
Knowledge base articles — In-depth technical or product information

How It Works

Documents are linked to localization projects and translated on a per-language basis, just like strings. Here is the typical workflow:

Link a document to a localization project. The original document becomes the source content.
Create translations for each target language. Translators can work directly in the system or use the HTML export/import workflow.
Review and approve — Document translations go through the same review workflow as string translations.
Publish — Once approved, the translated document is available for use.

Each document can have one translation per target language, and each translation tracks its status, origin, and review history independently.

Structured Content

Document translations are stored as structured data that preserves the formatting and layout of the original content. This means headings, paragraphs, lists, links, bold text, and other formatting elements are maintained in the translated version. Translators work with the text content while the structure stays intact.

HTML Round-Tripping

For teams that prefer to translate documents using external tools — such as computer-assisted translation (CAT) tools, translation agencies, or even a simple text editor — Bosca supports HTML round-tripping:

Export as HTML — Download the source document as a clean HTML file. The exported HTML preserves structural markers that allow accurate re-import.
Translate externally — Send the HTML file to your translators, agency, or tool of choice. They translate the text content while keeping the HTML structure.
Import the translation — Upload the translated HTML back into Bosca. The system parses it and stores the translation as structured content.

Imported translations start in the Draft state, so they still go through the standard review process before being published.

HTML round-tripping is especially useful when working with translation agencies. You send them a standard HTML file they can work with in any tool, and they send back a translated HTML file you can import directly.

Review Workflow

Document translations follow the same review workflow as string translations. Every translation moves through states like Draft, In Review, Approved, and Published. AI-generated document translations must be reviewed by a human before publishing, just like string translations. See the Workflow page for full details on the review process.

When to Use Documents vs. Strings

Choosing between document translation and string translation depends on the type of content you are localizing:

Use Strings For	Use Documents For
Button labels and menu items	Help articles and guides
Error and success messages	Legal and compliance pages
Form labels and placeholders	Marketing landing pages
Notification text	Release notes and changelogs
Short UI copy (a few words to a sentence)	Long-form content (multiple paragraphs or pages)

You can use both strings and documents within the same project. For example, a "Help Center" project might contain strings for the UI of the help center itself (search labels, navigation, category names) and documents for the actual help articles.