git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Jean-Noël AVILA" <avila.jn@gmail.com>
To: rsbecker@nexbridge.com, Junio C Hamano <gitster@pobox.com>
Cc: "'Ævar Arnfjörð Bjarmason'" <avarab@gmail.com>, git@vger.kernel.org
Subject: Re: [Question] Translation Dictionary
Date: Thu, 03 Feb 2022 20:59:08 +0100	[thread overview]
Message-ID: <11498572.Kui42GGras@cayenne> (raw)
In-Reply-To: <xmqqwnibvmtf.fsf@gitster.g>

On Thursday, 3 February 2022 19:15:24 CET Junio C Hamano wrote:
> <rsbecker@nexbridge.com> writes:
> 
> > I would even suggest that gitglossary(7) might ultimately be
> > deprecated particularly on systems without 'man(1)'.
> 

I'd rather gitglossary and `git glossary` did not compete and they could share 
their translations.


> Yes, I think the entries in the "git help -w glossay" are good
> things to have in the dictionary.  I thought there are folks who are
> already translating our manual pages (perhaps with po4a if I recall
> correctly but I may be misremembering)?
> 
> Thanks.
> 

Yes, there are. You can find the project at 
https://github.com/jnavila/git-manpages-l10n

The Portuguese is fully translated, gitglossary included.

This makes me think that translating gitglossary should come first, in order to 
set the standard for the other manpages.




  reply	other threads:[~2022-02-03 19:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 19:35 [Question] Translation Dictionary rsbecker
2022-02-03  9:37 ` Jean-Noël Avila
2022-02-03  9:54   ` Ævar Arnfjörð Bjarmason
2022-02-03 13:27     ` rsbecker
2022-02-03 18:06       ` Ævar Arnfjörð Bjarmason
2022-02-03 18:15       ` Junio C Hamano
2022-02-03 19:59         ` Jean-Noël AVILA [this message]
2022-02-03 21:33           ` Junio C Hamano
2022-02-03 23:45             ` rsbecker
2022-02-03 12:58   ` rsbecker

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=11498572.Kui42GGras@cayenne \
    --to=avila.jn@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=rsbecker@nexbridge.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).