From: Yamada Saburo <devil.tamachan@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Pat Thoyts <patthoyts@users.sourceforge.net>
Subject: Re: [PATCH v2 3/3] Update po/ja.po
Date: Tue, 23 Jul 2013 07:58:33 +0900 [thread overview]
Message-ID: <CAPM==H+_rpNojKjJe3-fJSXp0_8ishws=N7BsU7TJpfr2yG31A@mail.gmail.com> (raw)
In-Reply-To: <7vsiz69qfh.fsf@alter.siamese.dyndns.org>
Is free translation impossible? I want to give priority to ease of use.
Does Mr. Hamano know that it is said that Japanese translation of
Git-gui is very unclear? It is wonderful that my translation is
severely examined so far by me compared with a former translator.
Compiled .msg file so that it can try easily was uploaded.
https://docs.google.com/file/d/0B7h5NcRw8uVCSHMyVnFzQzJaZFU/edit?usp=sharing
2013/7/23 Junio C Hamano <gitster@pobox.com>:
> Yamada Saburo <devil.tamachan@gmail.com> writes:
>
>> -#: git-gui.sh:2893
>> +#: git-gui.sh:2983 git-gui.sh:3115
>> +msgid "Usage"
>> +msgstr "使用状況"
>
> Is this correct? I am not familiar with the context this string
> appears, but shouldn't it be "使い方"?
>
>> -#: lib/choose_repository.tcl:479
>> +#: lib/choose_repository.tcl:480
>> msgid "Source Location:"
>> msgstr "ソースの位置"
>>
>> -#: lib/choose_repository.tcl:490
>> +#: lib/choose_repository.tcl:489
>> msgid "Target Directory:"
>> -msgstr "先ディレクトリ:"
>> +msgstr "保存ディレクトリ:"
>
> I think this is better translation than the original (the Target is
> about where the new clone appears), but a few lines above we see
> "Source Location", which may want to be reworded. Perhaps
>
> クローン元リポジトリ
> クローン先リポジトリ
>
> ???
>
>> -#: lib/commit.tcl:272
>> +#: lib/commit.tcl:269
>> +msgid ""
>> +"You are about to commit on a detached head. This is a potentially dangerous "
>> +"thing to do because if you switch to another branch you will lose your "
>> +"changes and it can be difficult to retrieve them later from the reflog. You "
>> +"should probably cancel this commit and create a new branch to continue.\n"
>> +" \n"
>> +" Do you really want to proceed with your Commit?"
>> +msgstr ""
>> +"あなたはdetached "
>> +"head状態でコミットしようとしています。これは危険な操作です。もし続行すれば、他ブランチへ切り替えた際に変更を失ったり、reflogで変更を復元することが困難になります。あなたは次の操作をするべきです。1.
>> "
>
> The line wrapping of this look somewhat fishy. It technically is
> correct, but ending the line with an explicit \n and closing dq,
> i.e.
>
> "あなたはdetached head状態...べきです。\n"
>
> would be more natural and less error prone.
>
> Also, the original says "potentially dangerous", but "potentially"
> is lost in translation. I am not sure if the difference matters
> very much, but since I noticed it....
>
>> +"このコミットをキャンセルする。2. 新しいブランチを作り、コミットし直す。\n"
>
> Also, the original doesn't say "1. cancel this commit. 2. Create a
> new branch to recommit", and it is better without 1./2., which may
> be mistaken as if the user can do one of two things.
>
>> +"\n"
>> +"本当にこの危険なコミットを実行しますか?"
>
> The last sentence in the original only says "your Commit", without
> saying "Dangerous".
>
> In short, the translated text is far more alarming than the original
> phrasing.
>
>> -#: lib/option.tcl:132
>> +#: lib/option.tcl:134
>> msgid "Global (All Repositories)"
>> -msgstr "大域(全てのリポジトリ)"
>> +msgstr "標準設定(全てのリポジトリ)"
>
> The translation reads "Standard", not "Global". 「全体設定」, perhaps?
>
>> -#: lib/option.tcl:142
>> +#: lib/option.tcl:144
>> msgid "Merge Verbosity"
>> -msgstr "マージの冗長度"
>> +msgstr "マージのエラー出力レベル (0-5, 標準2、最高5)(merge.verbosity)"
>
> The original does not have 0-5, 2, nor 5. Translation shouldn't add
> one.
>
> If it will help the users to add these, please first add them to the
> original so that users of all languages would benefit and then
> translate the result.
>
>> -#: lib/option.tcl:143
>> +#: lib/option.tcl:145
>> msgid "Show Diffstat After Merge"
>> -msgstr "マージ後に diffstat を表示"
>> +msgstr "マージ後に変更量のグラフを表示 (git diff --stat)"
>
> Ditto.
>
>> -#: lib/option.tcl:150
>> +#: lib/option.tcl:153
>> msgid "Minimum Letters To Blame Copy On"
>> -msgstr "コピーを検知する最少文字数"
>> +msgstr "他ファイルから移動/コピーを検知する最少文字数 (標準値40)"
>
> Ditto.
>
> Pat, this patch is not quite ready.
>
> Thanks.
next prev parent reply other threads:[~2013-07-22 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 12:32 [PATCH v2 3/3] Update po/ja.po Yamada Saburo
2013-07-22 22:32 ` Junio C Hamano
2013-07-22 22:58 ` Yamada Saburo [this message]
2013-07-22 23:37 ` Junio C Hamano
2013-07-23 14:40 ` Yamada Saburo
2013-07-23 18:17 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPM==H+_rpNojKjJe3-fJSXp0_8ishws=N7BsU7TJpfr2yG31A@mail.gmail.com' \
--to=devil.tamachan@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=patthoyts@users.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).