From: Yamada Saburo <devil.tamachan@gmail.com>
To: git@vger.kernel.org
Subject: Fwd: [PATCH 4/4] Update Japanese translation (Git-gui)
Date: Fri, 19 Jul 2013 05:52:08 +0900 [thread overview]
Message-ID: <CAPM==HLEiwcP6ubgBh42j3w0VPMzXVhfjB9VM=6QWGxvk7M9jg@mail.gmail.com> (raw)
In-Reply-To: <CAPM==HK6o+vMbrb0o16qiKAG2azvBDPdXrXWaVro1W=Z-rXr7Q@mail.gmail.com>
---------- Forwarded message ----------
From: Yamada Saburo <devil.tamachan@gmail.com>
Date: 2013/7/19
Subject: Re: [PATCH 4/4] Update Japanese translation (Git-gui)
To: Junio C Hamano <gitster@pobox.com>
Hi Hamano,
> dubious ones like this (there is no change to the string, just the
> way msgstr is formatted to make them all overlong single strings).
changed by QT Linguist for Win.
> Perhaps "元のファイルタイプでの変更をコミット予定済", or something?
Your translation looks right. New mail is due to be thrown later here.
Thanks
2013/7/19 Junio C Hamano <gitster@pobox.com>:
> 悪魔野玉茶無 <devil.tamachan@gmail.com> writes:
>
>> @@ -124,26 +127,23 @@ msgstr "コミット予定済、ファイル無し"
>>
>> #: git-gui.sh:2087
>> msgid "File type changed, not staged"
>> -msgstr "ファイル型変更、コミット未予定"
>> +msgstr "ファイルタイプ変更、コミット未予定"
>
> There are good changes like this in this patch, and ...
>
>> #: git-gui.sh:3095
>> #, tcl-format
>> msgid "fatal: cannot stat path %s: No such file or directory"
>> -msgstr ""
>> -"致命的: パス %s が stat できません。そのようなファイルやディレクトリはありま"
>> -"せん"
>> +msgstr "致命的: パス %s が stat できません。そのようなファイルやディレクトリはありません"
>
> dubious ones like this (there is no change to the string, just the
> way msgstr is formatted to make them all overlong single strings).
>
>> #: git-gui.sh:2088 git-gui.sh:2089
>> -#, fuzzy
>> msgid "File type changed, old type staged for commit"
>> -msgstr "ファイル型変更、コミット未予定"
>> +msgstr "ファイルタイプ変更、コミット予定の形式が古い"
>
> Is this correct? I do not personally use git-gui, but I _think_
> this message is given when you did something like this:
>
> edit file ;# "file" is a regular file
> git add file
> rm file
> ln -s something file ;# "file" is now a symbolic link
>
> at this point, "git status" would say "MT file". The latter half of
> the translated Japanese reads "format planned to commit is ancient".
>
> Perhaps "元のファイルタイプでの変更をコミット予定済", or something?
>
> In any case, I think the organization of the series should be
>
> [PATCH 1/3] git-gui: mark yes/no/ask for translation
>
> which is your 3/4, and then
>
> [PATCH 2/3] git-gui: update git-gui/po/git-gui.pot
>
> which is your 1/4, and then
>
> [PATCH 3/3] git-gui: update Japanese translation
>
> which is all the changes to git-gui/po/ja.po in your 2/4 and 4/4.
>
> Also I forgot to notice when I was reading the earlier patches, but
> git-gui has a separate root commit, so please base your work on
> Pat Thoyts's tree at:
>
> git://repo.or.cz/git-gui
>
> Thanks.
prev parent reply other threads:[~2013-07-18 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 17:15 [PATCH 4/4] Update Japanese translation (Git-gui) 悪魔野玉茶無
2013-07-18 18:39 ` Junio C Hamano
[not found] ` <CAPM==HK6o+vMbrb0o16qiKAG2azvBDPdXrXWaVro1W=Z-rXr7Q@mail.gmail.com>
2013-07-18 20:52 ` Yamada Saburo [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPM==HLEiwcP6ubgBh42j3w0VPMzXVhfjB9VM=6QWGxvk7M9jg@mail.gmail.com' \
--to=devil.tamachan@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).