The In-context preview feature offers a real-time preview of original or translated text directly in the editors and can be switched between source and target views.
The preview can be switched on and off from the menu in both the web and desktop editors.
Click to open the in-context preview in a separate window. Closing the separate window restores the preview to the bottom panel.
Clicking on a segment to be translated highlights the respective text in the preview window and displays the position of the translated segment within the document.
Clicking on text within the preview causes the translation grid to indicate the corresponding segment for editing.
During QA, clicking on a warning navigates the linguist to the position of the warning within the document.
Tables, columns, various graphics, formatting, and fonts (if installed by users) are supported. The feature is meant to provide context when translating and is not a perfect representation of the original or completed document; some visual differences are expected. It can also be influenced by enabling/disabling Allow loading of external content in editors option in Access and Security settings.
The preview also has zoom functionality as well as a right-click context menu.
Note
The in-context preview in the web browser may be affected by the editor having only a portion of segments loaded at a given time; skipping over large groups of segments can lead to an incomplete preview.
Scrolling through the translation table and loading segments from the beginning of a major section (e.g. a chapter) or from the beginning of a job improves the preview.
Supported CMS
-
AEM
-
Contentful
-
Drupal
-
Marketo
-
Sitecore
-
WordPress
For certain file types (e.g. .HTML files), the preview is generated directly.
In all other cases, Phrase downloads the .HTML from the third-party system and saves it as a preview template. When importing and processing the content for translation in the CAT editors, the .HTML preview template is matched with information from the .MXLIFF file to generate the In-context preview of the segments.
In-context preview for CSM content can be generated without building a custom CSM connector by using the preview package, which supports rich .HTML and .SVG preview formats. The preview is generated during job creation by importing an .HTML (optionally with contextual assets) or .SVG preview template.
Supported file types
-
AsciiDoc
-
.DITA
-
Google Docs, Sheets and Slides
-
.HTML
-
.IDML
-
Markdown
-
Microsoft Excel (including multilingual files)
-
Microsoft PowerPoint
-
Microsoft Word
-
.RTF
-
.SVG
-
.XML with style sheets (including multilingual files)
Previews are not generated for unsupported file types.
If a preview can not be generated due to unsupported file type or preview limits are exceeded, a preview can be downloaded from the menu but will not be in the original file type.
Tip
Microsoft Excel file previews are downloaded in SpreadsheetML (.XML) format, which can be opened in any compatible spreadsheet editor. If MSOffice is installed, they typically open in Excel automatically; if not, use the action from the file context menu to select an application.
A limited version of live in-context preview for InDesign files is available. The preview supports all in-context preview functions (source and target preview, real-time changes, navigating from the translation table to the preview window and the other way round, and zoom) and it supports a wide range of InDesign components.
Limitations
-
Images are displayed for imported .IDML files with embedded images.
-
The maximum size for any image is 500 KB, and the total size for all images must be 10 MB or less.
A live in-context preview is available for jobs synced from Phrase Strings that were created with the Strings Figma plugin.
The preview supports all TMS in-context preview functions (source and target preview, real-time changes, navigating from the translation table to the preview window and the other way round, and zoom) and the following Figma elements:
-
Text
-
Frames
-
Groups
-
Components
-
Shapes and images
End-to-end workflow overview
-
Push from Figma to Strings
Use the Figma plugin to select design content and send it to a Strings project.
A preview (up to 50 MB) is attached automatically. If a preview exceeds the 50 MB limit, a notification appears and the keys will still be pushed to Strings but a job with keys for JobSync will be not be created.
When uploading multiple frames in bulk, frames with previews larger than 50 MB are excluded from upload with an error message displaying the frame name and node ID.
Required plugin settings:
-
Enable the option.
-
Enable smart key naming and use the following macro to ensure that segments are sent to TMS in the same order as they appear in the plugin:
{ulid}This setting is remembered per Figma file only, not on new files.
-
Regenerate keys before each push to ensure updated naming.
-
If rich formatting is required in the TMS in-context preview, enable the option. This allows bold, italics, lists, and links to be displayed correctly in the preview using HTML formatting tags.
-
-
Jobs are created in the Strings project
Jobs are created automatically from pushed content and include all defined target languages.
-
Translate in TMS CAT editor
Sync the job(s) via the Phrase Strings connector and open them in the CAT editor to translate content with the Figma in-context preview.
-
Pull back to Figma
Completed translations are synced back to Strings and can be pulled into Figma via the Strings plugin.