From: Junio C Hamano <gitster@pobox.com>
To: しらいしななこ <nanako3@lavabit.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [PATCH] git-gui: update Japanese translation
Date: Sun, 03 Aug 2008 14:24:18 -0700 [thread overview]
Message-ID: <7vy73dssfx.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080803170150.6117@nanako3.lavabit.com> (nanako3@lavabit.com's message of "Sun, 3 Aug 2008 17:01:50 +0900")
しらいしななこ <nanako3@lavabit.com> writes:
> This updates Japanese translation to match the updated git-gui.pot.
>
> Signed-off-by: しらいしななこ <nanako3@lavabit.com>
Looks fine to me, thanks.
> ...
> -#: git-gui.sh:41 git-gui.sh:634 git-gui.sh:648 git-gui.sh:661 git-gui.sh:744
> -#: git-gui.sh:763
> +#: git-gui.sh:41 git-gui.sh:688 git-gui.sh:702 git-gui.sh:715 git-gui.sh:798
> +#: git-gui.sh:817
It makes me wonder if we can do something about these line number changes
appearing on the patch, though...
Yes, I know it is a useful piece of information for PO aware editors to
help translators, but still...
next prev parent reply other threads:[~2008-08-03 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 8:01 [PATCH] git-gui: update Japanese translation しらいしななこ
2008-08-03 21:24 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-26 10:21 Nanako Shiraishi
2008-11-26 21:27 ` Alexander Gavrilov
2008-11-26 21:28 ` Shawn O. Pearce
2008-11-26 21:50 ` Junio C Hamano
2008-11-26 21:58 ` Junio C Hamano
2008-11-26 22:03 ` Junio C Hamano
2008-11-26 22:14 ` Shawn O. Pearce
2008-11-26 22:10 ` Nanako Shiraishi
2010-02-01 15:16 git-gui translation updates needed Shawn O. Pearce
2010-02-02 10:20 ` [PATCH] git-gui: update Japanese translation Nanako Shiraishi
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=7vy73dssfx.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nanako3@lavabit.com \
--cc=spearce@spearce.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.