In a technical ebook, a translated term matters because of the definition, formula, or procedure around it. Consistent spelling alone does not establish that the reader will understand the same concept.
Prepare a short subject brief and a few important terms before translating. Afterward, compare the definition and its later uses, not just the opening chapter.
State the field and the reader's level
A word can mean one thing in statistics and another in everyday speech. Identify the subject and audience: an introductory electronics text, an advanced economics book, or a programming manual for beginners.
A hypothetical brief might say:
This is an introductory statistics textbook. Use established statistical terminology and clear English. Keep variable names, code identifiers, and product names unchanged.
Do not paste a long generic request for expertise. Include preferences that change a decision and that you can check. The instruction guide and terminology preparation guide show how to keep that brief manageable.
PDF Craft's translation instructions guide wording. They are not a guarantee that every term or identifier will remain consistent, and they do not turn automated output into a certified technical service.
Track abbreviations and units with their definitions
List recurring abbreviations that would be confusing if expanded differently. Locate the first definition in the source, then check a later use in the result. Do not invent an expansion merely because the letters match a familiar phrase.
For quantities, compare the number, unit, prefix, and surrounding condition as one item. A correct number with a changed unit is still wrong. Check decimal separators, minus signs, percentages, and whether a value is an example or a requirement.
Avoid asking a translator to convert all units casually. Translation and unit conversion are distinct operations. If your project needs converted values, handle and verify that requirement explicitly rather than assuming it follows from a regional-language preference.
Read formulas and code explanations together
For a formula, compare symbols, subscripts, superscripts, and inequality direction. Then check the paragraph defining those symbols and the claim made from the formula. A correct expression with an incorrect interpretation can mislead just as easily as a transcription error.
For code, inspect identifiers and literal strings where they matter. Read the explanation against the example: does it describe the same parameter, input, return value, and error condition? Do not assume code remains executable merely because it is displayed in a code block.
For tables and diagrams, check references and captions. Retained images may still contain source-language lettering; keeping the artwork is not proof that embedded labels were translated.
Translate the complete EPUB and choose reviewability
Upload the usable file in the EPUB translator, select the target language, and choose translation-only or bilingual output. Add your concise brief and check current limits before submitting.
Bilingual output places each original passage before its translation, which helps with comparing definitions and unfamiliar wording. Translation-only is easier for uninterrupted reading. Keep the source available whichever mode you choose.
New users receive trial credits and translation is charged by usage. Consult Pricing for current rates, then download the result from the completed task.
Review key conclusions, not only terminology
Choose samples from different parts of the argument:
| Sample | Review question |
|---|---|
| A definition | Is the concept still distinguished from related terms? |
| A worked example | Do values, units, and steps correspond? |
| A limitation | Are assumptions, negatives, and uncertainty retained? |
| A conclusion | Does it claim the same result, with the same conditions? |
| A later application | Is the earlier definition used consistently? |
Check chapter navigation, notes, and tables as a separate structural pass. For a scanned source, recognition errors must also be considered; the formula and footnote checklist helps there.
For consequential technical decisions, verify the relevant passage against the original and obtain the review your project requires. A translated ebook can make a subject accessible, but it does not validate the book's claims or replace qualified judgment about how to use them.