Does linking libcurses-ruby against ncursesw break legacy ASCII-only ncurses applications? I suspect not, but I could be wrong.
Using a ruby ncurses library linked against ncursesw isn't *sufficient* for an app to magically work with non-ASCII encodings, as you illustrate. However, it is *necessary*. If legacy apps aren't broken, then I don't see a reason to produce a separate libncursesw-ruby package. Also, to clarify the situation wrt Sup, and other Ruby ncurses programs: under Ruby 1.9, they can finally correctly slice, modify, determine the length in characters of, etc. non-ASCII strings. But even under 1.9, Ruby ncurses applications won't be able to correctly display non-ASCII strings without access to the wcwidth and wcswidth functions, which AFAIK aren't actually provided by any common Ruby library anywhere. FWIW. -- William <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
