A drawing can keep every line, dimension, and symbol exactly where it belongs and still become unusable after translation: a longer label spills into a neighboring part, a block attribute stays in the source language, or a font turns a technical symbol into a blank square. Translating AutoCAD drawings means managing text and drawing structure together, not just swapping words.
For a team preparing DWG or DXF files for customers, suppliers, or production, the core question is practical: how can you translate the labels without disturbing the geometry or losing the link between each translation and its original object? A controlled workflow makes that link explicit, protects nonlinguistic data, and includes a visual check after the translated strings go back into the drawing.
What AutoCAD drawing translation involves¶
AutoCAD drawing translation is the localization of linguistic content in a CAD file while preserving the drawing’s structure and nonlinguistic data. The text may appear as single-line labels, multiline text, block attributes, tables, fields, or content linked through external references.
A DWG is not a simple document with text arranged in reading order. The file contains objects with different roles: some hold words, others hold geometry, coordinates, dimensions, or identifiers. A translation workflow has to distinguish those categories before any text leaves the drawing.
DXF makes that distinction visible through group codes, which identify whether a value is a string, a number, a coordinate, or another data type. Autodesk’s AutoCAD 2020 DXF reference explains why a translation exchange must isolate strings rather than treat every value as editable prose.
A stable handoff also needs to connect each source label to the right destination object. A CADTutor participant describes exporting the text together with its entity handle, then requiring the translator not to alter the handles. An entity handle is an object’s identifier in the drawing; it functions like a key that points a returned translation back to its source object.
As one CADTutor participant explains:
“Alternatively you need to extract the text and its handle from the whole drawing and send this to your translators with the requirement that none of the handles are touched”
The practical lesson is straightforward: preserve the identifier column, translate only the intended text, and verify that the return file still maps each string to the right object.
Translation scope matters, too. A drawing may contain repeated standard labels alongside custom instructions, product names, part numbers, or text that must remain unchanged. Before extraction, agree on what gets translated, what stays as written, and which terminology the target audience expects. That decision prevents a linguist from changing an identifier that looks like a word or leaving a meaningful instruction untouched.
Teams handling technical manuals alongside drawings may also need a shared terminology process. The article on technical translation for manuals and product documentation covers how related technical content can inform terminology choices across file types.
Choose a method that fits the drawing and the work¶
The best method depends on the type of content, the drawing volume, and how much control you need over context. AutoCAD’s built-in search, AutoCAD Mechanical’s dictionary-based functions, a structured text export, and a document-translation tool solve different parts of the problem.
| Method | Useful for | Main limitation |
|---|---|---|
| AutoCAD FIND | Locating or replacing repeated text content | It does not provide a complete translation exchange or change character properties |
| AutoCAD Mechanical Translator | Dictionary-based in-drawing and batch translation | Custom phrases may not have a dictionary match |
| Text export with object handles | Review by a translator or localization team | Requires a controlled export and reinsertion process |
| Document-translation tool | Translating supported document formats while preserving their layout | A document tool is not a CAD editor and cannot replace a DWG-specific extraction and reinsertion workflow |
AutoCAD’s FIND command searches and replaces text by its content. Autodesk says the replacement does not change character formatting or text properties, so FIND can help with straightforward repeated replacements but does not turn a drawing into a reviewable translation package. Its wildcard options can locate patterns such as any string, a single character, a digit, or an alphabetic character, but pattern matching does not explain what a label means in context. See AutoCAD 2026 Help on finding and replacing text.
AutoCAD Mechanical offers another route. Its documentation describes an in-drawing translation dialog and the batch command AMLANGCONV for translating quantities of text strings. Batch mode can search additional multilingual dictionary files in sequence and creates a log for each drawing, including counts of found and translated strings and strings that could not be translated. The AutoCAD Mechanical 2026 batch translation documentation describes those functions.
A dictionary match is not the same as a human decision. Autodesk’s AutoCAD Mechanical 2025 Translator documentation says the Translator compares drawing phrases with multilingual dictionaries and proposes matching text. User-entered phrases may have no dictionary match, so custom instructions and project-specific terminology still need review.
The Translator documentation lists support for text, attribute values, multiline text, parts references, and parts lists, with available languages depending on the installed product and version. Confirm the functions and languages in the target installation rather than assuming that a different Mechanical release behaves identically.
For drawings with custom wording, structured extraction usually gives the translator more context than a blind replacement. An export can include the source string, handle, object type, and a note about where the label appears. That context helps distinguish a command label from a part name or a warning, while preserving the identifier needed for reinsertion.
A language team working on technical files can also use the MTPE workflow and quality process guide to plan review roles and terminology checks. That guidance applies to the text work; the CAD-specific file exchange still needs its own safeguards.
Prepare the drawing and the translation handoff¶
A clean handoff starts before the first string is translated. The project owner should identify the authoritative source file, clarify what the translator may edit, and decide how the translated strings will return to their corresponding objects.
Use this checklist as a practical handoff sheet:
| Check | What to record |
|---|---|
| Source files | Identify the editable DWG or DXF and the version that should be treated as authoritative |
| Translation scope | Mark which labels, notes, attributes, and tables are in scope |
| Protected content | List identifiers, dimensions, coordinates, symbols, and wording that must not change |
| Object mapping | Include a stable handle or another verified key for each extracted string |
| Context | Add object type, nearby label, sheet or view context, and any relevant usage note |
| Terminology | Supply approved equivalents for repeated technical terms and product names |
| Fonts | Name the target font requirements and ask the recipient to test the file in the target environment |
| Return checks | Specify who will reinsert the text and who will approve the visual result |
The checklist is deliberately about the exchange, not a universal export command. The dossier does not establish one standard AutoCAD-to-Excel process that works for every version, object type, or configuration. A CAD specialist should choose the extraction method, then confirm that it captures the required objects and leaves protected data untouched.
If the project uses Excel for translation review, treat the file as a structured table, not as a free-form document. Keep the source text and object key in separate columns. Lock or clearly mark the key column, and ask the linguist to return the same rows without changing their order or identifiers. A translated string without its mapping key may be accurate but impossible to put back reliably.
A practical sample row might include a handle, an object type, a source string, a context note, and a target string. The exact data fields depend on the extraction method. The point is to keep the relationship between the source object and its translation visible throughout the handoff.
Decide how to handle repeated strings before translation begins. Some repeated labels are exact matches and can share an approved translation; other strings look similar but have different meanings depending on the component or instruction. A glossary should record the preferred term and enough context to prevent accidental reuse where it does not fit.
Keep the editable source. A CADTutor forum discussion describes a case where drawings had been converted into flat WMF images, leaving the text no longer selectable as editable CAD text. The participant’s report is not an Autodesk rule, but it illustrates a key workflow risk: an image may show the drawing while removing the text layer needed for controlled extraction and reinsertion. See the CADTutor discussion on translating drawings.
A scan or flattened image may still be useful as a visual reference, but it is not a substitute for an editable DWG or DXF when the task requires changing text objects. Ask for the source file before quoting or planning a round-trip. If the source is unavailable, clarify whether the job is translation of visible text for a separate deliverable or actual editing of the CAD drawing.
When a project has related labels in manuals, forms, or other files, keep terminology consistent across those materials. The guide to technical labels and EU product descriptions may help teams that need to align drawing terminology with product-facing documentation.
Run a controlled translation round-trip¶
A translation round-trip is the process of extracting text, translating it, reinserting it into the source objects, and checking the result in the drawing. Each stage should have a clear owner and a defined handoff so that text changes do not silently become geometry or data changes.
- Freeze the working source. Identify the authoritative drawing and retain an unchanged copy. Record the file name and revision in the handoff so that translations do not return to a different drawing by mistake.
- Inventory the text objects. Ask the CAD specialist to identify which object types contain in-scope text. Include the relevant tables, fields, external references, or Mechanical parts data rather than assuming that a search of visible labels found everything.
- Extract strings with mapping information. Export each string with a stable object handle or another verified identifier. Add context where a label could be interpreted in more than one way.
- Translate the text, not the data structure. Send the translation team only the linguistic content intended for translation, along with protected terminology and any instructions for preserving identifiers, symbols, and placeholders.
- Review the returned table. Check that the number of rows and mapping keys remain consistent with the handoff. Flag missing strings, altered keys, unresolved notes, and terms that do not match the agreed glossary.
- Reinsert into the corresponding objects. Have the CAD specialist apply the translated strings to their mapped objects, rather than pasting text into locations by visual guesswork.
- Inspect the drawing in context. Review the resulting labels for overlap, clipping, missing glyphs, incorrect symbols, and awkward line breaks. Compare the returned drawing with the source to confirm that nonlinguistic data has not changed.
The mapping key is what makes the process auditable. If a label is missing, the team can trace it to the extracted row and source object. If a translation appears in the wrong place, the handle helps pinpoint where the handoff failed.
AutoCAD FIND can support targeted search work within this flow, but it should not replace the extraction and review steps. Autodesk describes FIND as a text-content replacement feature, not a full translation round-trip. Its documentation also notes that Windows Search excludes text in tables, fields, and external references when that search method is used. Teams should inventory those content types separately rather than assume a single search captures every label. See Autodesk’s FIND documentation.
AutoCAD Mechanical’s batch option can help when a drawing has many dictionary-supported strings. The command’s log can show which strings were found, translated, or left unresolved, giving a reviewer a concrete list to inspect. That log does not prove that a proposed translation is technically correct; it records what the batch process did. A qualified reviewer still needs to resolve custom phrases and check terminology.
For a translation team that needs a readable review copy as well as the CAD text exchange, ChatsControl can translate supported DOCX or PDF files while keeping their document layout, and its bilingual view shows source and translated text together for review. That can help with a separate label list, glossary, or accompanying manual, but it does not edit a DWG or replace the CAD specialist’s extraction and reinsertion work. PowerPoint and Excel are not supported by the tool, so an Excel-based handoff needs a different workflow.
Check layout, symbols, and fonts after reinsertion¶
A translated label can be linguistically correct and still fail in the drawing. Longer wording may overlap nearby geometry or another label, and a missing font glyph may hide a character even though the text is stored in the file.
A CADTutor participant gives a blunt reminder about the final visual review:
“When you get the translated text back you need to insert the translated text back into the drawing and visually check there are no overlapping texts.”
That check is not cosmetic. A label that collides with a dimension or adjacent instruction can make the drawing hard to interpret. Review the drawing in the target language and at the intended viewing scale, then record any labels that need repositioning or a wording adjustment.
Treat any text shortening as a technical decision, not a translator’s guess. A shorter alternative may fit better but can change the instruction’s meaning. Ask the technical owner to approve abbreviations, line breaks, or revised placement before final delivery.
Special characters need their own check. AutoCAD’s AutoCAD 2025 reference for text symbols and special characters describes inserting special characters in MText through the editor’s Symbol menu or Unicode strings and control codes. A reviewer should compare technical symbols with the source rather than treating them as ordinary words to translate.
Font support depends on the target environment. AutoCAD’s 2026 Big Font SHX documentation explains that Asian Big Fonts support alphabets with thousands of non-ASCII characters and that a text style can specify a normal font and a Big Font together. The reference lists included SHX files for Japanese, Traditional Chinese, Simplified Chinese, and Korean scripts, but a team still needs to check that suitable glyphs are available in the target environment.
The STYLE command setting is worth checking when CJK characters display incorrectly. In the AutoCAD 2026 documentation, the normal font and Big Font are specified as a pair separated by a comma; specifying only one can remove an associated Big Font. A CAD specialist should inspect the style and open the delivered drawing in the environment where it will be used, rather than inferring font support from the text being stored.
DXF encoding adds another version-sensitive consideration. Autodesk’s AutoCAD 2020 DXF reference says UTF-8 is supported in AutoCAD 2007 DXF and later; earlier DXF formats use plain ASCII and CIF for string output, with Unicode characters represented by control-character sequences. A team converting between versions should test the actual file in the target software instead of assuming that a character will render because it was visible in the translator’s environment.
String capacity also depends on the DXF group code. The same AutoCAD 2020 reference documents a 255-character maximum for certain string group codes, with lower capacity for Unicode strings; group-code ranges 0-9 have a different documented limit of up to 2049 single-byte characters. Those limits are not interchangeable, so avoid applying one universal maximum to every text field.
Common failure points and how to catch them¶
Most avoidable problems come from treating a drawing as a flat list of words. The drawing’s text objects have different roles and locations, and the translation process can miss them or return them without reliable mapping.
A search misses text that lives in another content type. AutoCAD’s 2026 documentation says that Windows Search excludes text in tables, fields, and external references when using that search method. Inventory those types separately and confirm that the extraction method covers the actual drawing content. A search result is not proof that every label has been found.
A repeated phrase gets replaced without context. FIND supports wildcards, which can help locate repeated patterns, but a pattern cannot tell whether a phrase is a warning, a part name, or a command. Use the search to locate candidates, then review the phrase in context before applying a replacement.
A dictionary workflow leaves custom text unresolved. AutoCAD Mechanical documentation warns that user-entered phrases may not have dictionary matches. Review the batch log and route unmatched strings to a human translator instead of assuming they are already handled.
An identifier changes during translation. A translated string without its original mapping key can be difficult to return to the right object. Preserve the handle or verified key as a protected field, and check the returned table before reinsertion. The CADTutor discussion offers practitioner advice on retaining handles; treat it as a workflow recommendation, not an Autodesk requirement.
The source is no longer editable. A flat WMF image can show text without retaining selectable CAD text objects. The CADTutor thread reports this problem in a particular workflow. If the project requires text extraction and reinsertion, request an editable source file rather than expecting a flattened image to behave like a DWG.
The translated string does not fit. Text expansion can produce overlap or clipping even when the translation is accurate. The forum participant’s recommendation to inspect the returned drawing visually is a useful practical check, but the person responsible for approving technical meaning should also approve any layout-driven shortening.
The target font cannot display the characters. A drawing can contain the translated Unicode text while a missing or unsuitable font prevents correct display. Check the actual text style, including the normal-font and Big-Font pairing where relevant, and test the file in the recipient’s environment.
A separate document-translation tool can help with related materials, but it has limits. ChatsControl can process supported DOCX and PDF files, including scanned PDFs and image documents, and presents source and translation side by side for review. Its automatic checks cover items such as numbers, names, terminology, and omissions, but the product is a document-translation tool rather than a full CAD editor or CAD project-management system. Keep the CAD review and approval steps with the drawing team.
Regional and language considerations¶
The target language changes more than the words. It can affect character support, label length, special symbols, and which terminology the local technical team expects. These requirements should be part of the project brief, not left for the final export check.
AutoCAD Mechanical’s documented Translator supports several languages, but the available set depends on the installed product and version. The AutoCAD Mechanical 2025 Translator reference lists English, French, German, Japanese, Korean, Polish, Russian, Spanish, and other languages. Confirm the options in the installed version before promising a dictionary-based workflow for a specific language pair.
Scripts that use many non-ASCII characters need a font check, not just a language check. AutoCAD’s Big Font documentation describes special shape definitions for alphabets with thousands of non-ASCII characters and lists included SHX files for Japanese, Traditional Chinese, Simplified Chinese, and Korean. The recipient’s installed fonts and styles still determine whether the drawing displays as intended.
DXF version also matters when the target text includes Unicode. AutoCAD’s 2020 reference states that UTF-8 support applies to AutoCAD 2007 DXF and later, while earlier formats handle string output differently. Record the expected file version in the handoff and test a representative file before translating a large set.
Regional terminology is a separate issue from encoding. A product term that is technically correct in one market may not be the wording used by the local engineering team. Ask the client or technical owner for approved terms, and keep product names, model codes, and controlled identifiers as protected content unless the project brief explicitly says otherwise.
Compare delivery options and set acceptance criteria¶
The right delivery setup depends on who can access the CAD file, how much text needs translation, and whether the team needs a human review stage. A CAD specialist may handle extraction and reinsertion while a translator handles the linguistic work; a Mechanical dictionary workflow may cover standard strings; a document tool may help with associated manuals or a review list.
| Option | What it handles | What the team still needs to do |
|---|---|---|
| CAD specialist plus translator | Controlled export, contextual translation, and reinsertion into drawing objects | Define protected data, preserve mapping keys, and run visual and technical checks |
| AutoCAD Mechanical dictionary translation | Dictionary-supported strings and batch translation logs | Review unmatched phrases, verify terminology, and inspect the drawing |
| Document-translation tool for related files | Supported DOCX and PDF content, with layout preservation and bilingual review | Keep DWG extraction, reinsertion, and CAD-specific validation in the CAD workflow |
| FIND for repeated text changes | Search and replacement by text content | Confirm context and do not treat the command as a complete translation workflow |
Before work starts, agree on acceptance criteria in writing. A useful definition includes which objects are in scope, which values are protected, who approves terminology, who reinserts the strings, and who signs off on the visual result. If the file will be opened in a different AutoCAD environment, include a font and version check in that approval process.
The final delivery should include the translated drawing and a record of unresolved items. Unmatched dictionary strings, unclear source wording, missing glyphs, or labels that need layout changes should not disappear into the final file without an owner. A short issue list makes those decisions visible to the technical reviewer.
A reliable translation is not just a set of correct words. It is a traceable set of changes that stays attached to the correct objects, preserves nonlinguistic data, and remains legible in the target environment. That is the standard to use when comparing a manual process, Mechanical translation functions, and supporting document tools.
Before the file goes out, a second person should compare the translated drawing with the source and the issue list. The comparison should confirm that the intended labels changed, protected values stayed as supplied, and every unresolved item has a documented decision. The guide to translator skills and technical literacy discusses the review skills that help translators work with technical material, while the CAD owner remains responsible for approving the drawing itself.
FAQ¶
How do you translate text in an AutoCAD drawing without changing the geometry?¶
Extract linguistic strings separately from coordinates, dimensions, identifiers, and other nonlinguistic values. Preserve a stable object handle through translation and reinsertion, then compare the returned drawing with the source and inspect it for overlaps.
How can I extract AutoCAD labels to Excel and put them back?¶
Use a structured export that keeps each string beside a stable object identifier, translate only the text fields, and return the same identifiers unchanged. The available sources do not establish one universal Excel export command for every AutoCAD version and object type, so have a CAD specialist validate the chosen method.
Which AutoCAD text objects should be checked after translating a drawing?¶
Check single-line text, MText, block attributes, tables, fields, and external references, as well as parts references and parts lists when the drawing uses AutoCAD Mechanical. Autodesk’s 2025 Mechanical Translator documentation names several of those object types, while AutoCAD’s 2026 FIND documentation warns that tables, fields, and external references can be excluded from Windows Search.
How do I prevent missing characters and font problems in a multilingual DWG?¶
Check that the target environment has suitable glyphs and review the text style. AutoCAD’s 2026 Big Font documentation says a style can pair a normal font with a Big Font, so inspect both settings where the target script needs them and test the saved file in the recipient’s environment.
Can AutoCAD translate every custom label automatically?¶
No. AutoCAD Mechanical’s dictionary-based Translator proposes matches for phrases found in its multilingual dictionary files, but Autodesk warns that user-entered phrases may not have a dictionary match. Review its log and send unresolved custom wording for human translation and technical approval.
Will translating a DWG change its geometry?¶
A controlled text-only workflow aims to preserve geometry, but the translation exchange must keep coordinates and other nonlinguistic data out of the translated text fields. DXF group codes distinguish strings from coordinates and other values, so the return file still needs a source comparison and technical review.
Is AutoCAD FIND enough to translate a drawing?¶
FIND can search and replace text by content, including patterns using wildcards, but Autodesk says it does not change character formatting or text properties. The command does not provide the contextual review, object mapping, and visual validation needed for a complete drawing-translation workflow.
What should I do if the translated labels overlap?¶
Have the CAD specialist inspect the drawing after reinsertion and identify each collision or clipped label. The technical owner should approve any shortened wording or revised placement, because a layout adjustment must not change the instruction’s meaning.