Project

General

Profile

Bug #975

ruby curses extension does not support multibyte characters

Added by hramrach (Michal Suchanek) over 11 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
ruby -v:
Backport:
[ruby-core:21094]

Description

=begin
ncurses supplies a ncursesw library that works as drop-in replacement for the ncurses with added multibyte character support. Just updating the library test enables printing UTF-8 for me.

test (run with ruby -KU) in utf-8 locale:

require 'curses'

test_string = "あ"

Curses.init_screen

Curses.addstr test_string

Curses.refresh

Curses.getch

Curses.close_screen

STDOUT.puts test_string
=end


Files

cursesw.patch (864 Bytes) cursesw.patch a patch to add transparent multibyte support with ncurses hramrach (Michal Suchanek), 01/04/2009 03:18 AM
#1

Updated by matz (Yukihiro Matsumoto) over 11 years ago

=begin

In message "Re: [ruby-core:21094] [Bug #975] ruby curses extension does not support multibyte characters"
on Sun, 4 Jan 2009 03:17:20 +0900, Michal Suchanek redmine@ruby-lang.org writes:

|ncurses supplies a ncursesw library that works as drop-in replacement for the ncurses with added multibyte character support. Just updating the library test enables printing UTF-8 for me.

As far as I know, ncursesw is NOT a drop-in replacement. It has whole
new API around cchar_t, wchar_t and wint_t, e.g. wadd_wch in place of
waddch. Am I missing something?

                        matz.

=end

#2

Updated by hramrach (Michal Suchanek) over 11 years ago

=begin
On 03/01/2009, Yukihiro Matsumoto matz@ruby-lang.org wrote:

In message "Re: [ruby-core:21094] [Bug #975] ruby curses extension does not support multibyte characters"

on Sun, 4 Jan 2009 03:17:20 +0900, Michal Suchanek <redmine@ruby-lang.org> writes:

|ncurses supplies a ncursesw library that works as drop-in replacement for the ncurses with added multibyte character support. Just updating the library test enables printing UTF-8 for me.

As far as I know, ncursesw is NOT a drop-in replacement. It has whole
new API around cchar_t, wchar_t and wint_t, e.g. wadd_wch in place of
waddch. Am I missing something?

Yes.

You do not need to use that additional wide character API to get utf-8
characters printed on the screen.

Thanks

Michal

=end

#3

Updated by matz (Yukihiro Matsumoto) over 11 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

=begin
Applied in changeset r21508.
=end

Also available in: Atom PDF