[ruby-core:25325] Re: [Feature #2034] Consider the ICU Library for Improving and Expanding Unicode Support

On Thu, Sep 3, 2009 at 18:30, Run Paint Run Run<[e-mail]> wrote:
> Issue #2034 has been updated by Run Paint Run Run.

>>> If ICU is unfeasible, I'd appreciate understanding why.

>> It converts everything to UTF-16 internally.

> Thank you, Nikolai. I understand how that would make its conversion or transliteration APIs problematic, but for property lookup/resolution would it not be easier to use its functions that accept a codepoint than write our own? Or is it just a downside of the CSI model that String methods can't work correctly with Unicode? (As ever, I apologise for using the BTS to ask questions, but I don't know where else I can).

I’m not quite sure that I understand what you mean, but I see no
reason for Ruby not supporting what you want by itself.  I mean, it’s
mostly table lookups and stuff like that.  Most of the necessary stuff
is available in my library [1].  It’s based on the code in GLib,
however, and they haven’t gotten back to me on possibility of allowing
us to use it in Ruby (since GLib uses LGPL and Ruby uses it’s own
license and since my code is a rewrite with GLib as a reference…well,
licensing is a quagmire).

[1] http://git.bitwi.se/?p=ruby-character-encodings.git;a=summary