# What Should Stay Unchanged When You Translate a PDF?

Identify code, formulas, trademarks, names, and identifiers before PDF translation, then use instructions and source checks to protect their meaning.

A translated manual should explain an action in the reader's language without changing the command they must type. The same distinction applies to product identifiers, formulas, and names: some text carries meaning by remaining exact.

Decide what should stay unchanged before submitting the PDF. A short, precise brief is easier to review than a general request to “preserve everything important.”

## Separate prose from exact-match information

Read a representative page and mark items whose characters matter independently of the surrounding sentence. These often include commands, file paths, URLs, email addresses, version strings, product models, and mathematical variables.

Then distinguish three treatments:

| Content                                        | Possible treatment         | Review question                                       |
| ---------------------------------------------- | -------------------------- | ----------------------------------------------------- |
| Explanatory paragraph                          | Translate normally         | Does it retain the original instruction or claim?     |
| Identifier or executable command               | Keep exact text            | Can the reader locate or use the same thing?          |
| Specialist term with an established equivalent | Use the chosen translation | Is it used consistently and appropriate to the field? |

A brand slogan is different from a brand name. A name may remain unchanged while a slogan needs translation for its audience. Decide based on the document's purpose rather than preserving every capitalized phrase automatically.

## Protect code and notation with context

In a code sample, changing quotation marks, indentation, a variable name, or a minus sign can alter behavior. Keep executable text separate from comments and surrounding explanation when reviewing it.

For formulas, record which variable names and symbols must remain intact. Translate explanatory sentences without changing indices, units, equation numbers, or the definition attached to a symbol. Do not assume a fluent translation validates the mathematics.

Names can also be ambiguous. An organization may have an official target-language name; a person's name may need a specific transliteration. Provide that established form if you have evidence for it, and avoid inventing a new localized name.

For safety-related documentation, the [technical-manual guide](https://pdfcraft.ai/en/blog/translate-technical-pdf-manual/) covers the relationship between exact identifiers and operational instructions.

## Write a brief the result can be checked against

Use the translation instructions field to describe the subject and give a few high-value preferences. For example:

> This is a software installation manual. Keep commands, file paths, API identifiers, and product model codes unchanged. Translate explanatory prose into clear English. Use “controller” for the hardware component described as X in the source.

This is an illustrative brief. Replace the example with terminology from your document, and do not include sensitive information that is unnecessary for processing it.

PDF Craft's instructions guide the translation; they are not an enforced glossary or a set of protected page regions. The current interface does not provide the selection boxes or separator-line controls described in some competing workflows. Do not treat an instruction as proof that a region will be skipped perfectly.

If you require mechanically locked strings or regulated terminology enforcement, evaluate a workflow that explicitly provides those controls and still verify the delivered file.

## Check preserved content after downloading

Compare several exact-match items with the original character by character. Search the result for a model number or distinctive command, then inspect each occurrence in context.

Check look-alike characters, straight versus typographic quotes, spaces inserted into URLs, and code lines wrapped in ways that obscure their meaning. Search cannot find an item that OCR misrecognized differently, so also examine a few source locations directly.

For a long document, keep a list of recurring names and terms and record the variants you find. Fix terminology in a working copy only after establishing which form is correct. Repeated wording is not always the same concept.

## Keep the original as the final reference

In [PDF Craft](https://pdfcraft.ai/en/pdf-craft/), upload the PDF, choose the output and target language, add your brief, and review the plan before starting. Download the completed result and compare it with the source. Current usage charges are on [Pricing](https://pdfcraft.ai/en/pricing/).

Preserved wording and preserved layout are separate checks. An unchanged command can still be clipped inside a narrow text box, while an intact logo may still have untranslated labels around it. Use the [PDF formatting checklist](https://pdfcraft.ai/en/blog/pdf-translation-preserve-layout/) to review those visual relationships.

Keep the source and exported translation separately from edited copies. That lets another reader verify whether a disputed string came from the original, recognition, translation, or a later correction.