Calling for a script for standardization

Open
#1,082 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
localization

Research direction

Start by reviewing the glossary and the existing translation workflow to determine where standardized replacements could be applied. The issue does not name files, tests, or an entry point, so the implementation scope and validation method still need to be defined. Done would mean a community-maintained replacement tool based on the glossary, with a documented way to verify that translations are standardized without changing meaning.

Written by the indexing model from the issue text.

Description

各位好！

我們有很多統一的翻譯習慣和標準在glossary那裏。但是，由於不同翻譯者的語言習慣不同，用詞上往往短期内很難改變

爲了降低翻譯門檻和促進用詞的標準化，我提議我們可以編寫一個統一替換的脚本（或者什麽具有類似功能的東西）將常見的不符合翻譯標準的譯文改變。如直接將”支持“改爲”支援“，不會影響語義的同時，也能夠使翻譯者更方便的產出更高質量的翻譯。

因此我希望我們能有一個社區化的統一脚本，基於我們的glossary規範，同義替換譯文中所有不標準的翻譯。

Dominant language
Python
Stars
282
Forks
226
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from python/python-docs-zh-tw

All issues in python/python-docs-zh-tw

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.