Skip to content
Interface language: English
Oriens / Signal

How to prepare a technical glossary for Japanese and Korean translation

Define each technical concept before choosing its Japanese or Korean equivalent. Review the meaning and test the terms in the finished material.

Article language: English

Fine white strands cross a wooden piece with gold-coloured teeth on a workbench.
In this article

If the same product component has three names in your offer, manual and drawing, the translator first has to reconstruct your technical knowledge. Then the reader faces the same puzzle. A glossary of agreed concepts helps establish meaning before translation into Japanese or Korean. The definition of the thing being discussed matters most. Adding a foreign-language equivalent alone is not enough.

A useful glossary brings together a product specialist, a translator and someone who checks usage in the target market. Each role answers a different question: what is it, what should it be called, and does that name suit the reader's situation? You can start the process in a spreadsheet, provided the team has a shared version and a clear procedure for approving changes.

Select concepts that affect understanding of the product

Do not begin by copying the whole catalogue. Collect terms that recur across materials and words whose misunderstanding could change how the product is used or what the offer covers. These include component names, operating modes, parameters, test conditions and user actions. Mark trade names and expressions describing service levels separately. Different groups may need different treatment.

Also check everyday words your company uses in a special sense. “Module”, “set” or “basic version” may mean different things to engineering and sales. If the inconsistency already exists in Polish, translation will not remove it. Assign someone responsibility for the definition and agree on its meaning for a specific product. Only then ask for an equivalent in the other language.

Prepare the glossary as part of a localization brief for Korea and Japan (in Polish). In the brief, also identify the intended readers: an operator, a purchasing engineer, a distributor or a marketing audience. The same concept may need a short explanation in an offer and a precise name in a manual. The difference is acceptable when it follows an agreed context rather than the accidental choices of successive authors.

Build a concept record, not a pair of words

Give each concept a stable identifier. Its name may change, but related materials should still point to the same thing. Add a plain-language definition and an example from actual product material. If a visual distinction is needed, refer to the correct versioned drawing or photograph. A translator should not have to guess which part the author meant.

Microsoft's guidance on terminology management highlights definitions, context, status and examples of use. It also recommends notifying stakeholders about term changes. You can use these principles to build a simple register of your own; its fields should reflect the company's materials. See Microsoft Learn: Manage terminology.

A practical record might contain:

  • A concept identifier and preferred source-language name.
  • A definition, scope of use and distinction from similar concepts.
  • A sentence fragment or drawing showing its use in the product.
  • A Japanese or Korean equivalent and the reason for choosing it.
  • Prohibited variants and names that are not translated.
  • The person approving the meaning and the person checking the language.
  • Status, version and a list of materials requiring a change.

Not every field needs a long entry. What matters is that someone outside the team can distinguish an approved concept from a proposal. A blank cell should not mean both “not yet reviewed” and “not applicable”. Use a few clearly defined states and direct disputed questions to a specific person instead of leaving them unresolved in comments.

Review technical meaning and language separately

The product specialist checks the definition against the actual solution. The translator proposes an equivalent and identifies ambiguities. A reviewer who knows the target language and industry context assesses whether the term will be understood as intended. One person may fill several roles, but the review result should state clearly what was assessed. A fluent sentence is not evidence of technical accuracy.

For ambiguous concepts, request a short comparison of possible alternatives. Rather than a contest for the most elegant word, you need to know what the reader will understand and what use they will associate with it. If the name cannot be chosen without more information, complete the definition. That takes less organizational effort than correcting several documents after they have been sent to partners.

Watch units, symbols and variant names. Keep a parameter tied to its particular measurement method or condition. For technical textiles presented to Korean readers (in Polish), also distinguish the fibre name, the form of the material and its function in the finished product; the translation must not turn one description into another. Do not add a local industry designation merely because it looks familiar. If the product must be assessed against a particular requirement, that calls for a separate assessment appropriate to the case. A glossary organizes communication; it does not grant compliance or approval.

Test terms in the finished material

After approving the glossary, test it on part of an offer, a manual and drawing captions. Choose materials where terms appear in different sentences. Also check a short heading, a parameter list and an interface label if the product has one. A name that works in a paragraph may be hard to read in a narrow column or need an explanation on first use. In localization for a Japanese game audience (in Polish), meaning can also depend on when a message appears and what the player is doing, so the test should cover its actual context of use.

Microsoft describes localization review in the context of the material's actual presentation, separately from linguistic correctness. In practice, look at the finished file or page rather than only the translation spreadsheet. See Microsoft's product localization guidance. This is especially useful for tables, charts and drawings, where layout affects how information is read.

Combine this test with a review of the B2B offer for Japan (in Polish). The reader should be able to connect the product name, variant and parameter with the next step in their assessment. If the translation is consistent but the offer still fails to explain its scope, the problem lies in the content. A glossary cannot replace missing information about what the company actually provides.

Aeneia conceptual photography

Hypothetical scenario: two meanings of the Polish word “wkład”

In this working example, a Polish company prepares equipment documentation for a partner in Korea. In its Polish materials, “wkład” refers both to a replaceable working component and to a part of the transport packaging. A list of word pairs could lead someone to use one equivalent in two different situations. The reader might confuse a product component with protective packaging.

The team creates two records with separate identifiers. An engineer defines the working component's function and adds a drawing. A logistics specialist describes the packaging component. The translator chooses equivalents, and a reviewer checks them in the unpacking and replacement instructions. The work therefore begins with the source content, before any discussion of translation style.

The company then reviews earlier files and marks those needing correction. It does not change names only in the latest folder while leaving an old manual in sales correspondence. In Poland-Asia localization (in Polish), consistency also covers answering questions and handing over materials. The new term must reach the people speaking with the reader.

Set rules for changes and glossary acceptance

Before handing over the glossary, specify who can propose new concepts and who approves them. Distinguish correcting a typo from changing a meaning. For a meaning change, check the documents using the term and set a time for updating them. If an earlier name still applies to an older product, retain information about that use rather than deleting the history.

Test acceptance through several tasks: finding a term by its source name, recognizing a prohibited variant, identifying the correct definition and reconstructing the latest change. Ask someone who did not create the glossary to perform them. If they need constant help from its author, improve the instructions or field names. The number of records matters less than being able to use them without an informal explanation.

Record questions received from the market too. If several people understand an expression differently, check the context and the version of the materials they received. Do not change the glossary because of one comment taken out of context. Use the principles for a conversation with a Japanese partner (in Polish) to confirm which concept is in question and what the reader is trying to do with it.

Use AI without losing control of meaning

An AI tool may help detect inconsistent names in materials approved for that use or propose a list of concepts for review. Treat its suggestions as candidates to check. A model can merge two different meanings or introduce a name that sounds technical but does not match the product. The designated people approve the final definition and equivalent.

Before using a tool, check the scope of data and access. Drawings, project names and variant information may need different rules from a public catalogue. A register of AI data flows (in Polish) can help. Do not send the entire documentation just to find a dozen recurring words if the task can be done with a smaller, prepared set.

Use agreed terms for searching in the local language (in Polish) as well. Record the context of the equivalents you find. A popular name in search results is not necessarily a term that fits the documentation for your particular product.

What to include in the handover package

At the end of the work, accept the glossary in a format the company can read and maintain. Include status instructions, a list of open questions and the names of the people responsible. If the provider uses a specialist tool, also agree how to export the glossary and retain identifiers. The company should be able to give approved concepts to the next translator without reconstructing them from finished PDFs.

Test an import or opening on your own equipment. Japanese and Korean characters, links between definitions and references to drawings matter. Make sure comments do not disappear during export and a proposed status does not become approved. A technically valid file can lose important information about where a term applies, so the absence of an error message does not complete acceptance.

Specify who maintains the glossary after the project. A new product variant may require further definitions, while a removed component remains in documentation for older devices. The register should preserve that history. During the first update, test the whole workflow briefly: submission, definition, equivalent, review and a change to the material. Only then will you know whether the glossary is a working tool rather than a one-off attachment to an invoice.

You can present a task combining product knowledge with Japanese or Korean materials to the Aeneia Oriens team.

Aeneia Oriens

Prepare several documents and the concepts that raise the most questions on both sides of the collaboration. We can discuss the scope of language support and checks on meaning in product materials.

Organize terminology for materials for Japan and Korea

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear