[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ PATCH 1/1 ] l10n: zh_{CN,TW} localization update for bash 4.3

From: Eric Blake
Subject: Re: [ PATCH 1/1 ] l10n: zh_{CN,TW} localization update for bash 4.3
Date: Fri, 21 Aug 2015 07:06:49 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0

On 08/20/2015 04:19 PM, Jeff Bai wrote:
> Hello, and here is a patch set for both zh_CN and zh_TW localization update.
> I will send a separate message for bash 4.4.

Thanks, but please don't.  Spamming the wrong list with 600k of
information that the majority of list readers can't read is
inappropriate.  Instead, send your patches to the appropriate
translation teams.

See the following for more details:

Once the appropriate translation teams incorporate your work on
translationproject.org, then it can automatically be picked up by
distros, without upstream bash having to do anything.

However, to make this relevant to the upstream list:

GNU Coding Standards recommend that '$program --help' should list the
preferred bug-reporting address, and that the corresponding .po file
should then expand that information to ALSO list the preferred address
for reporting translation bugs in that .po file.  For example:

$ ls --help | tail -n2

GNU coreutils online help: <http://www.gnu.org/software/coreutils/>
For complete documentation, run: info coreutils 'ls invocation'
$ LC_ALL=zh_CN.UTF-8 ls --help | tail -n3
GNU coreutils online help: <http://www.gnu.org/software/coreutils/>
请向<http://translationproject.org/team/zh_CN.html> 报告ls 的翻译错误
要获取完整文档,请运行:info coreutils 'ls invocation'

Unfortunately, 'bash --help' violates this rule in the original English.
 But .po writers could STILL at least add their preferred
translation-bug reporting address into bash's (incomplete) --help output.

Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]