So, as someone might have read in my blog[1] I've been thinking for a couple 
of days about creating an i18n project.

What would an i18n project be needed for? Mainly, to try to provide to our 
non-English native users a more friendly environment. We discussed many times 
in the past about making simpler having UTF-8 support, or even enabling it by 
default, but of course it's difficult to handle this right now, and this is 
not the only concern.

What I have in mind is establishing some kind of team that would collaborate 
with the current doc translators that would like to help, trying to get other 
parts of Gentoo accessible to non-English speakers. Translating man pages for 
Gentoo-specific software, making Portage and other gentoo-specific packages 
i18n-capable and translating them, translating forums (I think the Forums 
stuff already handle that, but maybe it would help if we're able to get a 
more "complete" team).

Least but not last, also translating software that's missing translator, like 
I did for xine-lib/xine-ui/gxine and Italian this week, or at least 
release "poupdate" tarballs with translations updated from CVS when the ones 
in the releases are obsolete.

This might also help to find a "home" to utf8 and cjk herds, for instance.

I'm actually going to work to add to Portage (will-be-2.2) i18n capabilities 
next week, and I'll be doing for sure the Italian translation.

Comments, thoughts, translation, are all welcome :)

[1] 
http://farragut.flameeyes.is-a-geek.org/articles/2006/06/08/do-we-need-an-i18n-project
-- 
Diego "Flameeyes" Pettenò - http://farragut.flameeyes.is-a-geek.org/
Gentoo/Alt lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE