From: Michael Selig Date: 2008-10-27T08:48:39+09:00 Subject: [ruby-core:19526] Re: Default source encoding (Was: [Bug #680] csv.rb: CSV.parse is toolate when encoding is mismatch) On Sat, 25 Oct 2008 00:07:13 +1100, James Gray wrote: > However, I can give a very real counter example to your scripts moving > environment example. I work on TextMate and we use Ruby all over the > place inside that application. I'm sure we have hundreds of scripts in > there. We try hard to make sure everything in TextMate is UTF-8, so now > we get errors out of Ruby 1.9. To fix, we need to add hundreds of magic > comments and worse, train our users who often write their own > automations in Ruby why they have to do the same to make their code > work. So in our case, a default to UTF-8 or the local encoding would be > a huge win. I too have been concerned about 1.8 script compatibility regarding encodings. For my own interest, can you explain a bit more about what goes wrong with these scripts in 1.9? I know absolutely nothing about Textmate. Do they contain multibyte string literals? Cheers Mike