Translate Product Manual Diagrams Without Breaking Callouts

A single untranslated arrow label can send a technician to the wrong part, while a translated callout that no longer fits can make a clear manual hard to use. Translating a product manual with diagrams takes more than replacing words: the text, its references, the artwork and the page layout all need to agree.

The key is to plan the graphics as part of the translation project, not as decoration added after the text is finished. Editable files make that work easier, but a PDF-only manual can still be assessed and handled with a careful workflow.

What product manual diagram translation involves¶

Product manual diagram translation is the process of translating text inside or around technical illustrations while preserving the relationship between each label and the part, control or action it describes. The text may sit in a vector layer, a callout box, a table, a legend or pixels in a flattened image.

A callout is a label connected to a point in an illustration, often with a leader line or arrow. The line might identify a fastener, switch, safety guard or component. If the translated label moves, wraps or gets paired with the wrong pointer, the drawing can still look polished while giving the reader incorrect guidance.

Manual graphics also carry information that isn’t written as ordinary prose. A number beside a part may refer to a parts list. A symbol may indicate a warning level. An arrow may show direction or sequence. The translator and layout specialist need to preserve those relationships, not simply produce a fluent translation.

A useful project scope therefore treats the manual as a set of connected assets:

• Running text, headings, tables and warnings.
• Diagram labels, legends, keys and callouts.
• Figure numbers and cross-references in the prose.
• Captions and notes below illustrations.
• Source artwork and its editable text layers.
• Exported pages that show how the final manual will appear.

The project can be split across translators, engineers and desktop-publishing specialists, but the handoffs need to be explicit. A translator should know whether a label is a part name, an instruction or a warning. A layout specialist should know which strings are approved and which references must not change.

For a broader overview of technical documentation work, see technical translation for manuals and product documentation. Teams working with process maps and editable diagrams may also find a workflow for translating Visio diagrams useful.

Graphics become especially difficult when their source files are missing. The ISTC checklist describes lost graphic source files and editable text inside graphics as major project challenges. It also notes that changing labels in bitmap images can cost more effort than editing vector artwork with accessible text layers. Read the ISTC translation-project checklist before deciding that a finished PDF is enough for a reliable quote.

What files to prepare before requesting a quote¶

The files you send shape the estimate, schedule and production method. A complete scope should include the approximate word count and the number and type of graphics, rather than describing the job only as “a manual.”

The ISTC checklist recommends supplying source files where possible. A PDF-only handoff gives the team less information about how the manual was built, and the editable file can expose older layout or authoring issues that affect the work. Read the checklist’s guidance on translation projects when assembling the package.

The table is a practical handoff checklist, not a certification checklist. If the source files are old or the software version is unknown, file analysis and spot checks may be needed to identify the authoring setup. The ISTC checklist specifically points to software and version identification as a possible issue with legacy manuals.

A clean project brief should answer a few additional questions in plain language:

• Which product model and manual revision does the package cover?
• Are all diagrams in scope, or only selected chapters?
• Should the translation keep the original figure numbering and callout sequence?
• Are translated labels expected in editable artwork, in a keyed table or in a separate text layer?
• Who will confirm technical terminology and the meaning of unclear labels?
• Who approves the final pages and their safety-related content?
• Does the destination market require particular instruction languages or document wording?

A concrete example: a company sends a PDF and asks for a quote on its installation manual. The PDF shows the pages, but doesn’t reveal whether each callout is editable, whether an illustration is a vector file or a flattened image, or whether the words are already embedded in the artwork. The team can make an initial assessment, but the estimate is less certain until the graphic sources are checked.

The most useful first step is to send the editable manual and graphics alongside the PDF, even if you aren’t sure which files the translator needs. The project team can then identify what is usable and flag missing or damaged assets before translation begins.

How to handle text inside diagrams¶

There isn’t one universal way to translate diagram text. The right method depends on whether the artwork is editable, how labels connect to the illustration and whether readers need to identify a part quickly.

Three workable patterns for text-heavy diagrams are to use numbers, letters or symbols with a key; move callouts into the margins; or put the text in a separate editable layer. The ISTC checklist PDF presents these as authoring approaches, not as a formal standard.

Editable text helps because a translator or designer can change the words without redrawing the entire picture. If a label is baked into a bitmap, changing it can mean covering the original text, matching the background, adding new type and checking that the result still looks natural. A vector file with accessible text may expose the wording directly for revision. The difference matters most when diagrams are numerous or likely to change.

As Maxwell Hoffmann explains in the ISTC checklist:

“The two biggest issues with graphics are: (a) ‘lost’ graphics source files and (b) editable text in graphics.”

The quote points to a planning problem, not just a translator’s problem: if the graphic source has disappeared, the team may have to recreate work that the original authoring files would have made editable. Before production starts, check that the source assets open and that their text layers can be selected.

Labels should be translated against a controlled vocabulary. A “guard” in one section shouldn’t quietly become a “cover” in a diagram if the product uses those terms differently. Glossaries help, but they don’t replace technical review: a term may vary with the component, figure or instruction.

How it works in ChatsControl: a translation brief can include the product domain, audience, tone and preferred terminology. The tool applies that context across its planning, translation and review stages. The brief can help keep repeated wording consistent in the document, but the workflow doesn’t replace editing labels in the original vector or CAD artwork. A human still needs to place, inspect and approve diagram text.

A typical ambiguity might be a short label such as “lock.” Without context, the word could refer to a locking action, a lock mechanism or a state shown in a drawing. A translator should ask for the source context or an engineer’s clarification rather than guess and propagate the wording through a parts key.

Use a stable reference system when drawings contain many labels. If the figure uses numbered markers and a translated key, check that each number still points to the same part and that the key hasn’t lost an entry. If the drawing uses direct labels, compare each translated label against the original and trace its leader line to the intended component.

Teams adapting diagrams in Visio can consult the Visio diagram translation workflow. The file format and editing method may differ, but the same basic requirement applies: preserve the connection between the words and the shapes they describe.

Why translated text breaks a layout¶

Translated text can take more or less space than its source. A short English label may become a longer phrase; a sentence can wrap onto extra lines; a caption can push an illustration onto another page. Those changes affect both readability and the alignment between callouts and the drawing.

The ISTC checklist reports that English translated into Dutch or German can often produce about 38% more line breaks, while English translated into Korean may show little expansion. The checklist presents that figure as a rule of thumb, not a guarantee for a particular manual or language pair. See the ISTC discussion of text expansion.

Text expansion doesn’t mean every translated string grows by the same amount. A part name may remain compact while an instruction expands. A warning that fits in a box in one language might need more lines in another. The layout should therefore be checked against the actual translated text, not against a single assumed percentage.

The problem can get worse in tables that contain both descriptive text and graphics. A table cell has to fit its wording and image within the same constrained area. The ISTC checklist recommends anticipating expansion and leaving at least 30% white space below a table when it has to fit on a translated page. That is the checklist author’s recommendation, not a universal standard.

Layout flexibility is usually safer than squeezing. The ISTC checklist warns that shrinking type, condensing fonts, tightening kerning or reducing line spacing to force expanded text onto a fixed page can impair readability. If the source file allows room for translated text, the layout specialist can adjust a caption or callout without making the manual harder to read.

Common constraints include:

• Callout boxes sized for short source labels.
• Leader lines that cross after labels move.
• Tables with little spare space beneath a row.
• Captions that sit too close to the illustration.
• Page breaks tied to manual line breaks.
• Text boxes placed too close to page edges.
• Warnings whose emphasis depends on a fixed visual hierarchy.

The source document can contain less visible layout traps too. The ISTC checklist flags manual page breaks, manual line breaks, hard spaces and hidden word-level formatting overrides as possible trouble spots in non-structured files. Those features may make the source look stable while making changes harder to control.

Before layout work starts, ask whether the source is built with paragraph and character styles or with many local overrides. Styles make related formatting easier to manage. Manual formatting can behave unpredictably when text changes, especially in a long document with tables and repeated warning blocks.

ChatsControl can help with one part of this problem: the document text. When a DOCX or text-based PDF is uploaded, the app returns a translated Word file with document formatting such as tables, headings, lists and layout kept in place. That doesn’t translate text embedded in artwork as a substitute for graphic editing, and the result still needs human review. The ChatsControl translator is one option for preparing a document draft when keeping the surrounding Word layout matters.

For scanned manuals, the product workflow first reads the page and rebuilds it as a formatted Word document. The output can help with text that would otherwise be difficult to extract, but handwriting and very degraded scans are read unreliably. A reconstructed Word file also doesn’t remove the need to check diagram labels against the original artwork.

Three ways to commission the work¶

Teams usually choose among a specialist language-services provider, a freelance translator with technical-documentation experience, or a document-translation tool used as part of a review workflow. The right option depends on the file condition, the complexity of the graphics and who will take responsibility for technical and layout checks.

Ask each provider to describe the deliverable rather than quote only a per-word translation. Will the supplier return a translated manual, edited illustrations, a bilingual review file, a proof PDF or all of those? Who handles text embedded in raster images? Who resolves inconsistent component names? Who signs off on safety-related meaning?

A bureau may coordinate several specialists, but the word “bureau” doesn’t automatically mean the quote includes graphics work. Request a clear breakdown for translation, artwork adaptation, desktop publishing, review and final file delivery. If a provider doesn’t handle a particular file type, agree who will take it on before the project begins.

A freelancer can be a good fit when your organization already has a technical reviewer and a person who can edit the layout. Give the translator a contact who can answer questions about components and procedures. Don’t make the translator infer product function from a cropped label when an engineer can confirm it.

A tool can assist with editable document text while a human handles technical and visual decisions. How it works in ChatsControl: upload a DOCX or text-based PDF, receive a translated Word file, and use the bilingual view to compare source and translation. The side-by-side view can help a reviewer spot wording that needs attention. The tool doesn’t provide a full CAT or TMS workflow, doesn’t edit PowerPoint or Excel, and doesn’t replace a graphics specialist for embedded diagram text.

The price model may matter when the team is assessing a draft workflow. ChatsControl’s published pay-as-you-go rate is $1.50 per 1,000 characters, equivalent to $2.70 per 1,800-character page; scans use the same rate for recognized characters, with a minimum of 1,000 characters per page. The free tier provides 6,000 characters at sign-up, with the remaining balance topped up to 1,000 each month rather than added to a larger remainder. Those are tool prices, not a complete quote for technical review, diagram adaptation or engineering approval.

Don’t compare options by speed or price alone if the graphic files need extensive work. A low translation-only quote may leave artwork editing, proofing and technical questions outside the scope. Request a quote based on the full manual package, including graphics and target languages.

A step-by-step workflow from files to approved manual¶

A predictable workflow gives translators and technical reviewers a shared way to track labels, questions and revisions. Each step should end with a checkable output, not simply a handoff email.

1. Inventory the manual and artwork. List the editable manual files, reference PDFs, figures, graphic source files, glossary and target languages. Note which graphics appear to contain editable text and which appear flattened. Record the manual revision and product model so reviewers don’t mix versions.

2. Define the translation and layout scope. Agree whether the project includes body text, labels, captions, tables, warnings and updated artwork. Confirm the expected deliverables and file formats. Identify who can edit each asset and who approves technical meaning.

3. Build the terminology and query list. Gather approved product names, component names, control labels and warning wording. Mark ambiguous labels for questions to the engineering contact. A brief with no terminology guidance leaves more room for inconsistent choices.

4. Translate the manual and graphics as connected content. Keep each callout tied to its figure and reference. If the design uses a key, ensure the translated key keeps the source identifiers. If artwork text is on a separate editable layer, preserve that structure for later updates.

5. Adapt the layout using the actual translated text. Check callout space, line breaks, table fit, captions and page flow. Don’t force every page to match the source by making text smaller or more condensed. Adjust the layout while preserving legibility and the connection between labels and diagram features.

6. Review meaning, references and completeness. Compare every source label with the target version. Confirm that no label, symbol key or caption disappeared. Check part references, warning levels and cross-references in the prose against the drawing.

7. Proof the exported pages. Review the final PDF or other agreed output at page level. Look for clipped text, overlapping leaders, hidden layers, unreadable type and labels that point to the wrong component. Check the exported file, not only the editable source.

8. Approve and archive the deliverables. Record the approved manual revision and retain the final editable files, reference output and terminology decisions according to your organization’s process. A future update is easier when the translated label layer and source artwork remain available.

A practical handoff should make ownership visible. For example, the translator can flag an ambiguous label, the engineer can confirm what it names, and the layout specialist can place the approved wording. If nobody owns the engineering response, the question can remain unresolved until the proof stage, when correcting it may involve both text and artwork.

A built-in document check can support review without taking over that responsibility. ChatsControl’s separate QA validator checks translation issues such as numbers, names, terminology and omissions. A reviewer can use the check as an additional pass, then compare the flagged source and target wording with the product context. Automated checks can point to a problem; they can’t decide what a physical component is called in your product documentation.

The final proof is a distinct quality gate. A correct translation can still appear incorrectly after a text box moves or a font changes. Conversely, an attractive page can contain a wrong callout reference. Review both the language and the image-text connection before approval.

For teams building a broader post-editing process, the MTPE workflow for technical manuals explains how translation, review and quality checks fit together. Scanned or photographed source documents may need a separate assessment; the guide to translating scanned documents with OCR covers the limits of recognition and layout reconstruction.

Pitfalls that cause rework¶

The expensive mistakes often begin before translation: a missing source file, an unclear scope or a label that has no context. A few specific checks can prevent avoidable layout and review cycles.

Treating a PDF as though it reveals the production file. A PDF shows how pages look, but it may not expose the original text layers, authoring structure or graphic source. Ask for editable files and let the project team inspect them. The ISTC checklist says source files can help estimation and reveal legacy layout issues. Read the ISTC checklist on source files and graphics before setting a fixed scope based only on PDF pages.

Translating labels without their image context. A list of strings taken from a diagram may contain short terms with several possible meanings. Give the translator a full-resolution image, figure number and surrounding instruction. Ask an engineer to clarify any term that can’t be resolved from the material.

Changing a label without changing its key or reference. A number or symbol can be reused across a drawing, a parts list and a paragraph. Treat the label and its references as one content unit. A completeness check should compare the graphic, its key and the related text, rather than review each asset in isolation.

Leaving artwork edits until after approval. A translated label may require additional space or a different line break. If the project team only checks the text document, the final illustration can still contain the source language or an outdated term. Include graphic proofing in the deliverables.

Solving overflow by making text hard to read. Reducing type size, tightening spacing or condensing fonts can hide the symptom while making instructions less legible. The ISTC checklist warns against those fixes and encourages flexible source layouts. Create space or revise the layout instead of treating the source page as an unchangeable template.

Assuming every graphic is editable because it looks sharp. A high-resolution image can still have its text flattened into pixels. Confirm that graphic text can be selected in the source file. If labels are not editable, agree how they will be replaced and who will check the rebuilt image.

As Maxwell Hoffmann writes in the ISTC checklist:

“It is much more expensive to alter call-outs and labels in bitmapped graphics vs. vector files that have accessible text layers.”

The cost mechanism is straightforward: a bitmap stores the label as part of the image, so changing the wording can require image editing and visual reconstruction. Accessible vector text can often be edited more directly. The actual work still depends on the source file and the complexity of the artwork.

Assuming one expansion estimate fits every language. The ISTC’s about-38% figure describes a rule of thumb for some English-to-Dutch or English-to-German line breaks, not a guaranteed increase for every sentence or manual. Use the translated text to check the actual layout. Don’t use an average as permission to shrink labels or skip proofing.

Skipping the final export review. An editable file can contain hidden text, missing fonts or a layer that doesn’t appear in the exported PDF. Inspect the delivered output page by page. Check that every label is readable and points to the intended part.

EU machinery instructions and language planning¶

Language requirements depend on the product, market and applicable legal framework. A translation team can support documentation work, but your manufacturer or compliance lead must confirm which rules apply to the product and destination.

For machinery currently covered by Directive 2006/42/EC, instructions must accompany the machinery in the official language or languages of the Member State where it is placed on the market or put into service. The directive distinguishes “Original instructions” from a “Translation of the original instructions”; a translation must be accompanied by the original instructions. See Directive 2006/42/EC, Annex I, section 1.7.4.

Under Annex I, section 1.7.4.1, language versions verified by the manufacturer or its authorised representative carry the words “Original instructions.” Translations carry the words “Translation of the original instructions.” Confirm the applicable wording and destination-market requirements with the responsible compliance contact using the Machinery Directive text.

The directive also makes a limited exception for maintenance instructions intended for specialised personnel mandated by the manufacturer or authorised representative: those instructions may be supplied in one Community language that those personnel understand. The exception is narrow. Don’t assume that a service document qualifies without checking its audience and purpose against the directive’s instructions requirements.

Regulation (EU) 2023/1230 replaces Directive 2006/42/EC from 20 January 2027, according to the EUR-Lex summary of machinery safety requirements. Check the current consolidated regulation and relevant transitional provisions before relying on that date for a product launch.

Article 10(7) of Regulation (EU) 2023/1230 requires manufacturers to ensure machinery or related products are accompanied by instructions for use and specified information. The article also provides for digital instructions and requires a clear way to access them to be indicated on the product, packaging or an accompanying document. Digital instructions must be in a format that lets users print, download and save them for access, including during a breakdown. Read Article 10(7) of Regulation (EU) 2023/1230.

The article says digital instructions must remain accessible online during the product’s expected lifetime and for at least 10 years after the product is placed on the market. It also says a manufacturer must provide paper instructions free of charge within one month when a user requests them at purchase. Those provisions generally apply from 20 January 2027; check the regulation’s current text and applicable exceptions.

ISO 20607:2019 covers preparation of safety-related parts of machinery instruction handbooks, including safety content, structure and presentation across the machine lifecycle and communication of residual risks. The ISO page for ISO 20607:2019 describes the edition as adding specifications to general information-for-use requirements in ISO 12100:2010, clause 6.4.5. The ISO page has also surfaced a replacement draft, so check its catalogue and status before treating the edition as current.

A translation project can preserve the source’s labels and warnings, but it can’t decide which languages your product must carry or whether a digital manual satisfies the requirements for your product. Give the compliance lead the target-market list early, and make sure the same approved terminology appears in the manual text, diagram labels and any access information.

FAQ¶

How do you translate labels and callouts inside product manual diagrams?¶

Extract each label into an editable layer, keyed table or margin callout, then translate it in context with the figure and terminology list. Place the approved text in the artwork and check that each label still identifies the correct component.

Should diagram text be translated in the image or in a separate editable layer?¶

A separate editable layer is usually easier to update than text flattened into a bitmap. Numbered references with a translated key or margin callouts can also work when the illustration is crowded, as long as every reference remains consistent.

What files should I provide to translate a technical manual with diagrams?¶

Provide the editable manual file, graphic source files where available, reference PDF, glossary, product model and revision, and a list of target languages. The ISTC translation-project checklist recommends supplying source files where possible because PDF-only scoping can make estimation less certain.

How can I check translated diagrams for missing labels and layout problems?¶

Compare each source label with the translated artwork, verify figure references and terminology, then inspect the exported pages for clipping, overlap, legibility and missing layers. Review the drawing alongside its key and related instructions so that a correct label hasn’t been paired with the wrong reference.

What language requirements apply to translated machinery instructions in the EU?¶

Directive 2006/42/EC requires instructions for covered machinery in the official language or languages required where the machinery is placed on the market or put into service. Regulation (EU) 2023/1230 generally applies from 20 January 2027; confirm the product scope and transition provisions in the EUR-Lex summary and regulation text.

Can I translate a manual from a PDF if I don’t have the source files?¶

A PDF can be used for an initial assessment, but it doesn’t reveal every editable text layer or source graphic. Ask the project team to inspect the PDF and check whether the original authoring files can be recovered before agreeing on the artwork scope.

Does translation software edit labels inside CAD drawings?¶

Don’t assume that a document-translation tool edits CAD artwork. ChatsControl translates DOCX and PDF documents, but the translated labels in a separate CAD or vector source still need an appropriate editing workflow and human review. A document draft can support the text work; it doesn’t replace checking the drawing itself.