Hi,
>>. Doing braille translation on the server side would be
>> repeating the design mistake that X11 did decades ago.
Related to calling liblouis/brltty, in our application we extract the
text and follows the following call sequence
example text: "The abc"
1. lou_translate ("The abc") => "! abc"
2. The 16 bit integer array output buffer from above call to copied to 8
bit char array. Each letter/pointer value is casted from int to char.
3. Calls brlapi_writeTextWin(). Looks like it display the right info.
>>doing braille translation on server side.. can you please clarify it
is the brltty_server using en-us-g2.ctb ?
siju
On Sun, Aug 25, 2013 at 8:31 AM, Samuel Thibault <
[email protected]> wrote:
> Siju Samuel, le Thu 22 Aug 2013 18:16:54 -0500, a écrit :
> > >> BRLTTY already handles this range so it should be possible to pass it
> > directly
> > >> as the text to be written.
> >
> > So.. does this suggest no need to call libLouise
> and brlapi_writeDots(),
> > instead
> > just call bailApi_writeTextWin() after setting the translation table
> > as en-us-g2.ctb in brltty?
>
> No, he means that you can call liblouis, which gives you unicode
> braille, and you can simply pass that to brlapi_writeText() without any
> conversion. Doing braille translation on the server side would be
> repeating the design mistake that X11 did decades ago.
>
> Samuel
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: [email protected]
> For general information, go to: http://mielke.cc/mailman/listinfo/brltty
>
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: [email protected]
For general information, go to: http://mielke.cc/mailman/listinfo/brltty
