In this article, you'll learn more about how XLIFF is used in Translations for Scroll Documents. Before reading on, make sure you've learned about the basics of external translation.

XLIFF ZIP File Structure

When exporting a document (version) as an XLIFF file, an .xlf file is created for each page. Both the export and import required the individual files to be within a ZIP archive, on top level.

The ZIP archive and individual XLIFF files are named with the following structure: 

ZIP: Document_Name_sourceLanguageKey
XLIFF: Page_Name_sourceLanguageKey
CODE

The file names don't need to be adjusted after they have been translated.

Translated Macros and Parameters

The XLIFF export generally includes body content of bodied macros, with some notable exceptions, for example the Code macro. Besides that, macro parameters are translated on an allowlist basis as documented below.

Confluence macros

Macro

Translated parameters

Body translated

Chart

  • Title

  • Subtitle

(error)

Code

  • Title

(error)

Content by label

  • Title

-

Create from template

  • Button label

-

Expand

  • Title

(tick)

Gallery

  • Title

-

Live search

  • Placeholder

-

Navigation map

  • Title

-

Page properties

-

(error)

Page properties report

  • Title column heading

-

Panel macros (Panel, Info, Note, Tip, Warning)

  • Title

(tick)

Status

  • Title

-

Scroll App macros

Macro

Translated parameters

Body translated

Scroll Title

  • Title

-

Scroll Export Button

  • Caption

-

Viewport Tab

  • Title

(tick)

Viewport Meta Tag

  • Share title

  • Share description

-