MK> Does that mean that my hunch about the "CHRS: UTF-8 4" kludge you were MK> flying up to now was indeed bogus?
Yes, your hunch is bogus.
MK> The message I am replying to appears to be accurate with respect to MK> it's "CHRS: CP866 2" kludge since it matches the same characters I MK> originally sent as UTF-8 characters.
So what is the problem?
MK> The only problem is that the Møøse ends up getting ditched in the MK> process since CP866 cannot handle Norwegian characters
It is a well known fact that there is no 8 bit character encoding scheme in use in Fidonet that can do both Cyrrilic and Norwegian. Your point?
MK> and the Møøse thinks it is Norwegian despite the fact that it really MK> isn't.
This message flies a UTF-8 4 chrs kludge. That means that whatever is in the message is encoded in UTF-8.
Flying a UTF-8 chrs kludge does NOT mean that the system generating the message is capable of displaying or generating all 109,384 characters defined in the Unicode Standard. It just means that whatever is there, is encoded in UTF-8. No more no less.
MK> Stinkin' Møøse.
MvdV>> Now can we get back on topic please?
MK> Sure. Errrr ... which was what?
Since we are discussing character encoding schemes, the topic seems to be FTS-5003.
