Subj : Is Synchronet UTF8 Ready?
To   : Maurice Kinal
From : Kees van Eeten
Date : Sun Feb 19 2017 13:53:58

Hello Maurice!

19 Feb 17 10:32, you wrote to me:

 MK> What's your excuse?

 Within the languages that I can speak, I can sufficiently express myself
 with an ASR33. A mix of upper and lowercase is just a addition for
 readabillity.

 A few years ago I started a proof of concept in Python for a character
 encoding smart message reader. It uses somthing like uchardet and some
 additional tweaking to define a plausible enoding of the textblock that I
 access. Subsequenly is uses iconvert to convert to UTF-8.

 I does a fair job at making all messages presentable as they should, with
 the proper glyphs. So some would be thrilled, but to me it is no use,
 because I cannot read (understand) the text anyway. But it look much
 nicer.

 One of the reasons I did not continue, is the access to the message store.
 Currently it can extract messages from squish. But I cannot store messages.

 I could solve it the way, I think you use, by builing a PKT and use the
 tosser to cope with the message store.

 I think in my case Jamm as a message store would be more feasible, but there
 are so many other things to do, that are more fun than writing code to
 read and write to a Jamm message base.

 Well I could take a easy intermediate, use *.msg.

 The message to you, is I can properly present whatever you write, but I may
 not be able to understand it. If I give an answer it will most likely be
 encoded in Latin-1 of ISO-8859-1.

 Whenever I feel the urge to write UTF-8 encoded messages, you and Michiel
 will be the first to receive the crappy results. ;)

 Some day this may happen if I can complete it in this life. Don't hold
 your breath.

Kees

--- GoldED+/LNX 1.1.5
 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

.