You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Ruby 1.8, string was binary array with no encoding information. But since Ruby 1.9, string are forced to be attached to a specific encoding. That broke the whole simplified Chinese support (the typical "invalid byte sequence in UTF-8").
As Ruby 1.8 was already end-of-life, do we have plan to port deplate to make it Ruby 1.9 compatible?
Thanks!
The text was updated successfully, but these errors were encountered:
As Ruby 1.8 was already end-of-life, do we have plan to port deplate
to make it Ruby 1.9 compatible?
I gave up on making it 1.9 compatible. I might try to make it work with
2.1 again but not now. You could try to use jruby, which IIRC has an 1.8
mode.
In Ruby 1.8, string was binary array with no encoding information. But since Ruby 1.9, string are forced to be attached to a specific encoding. That broke the whole simplified Chinese support (the typical "invalid byte sequence in UTF-8").
As Ruby 1.8 was already end-of-life, do we have plan to port deplate to make it Ruby 1.9 compatible?
Thanks!
The text was updated successfully, but these errors were encountered: