![\"\"](\"https:\/\/www.yaraku.com\/wp-content\/uploads\/2026\/09\/image-edited-1024x423.png\")
<\/figure>\n\n\n\nWebsites contain many types of text besides body copy:<\/p>\n\n\n\n
- \n
- Page titles and headings<\/li>\n\n\n\n
- Buttons and menus<\/li>\n\n\n\n
- Graph axes and labels<\/li>\n\n\n\n
- Input instructions and error messages<\/li>\n\n\n\n
- Keys and tags that indicate the function of the source text<\/li>\n<\/ul>\n\n\n\n
With short strings like these, the intended use may not be clear from the source text alone. Microsoft\u2019s localization guidance<\/a> recommends providing contextual comments so translators can understand how strings, parameters, and other elements are intended to function.<\/p>\n\n\n\n
Google\u2019s guidance for global-ready content<\/a> likewise recommends clear and concise wording, short sentences, active voice, and consistent terminology to make source content easier to translate.<\/p>\n\n\n\n
Improving AI translation therefore requires more than entering the source text. You also need to explain where each string will appear and what it is intended to do.<\/p>\n\n\n\n
2. Five lessons from native review<\/strong><\/h2>\n\n\n\n
In the examples below, \u201cafter AI review\u201d refers to the stage where AI was used to review translation quality. \u201cAfter native review\u201d refers to the subsequent stage where a native Indonesian speaker checked and revised the translation. The AI review followed MQM<\/a> (Multidimensional Quality Metrics), an internationally used framework for evaluating translation quality.<\/p>\n\n\n\n
2-1. Choose between<\/strong> tidak<\/em><\/strong> and<\/strong> jangan<\/em><\/strong> based on sentence function<\/strong><\/h3>\n\n\n\n
The Indonesian words tidak<\/em> and jangan<\/em> can both correspond to negative expressions in Japanese, but they serve different functions:<\/p>\n\n\n\n
- \n
- tidak<\/em>: negates a state or fact<\/li>\n\n\n\n
- jangan<\/em>: tells someone not to do something<\/li>\n<\/ul>\n\n\n\n
The translation record contains the following example:<\/p>\n\n\n\n
Primary source (Japanese): \u30c7\u30fc\u30bf\u306f\u5b66\u7fd2\u306b\u4e00\u5207\u4f7f\u7528\u3055\u308c\u306a\u3044<\/em><\/p>\n\n\n\n
Supplementary source (English): Never use data for training<\/em><\/p>\n\n\n\n
After native review<\/em>: Data sama sekali tidak digunakan untuk pelatihan<\/em><\/p>\n\n\n\n
This copy describes a state or fact: the data is not used for training. It does not ask the user to avoid an action, so tidak is appropriate. The supplementary English source, however, can also be read as a prohibition. Because nuance can vary between languages, when working with files that contain multiple source languages, it is important to define the role of each one explicitly\u2014for example: \u201cUse Japanese as the primary source and English as a supplementary source when additional context is needed.\u201d<\/p>\n\n\n\n
By contrast, an instruction asking the user not to take an action would use jangan, as in Jangan terjemahkan segmen ini.<\/p>\n\n\n\n
When asking AI to translate a string, specify its function, such as \u201can operational instruction expressing a prohibition\u201d or \u201ca sentence describing a service specification.\u201d This context helps the AI choose the appropriate expression.<\/p>\n\n\n\n
2-2. A graph axis may represent a scale, not a quantity<\/strong><\/h3>\n\n\n\n
For one graph axis, the AI-reviewed version used Banyak\/Sedikit<\/em>, while the native-reviewed version used Tinggi\/Rendah<\/em>.<\/p>\n\n\n\n
Banyak\/Sedikit<\/em> describes a large or small quantity. Tinggi\/Rendah<\/em>, by contrast, indicates a high or low level on a scale.<\/p>\n\n\n\n
This graph represents levels of translation volume and editing time rather than simple item counts. The native reviewer therefore changed the labels to Tinggi\/Rendah<\/em>.<\/p>\n\n\n\n
When translating graph labels, also provide the graph title, what each axis represents, whether the values indicate quantities or levels, where the labels appear (a screenshot is also acceptable), and any character limits.<\/p>\n\n\n\n
2-3. Use extracted keys to explain the function of source text<\/strong><\/h3>\n\n\n\n
In this translation dataset, keys such as h2.section1_title are extracted alongside the source text. These keys are not text for the AI to translate. They provide information about how the source text functions on the website. In this dataset, h2 indicates the heading level, while section1_title indicates that the string is the title of the first section.<\/p>\n\n\n\n
When given only the source text, AI may not know whether a string is a heading, body copy, or button label. Defining the key as context helps the AI keep headings concise and choose wording appropriate for each type of content.<\/p>\n\n\n\n
Do not assume that the AI will understand a naming convention from the key alone. Define its meaning explicitly, for example: \u201ch2.section1_title indicates a second-level heading for the first section.\u201d<\/p>\n\n\n\n
2-4. Check that a heading fits its content, not only that it is concise<\/strong><\/h3>\n\n\n\n
The heading changed from the AI-reviewed Kurangi waktu perbaikan setelah penerjemahan secara signifikan<\/em> to the native-reviewed Waktu penyuntingan berkurang secara signifikan<\/em>.<\/p>\n\n\n\n
The first version functions more like a call to action: \u201cSignificantly reduce editing time after translation.\u201d The second describes a result: \u201cEditing time is significantly reduced.\u201d<\/p>\n\n\n\n
The appropriate choice depends on the body copy below the heading and the tone of the page as a whole. Translating a heading in isolation can make it unnecessarily long in another language or shift it away from its intended effect.<\/p>\n\n\n\n
Provide the heading together with the body copy immediately below it. Also identify whether it is a feature name, benefit statement, instruction, CTA, or tagline.<\/p>\n\n\n\n
2-5. Split long sentences at meaningful boundaries<\/strong><\/h3>\n\n\n\n
The following copy was divided into two sentences after native review:<\/p>\n\n\n\n
Semakin sering digunakan, sistem akan semakin belajar dari hasil penyuntingan Anda. Hasilnya, terjemahan akan semakin sesuai dengan kebutuhan perusahaan dan waktu pasca-penyuntingan dapat berkurang secara signifikan.<\/em><\/p>\n\n\n\n
The first sentence explains that the system learns from editing results. The second explains the outcome: translations can become better aligned with the company\u2019s needs, potentially reducing post-editing time.<\/p>\n\n\n\n
Where a sentence should be divided to make it easier to read and understand differs from language to language. It may be helpful to tell the AI in the prompt that it can split sentences at meaningful boundaries.<\/p>\n\n\n\n
3. Store the information you give AI in four places<\/strong><\/h2>\n\n\n\n
You do not need to put every detail into one long instruction. Organizing information by type makes it easier to reuse in future translations.<\/p>\n\n\n\n
- \n
- Glossary:<\/strong> Register approved translations for product names, feature names, technical terms, and other terminology that must remain consistent across the site.<\/li>\n\n\n\n
- Style guide:<\/strong> Document site-wide rules for formality, heading tone, numbers, symbols, and other writing conventions.<\/li>\n\n\n\n
- Translation Memory:<\/strong> Store approved translations of standard wording, recurring descriptions, and other reusable content. Because these translations are important data that reflect the website\u2019s style, they remain valuable even if the exact same text is unlikely to appear again.<\/li>\n\n\n\n
- Context for individual strings:<\/strong> Attach keys such as h2.section1_title, the screen where the string appears, its role, surrounding text, character limits, and the presence of variables or tags.<\/li>\n<\/ul>\n\n\n\n
A glossary alone cannot explain how a string functions on screen. You also need details such as \u201cthis string labels the graph\u2019s vertical axis,\u201d \u201cthis string is a button label,\u201d or \u201cthis key indicates an H2 heading.\u201d When the on-screen role is important, you can also provide the AI with a screenshot of the web page.<\/p>\n\n\n\n
4. Five steps to improve translation data<\/strong><\/h2>\n\n\n\n
![\"\"](\"https:\/\/www.yaraku.com\/wp-content\/uploads\/2026\/09\/\u7ffb\u8a33\u30b5\u30a4\u30af\u30eb-edited-1024x260.png\")
<\/figure>\n\n\n\n- \n
- Step 1: Organize the source text and context<\/strong>
Separate user-visible source text from keys, tags, variables, display locations, and other contextual information. Define what each item represents.<\/li>\n\n\n\n- Step 2: Define terminology and writing rules.<\/strong>
Register approved translations for product names, feature names, and technical terms in a glossary. Document rules for formality, heading tone, numbers, and symbols.<\/li>\n\n\n\n- Step 3: Give the source text and requirements to AI.<\/strong>
When using source text in multiple languages, specify which language is primary and which provides secondary context. Include the function and display conditions of each string.<\/li>\n\n\n\n- Step 4: Review translation quality and on-screen function.<\/strong>
Check for omissions, additions, terminology issues, accuracy, and fluency. Separately confirm that the translation fits its role as a heading, graph axis, button, or other UI element.<\/li>\n\n\n\n- Step 5: Reuse approved translations and revision rationale.<\/strong>
Record both the final translation and the reason for each change. Store the result in the appropriate glossary, style guide, Translation Memory, or string-specific context.<\/li>\n<\/ul>\n\n\n\nThis feedback loop reduces the need to reconsider the same decisions for every translation. Over time, it helps your company reuse previous decisions and maintain wording that reflects its brand identity.<\/p>\n\n\n\n
5. A 30-second context check<\/strong><\/h2>\n\n\n\n
Before you start translating with AI, check the following four points:<\/p>\n\n\n\n
- \n
- Does the source contain unregistered company-specific terms?<\/li>\n\n\n\n
- Does the style guide cover the source text\u2019s function?<\/li>\n\n\n\n
- Is the translation memory up to date?<\/li>\n\n\n\n
- Does the context support one clear interpretation?<\/li>\n<\/ul>\n\n\n\n
Completing all four checks increases the likelihood that the first translation will meet the required quality level.<\/p>\n\n\n\n
6. When AI translation should not be the final step<\/strong><\/h2>\n\n\n\n
Human review is especially important for contracts and content involving legal matters, privacy, or security; buttons and error messages where misunderstandings could cause operational mistakes; homepage and advertising copy that shapes brand perception; culturally sensitive expressions; and strings containing variables or tags.<\/p>\n\n\n\n
A quick translation may be sufficient for internal drafts used only to understand the general meaning. Decide the extent of human review based on the required quality and the associated risks.<\/p>\n\n\n\n
7. Reuse translation results with Yaraku Translate<\/strong><\/h2>\n\n\n\n
Yaraku Translate lets you compare results from multiple translation engines, customizable prompts, and an interface designed for human post-editing. You can also use Glossary and Phrases to standardize wording. See the Yaraku Translate product information<\/a> for current features and availability.<\/p>\n\n\n\n
The Company plan offers a 14-day free trial.<\/p>\n\n\n\n
If you want to organize source text, existing translations, native review results, and other materials into translation data that is easy to provide to AI, contact us about our Translation data building service. We will explain the available scope after you get in touch.<\/p>\n\n\n\n
\n\n\n
- Step 2: Define terminology and writing rules.<\/strong>
- Style guide:<\/strong> Document site-wide rules for formality, heading tone, numbers, symbols, and other writing conventions.<\/li>\n\n\n\n
- jangan<\/em>: tells someone not to do something<\/li>\n<\/ul>\n\n\n\n
- tidak<\/em>: negates a state or fact<\/li>\n\n\n\n