Opened 18 years ago
Last modified 16 years ago
#23 new defect
Unicode broken in ncurses / (slang)
| Reported by: | Sam Hocevar | Owned by: | Sam Hocevar |
|---|---|---|---|
| Priority: | critical | Milestone: | Final |
| Component: | core | Version: | SVN |
| Keywords: | Cc: | ||
| Product: | libcaca |
Description
In some terminals (exact list to be investigated) ncurses fails to display Unicode characters even though the terminal is perfectly Unicode-capable.
Change History (5)
comment:1 Changed 18 years ago by
| Priority: | major → critical |
|---|
comment:2 Changed 18 years ago by
| Summary: | Unicode broken in ncurses → Unicode broken in ncurses / (slang) |
|---|
comment:3 Changed 17 years ago by
| Summary: | Unicode broken in ncurses / (slang) → libcaca: Unicode broken in ncurses / (slang) |
|---|
comment:4 Changed 16 years ago by
| Component: | libcaca → core |
|---|---|
| Product: | → libcaca |
| Summary: | libcaca: Unicode broken in ncurses / (slang) → Unicode broken in ncurses / (slang) |
comment:5 Changed 16 years ago by
The situation here:
- By default, my locale is using ISO-8859-15 encoding, gnome terminal expects ISO-8859-15, and both slang and ncurses are broken
- If I tell gnome-terminal to expect UTF-8, slang is OK but not ncurses
- If I use an UTF-8 locale and tell gnome-terminal to expect UTF-8, both are OK
- If I use an UTF-8 locale and tell gnome-terminal to expect ISO-8859-15, both are broken but that's expected :)
So it seems that ncurses recodes its output to current locale encoding while slang does not
Note: See
TracTickets for help on using
tickets.

Replying to sam:
It seems I've the very same issue with SLang, too.