From: "Luke-Jr" <luke-jr@gentoo.org>
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] i18n herd
Date: Tue, 21 Oct 2003 12:55:50 -0400 [thread overview]
Message-ID: <006b01c397f4$2eddfb60$5c522b9b@TXOLAB27> (raw)
In-Reply-To: 200310211429.47438.pauldv@gentoo.org
(sorry for the toppost; at baka windoze PC right now and Outlook Express
makes anything else impossible)
m17n is multilingualization. Basicly, it's i18n, but having support for all
languages without restarting the application. For example, a m17n-compatible
text editor would let you mix languages within a single document (and
possibly even let you change interface language on the fly, though that
might need a restart of the app).
----- Original Message -----
From: "Paul de Vrieze" <pauldv@gentoo.org>
To: <gentoo-dev@gentoo.org>
Sent: Tuesday, October 21, 2003 8:29 AM
Subject: Re: [gentoo-dev] i18n herd
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 20 October 2003 05:10, Luke-Jr wrote:
> >
> > a) Creating a general i18n herd for all i18n-related packages (the cjk
> > herd could probably be merged into that).
>
> I'd much rather a m17n herd to focus on having all the languages work at
> once... i18n is pretty undesirable, IMO, since it makes systems different.
What is m17n? If it is about internationalisation it makes sense to include
it
in the project, but I leave that to the people who are going to do the work.
>
> > b) Creating specialized herds for each region/language group - ie.
> > middle-east, cjk, anything else?
>
> That probably makes more sense since such stuff could probably be handled
> better by those who understand the language. But then, some packages
> involve every language so it might get a bit messy...
That's why I suggested creating a project for all, and having herds for
specific languages. Many issues are similar for any language != US English.
The XIM specification is the same for any language. However, specific IM's
are often only easilly maintained by people who use it (allready because the
English docs of such things are either lacking or horrible in most cases)
Paul
- --
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/lSa5bKx5DBjWFdsRAqJTAJ4xFMgfkm6th7FMaiPkRlj474ouRwCg2RPh
rvZkffenL4EMm4GCsgzpog8=
=GUsl
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-10-21 16:44 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
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 [this message]
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='006b01c397f4$2eddfb60$5c522b9b@TXOLAB27' \
--to=luke-jr@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