From: Marc Heiler <shevegen@...>
Date: 2009-12-31T02:26:57+09:00
Subject: Re: ruby 1.9 hates you and me and the encodings we rode in o

If I would have one wish open, I would want to have a compile-time 
option for ruby 1.9 where I could keep the old ruby 1.8 behaviour. Ruby 
1.8 simply gave me less problems here.

I am using loads of umlauts like "辰旦端" in my comments and ruby 1.8 is 
totally happy with it. Ruby 1.9 however hates it, refuses to run it, and 
I dont think I want to add something like "Encoding: ISO-8859-1" to all 
my .rb scripts.

I'd wish there would be more than one way to treat encodings - and one 
way should be to use ruby 1.8 behaviour, because ruby 1.9 just forces me 
to make all kind of changes before my old .rb scripts run again, simply 
because of the encoding issue (there seem to be some other minor changes 
as well, I have had problems in case/when code too, but the encoding 
issue seems larger)

This is not really a rant - I am using ruby 1.8.x without any problem, 
and I actually LOVE that ruby 1.8.x is not feature frozen. It is also 
good that a language can keep evolving.

Personally however I don't need UTF or another exotic encoding, so the 
encoding add-on is of no real advantage to me and rather a burden as I 
have to modify .rb files. I can see that other people have different 
needs. though.
-- 
Posted via http://www.ruby-forum.com/.