github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-18 06:03:09 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

About locale zh-CN，letting "issue=工单" is troublesome. 简体中文本地化时将 issue 翻译成「工单」，这是令人困扰的 #3082

New Issue
Closed
opened 2025-11-02 05:00:16 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 05:00:16 -06:00
Owner
Copy Link

Originally created by @hnlxl on GitHub (Mar 20, 2019).

  • Gitea version (or commit ref):1.7.2, or HEAD b78cbbc when creating this issue

this question is about Chinese localization, so I will only use Chinese to describe it later.

Description

中文三个本地化配置中关于 issue 的翻译如下：

  • gitea/options/locale/locale_zh-CN.ini：issues=工单 在626行.
  • gitea/options/locale/locale_zh-HK.ini:：issues=問題管理 在287行.
  • gitea/options/locale/locale_zh-TW.ini：issues=問題 在512行.

「工单」这个意译基本上失败了，第一次看到界面的时候，我还以为工单是「Pull Request」。（「Pull Request 」翻译成了合并请求，感觉也有点过度意译了）非敏捷开发场景下，「issue」的实际含义可能是缺陷/Bug、疑问、讨论、待开发功能，敏捷开发场景下还可能是任务、改进、用例故事，几乎没有场景中回表示工单的含义。

我觉得还是翻译成问题比较好。实际上问题也是包含意译的效果的，简体中文语境下问题本来就是一个泛称的词，程序不运行（严重缺陷）、提示信息看不懂（疑问）、代码看着不工整（改进/讨论）、领导看着不爽（突发任务），都可以叫做问题。

Screenshots

JIRA就是翻译成问题的，看起来并不违和。
JIRA关于issue的翻译

Originally created by @hnlxl on GitHub (Mar 20, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref):1.7.2, or `HEAD b78cbbc` when creating this issue > this question is about Chinese localization, so I will only use Chinese to describe it later. ## Description 中文三个本地化配置中关于 issue 的翻译如下： - gitea/options/locale/locale_zh-CN.ini：`issues=工单` 在626行. - gitea/options/locale/locale_zh-HK.ini:：`issues=問題管理` 在287行. - gitea/options/locale/locale_zh-TW.ini：`issues=問題` 在512行. 「工单」这个意译基本上失败了，第一次看到界面的时候，我还以为工单是「Pull Request」。（「Pull Request 」翻译成了合并请求，感觉也有点过度意译了）非敏捷开发场景下，「issue」的实际含义可能是缺陷/Bug、疑问、讨论、待开发功能，敏捷开发场景下还可能是任务、改进、用例故事，几乎没有场景中回表示工单的含义。 我觉得还是翻译成`问题`比较好。实际上`问题`也是包含意译的效果的，简体中文语境下`问题`本来就是一个泛称的词，程序不运行（严重缺陷）、提示信息看不懂（疑问）、代码看着不工整（改进/讨论）、领导看着不爽（突发任务），都可以叫做问题。 ## Screenshots JIRA就是翻译成问题的，看起来并不违和。 ![JIRA关于issue的翻译](https://user-images.githubusercontent.com/11850956/54671629-3f5c3900-4b31-11e9-83d3-2a8bb187f20f.png) <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/not-a-bug label 2025-11-02 05:00:16 -06:00
GiteaMirror commented 2025-11-02 05:00:17 -06:00
Author
Owner
Copy Link

@hnlxl commented on GitHub (Mar 20, 2019):

刚从培训资料里面发现的一个问题的专项定义：问题=目标与现状的差距。从这方面看，issue 翻译成问题是完全没问题的。

@hnlxl commented on GitHub (Mar 20, 2019): 刚从培训资料里面发现的一个问题的专项定义：问题=目标与现状的差距。从这方面看，issue 翻译成问题是完全没问题的。
GiteaMirror commented 2025-11-02 05:00:17 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 20, 2019):

Please go to https://crowdin.com/translate/gitea/68/enus-zhcn to discuss that.

@lunny commented on GitHub (Mar 20, 2019): Please go to https://crowdin.com/translate/gitea/68/enus-zhcn to discuss that.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/not-a-bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3082
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?