FreeBSD's new console project is almost ready for primetime

First, let's be clear that I think it is dandy to address this shortcoming.

Having said that, and the tiny sprinkling of FreeBSD workstations aside, who uses the local text-mode console in a FreeBSD server for anything aside from dealing with hardware failure and dealing with a boot process which has gone awry?

All my text mode interaction with FreeBSD servers is through ssh, whether from a text mode terminal (very occasionally) or using an X terminal (most of the time). Does this change have any effect on that at all? Because it appears to work fine as is.

[2][root@fnjomega ~/unitest]# locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_ALL=
[2][root@fnjomega ~]# mkdir unitest
[2][root@fnjomega ~]# cd unitest
[2][root@fnjomega ~/unitest]# touch ͲͻΉΏπξηθ
[2][root@fnjomega ~/unitest]# cat > ЉЏГЯШ
now is the time
[2][root@fnjomega ~/unitest]# ls -l
total 4
-rw-r--r-- 1 root wheel 0 Jun 26 09:07 ??ΉΏπξηθ
-rw-r--r-- 1 root wheel 16 Jun 26 09:08 ЉЏГЯШ
[2][root@fnjomega ~/unitest]# cat ЉЏГЯШ
now is the time
[2][root@fnjomega ~]# rm ͲͻΉΏπξηθ
[2][root@fnjomega ~/unitest]#

I'm guessing the "??" in the Greek string above is a font shortcoming rather than a basic problem using unicode in bash on FreeBSD.