From: Miklos Vajna <vmiklos@frugalware.org>
To: Thiago Farina <tfransosi@gmail.com>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Documentation - pt-BR.
Date: Thu, 8 Oct 2009 02:12:49 +0200 [thread overview]
Message-ID: <20091008001248.GS32702@genesis.frugalware.org> (raw)
In-Reply-To: <a4c8a6d00910060820se973fcci31c94c42937c7eb2@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
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.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-10-08 0:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 18:25 [PATCH] Documentation - pt-BR Thiago Farina
2009-09-30 22:18 ` Thiago Farina
2009-10-01 8:02 ` Jeff King
2009-10-01 8:16 ` Jeff King
2009-10-01 11:58 ` Carlos R. Mafra
2009-10-01 12:07 ` Carlos R. Mafra
2009-10-01 12:22 ` Jeff King
2009-10-01 22:35 ` Thiago Farina
2009-10-05 1:53 ` Junio C Hamano
2009-10-05 7:18 ` Miklos Vajna
2009-10-05 10:09 ` Jeff King
2009-10-06 9:47 ` Miklos Vajna
2009-10-06 15:20 ` Thiago Farina
2009-10-08 0:12 ` Miklos Vajna [this message]
2009-10-08 3:25 ` Thiago Farina
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=20091008001248.GS32702@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=tfransosi@gmail.com \
/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).