Characters not inside the basic ascii codes are not displayed in the led sign. It seems to be due to a limitation in the jetfile library because it is causing an exception when creating the message string.
This could be solved by including a special configuration command in the message content that allows these characters to be displayed.
According to the JetFile 2.8.7 protocol specification [1], the control character '0x17' allows the insertion of extended ascii codes ( 0 - 255 ) in the message content. This could be tested with the following line:
echo '015A3030024141061B30621C311A310A49310A4F311757826C636F6D6504'|xxd -r -p | nc 192.168.1.101 9520
'015A3030024141061B30621C311A310A49310A4F31 + 17(extended ascii control char) + 57 + 82(special char é) + 6C636F6D6504'
Since i don't have a screen at hand to test it i can't confirm that, because I'm not sure in which position it must be inserted. But if it works, this character should be added to the markup in the LEDsign library in order to support extended ascii.