Package: rolo
Severity: important

Hi,

UTF-8 in rolo is broken, lines including UTF-8 are simply not displayed.

Build-depending on libncursesw5-dev and linking against menuw and formw
(libncursesw5) instead of menu and form (libncurses5) fixes this partly.

The following example shows what would be displayed after linking against menuw
and formw when one decorates entry 26 of the example file with umlauts. As you
can see, the beginning of the columns is messed up. This example is when entry
26 is selected, if it is not selected the telephone number is displayed
correctly but the other columns look still like in this example.

  25 Thomson      Nigel        [email protected]                  
+420-2607-1234-123
- 26 Träcy       Richürd     [email protected]öm                +1-555-222-0001   
  27 Winter       Alex         [email protected]                +1-413-545-2911

Fixing this probably requires something like g_utf8_strlen(str, -1), which is
included in glib but can easily be reimplemented, to be used instead of strlen
(or whatever rolo uses for detecting the number of characters of the string).
Alternatively mbstowcs(NULL, str, 0) should also work but I did not use this to
determine the number of characters of strings until now, so I can't be sure.

Correctly displaying columns when using double wide characters (e.g. タ) will
not work when g_utf8_strlen(str, -1) or mbstowcs(NULL, str, 0) is used since
they return the number of characters instead of the number of columns needed to
display a string.  Maybe you find a sane way to fix get the number of columns
needed, e.g. by combining mbstowcs() and wcswidth().  I don't consider the wide
character support to be a part of this bug report.

I'd be happy when you would at least link against menuw and formw, feel free to
set the severity of this bug to minor when the linking has been done but
correctly displaying the columns has not yet been implemented.


Regards
Carsten



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to