Aura Kelloniemi, le jeu. 15 avril 2021 13:19:26 +0300, a ecrit: > brlapi__writeText, which pads/truncates the output as necessary. > > But this function cannot be called safely from languages that are Unicode > only.
As mentioned previously, we can add a brlapi_writeUtf8Text, just like we already have brlapi_writeWText > > > Also, this does not need to break the protocol, because padding can be > applied > > > in the C client library. > > > No, because the display may have changed size in between, so the padding > > will not be enough. > > Isn't this always the case? The display size can always change while the > application renders the output or BrlAPI processes it. brlapi__writeText works > this way – it does the padding/truncation on the client side. And it shouldn't :) > I guess that if the display size changes, the write operation either > fails or is applied partially (or part of the display won't be > refreshed). It will be applied partially, the application will receive a parameter update, and re-submit the write, possibly with more text, then. 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://brltty.app/mailman/listinfo/brltty
