[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#680648: [BRLTTY] Bug#680648: brltty: A new accent problem

Dave Mielke, le Sat 07 Jul 2012 13:54:18 -0400, a écrit :
> [quoted lines by Samuel Thibault on 2012/07/07 at 14:04 -0300]
> >Jean-Philippe MENGUAL, le Sat 07 Jul 2012 16:04:06 +0200, a écrit :
> >>    * What led up to the situation? I use brltty running orca on gdm3.
> >> 
> >>    * What was the outcome of this action? "L'??cran n'est pas en mode texte"
> As it appears to me, the message is being translated correctly except for one 
> letter - the é. Is that correct?

Yes, most probably because it is non-ascii.

> If yes, do we know what it's being translated to?


> I've checked, and the translation looks correct within the fr.po file.
>    msgid "screen not in text mode"
>    msgstr "L'écran n'est pas en mode texte"

Agreed, that's what I meant.

> >It seems that the message returned by the screen driver when the screen
> >is not readable does not get properly decoded by the core. Dave?
> 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 to 
> mbstowcs().

Except that the end result is not correct for some reason.


Reply to: