Hello Sebastien en Samuel,
The problems with the é character are still there but like you wrote
camouflaged.
- What is see is that writing to a Voayager gives more problems than to a alva
bc640.
- But in both cases sending a long string - more then 40 characters - with the
é characters gives the next time i send a string different characters on the
brailledisplay then i want.
brlapi_write("ééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééééé");
shows the é's
but then next one
brlapi_write("dog cat horse");
give different characters.
Maybe the é characters takes more memory space?
Anyway still puzzled - but not desperate - by the behaviour.
Regards,
Eric de Quartel
Bartiméus onderwijs VSO
Leraar biologie en tuinpraktijk
Coördinator Braille en tactiele ontwikkeling
Volg twitter @tactielactief
________________________________
Van: BRLTTY <[email protected]> namens [email protected]
<[email protected]>
Verzonden: zondag 1 oktober 2017 18:00:01
Aan: [email protected]
Onderwerp: BRLTTY Digest, Vol 13, Issue 156
Send BRLTTY mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://brltty.com/mailman/listinfo/brltty
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of BRLTTY digest..."
Today's Topics:
1. Re: Crash when sending char ? ?? (Samuel Thibault)
----------------------------------------------------------------------
Message: 1
Date: Sun, 1 Oct 2017 13:38:45 +0200
From: Samuel Thibault <[email protected]>
To: "Quartel, Eric de" <[email protected]>
Cc: "[email protected]" <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [BRLTTY] Crash when sending char ? ??
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=us-ascii
Hello,
Quartel, Eric de, on sam. 30 sept. 2017 15:39:24 +0000, wrote:
> In the source code add
> setlocale(LC_ALL, "nl_NL.UTF-8");
And then it was working?
We would still be interested in knowing what is crashing without this
line, because this is really not supposed to happen and means there is a
bug somewhere which we have to fix, and for now this line is only hiding
it, not fixing it :)
Samuel
------------------------------
Subject: Digest Footer
_______________________________________________
This is a message digest of the BRLTTY mailing list.
To post a message, send an e-mail to: [email protected]
For general information, go to: http://brltty.com/mailman/listinfo/brltty
------------------------------
End of BRLTTY Digest, Vol 13, Issue 156
***************************************
_______________________________________________
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.com/mailman/listinfo/brltty
