git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Krefting <peter@softwolves.pp.se>
To: Git Mailing List <git@vger.kernel.org>
Cc: Mike Hommey <mh@glandium.org>, Jakub Narebski <jnareb@gmail.com>,
	Dill <sarpulhu@gmail.com>,
	Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: Translations [of Documentation] in Git release?
Date: Tue, 27 Jan 2009 08:01:53 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0901270800100.26770@ds9.cixit.se> (raw)
In-Reply-To: <bd6139dc0901261130ic64f767gddc960ebe3dfecf2@mail.gmail.com>

Sverre Rabbelier:

> Perhaps the basics can be translated at least, the documents that do
> not require much change because they represent stable concepts?

I usually start out translating the program output, then manual pages,
and then, time permitting, documentation.

Git is a bit special in that regard since "--help" gets hardwired to
display the manual page, so one can't just translate the help screen.

-- 
\\// Peter - http://www.softwolves.pp.se/

  reply	other threads:[~2009-01-27  7:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-25 17:41 Translations in Git release? Dill
2009-01-25 18:54 ` Jeff King
2009-01-26  9:54 ` Johannes Gilger
2009-01-26 10:07   ` Peter Krefting
2009-01-26 12:31 ` Translations [of Documentation] " Jakub Narebski
2009-01-26 13:27   ` Peter Krefting
2009-01-26 13:34     ` Miklos Vajna
2009-01-26 15:31     ` Jakub Narebski
2009-01-26 16:23       ` Mike Hommey
2009-01-26 19:30         ` Sverre Rabbelier
2009-01-27  7:01           ` Peter Krefting [this message]
2009-01-27 11:16             ` Jakub Narebski
2009-01-27 14:45               ` Peter Krefting
2009-01-26 19:58       ` Dill
2009-01-26 20:38         ` Junio C Hamano

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=Pine.LNX.4.64.0901270800100.26770@ds9.cixit.se \
    --to=peter@softwolves.pp.se \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=mh@glandium.org \
    --cc=sarpulhu@gmail.com \
    --cc=srabbelier@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).