input Terminology

Avoid overly technical terms when possible and focus instead on what the player needs to do. Edit ruthlessly to clarify the core function or information. Often this may mean abandoning Chinese writing conventions (see [Glossary] and [Bad Examples] for more info) and prioritizing how the information typically appears in target language contexts.

Seek clarity whenever possible. If a function is unclear without context, contact the PM and ask what a function does, or what happens after players engage with it. Ask for visual aids whenever possible. The last thing we want our games to do is frustrate players with walls of text, unclear instructions, or misleading information. All of this could keep them from enjoying the game. When possible, use language that is friendly and emphasizes benefit and possibilities, rather than limitation and negative consequences.

For more detailed information and examples of specific UI language and interface conventions, please refer to the Microsoft Style Guide here. Below are some areas to pay particular attention to, as well as key places where NetEase deviates from Microsoft.

Acronyms and Jargon

Unlike Microsoft, NetEase uses acronyms and common gaming terms to maintain concise language fitting for games. However, translators should avoid overusing acronyms in full sentences or using lesser-known or overly niche terminology to keep language clear and accessible. See the [Glossary] section below for commonly-used acronyms and terms.