Compare two lists line by line for localization

A revised translation can look fine at a glance while a short label has disappeared, a placeholder has changed, or several lines have shifted out of alignment. Checking two lists line by line makes those differences easier to find before localized text goes into an app, website, or document.

Use Text Compare to compare two versions of a list in your browser. For the clearest review, compare the current localized text with the previous approved version, and keep the entries in the same order.

Compare the lists line by line

1. Open Text Compare. Prepare the two versions you want to review, such as the approved translation and the updated translation.
2. Put one version in each text area. Keep one string or list item on each line, and preserve the same order in both versions.
3. Compare the two texts. Scan the highlighted differences from the top down, noting changed wording, missing entries, and lines that appear to be paired with the wrong item.
4. Check every changed line against your source material or localization notes. Decide whether the difference is an intended edit, a formatting change, or a mistake that needs correction.
5. After making corrections in your working file, compare the revised list again. Keep the approved version separate so you can refer back to it.

If you are checking whether translated strings match their source entries, do not expect the source and translation to look alike. Instead, use a source list as a reference for meaning and order, then compare two versions of the localized list to identify what changed between them.

What the differences mean

A few words changed on an otherwise matching line

This is often a normal translation edit. Check whether the new wording preserves the intended meaning, tone, and any terminology already used elsewhere in the product. A text comparison identifies the change, but it cannot judge whether the translation is accurate or natural.

A line is missing or added

Look for an omitted string, a new entry, or a difference in how line breaks were saved. A single missing line can make every later item appear to be different if the comparison pairs entries by position. Check the surrounding lines and confirm the list lengths before treating a long run of differences as many separate translation edits.

Many lines differ after one point

This pattern can mean that an item was inserted, deleted, or moved in one list. Find the first line where alignment changes. Compare nearby entries with the original file or a stable string ID list, then restore the intended order before reviewing the rest.

Only punctuation, spaces, or capitalization changed

These details can matter in a user interface. A missing space can join words, punctuation can change the tone, and capitalization rules vary by language. However, some differences may come from formatting or line-ending changes rather than a visible wording edit. Check the actual text and the style guide before approving or rejecting them.

A placeholder or variable looks different

Check values such as {name}, %s, \n, or markup that must remain exactly as expected by the software. A translator may change the surrounding sentence while the placeholder itself needs to stay intact. Confirm the required format with the project files or developer instructions, because Text Compare cannot tell whether a variable is valid for the application.

How to resolve mismatches

1. Confirm that the lists are aligned. Make sure both versions start at the same entry and use the same sequence. If the project has string IDs or a spreadsheet key column, use those to verify which lines correspond.
2. Check missing and extra entries first. Compare the number of items and inspect the area around the first mismatch. Fixing one inserted or deleted line may make many later comparisons meaningful again.
3. Review placeholders and tags carefully. Match each variable, escape sequence, and required markup against the product's reference. Do not change code-like text just to make the two lines look more alike.
4. Check language-specific formatting. Review punctuation, spacing, capitalization, quotation marks, and date or number formats against the locale guide. Languages do not all use the same conventions, so a difference from the source language is not automatically an error.
5. Ask a reviewer to verify uncertain wording. Send the changed line with enough context to understand where it appears. A short button label may need a different translation from the same term in a help article.
6. Compare the corrected version again. Repeat the check after edits and save the final list with a clear version name. This catches accidental changes introduced while fixing earlier issues.

Make the comparison easier to trust

Use clean text, not a screenshot or a copied table with extra columns. Remove headings that appear in only one version, or include the same headings in both. If your source file has IDs, notes, or character limits, keep a separate copy of that information nearby rather than mixing it into the text being compared.

For a large list, review a manageable section at a time, such as one screen, feature, or message group. Smaller sections make it easier to spot where an alignment problem starts and reduce the chance of missing a short string among hundreds of changes.

Text comparison shows differences between characters and lines, not the quality of a translation. Check the localized wording in its interface context as well, especially when buttons, menus, and error messages have strict space limits.