It depends on your client (i.e., the program you use to connect to MUME) which one you should choose. Some clients may set it automatically if they support RFC 2066.
You change your current character encoding using one of:
> change encoding ascii > change encoding latin-1 > change encoding utf-8
If your terminal doesn't show accented characters correctly in either Latin-1 or UTF-8 modes, use "change encoding ascii". In this mode, MUME changes accented characters into their unaccented 7 bit version (or the closest match available; e.g., the copyright sign gets replaced by 'C').
Using "change encoding latin-1", MUME will send you accented characters.
On modern Unix installations, the default is to use the UTF-8 character encoding. Note, however, that while UTF-8 can encode any Unicode character, MUME will only accept those that exist in Latin-1. See "help latin-1" for a list of the allowed characters.
In order to save people from having to type all the obscure characters to identify objects, players and such, all keyword comparison is done on unaccented letters.
If your keyboard lacks the keys to type accented letters, there are various ways to do this. If you are running Windows, you can use an "International" character set which lets you type "'A" for an accented A.
A Compose key is a special prefix key that you press in order to write compound characters, so Compose " E would give you an E with an umlaut.
If your computer is running some Unix variant, you can configure your keyboard to have a Compose key. On most modern Linux installations you can do this in the normal keyboard configuration dialogs.
For older installations, you can change your xmodmap file to reprogram your keyboard to give you a Compose key (a.k.a. Multi_key). This may be slightly confusing, but there are tools available that make this somewhat easier (e.g., xkeycaps which can be found at http://www.jwz.org/xkeycaps/).
See also: CHANGE, LATIN1, https://tools.ietf.org/html/rfc2066
This page was automatically generated on Mon Jan 7 11:13:10 2019