TE> Msged does not currently support UTF-8, and adding this support
 TE> requires change in the code; only making a mapping table will not
 TE> suffice.

Well, it should work somewhat, since the mapping tables allow *one* byte to
be mapped into either *one* or *two* bytes. That makes it possible to have
a mapping table from e.g. ISO8859-1 into UTF-8 (since most - or all? -
characters in that Unicode page are coded with only two bytes in UTF-8). It
won't work with characters that require three or more bytes in UTF-8
though.

It's impossible to map UTF-8 encoded strings into regular 8-bit encodings,
since the mapping tables only accept one byte as input. This makes it
impossible for other MsgEd users to read what Benny writes, and for Benny
to recode his messages into an other encoding when saving them. (I don't
know if MsgEd can do this anyway - is this what the writemap is for?)

Then there are a bunch of other problems that will emerge; such as names
and subjects that might exceed their 36/72 byte limit when they are UTF-8
encoded, while they might be valid in another encoding... ;-)

  Jesper,
  yeppe{at}enjoy.cc
---