TeamAmaze / TeamAmaze/AmazeFileManager

Questions about Chinese translation

Open
#4,127 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Translation Issue-Discussion
Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

  1. I noticed that there are some problems in the translation of Simplified Chinese: some abbreviations of proper nouns are translated according to their full names in the translation.
    For example: "FTP" is translated according to its full name "File Transfer Protocol", and the translation result is 6 Chinese characters, which is not intuitive. However, the word "FTP" is used directly in the translation of Traditional Chinese (Hong Kong) without translation, which is more in line with the habits of Chinese users.
    In addition to "FTP", "MD5", "SHA256", "Root mode", "WiFi Direct" and other words also have such problems.

  2. In addition, some translations in Chinese (Hong Kong) and Chinese (Honduras) have problems with loose capitalization (md5 uses lowercase) and extra colons in some entries in the properties dialog box.

  3. I noticed that the translation file is automatically submitted by a "robot"?
    If I want to contribute the modified translation mentioned above, how do I do that? Fork the project, modify it, and then submit a pull request?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No translation files or tests are named. Start by identifying the generated translation-file workflow and the Simplified Chinese, Hong Kong, and Honduras resources; compare entries for FTP, MD5, SHA256, Root mode, WiFi Direct, capitalization, and dialog colons. Done means the affected translations are corrected and the accepted contribution path is clear.

Written by the indexing model from the issue text.

Assessment

Domain
localization
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.