All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Peter Krefting <peter@softwolves.pp.se>
Cc: Dill <sarpulhu@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Translations [of Documentation] in Git release?
Date: Mon, 26 Jan 2009 16:31:17 +0100	[thread overview]
Message-ID: <200901261631.18157.jnareb@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0901261426350.7798@ds9.cixit.se>

On Mon, 26 Jan 2009, Peter Krefting wrote:
> Jakub Narebski wrote:
> 
> > With GUI translations we just use gettext conventions. I don't know
> > any such convention for docs:
> 
> There is a lot of documentation being translated using PO files. po4a -
> http://po4a.alioth.debian.org/ - is a nice starting point for that.

I'm not sure if XLIFF wouldn't be better format to use to translate
_documents_.  Gettext was meant to translate, I think, not very long
messages in programs.

Also I am not sure how much support this idea has. True, in last Git
User's Survey[1] 63% to 76% wanted (parts of) Documentation... but that
was out of 325 people who answered this question, with 3236 responses
to survey in total, so numbers are more like 6% - 8%.

[1] http://git.or.cz/gitwiki/GitSurvey2008
[2] http://translate.sourceforge.net/wiki/

-- 
Jakub Narebski
Poland

  parent reply	other threads:[~2009-01-26 15:32 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 [this message]
2009-01-26 16:23       ` Mike Hommey
2009-01-26 19:30         ` Sverre Rabbelier
2009-01-27  7:01           ` Peter Krefting
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=200901261631.18157.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peter@softwolves.pp.se \
    --cc=sarpulhu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.