Skip to content

Chinese correction : Adjust tone and accuracy of “CHEATER!” localization#884

Open
qyjoy wants to merge 1 commit into
CnCNet:developfrom
qyjoy:ChinesCorrection2
Open

Chinese correction : Adjust tone and accuracy of “CHEATER!” localization#884
qyjoy wants to merge 1 commit into
CnCNet:developfrom
qyjoy:ChinesCorrection2

Conversation

@qyjoy
Copy link
Copy Markdown
Contributor

@qyjoy qyjoy commented Apr 19, 2026

Adjust tone and accuracy of “CHEATER!” localization

This PR updates the Chinese translation of the CHEATER! warning to better match the tone, intent, and style of the original English string.

Change

Before

我超!你是挂逼!

After

挂逼!


Reasons

1. Align tone with the original English

The original string is simply:

CHEATER!

It is a short, direct system warning.
The previous translation added an emotional exclamation (“我超!”), which does not exist in the source text and changes the tone from a neutral system warning into a slang-heavy emotional reaction.

2. Avoid slang and profanity in system UI

  • “我超” carries strong slang / mild profanity connotations in modern Chinese internet culture.
  • System warnings should remain neutral, professional, and consistent with other UI messages.
  • Removing it keeps the translation closer to standard software localization practices.

3. Improve localization consistency

Across the project, system warnings and dialogs generally avoid casual internet slang.
This change helps keep the UI tone consistent and professional.

4. Accuracy and fidelity to source text

The previous version added meaning that is not present in the English original.
This PR restores a closer semantic match to the source string.


Additional note

The previous translation felt overly casual and slang-heavy compared to the rest of the localization.
This adjustment keeps the message concise, direct, and appropriate for a system warning.

No functional changes — localization only.

@MahBoiDeveloper
Copy link
Copy Markdown
Member

@SadPencil @DeathFishAtEase help with review, please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants