Skip to content
LionrapidLionrapid Docs

What gets translated

When a file is processed, its text is split into rows for the editor, and everything else (layout, images, styles, metadata) is kept aside to be reassembled at delivery. A row is what other translation tools call a segment or a translation unit. This page lists, per format, what ends up in a row and what does not, so you know what to expect before you open the file and what to check in the delivered result.

Rules that apply to every format

Section titled “Rules that apply to every format”
  • One row per block. A paragraph, heading, table cell, spreadsheet cell or slide paragraph becomes a row. Long paragraphs are split at sentence boundaries into several rows. Rows cannot be merged or split by hand in the editor.
  • Some rows are copied, not translated. A row that is only a URL, only an email address, or only numbers and symbols (a price, a date, a phone number) is copied into the target unchanged. So is a row that consists of nothing but a list marker. These rows are still part of the file’s word count.
  • Inline formatting travels with the text. Bold, italic, links, colours and font changes inside a paragraph are carried onto the translation, and the editor lets you adjust where they land; see Style & formatting. Where a translation cannot be mapped onto the source’s formatting runs, the formatting inside that paragraph may be simplified and a QA warning is raised.
  • Repeated headers and footers are one row. Text that repeats across a document’s headers and footers (a running title, a copyright line) is shown once in the editor; your translation is written into every occurrence.
  • Images stay where they are. Pictures, drawings and charts are kept in place. Text inside an image is not translated.

Word-processor documents

Section titled “Word-processor documents”

Applies to .docx; .odt, .fodt and .rtf are covered under other formats below.

Translated:

  • Body text: paragraphs, headings, list items and table cells
  • Headers and footers, including different first-page and section variants
  • Footnotes and endnotes
  • Text boxes and text inside shapes
  • Hyperlink text (the link target is preserved and can be edited in the editor)

Carried through, not translated:

  • Fields — page numbers, dates, cross-references, tables of contents and other auto-generated text keep their field definition. Refresh them in your word processor after delivery if they show stale values.
  • Comments — review comments are kept but not translated.
  • Hidden text — runs marked hidden in the document are skipped.
  • Charts and SmartArt — kept as-is; their labels are not translated in Word documents (they are in PowerPoint, see below).

Tracked changes are handled the way a reviewer would expect: deletions are not translated and stay recorded as deletions, and insertions are translated and remain marked as insertions in the delivered file. Accept all changes before uploading if you want a clean document.

The delivered .docx is the original file with the text replaced, so anchored objects, section breaks, styles and document settings survive exactly.

Presentations

Section titled “Presentations”

Applies to .pptx. Every text-bearing part of the deck is translated, in this order in the editor:

  1. Slides, in presentation order
  2. Chart text: titles, axis labels and legends
  3. SmartArt diagrams
  4. Speaker notes
  5. Slide layouts
  6. Slide masters

Slide-number, date and footer fields keep their field definition. Because layouts and masters are included, text that only exists on a master (a running footer, a template’s own headings) is translated too.

Legacy .ppt, .odp and .fodp decks go through a general conversion that covers slide text. For full coverage of notes, layouts and masters, save the deck as .pptx first.

Spreadsheets

Section titled “Spreadsheets”

Applies to .xlsx; .ods and .fods are covered under other formats.

  • Visible cells only. Text in hidden sheets, hidden rows and hidden columns is neither translated nor counted. Unhide anything you need translated before uploading.
  • Formulas are never changed. A cell that holds a formula keeps it. Text literals inside a formula, such as the labels in =IF(A1>0,"Paid","Open"), are translated and written back into the formula.
  • Chart text (titles, axis labels) is translated.
  • Numbers, dates and IDs come through unchanged under the copy rule above.

Each translated cell is one row. Cells that share a formula with a neighbour (filled-down or array formulas) are left to the formula.

CSV

Section titled “CSV”

The delimiter and text encoding are detected from the file, and the delivered file uses the same ones. Every text cell becomes a row. Cells that are purely numeric, dates, booleans, currency amounts, identifiers or product codes, URLs or email addresses are kept as they are.

Other document formats

Section titled “Other document formats”

.odt, .fodt, .rtf, .txt, .ods, .fods, .odp, .fodp and .ppt are handled through a general document conversion. Paragraphs, headings, lists, tables and inline formatting are translated and rebuilt in the original format. These formats do not get the format-specific handling described above for .docx, .pptx and .xlsx, so for anything beyond a plain document, convert to the Office equivalent first for the best result.

Plain .txt files are split into paragraphs and then into sentences, and delivered as plain text in the same encoding.

PDF

Section titled “PDF”

PDF is a fixed-layout format and gets its own page: PDF documents.

Section titled “Related”