The hard part of software translation is not the English but the context: one word may need three renderings in a button, an error message and a document, and variables must never be touched. Etrans builds glossaries per module and delivers resource files ready to merge.
Developer documentation and product interfaces from Microsoft, Google, Atlassian, SAP and Adobe are treated as writing references across the industry: stable terminology, short sentences, and one name for one action everywhere. Product localisation has to rebuild that consistency in the target language.
Engineering adds another layer: placeholders, plural forms, string length, date and number formats are controlled by code. We audit the resource file before translating, flag non-translatable fields and length caps, then run a variable integrity check before delivery.
Note: Etrans regularly handles document translation projects involving the international brands named above and is familiar with their terminology and layout conventions. Brand names describe document types and project context; they do not imply endorsement or authorisation by the brand owner.
Words such as Save, Apply and Run shift between noun, verb and state. We ask for screenshots or module notes and annotate by screen position where needed.
Placeholders, escape sequences, plural branches and HTML tags are non-translatable. We compare count and order against the source before delivery.
A renamed button with a help article still using the old word is a common complaint source. We maintain the glossary by release and rescan older documents on updates.
Two representative assignments from completed work in this field, with the scale, language direction and deliverables involved, so you can compare them with your own files.
Console, notification templates and help centre delivered together, with many placeholders and plural branches mapped to front-end resource files.
Endpoint descriptions, parameter tables, error codes and code comments must share one terminology set, with code blocks left untouched.
Note: These are representative assignments drawn from completed work. Volumes, language directions and turnaround are given at project level; some file details and contact information are withheld under confidentiality undertakings.
A short sample of terms that often need a fixed rendering in this field. Project glossaries are agreed with the client before bulk translation.
| Source term | Common Chinese rendering |
|---|---|
| placeholder | 占位符 / 变量 |
| deprecated | 已弃用 |
| rollback | 回滚 |
| rate limit | 速率限制 |
| single sign-on | 单点登录 |
| release notes | 版本说明 |
Send the source files, target languages, intended use and deadline. Screenshots or reference materials help where context is thin.
A clear price and turnaround within 30 minutes. Core terms and proper nouns are agreed before bulk translation begins.
A subject-matter linguist translates, an editor checks terminology, and a final reviewer checks figures, tags and formatting.
Files are delivered in the required format and layout, with a glossary and free revisions until the agreed quality is met.
Each topic page lists the materials we handle, the terminology pitfalls, project cases we have delivered and frequently asked questions. Select the field closest to your documents.
Etrans, your Shenzhen translation company · 70+ languages · NDAs and rush service available
Request a Quote Call Us