public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jan Kundrát" <jkt@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] i18n project
Date: Sun, 11 Jun 2006 13:17:52 +0200	[thread overview]
Message-ID: <448BFBE0.4040403@gentoo.org> (raw)
In-Reply-To: <1150012630.11071.35.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]

Peter Volkov (pva) wrote:
> On Сбт, 2006-06-10 at 15:11 +0200, Jan Kundrát wrote:
>> a) Translation of metadata.xml stuff in our tree (Is there any method to
>> keep them up-to-date when the English text changes? Something like
>> "revision" attribute that gets bumped when the English text gets updated?)
> 
> While we do not have "version" or "revision" attribute, just drop all
> translations whenever you update English.

Re-adding them again and checking RCS history seems like unnecessary
work to me.

>> c) l10n for other packages and sending patches upstream
>> d) Translation of manpages. man-pages-cs for example sucks :(.
> 
> Do we really need to do this inside Gentoo i18n project? This tasks are
> common for many distributions and should be done outside Gentoo. So just
> translate and send translations upstream.

Nope, that wouldn't be the primary job of the i18n team, just some kind
of task that they might do when they'd be idling otherwise :)

> Fex, to increase the profit from translated GWN
> translated versions should come out together with English one.

Tricky or even impossible one, considering the current time schedule.

> Personally I do not like idea to look at web for package documentation.
> There already exist decision to put all example files somewhere
> into /usr/share. I hope one day this happens and then all translated
> configuration files also can be put there.

While the comments in configuration files are certainly very useful, I
am persuaded that they shouldn't contain more information than the docs
available somewhere else. It's quite common for an administrator to work
on a remote box, possibly with a crappy network connection, and browsing
some doc over web is easier than launching yet another links session
under screen.

Cheers,
-jkt

-- 
cd /local/pub && more beer > /dev/mouth


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

  reply	other threads:[~2006-06-11 11:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 23:37 [gentoo-dev] [RFC] i18n project Diego 'Flameeyes' Pettenò
2006-06-10 13:11 ` Jan Kundrát
2006-06-11  0:16   ` Marius Mauch
2006-06-11  8:25     ` Peter Volkov (pva)
2006-06-11 11:08     ` Jan Kundrát
2006-06-19 15:12       ` Paul de Vrieze
2006-06-19 16:39         ` Jan Kundrát
2006-06-19 17:16           ` Flammie Pirinen
2006-06-20 21:35             ` Mike Frysinger
2006-06-11  7:57   ` Peter Volkov (pva)
2006-06-11 11:17     ` Jan Kundrát [this message]
2006-06-11  8:37   ` Nguyễn Thái Ngọc Duy
2006-06-11 11:20     ` Jan Kundrát
2006-06-12  6:43 ` Flammie Pirinen

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=448BFBE0.4040403@gentoo.org \
    --to=jkt@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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