From: "André Goddard Rosa" <andre.goddard@gmail.com>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org, Yasuaki Narita <yasuaki_n@mti.biglobe.ne.jp>
Subject: Re: [PATCH] Translate the tutorial to Brazillian Portuguese.
Date: Thu, 30 Jul 2009 14:42:25 -0300 [thread overview]
Message-ID: <b8bf37780907301042p4ed4c3e9x85e76ab04ca12696@mail.gmail.com> (raw)
In-Reply-To: <20090730154446.GD1727@vespa.holoscopio.com>
On 7/30/09, Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com> wrote:
> On Thu, Jul 30, 2009 at 12:26:14AM -0300, André Goddard Rosa wrote:
>> git gui uses 'po' at http://repo.or.cz/w/git-gui/git-gui-i18n.git to
>> handle all translations, including Brazilian Portuguese.
>>
>
> But do they use it for Documentation? It doesn't seem so. po4a seems to
> be a reasonable choice, which, in the end, means po too. But it would be
> interesting to gather others experiences in keeping Documentation
> translations updated, not only software strings.
Sure, that's what po4a is meant for.
>> @Thadeu: would you please double check it and perhaps add your Acked-by?
>>
>
> It seems OK, but for three fixes as I've sent before. Would you mind
> re-sending them?
I've sent it including the contributions/fixes from you and Carlos.
Thanks,
Andre
next prev parent reply other threads:[~2009-07-30 17:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 14:05 [PATCH 2/2] Translate the tutorial to Brazillian Portuguese Thadeu Lima de Souza Cascardo
2009-06-29 15:19 ` Junio C Hamano
2009-06-29 15:32 ` [PATCH] " Thadeu Lima de Souza Cascardo
2009-06-29 16:08 ` Junio C Hamano
2009-06-29 16:27 ` Thadeu Lima de Souza Cascardo
2009-06-29 18:35 ` Junio C Hamano
2009-07-30 3:26 ` André Goddard Rosa
2009-07-30 15:44 ` Thadeu Lima de Souza Cascardo
2009-07-30 17:42 ` André Goddard Rosa [this message]
2009-06-29 16:33 ` Jakub Narebski
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=b8bf37780907301042p4ed4c3e9x85e76ab04ca12696@mail.gmail.com \
--to=andre.goddard@gmail.com \
--cc=cascardo@holoscopio.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=yasuaki_n@mti.biglobe.ne.jp \
/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).