> ncurses-ruby should be linked against libncursesw? (Namely, it would
> enable multibyte Ruby curses programs,
No. It would enable ruby curses programs that use "wide character"
strings. Programs that use multi-byte character strings such as UTF-8
strings would still not run correctly. See my des
What's the status of this? Do you not buy my arguments about why
ncurses-ruby should be linked against libncursesw? (Namely, it would
enable multibyte Ruby curses programs, and it wouldn't break anything.)
Or are you, or anyone else, planning on producing a ncursesw-ruby?
--
William
--
To UNS
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 *necessar
Adeodato Simó suggests to follow through with the suggestion of this bug
report and link ncurses-ruby against ncursesw instead of ncurses because
he has observed that the sup email program will display non-ascii
characters better on a utf-8 terminal when linked like that.
I am the upstream author
Hello,
I don't really use the ncurses-ruby library, but I wanted to try the
"sup" mailed which is written in Ruby and makes use of this library.
Unfortunately, non-ASCII characters were not rendered correctly.
Applying the patch provided by Micah Anderson to ncurses-ruby 1.1-3
solved the renderin
5 matches
Mail list logo
