+@import "lib-lua/base.cpkg"
+
+@package MCharset {
+ /*
+ ** .pp
+ ** This variable is a colon-separated list of character encoding
+ ** schemes for messages without character encoding indication.
+ ** Header field values and message body content without character encoding
+ ** indication would be assumed that they are written in one of this list.
+ ** By default, all the header fields and message body without any charset
+ ** indication are assumed to be in \fTus-ascii\fP.
+ ** .pp
+ ** For example, Japanese users might prefer this:
+ ** .pp
+ ** \fTset assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
+ ** .pp
+ ** However, only the first content is valid for the message body.
+ ** This variable is valid only if $$strict_mime is unset.
+ */
+ string_t assumed_charset = m_strdup("us-ascii");
+
+ /*
+ ** .pp
+ ** Character set your terminal uses to display and enter textual data.
+ */
+ string_t charset = NULL;
+
+ /*
+ ** .pp
+ ** This variable is a colon-separated list of character encoding
+ ** schemes for text file attatchments.
+ ** If \fIunset\fP, $$charset value will be used instead.
+ ** For example, the following configuration would work for Japanese
+ ** text handling:
+ ** .pp
+ ** \fTset file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
+ ** .pp
+ ** Note: ``\fTiso-2022-*\fP'' must be put at the head of the value as shown above
+ ** if included.
+ */
+ string_t file_charset = NULL;
+
+ /*
+ ** .pp
+ ** A list of character sets for outgoing messages. Madmutt will use the
+ ** first character set into which the text can be converted exactly.
+ ** If your ``$$charset'' is not \fTiso-8859-1\fP and recipients may not
+ ** understand \fTUTF-8\fP, it is advisable to include in the list an
+ ** appropriate widely used standard character set (such as
+ ** \fTiso-8859-2\fP, \fTkoi8-r\fP or \fTiso-2022-jp\fP) either
+ ** instead of or after \fTiso-8859-1\fP.
+ */
+ string_t send_charset = m_strdup("us-ascii:iso-8859-1:utf-8");
+};