The tree is now utf-8 clean. Or it is to the extent that a computer can
reasonably determine... If the relevant people are prepared to smack
anyone who refuses to play nice then now would be a good time to
unwithdraw GLEP 31, make compliance mandatory and add glep31check [1] to
repoman or server-side.

There are still a few instances of munged character sequences that
happen to also be valid UTF-8. If you come across one, feel free to fix
it.

If you have weird characters in your name, please make especially sure
that you're getting your ChangeLog name right. These are far more common
than occasional user credit ChangeLog entries. Also, if your name on the
devlist [2] isn't accented, pester someone to update it.

Something strange I noticed... Some people are using funny quotes and
non breaking spaces in ebuilds. Some people are using weird characters
as substitution delimiters for sed. Don't! It will break on many
systems. I'm going to go and purge all of those, UTF-8 or not, whenever
my brain recovers.

As far as editor support... On those really rare occasions when you need
to enter UTF-8 text in ebuilds, vim, emacs and nano should all more or
less work. For ChangeLogs, echangelog is utf-8 transparent, meaning if
you run it from a UTF-8 terminal it should be ok. We have a guide [3] if
you want to know more...

[1]: http://dev.gentoo.org/~ciaranm/toys/glep31check-0.3.3.tar.bz2
[2]: http://www.gentoo.org/proj/en/devrel/roll-call/userinfo.xml
[3]: http://www.gentoo.org/doc/en/utf-8.xml

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm