From: Jonathan Nieder <jrnieder@gmail.com>
Date: Tue, 29 May 2012 20:37:59 GMT
Subject: Re: [PATCH 03/65] i18n: archive: mark parseopt strings for translation
Message-ID: <20120529203759.GC22151@burratino>
In-Reply-To: <7vr4u23f0i.fsf@alter.siamese.dyndns.org>

Junio C Hamano wrote:
> Nguyễn Thái Ngọc Duy  <pclouds@gmail.com> writes:

>> --- a/archive.c
>> +++ b/archive.c
>> @@ -7,10 +7,10 @@
>>  #include "unpack-trees.h"
>>  
>>  static char const * const archive_usage[] = {
>> -	"git archive [options] <tree-ish> [<path>...]",
>> -	"git archive --list",
>> -	"git archive --remote <repo> [--exec <cmd>] [options] <tree-ish> [<path>...]",
>> -	"git archive --remote <repo> [--exec <cmd>] --list",
>> +	N_("git archive [options] <tree-ish> [<path>...]"),
>> +	N_("git archive --list"),
>> +	N_("git archive --remote <repo> [--exec <cmd>] [options] <tree-ish> [<path>...]"),
>> +	N_("git archive --remote <repo> [--exec <cmd>] --list"),
>>  	NULL
>>  };
>
> I can understand the "help" text member of OPT_BLAH() construct, but
> do we really want to translate the above?

<repo>, <cmd>, [options], <tree-ish>, and <path> may be spelled
differently in other languages.  Would it be possible to take care
of this kind of substitution automatically?

At least "git archive --list" should probably be kept untranslated
to lessen the translator workload a bit.  Good catch.