----------------------------------------------------------------------------------
@MSGID: <2644889703@f8001.n240.z2.fidonet.org>
e4c38fd3
@REPLY: <1689284046@f10.n154.z1.fidonet.org>
8624595e
@REPLYADDR Sebastian Raase
<nospam.Sebastian.Raase@f8001.n240.z2.fidonet.org>
@REPLYTO 2:5075/128 Sebastian Raase
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
<2644889703@f8001.n240.z2.fidonet.org>
@RFC-References:
<1689284046@f10.n154.z1.fidonet.org>
@TZUTC: 1300
@PID: VSoup v1.2.9.47Beta [95/NT]
@TID: FIDOGATE-5.12-ge4e8b94
Hi Nicholas,
NB>> What is the correct way to get a Python 3.x script to output special
NB>> characters in Mystic?
NB>
NB> If I remember right, Python 3.x doesn`t work all that well with Mystic.
NB> Try using Python 2.x instead, as I believe that`s what was used when
NB> support for Python was initially added.
Unfortunately, Python 2.x is very much dead by now and the libraries I am
planning to use don`t support it. So that won`t work. Thanks for confirming
my suspicions, though...
It would be really nice if Mystic could take the incoming strings (which, in
Python 3.x, are always UTF-8) and convert them to the correct codepage. Same
for handling input. That way, all the encoding mess would be taken care of
outside the plugins. Dreaming is still allowed, isn`t it?
I haven`t found any (current) source code for Mystic, so I can`t fix it.
Best Regards,
Sebastian
--- VSoup v1.2.9.47Beta [95/NT]
* Origin: Agency HUB, Dunedin - New Zealand (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441