Encoding Problem (I think)

ruby-talk
1

I've been trying to figure out why gash won't work under Ruby 1.9. I
posted this issue:

  https://github.com/judofyr/gash/issues/4

In brief, it looks like strings contain "\x00" where as under Ruby 1.8
those were "\000" instead.

Am I right then that this is an encoding error, and if so how in the
word do I fix it? I.e. how do I get "\000"s back?

Thanks.

2

I aways have encoding problems doing screen scrapping, and I'm interested in better solutions, but sometimes iconv helps me.

Att
Thiago Alessio

···

Sent from my iPhone

On May 30, 2011, at 1:02 AM, Intransition <transfire@gmail.com> wrote:

I've been trying to figure out why gash won't work under Ruby 1.9. I
posted this issue:

1.9 Error · Issue #4 · judofyr/gash · GitHub

In brief, it looks like strings contain "\x00" where as under Ruby 1.8
those were "\000" instead.

Am I right then that this is an encoding error, and if so how in the
word do I fix it? I.e. how do I get "\000"s back?

Thanks.

3

Hi,

···

In message "Re: Encoding Problem (I think)" on Mon, 30 May 2011 13:02:59 +0900, Intransition <transfire@gmail.com> writes:

I've been trying to figure out why gash won't work under Ruby 1.9. I
posted this issue:

1.9 Error · Issue #4 · judofyr/gash · GitHub

In brief, it looks like strings contain "\x00" where as under Ruby 1.8
those were "\000" instead.

Am I right then that this is an encoding error, and if so how in the
word do I fix it? I.e. how do I get "\000"s back?

I don't call it an "encoding error", but I admit it is
incompatibility. I am not sure where we should fix. Need more
investigation.

              matz.