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
JRuby has had a limitation up through JRuby 9.1.x where some indentifiers which do not properly map to a Java charset are not possible beacuse internally we store all identifiers as Java Strings.
The solution to this is partially to move as much internally to using ByteList as we can. For things where this would not work out well we will still use java.lang.String but we will store those strings as an iso_8859_1 raw piece of data. Anything which accesses those String will need also to have their encoding and if they don't we will assume they are utf-8 data. This largely will allow things we could not do in the past to start working but things from the past which did work will still work since pretty much everything is utf-8.
Current work in progress for this feature is happening on bytelist_love. This feature should still figure out all issues reported against encoding issues and attach them to this issue.
Closing this feature (should have for 9.2.0.0). Only #3688 is not fixed and it is targetted for 9.2.1.0. I will look into it (it might not even technically be part of this...unsure).
JRuby has had a limitation up through JRuby 9.1.x where some indentifiers which do not properly map to a Java charset are not possible beacuse internally we store all identifiers as Java Strings.
The solution to this is partially to move as much internally to using ByteList as we can. For things where this would not work out well we will still use java.lang.String but we will store those strings as an iso_8859_1 raw piece of data. Anything which accesses those String will need also to have their encoding and if they don't we will assume they are utf-8 data. This largely will allow things we could not do in the past to start working but things from the past which did work will still work since pretty much everything is utf-8.
The text was updated successfully, but these errors were encountered: