{"thread":{"id":"21037","subject":"[PATCH] Documentation - pt-BR.","startedAt":"2009-09-23T18:25:39Z","lastAt":"2009-10-08T03:25:01Z","messageCount":15,"participants":["Thiago Farina","Jeff King","Carlos R. Mafra","Junio C Hamano","Miklos Vajna"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"123680","messageId":"1253730339-11146-1-git-send-email-tfransosi@gmail.com","threadId":"21037","inReplyTo":null,"subject":"[PATCH] Documentation - pt-BR.","fromName":"Thiago Farina","fromEmail":"tfransosi@gmail.com","sentAt":"2009-09-23T18:25:39Z","receivedAt":"2009-09-23T18:25:39Z","isPatch":true,"sender":{"key":"tfransosi@gmail.com","avatar":"https://avatars.githubusercontent.com/u/970071?v=4"},"body":"Translate some english words to portuguese and fix some typos on translation.\n\nSigned-off-by: Thiago Farina <tfransosi@gmail.com>\n---\n Documentation/pt_BR/gittutorial.txt |   22 +++++++++++-----------\n 1 files changed, 11 insertions(+), 11 deletions(-)\n\ndiff --git a/Documentation/pt_BR/gittutorial.txt b/Documentation/pt_BR/gittutorial.txt\nindex 81e7ad7..6fb396a 100644\n--- a/Documentation/pt_BR/gittutorial.txt\n+++ b/Documentation/pt_BR/gittutorial.txt\n@@ -1,15 +1,15 @@\n gittutorial(7)\n ==============\n \n-NAME\n+NOME\n ----\n gittutorial - Um tutorial de introdução ao git (para versão 1.5.1 ou mais nova)\n \n-SYNOPSIS\n+SINOPSE\n --------\n git *\n \n-DESCRIPTION\n+DESCRIÇÃO\n -----------\n \n Este tutorial explica como importar um novo projeto para o git,\n@@ -64,11 +64,11 @@ Git irá responder\n Initialized empty Git repository in .git/\n ------------------------------------------------\n \n-Você agora iniciou seu diretório de trabalho--você deve ter notado um\n-novo diretório criado, com o nome de \".git\".\n+Agora que você iniciou seu diretório de trabalho, você deve ter notado que um\n+novo diretório foi criado com o nome de \".git\".\n \n A seguir, diga ao git para gravar um instantâneo do conteúdo de todos os\n-arquivos sob o diretório corrente (note o '.'), com 'git-add':\n+arquivos sob o diretório atual (note o '.'), com 'git-add':\n \n ------------------------------------------------\n $ git add .\n@@ -126,8 +126,8 @@ mudanças com:\n $ git commit\n ------------------------------------------------\n \n-Isto irá novamente te pedir por uma mensagem descrevendo a mudança, e,\n-então, gravar a nova versão do projeto.\n+Ao executar esse comando, ele irá te pedir uma mensagem descrevendo a mudança,\n+e, então, irá gravar a nova versão do projeto.\n \n Alternativamente, ao invés de executar 'git-add' antes, você pode usar\n \n@@ -143,7 +143,7 @@ idéia começar a mensagem com uma simples e curta (menos de 50\n caracteres) linha sumarizando a mudança, seguida de uma linha em branco\n e, então, uma descrição mais detalhada. Ferramentas que transformam\n commits em email, por exemplo, usam a primeira linha no campo de\n-cabeçalho Subject: e o resto no corpo.\n+cabeçalho \"Assunto:\", e o resto no corpo.\n \n Git rastreia conteúdo, não arquivos\n ----------------------------\n@@ -155,7 +155,7 @@ usado tanto para arquivos novos e arquivos recentemente modificados, e\n em ambos os casos, ele tira o instantâneo dos arquivos dados e armazena\n o conteúdo no índice, pronto para inclusão do próximo commit.\n \n-Visualizando história do projeto\n+Visualizando a história do projeto\n -----------------------\n \n Em qualquer ponto você pode visualizar a história das suas mudanças\n@@ -165,7 +165,7 @@ usando\n $ git log\n ------------------------------------------------\n \n-Se você também quer ver a diferença completa a cada passo, use\n+Se você também quiser ver a diferença completa a cada passo, use\n \n ------------------------------------------------\n $ git log -p\n-- \n1.6.5.rc1.44.ga1675\n"},{"id":"124052","messageId":"a4c8a6d00909301518v43784d7ah6364be0134a6e7d@mail.gmail.com","threadId":"21037","inReplyTo":"1253730339-11146-1-git-send-email-tfransosi@gmail.com","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Thiago Farina","fromEmail":"tfransosi@gmail.com","sentAt":"2009-09-30T22:18:26Z","receivedAt":"2009-09-30T22:18:26Z","isPatch":true,"sender":{"key":"tfransosi@gmail.com","avatar":"https://avatars.githubusercontent.com/u/970071?v=4"},"body":"Ping\n"},{"id":"124069","messageId":"20091001080206.GB13436@coredump.intra.peff.net","threadId":"21037","inReplyTo":"a4c8a6d00909301518v43784d7ah6364be0134a6e7d@mail.gmail.com","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-10-01T08:02:06Z","receivedAt":"2009-10-01T08:02:06Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Sep 30, 2009 at 07:18:26PM -0300, Thiago Farina wrote:\n\n> Ping\n\nI think the original just got overlooked. My Portuguese is bad enough\nthat I will have to take your word on the correctness of the fixes.\n\nShawn, this can probably go straight onto master (tr/doc-pt-br in my\ntree).\n\n-Peff\n"},{"id":"124071","messageId":"20091001081647.GA23291@coredump.intra.peff.net","threadId":"21037","inReplyTo":"20091001080206.GB13436@coredump.intra.peff.net","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-10-01T08:16:47Z","receivedAt":"2009-10-01T08:16:47Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Oct 01, 2009 at 04:02:06AM -0400, Jeff King wrote:\n\n> Shawn, this can probably go straight onto master (tr/doc-pt-br in my\n> tree).\n\nEr, that should be \"tf/doc-pt-br\" of course.\n\n-Peff\n"},{"id":"124075","messageId":"20091001115846.GA5583@Pilar.aei.mpg.de","threadId":"21037","inReplyTo":"20091001080206.GB13436@coredump.intra.peff.net","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Carlos R. Mafra","fromEmail":"crmafra2@gmail.com","sentAt":"2009-10-01T11:58:46Z","receivedAt":"2009-10-01T11:58:46Z","isPatch":true,"sender":{"key":"crmafra2@gmail.com","avatar":null},"body":"On Thu  1.Oct'09 at  4:02:06 -0400, Jeff King wrote:\n> On Wed, Sep 30, 2009 at 07:18:26PM -0300, Thiago Farina wrote:\n> \n> > Ping\n> \n> I think the original just got overlooked. My Portuguese is bad enough\n> that I will have to take your word on the correctness of the fixes.\n\nI read the patch. The changes are correct and improve the quality\nof the text.\n"},{"id":"124077","messageId":"20091001120711.GB5583@Pilar.aei.mpg.de","threadId":"21037","inReplyTo":"20091001115846.GA5583@Pilar.aei.mpg.de","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Carlos R. Mafra","fromEmail":"crmafra2@gmail.com","sentAt":"2009-10-01T12:07:11Z","receivedAt":"2009-10-01T12:07:11Z","isPatch":true,"sender":{"key":"crmafra2@gmail.com","avatar":null},"body":"On Thu  1.Oct'09 at 13:58:46 +0200, Carlos R. Mafra wrote:\n> I read the patch. The changes are correct and improve the quality\n> of the text.\n\nFrom the Portuguese point of view the change below is\ncorrect,\n\n-cabeçalho Subject: e o resto no corpo.\n+cabeçalho \"Assunto:\", e o resto no corpo.\n\nbut I don't know if \"Subject:\" should be translated in\nthis context. Does git-am accept \"Assunto:\" instead\nof \"Subject:\" if one is using a Portuguese locale?\n"},{"id":"124078","messageId":"20091001122252.GA31919@sigill.intra.peff.net","threadId":"21037","inReplyTo":"20091001120711.GB5583@Pilar.aei.mpg.de","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-10-01T12:22:52Z","receivedAt":"2009-10-01T12:22:52Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Oct 01, 2009 at 02:07:11PM +0200, Carlos R. Mafra wrote:\n\n> On Thu  1.Oct'09 at 13:58:46 +0200, Carlos R. Mafra wrote:\n> > I read the patch. The changes are correct and improve the quality\n> > of the text.\n> \n> From the Portuguese point of view the change below is\n> correct,\n> \n> -cabeçalho Subject: e o resto no corpo.\n> +cabeçalho \"Assunto:\", e o resto no corpo.\n> \n> but I don't know if \"Subject:\" should be translated in\n> this context. Does git-am accept \"Assunto:\" instead\n> of \"Subject:\" if one is using a Portuguese locale?\n\nNo, it doesn't. It must be in English as it is an rfc2822 header. It is\nprobably best for it to remain in English here, then, as we are\nspecifically referring to the literal \"Subject\" mail header, as opposed\nto the more abstract concept of a subject. I think putting it in quotes\nmakes sense, though, to indicate clearly that it is a literal technical\nterm. I.e.:\n\n-cabeçalho Subject: e o resto no corpo.\n+cabeçalho \"Subject:\" e o resto no corpo.\n\nThe patch in my tree has been updated in this way.\n\nThanks, Carlos, for the review.\n\n-Peff\n"},{"id":"124104","messageId":"a4c8a6d00910011535q3d49f6c0l9248edd7bab6bdf8@mail.gmail.com","threadId":"21037","inReplyTo":"20091001122252.GA31919@sigill.intra.peff.net","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Thiago Farina","fromEmail":"tfransosi@gmail.com","sentAt":"2009-10-01T22:35:51Z","receivedAt":"2009-10-01T22:35:51Z","isPatch":true,"sender":{"key":"tfransosi@gmail.com","avatar":"https://avatars.githubusercontent.com/u/970071?v=4"},"body":"Hi,\n\nThanks Jeff to care about my patch and for the review :)\nThanks Carlos for the review too.\n\n-Thiago\n"},{"id":"124213","messageId":"7vhbuek3ma.fsf@alter.siamese.dyndns.org","threadId":"21037","inReplyTo":"1253730339-11146-1-git-send-email-tfransosi@gmail.com","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-10-05T01:53:49Z","receivedAt":"2009-10-05T01:53:49Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Thiago Farina <tfransosi@gmail.com> writes:\n\n> diff --git a/Documentation/pt_BR/gittutorial.txt b/Documentation/pt_BR/gittutorial.txt\n> index 81e7ad7..beba065 100644\n> --- a/Documentation/pt_BR/gittutorial.txt\n> +++ b/Documentation/pt_BR/gittutorial.txt\n> @@ -1,15 +1,15 @@\n>  gittutorial(7)\n>  ==============\n>  \n> -NAME\n> +NOME\n>  ----\n>  gittutorial - Um tutorial de introdução ao git (para versão 1.5.1 ou mais nova)\n>  \n> -SYNOPSIS\n> +SINOPSE\n>  --------\n>  git *\n>  \n> -DESCRIPTION\n> +DESCRIÇÃO\n>  -----------\n\nNot reading Portuguese, I have two comments.\n\n - How well does AsciiDoc and its manpage backend work with these standard\n   section names localized?\n\n - The length of the underline must match the section header word it\n   underlines.\n\nHas anybody actually tried to format this document, either before or after\nyour patch?\n"},{"id":"124226","messageId":"20091005071806.GT32702@genesis.frugalware.org","threadId":"21037","inReplyTo":"7vhbuek3ma.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2009-10-05T07:18:06Z","receivedAt":"2009-10-05T07:18:06Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Sun, Oct 04, 2009 at 06:53:49PM -0700, Junio C Hamano <gitster@pobox.com> wrote:\n> > -NAME\n> > +NOME\n> >  ----\n> >  gittutorial - Um tutorial de introduç??o ao git (para vers??o 1.5.1 ou mais nova)\n> >  \n> > -SYNOPSIS\n> > +SINOPSE\n> >  --------\n> >  git *\n> >  \n> > -DESCRIPTION\n> > +DESCRIÇ??O\n> >  -----------\n> \n> Not reading Portuguese, I have two comments.\n> \n>  - How well does AsciiDoc and its manpage backend work with these standard\n>    section names localized?\n\nAs long as the correct -a lang=foo option is passed to asciidoc, the\ngenerated docbook XML will be valid.\n"},{"id":"124238","messageId":"20091005100910.GA866@coredump.intra.peff.net","threadId":"21037","inReplyTo":"7vhbuek3ma.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-10-05T10:09:10Z","receivedAt":"2009-10-05T10:09:10Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sun, Oct 04, 2009 at 06:53:49PM -0700, Junio C Hamano wrote:\n\n> Not reading Portuguese, I have two comments.\n> \n>  - How well does AsciiDoc and its manpage backend work with these standard\n>    section names localized?\n> \n>  - The length of the underline must match the section header word it\n>    underlines.\n> \n> Has anybody actually tried to format this document, either before or after\n> your patch?\n\nNo, I didn't, and I should have when I picked up the patch in the first\nplace. You are right, asciidoc barfs (both for html and xml generation):\n\n  ERROR: gittutorial.txt: line 5: first section must be named NAME\n  ERROR: gittutorial.txt: line 9: second section must be named SYNOPSIS\n\n-Peff\n"},{"id":"124304","messageId":"20091006094701.GG32702@genesis.frugalware.org","threadId":"21037","inReplyTo":"20091005100910.GA866@coredump.intra.peff.net","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2009-10-06T09:47:01Z","receivedAt":"2009-10-06T09:47:01Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Mon, Oct 05, 2009 at 06:09:10AM -0400, Jeff King <peff@peff.net> wrote:\n> > Has anybody actually tried to format this document, either before or after\n> > your patch?\n> \n> No, I didn't, and I should have when I picked up the patch in the first\n> place. You are right, asciidoc barfs (both for html and xml generation):\n> \n>   ERROR: gittutorial.txt: line 5: first section must be named NAME\n>   ERROR: gittutorial.txt: line 9: second section must be named SYNOPSIS\n\nAh, there is no language config for pt_BR.\n\n$ ls -1 /etc/asciidoc/lang-*\n/etc/asciidoc/lang-de.conf\n/etc/asciidoc/lang-en.conf\n/etc/asciidoc/lang-es.conf\n/etc/asciidoc/lang-fr.conf\n/etc/asciidoc/lang-hu.conf\n/etc/asciidoc/lang-ru.conf\n\nOnce asciidoc will have a lang-pt_BR.conf, we could just use -a\nlang=pt_BR and it would happily accept this input.\n\nThiago, could you make a lang-pt_BR.conf? It's less than 100 lines, so\nit should be easy for you. (If you can send it to the asciidoc list\ndirectly, it's even better.)\n"},{"id":"124316","messageId":"a4c8a6d00910060820se973fcci31c94c42937c7eb2@mail.gmail.com","threadId":"21037","inReplyTo":"20091006094701.GG32702@genesis.frugalware.org","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Thiago Farina","fromEmail":"tfransosi@gmail.com","sentAt":"2009-10-06T15:20:00Z","receivedAt":"2009-10-06T15:20:00Z","isPatch":true,"sender":{"key":"tfransosi@gmail.com","avatar":"https://avatars.githubusercontent.com/u/970071?v=4"},"body":"Hi Miklos,\nOn Tue, Oct 6, 2009 at 6:47 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:\n> On Mon, Oct 05, 2009 at 06:09:10AM -0400, Jeff King <peff@peff.net> wrote:\n>> > Has anybody actually tried to format this document, either before or after\n>> > your patch?\n>>\n>> No, I didn't, and I should have when I picked up the patch in the first\n>> place. You are right, asciidoc barfs (both for html and xml generation):\n>>\n>>   ERROR: gittutorial.txt: line 5: first section must be named NAME\n>>   ERROR: gittutorial.txt: line 9: second section must be named SYNOPSIS\n>\n> Ah, there is no language config for pt_BR.\n>\n> $ ls -1 /etc/asciidoc/lang-*\n> /etc/asciidoc/lang-de.conf\n> /etc/asciidoc/lang-en.conf\n> /etc/asciidoc/lang-es.conf\n> /etc/asciidoc/lang-fr.conf\n> /etc/asciidoc/lang-hu.conf\n> /etc/asciidoc/lang-ru.conf\nIn my system I only have installed lang-es.conf, how I could install the others?\n>\n> Once asciidoc will have a lang-pt_BR.conf, we could just use -a\n> lang=pt_BR and it would happily accept this input.\n>\n> Thiago, could you make a lang-pt_BR.conf? It's less than 100 lines, so\n> it should be easy for you. (If you can send it to the asciidoc list\n> directly, it's even better.)\nSure, I made the lang-pt-BR.conf, and I sent it to asciidoc@googlegroups.com.\n"},{"id":"124353","messageId":"20091008001248.GS32702@genesis.frugalware.org","threadId":"21037","inReplyTo":"a4c8a6d00910060820se973fcci31c94c42937c7eb2@mail.gmail.com","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2009-10-08T00:12:49Z","receivedAt":"2009-10-08T00:12:49Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Tue, Oct 06, 2009 at 12:20:00PM -0300, Thiago Farina <tfransosi@gmail.com> wrote:\n> > $ ls -1 /etc/asciidoc/lang-*\n> > /etc/asciidoc/lang-de.conf\n> > /etc/asciidoc/lang-en.conf\n> > /etc/asciidoc/lang-es.conf\n> > /etc/asciidoc/lang-fr.conf\n> > /etc/asciidoc/lang-hu.conf\n> > /etc/asciidoc/lang-ru.conf\n> In my system I only have installed lang-es.conf, how I could install the others?\n\nThis is with asciidoc 8.5.0, I guess you have a bit older version.\n\n> Sure, I made the lang-pt-BR.conf, and I sent it to asciidoc@googlegroups.com.\n\nGreat, then sooner or later you could have those 'NAME' and 'SYNOPSIS'\nstrings localised. Till then, I would suggest having them in English -\ngit typically supports building with older asciidoc versions.\n"},{"id":"124355","messageId":"a4c8a6d00910072025l179541e1t67b6dd46f20d61d5@mail.gmail.com","threadId":"21037","inReplyTo":"20091008001248.GS32702@genesis.frugalware.org","subject":"Re: [PATCH] Documentation - pt-BR.","fromName":"Thiago Farina","fromEmail":"tfransosi@gmail.com","sentAt":"2009-10-08T03:25:01Z","receivedAt":"2009-10-08T03:25:01Z","isPatch":true,"sender":{"key":"tfransosi@gmail.com","avatar":"https://avatars.githubusercontent.com/u/970071?v=4"},"body":"Hi Miklos,\nOn Wed, Oct 7, 2009 at 9:12 PM, Miklos Vajna <vmiklos@frugalware.org> wrote:\n> On Tue, Oct 06, 2009 at 12:20:00PM -0300, Thiago Farina <tfransosi@gmail.com> wrote:\n>> > $ ls -1 /etc/asciidoc/lang-*\n>> > /etc/asciidoc/lang-de.conf\n>> > /etc/asciidoc/lang-en.conf\n>> > /etc/asciidoc/lang-es.conf\n>> > /etc/asciidoc/lang-fr.conf\n>> > /etc/asciidoc/lang-hu.conf\n>> > /etc/asciidoc/lang-ru.conf\n>> In my system I only have installed lang-es.conf, how I could install the others?\n>\n> This is with asciidoc 8.5.0, I guess you have a bit older version.\nI will check :)\n>\n>> Sure, I made the lang-pt-BR.conf, and I sent it to asciidoc@googlegroups.com.\n>\n> Great, then sooner or later you could have those 'NAME' and 'SYNOPSIS'\n> strings localised. Till then, I would suggest having them in English -\n> git typically supports building with older asciidoc versions.\nMy patch was added to the trunk -\nhttp://hg.sharesource.org/asciidoc/rev/5bc014ab7c52.\n"}]}