How to compare two translations in a browser

A revised translation can look almost identical to the previous one while changing a key term, a number, or the tone of a sentence. Reading both versions from top to bottom makes small differences easy to miss, especially in a long file or a set of short interface strings.

Use Text Compare to inspect two text versions and find what changed. Then review each difference in context. A comparison can reveal edits, but it cannot tell you whether the new translation is accurate or natural.

Compare two translation drafts

1. Open Text Compare. Keep the current approved translation and the proposed revision available as plain text.
2. Paste the approved translation into one text area and the revised translation into the other. Label or note which is which before you begin, so you do not mistake the older wording for the new one.
3. Compare the text and examine each marked difference. Check changed words, punctuation, numbers, placeholders, and any lines that were added or removed.
4. Use the source text, screenshots, or product context to judge whether each change preserves the intended meaning. If the strings belong to an interface, include where the text appears and what action it describes.
5. Record the accepted wording and any questions for the translator or reviewer. Do not approve a change just because it appears as a small edit.

For a fair comparison, use the same text scope in both versions. If one draft includes a heading or a note that the other does not, the comparison can show a large block of differences even when the sentence-level changes are small. You can compare a whole passage first, then compare a shorter section to inspect a confusing result.

What the differences mean

A few words are highlighted

This usually means the sentence was edited in place. Read the whole sentence, not only the changed words. A different verb can alter whether a button starts, saves, or cancels an action. Check that the new phrase fits the surrounding instructions and the product's established terminology.

A line appears added or removed

The two drafts may have different sentence breaks, list items, or paragraph structure. The text comparison shows that the content is not identical, but it cannot decide whether a sentence was intentionally moved, accidentally deleted, or added in the wrong location. Check the source document and the revision notes.

Only punctuation or spacing changed

Some edits are intentional. A locale may use different quotation marks, decimal separators, spacing, or punctuation conventions. Other changes can affect how text is parsed, especially around variables, tags, or code. Ask whether the difference follows the project's language rules before accepting it.

The comparison shows many differences at once

The drafts may have been reformatted, copied with different line breaks, or compared at different scopes. A text comparison detects character and line changes, so paragraph wrapping or a changed list structure can make the output look more dramatic than the content change. Compare the relevant sentences in smaller sections and check the source version.

The drafts look identical, but the translation still seems wrong

The comparison only checks the text you supplied. It cannot find a translation error shared by both versions, judge tone, or confirm that the text fits the product. Review against the source meaning and the locale's terminology list. For more on reviewing changes line by line, see line-by-line localization review.

How to resolve differences

1. Check that the versions are labeled correctly. Confirm which field contains the approved draft and which contains the proposed change. If the order is reversed, you may interpret the revision incorrectly.
2. Compare matching sections. Make sure both texts cover the same string, paragraph, or document section. Remove unrelated headers, comments, and notes from the comparison if they obscure the change you need to review.
3. Check variables and formatting tokens. Look for items such as {name}, %s, HTML tags, and line breaks. These may need to remain unchanged or appear in a particular order. Confirm the project's rules rather than translating or deleting them by instinct.
4. Check numbers and locale conventions. Verify dates, times, prices, percentages, and measurement units against the source. A comma or period may have a different role in another locale, so check the value as well as the punctuation.
5. Ask for context when a phrase is ambiguous. A short string such as “Open” can be a verb, an adjective, or a status. Share the source sentence and where it appears in the product, then ask the translator to confirm the intended sense.
6. Escalate unresolved terminology decisions. If two translations are both plausible, check the approved glossary and style guide. Ask the localization lead to choose a consistent term before updating other screens or documents.

Review meaning as well as matching text

Text comparison is useful for finding changed wording, but language quality requires a separate check. Compare the revised text with the source meaning, audience, and purpose. Confirm that a warning still sounds like a warning, that instructions remain clear, and that the level of formality fits the product.

For interface content, also check the text in its actual screen or layout. A browser text comparison does not show whether a translated label wraps, gets cut off, or no longer fits a button. Keep the source and product context beside the comparison, and follow your team's rules for handling confidential text.