bts tags 680648 + fixed-upstream
thanks
Dave Mielke, le Sun 08 Jul 2012 10:37:49 -0400, a écrit :
> In any event, setScreenMessage() has now (revision 6587) been
> converted to use mbrtowc(). Please test.
That now works indeed. The severity of the bug is quite minor however,
so concerning Debian
[quoted lines by Dave Mielke on 2012/07/08 at 08:53 -0400]
>[quoted lines by Samuel Thibault on 2012/07/07 at 16:17 -0300]
>
>>Where is convertTextToWchars called? What I see in the driver in
>>readCharacters_LinuxScreen() is a call to setScreenMessage which just
>>uses strlen() and copyScreenCha
[quoted lines by Samuel Thibault on 2012/07/07 at 16:17 -0300]
>Where is convertTextToWchars called? What I see in the driver in
>readCharacters_LinuxScreen() is a call to setScreenMessage which just
>uses strlen() and copyScreenCharacterText() without taking charset into
>account.
The message b
Paul Gevers, le Sun 08 Jul 2012 09:17:43 +0200, a écrit :
> Stupid question maybe, and I have not checked myself yet, but have
> people verified that the po file itself is indeed utf-8?
Again, it is, yes. All other messages are just fine, it's only this one
which doesn't show up fine (and all mess
Dave Mielke, le Sat 07 Jul 2012 14:57:00 -0400, a écrit :
> [quoted lines by Samuel Thibault on 2012/07/07 at 15:10 -0300]
>
> >> If yes, do we know what it's being translated to?
> >é
>
> That's what it's supposed to be. I guess I should've asked if we know what
> it's
> being mistranslated t
Dave Mielke, le Sat 07 Jul 2012 13:54:18 -0400, a écrit :
> The code looks correct to me. The screen driver already calls gettext(), so
> the
> message as rturned by the screen driver is already translated. Then it gets
> translated into wchars via brltty's convertTextToWchars(), which is mapped
