View menu

The View menu lets you change how the Editor displays your segments. The options it offers affect appearance only — they do not change your translations or any segment data. Adjusting them is a per-user preference saved in your browser, so the Editor opens the next time exactly the way you left it.

The View menu currently exposes:

• Whitespace: Show or hide whitespace marks (spaces, tabs, line breaks) in the segment text.

• Segment labels: Show or hide colored segment labels in the grid rows. Keyboard shortcut Alt+Shift+L.

• Reset column widths: Restore column widths to their default sizes after manual resizing.

The following options are coming soon and are described below for reference:

• Markup SOON: Choose how markup chips appear in the grid — minimal markers, default labels, or full inline content.

• Character count SOON: Show or hide the character count below each segment, on both the source and the target side.

Whitespace

The Whitespace option shows or hides whitespace marks in the segment text: spaces appear as small dots, tabs as arrows, and line breaks as a return symbol. Use it when you need to verify that whitespace is correctly preserved between source and target, or to spot accidental double spaces.

This is a simple on/off toggle. Click View > Whitespace to switch it.

Two side-by-side segments — left without whitespace marks, right with whitespace marks visible (dots between words, arrow for tab, return symbol for line break).

Segment labels

The Segment labels option shows or hides the colored segment labels in the grid rows. Labels are used to categorize segments (for example: "approved", "needs review", "client query"). Hiding them reduces visual noise when you want to focus on the text alone.

This is a simple on/off toggle, with the keyboard shortcut Alt+Shift+L assigned by default. Click View > Segment labels or press the shortcut to switch it.

Two side-by-side segments — left with colored labels visible at the start of each row, right with labels hidden.

Reset column widths

The Reset column widths action restores all grid columns to their default sizes after manual resizing. Useful after experimenting with column widths or when content changes have made the layout uneven.

Click View > Reset column widths to apply. The action is disabled when columns are already at their defaults.

Markup SOON

Translation files often contain markup: placeholder variables, formatting tags, or structural markers from the source document. By default, the Editor shows each piece of markup as a short label that hides its content, and you have to hover to see what it represents. The Markup submenu — coming in an upcoming release — will let you change this so the most useful information is visible at a glance.

Inserting markup from the Edit menu

While markup display modes are part of the View menu, you can also insert markup directly into a segment from the Edit menu, useful when the source contains placeholders, formatting tags, or structural markers that need to be carried over manually.

To insert markup into a segment:

1. Place your cursor in the target segment where you want the markup to appear.

2. Open the Edit > Markup submenu.

3. Choose the markup you want to insert.

Inserted markup respects the markup display mode (Minimal, Standard, or Inline) once that option ships under View > Markup. Until then, inserted markup follows the default labelled display.

Choosing a markup display mode

Open View > Markup to see the three available modes. Hover any entry to read a short description.

View > Markup flyout open with Minimal / Standard / Inline visible.

Your selection is saved in your browser and applies the next time you open the Editor.

How each mode looks

Minimal: a thin colored bar marks where each piece of markup sits in the segment. The surrounding text stays uninterrupted. Hover any marker to read its content.

Minimal mode — segment with three thin colored vertical bars in place of the markup.

Standard: each piece of markup appears as a short labeled block — a parser-generated placeholder like [1] or [/1], an HTML element like <span>, or a formatting code like b. Hover any block to read the underlying content.

Standard mode — segment "Hello [1], you have [2] gold and [3] potions." with three blue label blocks.

Inline: the label is replaced with the actual markup content, so you can read the placeholder name or formatting tag directly without hovering.

Inline mode — same segment showing "Hello {character_name}, you have {gold_count} gold and {potion_count} potions." with the placeholder names visible inline as blue label blocks.

Gaming use case before/after — top half Standard with hover tooltip, bottom half Inline with placeholder names visible directly.

The Inline view shows you the same content you would see today by hovering over each block. Nothing extra is exposed: if a markup is configured to display a custom description (for example, to mask sensitive content), Inline shows that description, not the original captured text.

Markup categories

The Editor distinguishes two kinds of markup using different colors. Both colors apply in every mode.

Two cards side by side — left blue document-markup chips around "Galaxy 1"; right amber font-styling chips around "Start".

For font styling markup, Standard and Inline display the same label (b for bold, i for italic, and so on): the format name is already the meaningful information. The amber color is what tells you it is a styling tag and not a placeholder.

Supported file formats

Inline mode is most valuable for files where each piece of markup represents a small, readable piece of content (a variable name, a placeholder, an HTML attribute). For files where the source carries large amounts of formatting metadata, Inline can become noisy, and for a small set of formats it is not available at all.

Where Inline works best

If your project uses regex-based markup capture in Do not translate > Words or terms, Inline shows whatever each regex was configured to expose: either the captured text, or the description if one was set.

Where Inline is available but markup can be verbose

For office document formats, Inline is enabled but the labels can be long because the source carries detailed run-level formatting. Switch back to Standard if Inline becomes noisy.

Where Inline is not available

For a small set of formats, Inline is greyed out in the menu and the Editor stays in Standard.

When you open one of these files, hovering the disabled Inline entry displays:

Inline view is not available for this file format.

Disabled menu state — Markup flyout open with Inline greyed out and tooltip visible.

Tip

You can assign a keyboard shortcut to the Markup mode menu in Preferences > Shortcuts. Once set, the shortcut appears next to Markup in the View menu and opens the picker with one keystroke — handy when you switch modes often, for example to verify markup details quickly while revising a translation.

Character count SOON

The Character count option will show or hide the character count below each segment, on both the source and the target side. It will be available from the View menu in an upcoming release.

Click View > Character count to switch it, or assign a keyboard shortcut in Preferences > Shortcuts, alongside the existing Toggle whitespace and Toggle labels shortcuts.

• Turn it on when you work on length-sensitive content (UI strings, subtitles, SMS, packaging, gaming text) and want a constant reference as you type.

• Turn it off to keep the grid compact when length is not a concern.

Segments with a configured minimum or maximum length always show their count, in the format "13 char (5, 10)", whether the toggle is on or off. This makes sure you never miss a length restriction enforced on the segment.

The space where the count appears will soon be customizable, so you can show it on the target side only and use it as a typing reference.

Learn More

• Quick Toolbar: Insert formatting markup (Bold, Italic, Underline, Subscript, Superscript) and other quick actions while editing.

• Memory Finder Panel: Search translation memories. Memory hits use a separate display path and currently always render markup as labels.

• Preferences: Configure your Editor settings including keyboard shortcuts, display options, and theme.