From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] i18n herd
Date: Sun, 19 Oct 2003 21:00:23 +0200 [thread overview]
Message-ID: <200310192100.31923.pauldv@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0310191925440.14722@err>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 960 bytes --]
On Sunday 19 October 2003 19:32, Tal Peer wrote:
> Hi,
> I'm currently co-maintaining (with coronalvr) some packages which are used
> by middle-eastern users (namely - fribidi, hspell, bidiv, and i'm probably
> forgetting something here..).
>
> Your comments are more than welcome.
I think one other main issue is the forming of an i18n project. This could be
a subproject of desktop. There are many issues that are similar accross all
i18n targets except US English. Allready look at XIM and the related
complexity. So try to get together other people who are working on i18n. Form
a subproject, and decide together which herds you will use. Just know that
herds normally should have at least 2 maintainers.
Paul
ps. You might also want to look at being a secondary herd for packages that
need i18n specific changes/configuration
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-19 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 17:32 [gentoo-dev] i18n herd Tal Peer
2003-10-19 19:00 ` Paul de Vrieze [this message]
2003-10-20 9:21 ` Tal Peer
2003-10-20 10:47 ` Mamoru KOMACHI
2003-10-22 12:15 ` Alastair Tse
2003-10-20 3:10 ` Luke-Jr
2003-10-21 12:29 ` Paul de Vrieze
2003-10-21 16:55 ` Luke-Jr
2003-10-20 9:01 ` Svyatogor
2003-10-22 7:48 ` Zarick Lau
2003-10-22 9:35 ` Tal Peer
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=200310192100.31923.pauldv@gentoo.org \
--to=pauldv@gentoo.org \
--cc=gentoo-dev@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