Hi!

 MB> under which of the many licenses can the charmaps be used?
 MB> I'd like to add the latin1 charmaps to TimEd, which is not
 MB> part of the Husky project. However TimEd is licensed under
 MB> the GPL. So is there any problem with this?

Due to the fact that Msged (unlike TimED) is licensed under a really *FREE*
license, you can take its charmaps and do with them whatever you want,
including committing them into the TimED source code. 

In fact, the charmaps in Msged where developed based on those found in the
original, non-free, timed, because that part of Timed, back then, was
declared as "reference material". 

So, the things should be quite compatible ;-)

You only must take care about the IBMPC charset. In agreement with FSP
1013, I do not have any character maps for the "IBMPC" charset,
as it is not clear which codepage is meant. I only have charmaps for CP437,
CP850, and CP865 CP866 and so on.

You can then use the "CharsetAlias" feature of Msged to tell
Msged that in the area where you, personally, are living, "IBMPC"
usually means. In Europe, you would set IBMPC to be an alias for CP850, in
Russia for CP866, in America for CP437, and so on.

Such a feature is absent from Timed AFAIK, so you would probably have to
decide what you want to use as IBMPC and then copy that charmap over and
change the CPxxx string in the header to IBMPC.

Also, Msged has another feature: If you export Messages with e.g. CP850
charset, Msged by default does *NOT* write a CHRS: CP850 kludge, but
instead it write CHRS: IBMPC and adds CODEPAGE: 850. That's because a lot
of mailreaders that exist do not know about the CPxxx charset kludges, and
using CHRS + CODEPAGE is permittable by FSP 1013 and turned out to be the
most compatbile approach.

Maybe you should ask Andrew Clarke's opinion about the codepage issue... :-)

Regards,
Tobias.

--- Msged/MAC 6.1.2