Would the resulting module still work with terminals in other character
encodings?
i think so, at least my test ncurses_bin.so linked against both libncursesw.so
and libncurses.so.5 does work without problems in my non-utf8 terminal (at
least the hello_world example).
I have tried out the stock ncurses-ruby, i.e. presumably "without"
unicode support on a terminal set so UTF-8 Unicode character encoding.
All examples work fine with the stock version on the unicode terminal.
An exception are the forms examples. They do not allow input of
non-ascii characters.
Therefore I have applied the patch and used the "unicode supporting"
ncurses-ruby module to try out the examples.
I do not see any differences of behaviour. Non-ascii characters are
still not allowed in the forms examples.
Therefore, I do not see a compelling reason why to make the switch.
Perhaps the reporter of this whishlist item can shed some light on this
issue and show what the difference is. Otherwise, I'd suggest to close
this item.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
