From: "Gonçalo Silva" Date: 2011-10-22T07:28:58+09:00 Subject: [ruby-core:40264] Re: Counseling --002215b0316246e66604afd69964 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all, -Ku allows one to specify the UTF-8 as the default encoding for strings and default_external. Check the man page. While I believe that this is a necessary evil for the real encoding support that ruby currently provides, it would be great to have a compile time flag to revert back to the old behavior (or something similar). I don't think this is implemented, but I could be wrong. Gon=E7alo On Fri, Oct 21, 2011 at 23:21, Haase, Konstantin < Konstantin.Haase@student.hpi.uni-potsdam.de> wrote: > What's your $LC_CTYPE? What OS are you on? > > Konstantin > > On Oct 21, 2011, at 09:43 , Perry Smith wrote: > > > Ruby and I are back in counseling... Its always the same thing with he= r. > "I'm throwing an Encoding exception!!!" > > > > Every time I install a gem like thin, I have to remember to go and edit > the script to add in the -KU. I sprinkle -KU like 12 step programs sprin= kle > mottos. > > > > It really has been an extremely frustrating and draining experience. > Ruby is no longer the love of my life. > > > > Rails, thin, rvm, almost nothing is really and truly ruby 1.9 compliant > -- not really. Not when you include all the encoding problems that are > still very common in my life and I assume in the life of anyone trying t= o > use Ruby in any serious fashion. > > > > Is there a compile time option (or can one be added) that says "I don't > care!!! -- just cram the two strings together and eat your spinach!" > Because, ultimately, I've yet to find anything except ruby that actually > cares. > > > > Thank you, > > pedz > > > > > > > --002215b0316246e66604afd69964 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,

-Ku allows one to specify the UTF-8 as the defau= lt encoding for strings and default_external. Check the man page.

While I believe that this is a necessary evil for the real = encoding support that ruby currently provides, it would be great to have a = compile time flag to revert back to the old behavior (or something similar)= . I don't think this is implemented, but I could be wrong.

Gon=E7alo

On F= ri, Oct 21, 2011 at 23:21, Haase, Konstantin <Konstantin.Haase@st= udent.hpi.uni-potsdam.de> wrote:
What's your $LC_CTYPE? What OS are you = on?

Konstantin

On Oct 21, 2011, at 09:43 , Perry Smith wrote:

> Ruby and I are back in counseling... =A0Its always the same thing with= her. =A0"I'm throwing an Encoding exception!!!"
>
> Every time I install a gem like thin, I have to remember to go and edi= t the script to add in the -KU. =A0I sprinkle -KU like 12 step programs spr= inkle mottos.
>
> It really has been an extremely frustrating and draining experience. = =A0Ruby is no longer the love of my life.
>
> Rails, thin, rvm, almost nothing is really and truly ruby 1.9 complian= t -- not really. =A0Not when you include all the encoding problems that are= still very common in my life and I assume =A0in the life of anyone trying = to use Ruby in any serious fashion.
>
> Is there a compile time option (or can one be added) that says "I= don't care!!! -- just cram the two strings together and eat your spina= ch!" =A0Because, ultimately, I've yet to find anything except ruby= that actually cares.
>
> Thank you,
> pedz
>
>



--002215b0316246e66604afd69964--