Bug#680648: [BRLTTY] Bug#680648: brltty: A new accent problem
[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 to?
>> 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
>Except that the end result is not correct for some reason.
Is there a problem if the .po file specifies:
"Content-Type: text/plain; charset=UTF-8\n"
but the user isn't using a UTF-8 locale?
In other words, I'm theorizing that our translations are stored - and returned
- in UTF-8, but mbstowcs() is using the locally-specified system encoding.
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario | 2011 May 21 is the End of Salvation.
EMail: firstname.lastname@example.org | Canada K2A 1H7 | http://Mielke.cc/now.html
http://FamilyRadio.com/ | http://Mielke.cc/bible/