# [PATCH] Documentation - pt-BR.

15 messages from 2009-09-23 to 2009-10-08. Participants: Thiago Farina, Jeff King, Carlos R. Mafra, Junio C Hamano, Miklos Vajna.
Thread: https://gitlist.dev/t/21037

## Thiago Farina, 2009-09-23 18:25

Subject: [PATCH] Documentation - pt-BR.
Message-ID: <1253730339-11146-1-git-send-email-tfransosi@gmail.com>
URL: https://gitlist.dev/e/1253730339-11146-1-git-send-email-tfransosi%40gmail.com

```
Translate some english words to portuguese and fix some typos on translation.

Signed-off-by: Thiago Farina <tfransosi@gmail.com>
---
 Documentation/pt_BR/gittutorial.txt |   22 +++++++++++-----------
 1 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/Documentation/pt_BR/gittutorial.txt b/Documentation/pt_BR/gittutorial.txt
index 81e7ad7..6fb396a 100644
--- a/Documentation/pt_BR/gittutorial.txt
+++ b/Documentation/pt_BR/gittutorial.txt
@@ -1,15 +1,15 @@
 gittutorial(7)
 ==============
 
-NAME
+NOME
 ----
 gittutorial - Um tutorial de introduÃ§Ã£o ao git (para versÃ£o 1.5.1 ou mais nova)
 
-SYNOPSIS
+SINOPSE
 --------
 git *
 
-DESCRIPTION
+DESCRIÃÃO
 -----------
 
 Este tutorial explica como importar um novo projeto para o git,
@@ -64,11 +64,11 @@ Git irÃ¡ responder
 Initialized empty Git repository in .git/
 ------------------------------------------------
 
-VocÃª agora iniciou seu diretÃ³rio de trabalho--vocÃª deve ter notado um
-novo diretÃ³rio criado, com o nome de ".git".
+Agora que vocÃª iniciou seu diretÃ³rio de trabalho, vocÃª deve ter notado que um
+novo diretÃ³rio foi criado com o nome de ".git".
 
 A seguir, diga ao git para gravar um instantÃ¢neo do conteÃºdo de todos os
-arquivos sob o diretÃ³rio corrente (note o '.'), com 'git-add':
+arquivos sob o diretÃ³rio atual (note o '.'), com 'git-add':
 
 ------------------------------------------------
 $ git add .
@@ -126,8 +126,8 @@ mudanÃ§as com:
 $ git commit
 ------------------------------------------------
 
-Isto irÃ¡ novamente te pedir por uma mensagem descrevendo a mudanÃ§a, e,
-entÃ£o, gravar a nova versÃ£o do projeto.
+Ao executar esse comando, ele irÃ¡ te pedir uma mensagem descrevendo a mudanÃ§a,
+e, entÃ£o, irÃ¡ gravar a nova versÃ£o do projeto.
 
 Alternativamente, ao invÃ©s de executar 'git-add' antes, vocÃª pode usar
 
@@ -143,7 +143,7 @@ idÃ©ia comeÃ§ar a mensagem com uma simples e curta (menos de 50
 caracteres) linha sumarizando a mudanÃ§a, seguida de uma linha em branco
 e, entÃ£o, uma descriÃ§Ã£o mais detalhada. Ferramentas que transformam
 commits em email, por exemplo, usam a primeira linha no campo de
-cabeÃ§alho Subject: e o resto no corpo.
+cabeÃ§alho "Assunto:", e o resto no corpo.
 
 Git rastreia conteÃºdo, nÃ£o arquivos
 ----------------------------
@@ -155,7 +155,7 @@ usado tanto para arquivos novos e arquivos recentemente modificados, e
 em ambos os casos, ele tira o instantÃ¢neo dos arquivos dados e armazena
 o conteÃºdo no Ã­ndice, pronto para inclusÃ£o do prÃ³ximo commit.
 
-Visualizando histÃ³ria do projeto
+Visualizando a histÃ³ria do projeto
 -----------------------
 
 Em qualquer ponto vocÃª pode visualizar a histÃ³ria das suas mudanÃ§as
@@ -165,7 +165,7 @@ usando
 $ git log
 ------------------------------------------------
 
-Se vocÃª tambÃ©m quer ver a diferenÃ§a completa a cada passo, use
+Se vocÃª tambÃ©m quiser ver a diferenÃ§a completa a cada passo, use
 
 ------------------------------------------------
 $ git log -p
-- 
1.6.5.rc1.44.ga1675

```

## Thiago Farina, 2009-09-30 22:18

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <a4c8a6d00909301518v43784d7ah6364be0134a6e7d@mail.gmail.com>
URL: https://gitlist.dev/e/a4c8a6d00909301518v43784d7ah6364be0134a6e7d%40mail.gmail.com
In-Reply-To: <1253730339-11146-1-git-send-email-tfransosi@gmail.com>

```
Ping

```

## Jeff King, 2009-10-01 08:02

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <20091001080206.GB13436@coredump.intra.peff.net>
URL: https://gitlist.dev/e/20091001080206.GB13436%40coredump.intra.peff.net
In-Reply-To: <a4c8a6d00909301518v43784d7ah6364be0134a6e7d@mail.gmail.com>

```
On Wed, Sep 30, 2009 at 07:18:26PM -0300, Thiago Farina wrote:

> Ping

I think the original just got overlooked. My Portuguese is bad enough
that I will have to take your word on the correctness of the fixes.

Shawn, this can probably go straight onto master (tr/doc-pt-br in my
tree).

-Peff

```

## Jeff King, 2009-10-01 08:16

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <20091001081647.GA23291@coredump.intra.peff.net>
URL: https://gitlist.dev/e/20091001081647.GA23291%40coredump.intra.peff.net
In-Reply-To: <20091001080206.GB13436@coredump.intra.peff.net>

```
On Thu, Oct 01, 2009 at 04:02:06AM -0400, Jeff King wrote:

> Shawn, this can probably go straight onto master (tr/doc-pt-br in my
> tree).

Er, that should be "tf/doc-pt-br" of course.

-Peff

```

## Carlos R. Mafra, 2009-10-01 11:58

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <20091001115846.GA5583@Pilar.aei.mpg.de>
URL: https://gitlist.dev/e/20091001115846.GA5583%40Pilar.aei.mpg.de
In-Reply-To: <20091001080206.GB13436@coredump.intra.peff.net>

```
On Thu  1.Oct'09 at  4:02:06 -0400, Jeff King wrote:
> On Wed, Sep 30, 2009 at 07:18:26PM -0300, Thiago Farina wrote:
> 
> > Ping
> 
> I think the original just got overlooked. My Portuguese is bad enough
> that I will have to take your word on the correctness of the fixes.

I read the patch. The changes are correct and improve the quality
of the text.

```

## Carlos R. Mafra, 2009-10-01 12:07

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <20091001120711.GB5583@Pilar.aei.mpg.de>
URL: https://gitlist.dev/e/20091001120711.GB5583%40Pilar.aei.mpg.de
In-Reply-To: <20091001115846.GA5583@Pilar.aei.mpg.de>

```
On Thu  1.Oct'09 at 13:58:46 +0200, Carlos R. Mafra wrote:
> I read the patch. The changes are correct and improve the quality
> of the text.

From the Portuguese point of view the change below is
correct,

-cabeçalho Subject: e o resto no corpo.
+cabeçalho "Assunto:", e o resto no corpo.

but I don't know if "Subject:" should be translated in
this context. Does git-am accept "Assunto:" instead
of "Subject:" if one is using a Portuguese locale?

```

## Jeff King, 2009-10-01 12:22

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <20091001122252.GA31919@sigill.intra.peff.net>
URL: https://gitlist.dev/e/20091001122252.GA31919%40sigill.intra.peff.net
In-Reply-To: <20091001120711.GB5583@Pilar.aei.mpg.de>

```
On Thu, Oct 01, 2009 at 02:07:11PM +0200, Carlos R. Mafra wrote:

> On Thu  1.Oct'09 at 13:58:46 +0200, Carlos R. Mafra wrote:
> > I read the patch. The changes are correct and improve the quality
> > of the text.
> 
> From the Portuguese point of view the change below is
> correct,
> 
> -cabeçalho Subject: e o resto no corpo.
> +cabeçalho "Assunto:", e o resto no corpo.
> 
> but I don't know if "Subject:" should be translated in
> this context. Does git-am accept "Assunto:" instead
> of "Subject:" if one is using a Portuguese locale?

No, it doesn't. It must be in English as it is an rfc2822 header. It is
probably best for it to remain in English here, then, as we are
specifically referring to the literal "Subject" mail header, as opposed
to the more abstract concept of a subject. I think putting it in quotes
makes sense, though, to indicate clearly that it is a literal technical
term. I.e.:

-cabeçalho Subject: e o resto no corpo.
+cabeçalho "Subject:" e o resto no corpo.

The patch in my tree has been updated in this way.

Thanks, Carlos, for the review.

-Peff

```

## Thiago Farina, 2009-10-01 22:35

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <a4c8a6d00910011535q3d49f6c0l9248edd7bab6bdf8@mail.gmail.com>
URL: https://gitlist.dev/e/a4c8a6d00910011535q3d49f6c0l9248edd7bab6bdf8%40mail.gmail.com
In-Reply-To: <20091001122252.GA31919@sigill.intra.peff.net>

```
Hi,

Thanks Jeff to care about my patch and for the review :)
Thanks Carlos for the review too.

-Thiago

```

## Junio C Hamano, 2009-10-05 01:53

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <7vhbuek3ma.fsf@alter.siamese.dyndns.org>
URL: https://gitlist.dev/e/7vhbuek3ma.fsf%40alter.siamese.dyndns.org
In-Reply-To: <1253730339-11146-1-git-send-email-tfransosi@gmail.com>

```
Thiago Farina <tfransosi@gmail.com> writes:

> diff --git a/Documentation/pt_BR/gittutorial.txt b/Documentation/pt_BR/gittutorial.txt
> index 81e7ad7..beba065 100644
> --- a/Documentation/pt_BR/gittutorial.txt
> +++ b/Documentation/pt_BR/gittutorial.txt
> @@ -1,15 +1,15 @@
>  gittutorial(7)
>  ==============
>  
> -NAME
> +NOME
>  ----
>  gittutorial - Um tutorial de introdução ao git (para versão 1.5.1 ou mais nova)
>  
> -SYNOPSIS
> +SINOPSE
>  --------
>  git *
>  
> -DESCRIPTION
> +DESCRIÇÃO
>  -----------

Not reading Portuguese, I have two comments.

 - How well does AsciiDoc and its manpage backend work with these standard
   section names localized?

 - The length of the underline must match the section header word it
   underlines.

Has anybody actually tried to format this document, either before or after
your patch?

```

## Miklos Vajna, 2009-10-05 07:18

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <20091005071806.GT32702@genesis.frugalware.org>
URL: https://gitlist.dev/e/20091005071806.GT32702%40genesis.frugalware.org
In-Reply-To: <7vhbuek3ma.fsf@alter.siamese.dyndns.org>

```
On Sun, Oct 04, 2009 at 06:53:49PM -0700, Junio C Hamano <gitster@pobox.com> wrote:
> > -NAME
> > +NOME
> >  ----
> >  gittutorial - Um tutorial de introduç??o ao git (para vers??o 1.5.1 ou mais nova)
> >  
> > -SYNOPSIS
> > +SINOPSE
> >  --------
> >  git *
> >  
> > -DESCRIPTION
> > +DESCRIÇ??O
> >  -----------
> 
> Not reading Portuguese, I have two comments.
> 
>  - How well does AsciiDoc and its manpage backend work with these standard
>    section names localized?

As long as the correct -a lang=foo option is passed to asciidoc, the
generated docbook XML will be valid.

```

## Jeff King, 2009-10-05 10:09

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <20091005100910.GA866@coredump.intra.peff.net>
URL: https://gitlist.dev/e/20091005100910.GA866%40coredump.intra.peff.net
In-Reply-To: <7vhbuek3ma.fsf@alter.siamese.dyndns.org>

```
On Sun, Oct 04, 2009 at 06:53:49PM -0700, Junio C Hamano wrote:

> Not reading Portuguese, I have two comments.
> 
>  - How well does AsciiDoc and its manpage backend work with these standard
>    section names localized?
> 
>  - The length of the underline must match the section header word it
>    underlines.
> 
> Has anybody actually tried to format this document, either before or after
> your patch?

No, I didn't, and I should have when I picked up the patch in the first
place. You are right, asciidoc barfs (both for html and xml generation):

  ERROR: gittutorial.txt: line 5: first section must be named NAME
  ERROR: gittutorial.txt: line 9: second section must be named SYNOPSIS

-Peff

```

## Miklos Vajna, 2009-10-06 09:47

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <20091006094701.GG32702@genesis.frugalware.org>
URL: https://gitlist.dev/e/20091006094701.GG32702%40genesis.frugalware.org
In-Reply-To: <20091005100910.GA866@coredump.intra.peff.net>

```
On Mon, Oct 05, 2009 at 06:09:10AM -0400, Jeff King <peff@peff.net> wrote:
> > Has anybody actually tried to format this document, either before or after
> > your patch?
> 
> No, I didn't, and I should have when I picked up the patch in the first
> place. You are right, asciidoc barfs (both for html and xml generation):
> 
>   ERROR: gittutorial.txt: line 5: first section must be named NAME
>   ERROR: gittutorial.txt: line 9: second section must be named SYNOPSIS

Ah, there is no language config for pt_BR.

$ ls -1 /etc/asciidoc/lang-*
/etc/asciidoc/lang-de.conf
/etc/asciidoc/lang-en.conf
/etc/asciidoc/lang-es.conf
/etc/asciidoc/lang-fr.conf
/etc/asciidoc/lang-hu.conf
/etc/asciidoc/lang-ru.conf

Once asciidoc will have a lang-pt_BR.conf, we could just use -a
lang=pt_BR and it would happily accept this input.

Thiago, could you make a lang-pt_BR.conf? It's less than 100 lines, so
it should be easy for you. (If you can send it to the asciidoc list
directly, it's even better.)

```

## Thiago Farina, 2009-10-06 15:20

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <a4c8a6d00910060820se973fcci31c94c42937c7eb2@mail.gmail.com>
URL: https://gitlist.dev/e/a4c8a6d00910060820se973fcci31c94c42937c7eb2%40mail.gmail.com
In-Reply-To: <20091006094701.GG32702@genesis.frugalware.org>

```
Hi Miklos,
On Tue, Oct 6, 2009 at 6:47 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:
> On Mon, Oct 05, 2009 at 06:09:10AM -0400, Jeff King <peff@peff.net> wrote:
>> > Has anybody actually tried to format this document, either before or after
>> > your patch?
>>
>> No, I didn't, and I should have when I picked up the patch in the first
>> place. You are right, asciidoc barfs (both for html and xml generation):
>>
>>   ERROR: gittutorial.txt: line 5: first section must be named NAME
>>   ERROR: gittutorial.txt: line 9: second section must be named SYNOPSIS
>
> Ah, there is no language config for pt_BR.
>
> $ ls -1 /etc/asciidoc/lang-*
> /etc/asciidoc/lang-de.conf
> /etc/asciidoc/lang-en.conf
> /etc/asciidoc/lang-es.conf
> /etc/asciidoc/lang-fr.conf
> /etc/asciidoc/lang-hu.conf
> /etc/asciidoc/lang-ru.conf
In my system I only have installed lang-es.conf, how I could install the others?
>
> Once asciidoc will have a lang-pt_BR.conf, we could just use -a
> lang=pt_BR and it would happily accept this input.
>
> Thiago, could you make a lang-pt_BR.conf? It's less than 100 lines, so
> it should be easy for you. (If you can send it to the asciidoc list
> directly, it's even better.)
Sure, I made the lang-pt-BR.conf, and I sent it to asciidoc@googlegroups.com.

```

## Miklos Vajna, 2009-10-08 00:12

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <20091008001248.GS32702@genesis.frugalware.org>
URL: https://gitlist.dev/e/20091008001248.GS32702%40genesis.frugalware.org
In-Reply-To: <a4c8a6d00910060820se973fcci31c94c42937c7eb2@mail.gmail.com>

```
On Tue, Oct 06, 2009 at 12:20:00PM -0300, Thiago Farina <tfransosi@gmail.com> wrote:
> > $ ls -1 /etc/asciidoc/lang-*
> > /etc/asciidoc/lang-de.conf
> > /etc/asciidoc/lang-en.conf
> > /etc/asciidoc/lang-es.conf
> > /etc/asciidoc/lang-fr.conf
> > /etc/asciidoc/lang-hu.conf
> > /etc/asciidoc/lang-ru.conf
> In my system I only have installed lang-es.conf, how I could install the others?

This is with asciidoc 8.5.0, I guess you have a bit older version.

> Sure, I made the lang-pt-BR.conf, and I sent it to asciidoc@googlegroups.com.

Great, then sooner or later you could have those 'NAME' and 'SYNOPSIS'
strings localised. Till then, I would suggest having them in English -
git typically supports building with older asciidoc versions.

```

## Thiago Farina, 2009-10-08 03:25

Subject: Re: [PATCH] Documentation - pt-BR.
Message-ID: <a4c8a6d00910072025l179541e1t67b6dd46f20d61d5@mail.gmail.com>
URL: https://gitlist.dev/e/a4c8a6d00910072025l179541e1t67b6dd46f20d61d5%40mail.gmail.com
In-Reply-To: <20091008001248.GS32702@genesis.frugalware.org>

```
Hi Miklos,
On Wed, Oct 7, 2009 at 9:12 PM, Miklos Vajna <vmiklos@frugalware.org> wrote:
> On Tue, Oct 06, 2009 at 12:20:00PM -0300, Thiago Farina <tfransosi@gmail.com> wrote:
>> > $ ls -1 /etc/asciidoc/lang-*
>> > /etc/asciidoc/lang-de.conf
>> > /etc/asciidoc/lang-en.conf
>> > /etc/asciidoc/lang-es.conf
>> > /etc/asciidoc/lang-fr.conf
>> > /etc/asciidoc/lang-hu.conf
>> > /etc/asciidoc/lang-ru.conf
>> In my system I only have installed lang-es.conf, how I could install the others?
>
> This is with asciidoc 8.5.0, I guess you have a bit older version.
I will check :)
>
>> Sure, I made the lang-pt-BR.conf, and I sent it to asciidoc@googlegroups.com.
>
> Great, then sooner or later you could have those 'NAME' and 'SYNOPSIS'
> strings localised. Till then, I would suggest having them in English -
> git typically supports building with older asciidoc versions.
My patch was added to the trunk -
http://hg.sharesource.org/asciidoc/rev/5bc014ab7c52.

```
