User Tools

Site Tools


getting_utf-8_working

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
getting_utf-8_working [2014/04/13 20:09]
sgrubnick
getting_utf-8_working [2014/04/13 20:10] (current)
sgrubnick
Line 30: Line 30:
  
 ======COMMON PROBLEMS (and solutions)====== ======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'​t move).\\+====Problem 1: When you type non-English characters the input line gets corrupted (you don't see characters, the cursor doesn'​t move)====
 Cause: GNU Screen and EPIC do not agree on whether you are using UTF-8. ​ \\ 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. 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 <​something>​ which is wrong." ​ \\+====Problem 2: EPIC says "Your /ENCODING CONSOLE is <​something>​ which is wrong."​====
 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 \\ 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. 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 <​something>​ but you seem to be typing UTF-8." ​\\+====Problem 3: EPIC says "Your /ENCODING CONSOLE is <​something>​ but you seem to be typing UTF-8."​====
 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. \\ 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. 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. ​\\+====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. ​ \\ 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. ​ If you don't set LC_ALL on inside shells, EPIC will assume you're not using a locale and defaults to ISO-8859-1. Solution: You have to set LC_ALL before you start GNU Screen and again a second time afterwards. ​ If you don't set LC_ALL on inside shells, EPIC will assume you're not using a locale and defaults to ISO-8859-1.
  
-Problem 5: EPIC says that my locale isn't acceptable ​\\+====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. \\ Cause: Locale names are specific to each operating system, so you might have spelled it wrong. \\
 Solution: ​ Use the "​locale -a" command to see your system'​s valid LC_ALL values. ​ Choose an appropriate one. Solution: ​ Use the "​locale -a" command to see your system'​s valid LC_ALL values. ​ Choose an appropriate one.
  
getting_utf-8_working.txt ยท Last modified: 2014/04/13 20:10 by sgrubnick