Next: , Previous: , Up: Keywords   [Index]


6.2.6 AssumeCharset

Syntax:

AssumeCharset charset

Example:

AssumeCharset IBMPC

In Fidonet mail, mails that contain special characters must carray a charset kludge line (see Using Special Characters - The FSC 0054 Charset Kludge). However, still a good percentage of fidonetmail contains special characters, but no charset kludge line. Also, people often use wrong charset kludge names.

By default, MsgEd TE will replace all special characters with question marks in mails without charset kludge or with unknown charset kludge, because MsgEd TE does not know how to properly translate such special characters. If you do not like this, you can use the AssumeCharset keyword to specify that MsgEd TE should assume that all special characters in mails that do not contain a charset kludge, or have a unknown charset kludge, have been composed using the character set charset, and translate the special characters accordingly.

In Germany, for example, nearly all mail that contains special characters but does not contain a charset kludge has been composed using the IBMPC character set, so it makes sense to specify ‘AssumeCharset IBMPC’ here.

In Russia, it is best to use ‘AssumeCharset CP866’.