getting_utf-8_working
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | getting_utf-8_working [2014/04/13 20:10] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ======Getting output working in EPIC5====== | ||
+ | **If you are in a hurry, skip to the bottom of the file for a list of problems and solutions.** | ||
+ | |||
+ | Getting EPIC to handle your keypresses and output correctly requires the participation of every program between you and EPIC. | ||
+ | |||
+ | ====Your terminal emulator (Putty, xterm, App.Term, KTerm)==== | ||
+ | To your terminal emulator, the only thing that matters is whether you are using UTF-8 or not; and if not, what font you're using. | ||
+ | |||
+ | ====Your remote login shell==== | ||
+ | You have to tell your remote login shell what encoding you are using. | ||
+ | | ||
+ | You set your locale with the LC_ALL environment variable. | ||
+ | |||
+ | ====Your multiplexer (GNU Screen)==== | ||
+ | BEFORE you started GNU Screen the first time, you remembered to set LC_ALL, right? | ||
+ | |||
+ | There are three ways to do this. | ||
+ | |||
+ | 1. Put " | ||
+ | |||
+ | 2. Within your EPIC window, do control-A then **: | ||
+ | (27, | ||
+ | or | ||
+ | (27, | ||
+ | If you see the first, then you are in UTF-8 mode. If you see the second, you can turn on UTF-8 with control-A then **:utf8 on**. Don't forget to set LC_ALL to an appropriate UTF-8 locale! | ||
+ | |||
+ | 3. Tell EPIC what (non-utf8) locale you are using. | ||
+ | |||
+ | Remember -- if GNU Screen and EPIC do not agree on whether you are using UTF-8, then things are going to get screwed up. If GNU Screen and your terminal emulator do not agree on using UTF-8, things are going to get screwed up. | ||
+ | |||
+ | ======COMMON PROBLEMS (and solutions)====== | ||
+ | ====Problem 1: When you type non-English characters the input line gets corrupted (you don't see characters, the cursor doesn' | ||
+ | Cause: GNU Screen and EPIC do not agree on whether you are using UTF-8. | ||
+ | Solution: Make sure GNU Screen is set to UTF-8 mode and make sure your LC_ALL environment variable is correctly set **before** you start EPIC. | ||
+ | |||
+ | ====Problem 2: EPIC says "Your /ENCODING CONSOLE is < | ||
+ | Cause: You either didn't set a locale (EPIC assumes you are using ISO8859-1 if you don't set your locale) and you are using UTF-8, or you set a UTF-8 locale, but aren't typing in UTF-8 \\ | ||
+ | Solution: If you didn't set a locale (LC_ALL), set it. If you did set LC_ALL, make sure GNU Screen agrees with LC_ALL about whether you are using UTF-8 or not. | ||
+ | |||
+ | ====Problem 3: EPIC says "Your /ENCODING CONSOLE is < | ||
+ | Cause: You probably didn't set a locale (EPIC assumes you are typing ISO8859-1 if you don't set your locale) and you are using UTF-8. \\ | ||
+ | Solution: Set your LC_ALL environment variable to an appropriate UTF-8 locale before you start EPIC. | ||
+ | |||
+ | ====Problem 4: I set my LC_ALL but EPIC still says I'm typing UTF-8.==== | ||
+ | Cause: GNU Screen does **NOT** set LC_ALL on inside shells. | ||
+ | Solution: You have to set LC_ALL before you start GNU Screen and again a second time afterwards. | ||
+ | |||
+ | ====Problem 5: EPIC says that my locale isn't acceptable==== | ||
+ | Cause: Locale names are specific to each operating system, so you might have spelled it wrong. \\ | ||
+ | Solution: | ||
getting_utf-8_working.txt · Last modified: 2014/04/13 20:10 by 127.0.0.1