by Bitmonster » Fri Oct 03, 2008 7:13 pm
But if you get wrong chars from the serial port, the serial plugin has to do the input encoding. (This is actually missing in the serial plugin and this is a bug.) If you have a plugin that generates a playlist for example, the strings in the playlist should already be decoded to unicode. If you do otherwise and combine the two, there would be no way to handle it right, because there might be no common encoding.
So actually there is only one way to do it right: every code that receives something from the outside world has to immediately do the decoding to unicode and everything that sends something to the outside world has to do the encoding in the last step.
The longer I think about it, the more convinced I get, that we should drop the idea to give a choice of the input data encoding here.
Please post software-related questions in the forum - PMs will only be answered, if really private, thanks!