Description Martin Oberhuber 2014-05-27 23:41:32 EDT

As per my comment here:

   https://bugs.eclipse.org/bugs/show_bug.cgi?id=420474#c9

the winpty code requires UTF-8 encoding, so the handling of default encoding must be changed:

1. UTF-8 must be the default on Windows Local Terminals and Mac local terminals.
   1a) On Linux Local, the default local host encoding should be used as default
   1b) On Telnet, SSH and Serial, either ISO-8859-1 or UTF-8 is reasonable
   --> If UTF-8 is used as default on ALL connections it is a workable solution.

2. IDEEncoding.getResourceEncoding() should be used again to populate the 
   encoding selection combo, such that a custom encoding which a user has
   entered for his workspace is available in the selection combo.

3. When entering an invalid encoding, there should be an error message and not
   direct fallback to iso-8859-1. Test case: enter "cp437" as encoding, this
   is unsupported in Java7 (at least on my host) - would like to see an error.

4. Encoding should be remembered per host / connection. Today it seems shared
   across all terminal connectors. But it is very likely that I need UTF-8
   on my Windows Local terminal, ISO-8859-1 on my remote SSH session, and 
   US-ASCII on my Serial line. Different SSH hosts may use different encodings,
   and user's selection should be remembered.