threads / patch / 21037

patchDocumentation - pt-BR.

Subject: [PATCH] Documentation - pt-BR.

## tl;dr

15 messages between Sep 23, 2009 and Oct 8, 2009. Diffs are folded; open one to read it.

replies: 14people: 5as markdown or json

Thiago Farina· Sep 23, 2009, 18:25 UTC · lore
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(-)
Show changes to Documentation/pt_BR/gittutorial.txt +11 −11
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
Jeff King· Oct 1, 2009, 08:02 UTC · re: Thiago Farina · lore

Re: [PATCH] Documentation - pt-BR.

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· Oct 1, 2009, 08:16 UTC · re: Jeff King · lore

Re: [PATCH] Documentation - pt-BR.

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· Oct 1, 2009, 11:58 UTC · re: Jeff King · lore

Re: [PATCH] Documentation - pt-BR.

On Thu  1.Oct'09 at  4:02:06 -0400, Jeff King wrote:
Show 6 quoted lines
> 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· Oct 1, 2009, 12:07 UTC · re: Carlos R. Mafra · lore

Re: [PATCH] Documentation - pt-BR.

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· Oct 1, 2009, 12:22 UTC · re: Carlos R. Mafra · lore

Re: [PATCH] Documentation - pt-BR.

On Thu, Oct 01, 2009 at 02:07:11PM +0200, Carlos R. Mafra wrote:
Show 13 quoted lines
> 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
Junio C Hamano· Oct 5, 2009, 01:53 UTC · re: Thiago Farina · lore

Re: [PATCH] Documentation - pt-BR.

Thiago Farina <tfransosi@gmail.com> writes:
Show 21 quoted lines
> 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· Oct 5, 2009, 07:18 UTC · re: Junio C Hamano · lore

Re: [PATCH] Documentation - pt-BR.

On Sun, Oct 04, 2009 at 06:53:49PM -0700, Junio C Hamano <gitster@pobox.com> wrote:
Show 18 quoted lines
> > -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· Oct 5, 2009, 10:09 UTC · re: Junio C Hamano · lore

Re: [PATCH] Documentation - pt-BR.

On Sun, Oct 04, 2009 at 06:53:49PM -0700, Junio C Hamano wrote:
Show 10 quoted lines
> 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· Oct 6, 2009, 09:47 UTC · re: Jeff King · lore

Re: [PATCH] Documentation - pt-BR.

On Mon, Oct 05, 2009 at 06:09:10AM -0400, Jeff King <peff@peff.net> wrote:
Show 8 quoted lines
> > 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· Oct 6, 2009, 15:20 UTC · re: Miklos Vajna · lore

Re: [PATCH] Documentation - pt-BR.

Hi Miklos, On Tue, Oct 6, 2009 at 6:47 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:

Show 19 quoted lines
> 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?
Show 7 quoted lines
>
> 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· Oct 8, 2009, 00:12 UTC · re: Thiago Farina · lore

Re: [PATCH] Documentation - pt-BR.

On Tue, Oct 06, 2009 at 12:20:00PM -0300, Thiago Farina <tfransosi@gmail.com> wrote:
Show 8 quoted lines
> > $ 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· Oct 8, 2009, 03:25 UTC · re: Miklos Vajna · lore

Re: [PATCH] Documentation - pt-BR.

Hi Miklos, On Wed, Oct 7, 2009 at 9:12 PM, Miklos Vajna <vmiklos@frugalware.org> wrote:

Show 11 quoted lines
> 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 :)
Show 6 quoted lines
>
>> 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.

← back to recent threads