top of page

Technical Document Translation: A Buyer's Guide for Hungarian Projects

Writer: Umar Usman
Umar Usman
Nov 8
9 min read

Technical manual beside industrial machinery

Technical document translation means moving manuals, specifications, datasheets and similar material into another language without changing a single measurement, warning or term. Do it well and you need three things: a translator who knows the subject, a controlled terminology set, and a review step before delivery. This guide covers how to set those up, with notes for English-Hungarian projects, where the language adds its own complications.



TL;DR

 

  • Technical translation covers anything where a wrong term or number has a cost: manuals, patents, safety sheets, software strings, specifications.

  • Choose the method by text type: full human translation for safety-critical or customer-facing content, post-editing for large, repetitive, well-structured volumes.

  • Accuracy comes from process: an agreed glossary, translation memory, source files that are clean, and an independent check of numbers and units.

  • Hungarian expands, reorders and inflects terms, so layout, UI space and glossary entries need planning before translation starts.

  • Our rates start at €0.05 per word into Hungarian and €0.07 per word into English, German or French.

 

Table of Contents

 

 

What counts as a technical document

 

A technical document explains how something is built, operated, maintained or certified. The reader acts on it, so errors turn into returns, downtime, injuries or rejected filings.

 

 

In engineering and manufacturing work, the requests we see most often fall into these groups:

 

Document type

Who reads it

What goes wrong if it is sloppy

User and operator manuals

End users, technicians

Misused equipment, support tickets, liability

Maintenance and service manuals

Field engineers

Wrong torque, wrong part, wrong procedure

Specifications and datasheets

Buyers, engineers

Failed tenders, mismatched components

Drawings and BOM annotations

Production, suppliers

Wrong part ordered or built

Safety data sheets and warnings

Workers, inspectors

Compliance failures, injuries

Software UI and help content

Users, admins

Truncated strings, inconsistent terms

Test reports and validation protocols

Quality, regulators

Rejected submissions

If your material is in the medical field, the rules differ again; our guides on clinical trial translation and medical record translation cover them. For chemical products, see our safety data sheet translation guide.

 

Choosing the method: human, machine or post-edited

 

There are three main routes: human translation, machine translation and machine-translation post-editing (MTPE). The same guide notes that human translation brings context and nuance but can be slower and costlier, while machine translation suits structured texts with defined terminology and MTPE can suit large localization projects.

 

In practice, we sort documents like this:

 

  • Full human translation: safety warnings, regulatory files, contracts attached to a product, marketing-adjacent product pages, anything where tone matters.

  • Full post-editing: large manuals with repetitive sentences, where a machine draft is corrected line by line to the same standard as human work. We offer this from €0.04 per word.

  • Light post-editing: internal or short-lived material that only needs to be understandable and correct, such as internal knowledge-base articles. We offer this from €0.03 per word.

 

The cheaper routes only pay off when the source text is written consistently. Short sentences, one term per concept and no idioms help every method. Our article on machine translation post-editing explains the levels, workflow and pricing in more detail.

 

Getting accuracy: a process, not a promise

 

Accuracy in technical translation is the result of agreed rules. The ASTM guide for quality assurance in translation, ASTM F2575, describes quality factors for each phase of a translation project and a framework for agreeing on project specifications. That is the right mindset: define the job before the first word is translated.

 

Settle the specification first

 

Before you send files, write down:

 

  1. The target audience: installers, operators, regulators or consumers.

  2. The target region and register. Documentation language and target region can differ, as IBM notes with the example of Spanish documentation for Spanish speakers in the United States.

  3. Whether units are converted or kept. Hungarian readers expect metric units, so US-origin documents often need both.

  4. Which terms must never change: product names, part numbers, interface labels, standard designations.

  5. The delivery format: Word, InDesign, XML, XLIFF or a CMS export.

 

Build the glossary early

 

A glossary prevents the classic failure, where the same component is called three different things on three pages. Large projects show why this matters. A 2015 MT Summit paper on high-volume technical manuals reports that pre-translating frequent terms and sentences, sharing reference translations, and automated proofreading improved productivity while keeping quality high. Twenty-two professional translators completed a 97,000-page manual project in 42 months. Terminology sharing and automated checks work as coordination tools when many people touch one body of text.

 

On a project handled by one translator, the glossary does a different job: it makes the work repeatable when the next manual or the next revision arrives. We cover the method in our terminology management guide.


Build the glossary early

Use translation memory and keep sources tidy

 

Translation memory stores approved sentences so that repeated and revised text is not paid for or translated twice. Microsoft’s globalization guidance says CAT tools such as translation memories help keep localized documentation in sync, and tracking changes helps avoid unnecessary localization costs. The same page recommends structured authoring, such as consistent Word styles or markup like Markdown and DITA XML, because structured content can reduce localization costs.

 

For you, that means: use styles instead of manual formatting, keep editable source files, and send a change list when you update a manual rather than a fresh file with no history.

 

Check what a spellchecker cannot

 

The final pass for a technical text is not about style. It checks that every number, unit, tolerance, cross-reference, figure callout and part number matches the source. We run automated quality checks inside the CAT tool, then read the text against the source for sense. Where a project needs an independent second reviewer, for example for regulatory filings, tell us at the start so the schedule includes it.

 

Hungarian-specific points for manuals and engineering documents

 

Hungarian is not a language where you can translate word for word and fit the result into the same layout. Plan for these points.


Six Hungarian manual localization considerations

Text length. Hungarian is agglutinative: meaning that English prepositions and possessives become suffixes on words, and compound terms grow long. Interface labels, table headers and callouts in drawings often need extra space. Build flexible layouts, or tell us the character limits for each string.

 

Inflection and software strings. A term inserted into a sentence template, such as “Delete {item}”, cannot always be correct in Hungarian, because the suffix depends on the word. Concatenated strings are a known localization problem. Give translators the full sentences and context, and avoid building messages from fragments.

 

Terminology choices. Many engineering terms exist in both a Hungarian form and an English loanword that practitioners actually use. The right choice depends on the industry and the audience. A glossary approved by your Hungarian engineers or distributor is worth more than any rule of thumb.

 

Formal address. Manuals in Hungarian typically use a consistent, polite register. Agree it at the start so that warnings, instructions and UI text read as one voice.

 

Regulatory expectations. If your equipment is placed on the EU market, Hungarian-language instructions may be expected. The EU Machinery Regulation, which replaces Directive 2006/42/EC, says documentation such as instructions for use must be available in a language easily understood by users, as determined by the Member State concerned. Check the current requirements for your product category with your compliance advisor or the relevant Hungarian authority.

 

US documents. In the United States, an OSHA-covered safety data sheet must be in English, but translations for worker comprehension are allowed, according to a summary of the Hazard Communication Standard. If you employ Hungarian-speaking staff, a translated version sits alongside the English original.

 

What affects price and turnaround

 

Per-word pricing is the norm for text. These factors move the final quote:

 

  • Direction. Our rates start at €0.05 per word for translation into Hungarian and €0.07 per word for translation into English, German or French.

  • Method. Full post-editing starts at €0.04 per word and light post-editing at €0.03 per word.

  • Repetition. Repeated and similar sentences matched by translation memory can be discounted by agreement.

  • File condition. Scanned PDFs, text in images and broken layouts take longer than editable files. Typesetting and drawing text may be quoted separately.

  • Subject difficulty. Dense specifications with unusual terminology take more research time.

  • Deadline. Urgent work needs scheduling priority. Our rush translation guide explains how we handle it.

 

The quoted “from” prices apply to standard text. Send the files and we give you an exact figure and delivery date before work begins.

 

Perspective

 

Most translation problems in technical documents start before the translator opens the file. The source has three names for one part, the layout leaves no room for longer text, or nobody has decided who approves terms.   That is why we work the way we do. One experienced translator handles your project from the first file to the last, so the terminology you approve in the first manual is the terminology you get in the tenth. There is no handoff between several people to introduce drift. We combine over 15 years of subject experience with current CAT tools and quality checks, which lets us take high-volume projects without trading away precision.   We also know technical work does not stop at 5 p.m. When an urgent document arrives, we are often reachable after regular hours, and we give realistic deadlines we can keep. Confidentiality is part of the job: drawings and specifications are handled as the sensitive material they are.   Bernadett

 

Preparing your files for a smooth handoff

 

A short checklist saves days on larger projects:

 

  1. Send editable sources. Word, InDesign, XML or XLIFF files beat PDFs. If your content lives in a localization platform, send an XLIFF file that comes back intact.

  2. Include reference material. Previous translations, approved glossaries, style notes and product photos help.

  3. Mark what stays in English. Brand names, part numbers and standard codes should be listed.

  4. Provide context for short strings. A single word like “Set” is a noun or a verb. Screenshots or string IDs settle it.

  5. Name the reviewer. If a Hungarian engineer or distributor will check the text, say so, so their comments feed back into the glossary.

  6. Tell us the confidentiality needs. For sensitive projects, see how we protect confidential documents.

 

Training and course material follows the same logic with extra attention to media. Our e-learning translation guide covers it.

 

Translate your technical documents with us

 

We translate technical, automotive, medical, legal, financial, software and game content between Hungarian and English, with German and French also available, and we post-edit machine translation at two levels. Rates start at €0.05 per word into Hungarian and €0.07 per word into English, German or French. Localization is quoted per project.


Wordsbyme

Send us your files and the target audience, and we reply with a quote and a realistic deadline. Start at wordsbyme.hu.

 

FAQ

 

What is an example of technical translation?

 

A user manual for industrial equipment, translated from English into Hungarian, is a typical case. Others include patents, safety data sheets, software strings and product specifications. What they share is that readers act on the content, so terminology and numbers must be exact.

 

Which method suits technical documentation best?

 

It depends on the content. Safety-critical and customer-facing texts suit full human translation. Large, repetitive and well-structured manuals can suit post-editing of a machine draft. We recommend the route after reviewing a sample of your source files.

 

How do I keep terminology consistent across many documents?

 

Agree a glossary before translation starts, keep it updated, and use translation memory so approved sentences are reused. Working with a single translator across the whole project also keeps decisions consistent. Share earlier translations so we can align with them.

 

Do I need Hungarian instructions for products sold in Hungary?

 

Often yes. EU rules leave the language of instructions to each Member State, so confirm the requirement for your product category with your compliance advisor or the Hungarian authority. We can translate the documents once the requirement is clear.

 

Can you handle files that are not plain text?

 

Yes, within the formats your project uses, including Word, XML and XLIFF. Tell us the format when you request a quote, and send editable sources where you can. Text inside images or scans may add time and cost.

 

Sources

 

Recommended

 

 
 
 

Comments


bottom of page