From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] i18n project
Date: Sun, 11 Jun 2006 15:37:58 +0700 [thread overview]
Message-ID: <fcaeb9bf0606110137r7d6a4d32kd9bbc1b6754d6df1@mail.gmail.com> (raw)
In-Reply-To: <448AC516.2070003@gentoo.org>
On 6/10/06, Jan Kundrát <jkt@gentoo.org> wrote:
> So, let's rephrase it a bit. The following items represent my view about
> the i18n team's responsibilities:
>
> 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?)
Keep only English in metadata.xml. Using tools such as intltool or
xml2po to extract strings and let i18n translate/maintain .po files
themselves. Generated .mo files will be included in metadata directory
when rsycing. Another portage hack to use .mo files in metadata
directory instead of plain English if locale variables is not C.
But that's just part of the problem. What about strings inside ebuild?
--
Bi Cờ Lao
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-11 8:42 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
2006-06-11 8:37 ` Nguyễn Thái Ngọc Duy [this message]
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=fcaeb9bf0606110137r7d6a4d32kd9bbc1b6754d6df1@mail.gmail.com \
--to=pclouds@gmail.com \
--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