On 23-dec-2005, at 15:23, Jamis Buck wrote:
On Dec 23, 2005, at 3:49 AM, Thijs Van Der Vossen wrote:
Please, please, don't ignore this issue because David said that
i18n should be handled at the application level.
One more time, and then I sign out of this thread for good:
The rails team is NOT ignoring this issue. Rather, the rails team
is waiting for someone with i18n chops to come up with a decent
solution. If that person is you, then we're waiting for you to fix
the problem. If that person is not you, then you're in the same
boat we are.
That person is the collective consciense :-) Jamis, thanks for
chiming in.
I don't know if it's understandable - I just wanted someone to say
that it's indeed broken (I got nasty because I wanted to show that
it's also broken in Basecamp et al.)
Let's start simply : why don't we assume $KCODE = 'UTF-8' for test
environment in Rails so that you don't need to sandbox every Rails
test that has to do with multibyte characters? (i.e. embrace the fact
that most of the text in the world is mulibyte). So that you can type
wonky literals right in the test cases and see which stuff brakes
quickly, without starting an extra interpreter every time you want to
truncate a string? This would be the step 0 in the right direction. I
am not sure, but I assume all 37's apps run with that setting.
--
Julian 'Julik' Tarkhanov
me at julik.nl
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
