[ https://issues.jboss.org/browse/FORGE-192?page=com.atlassian.jira.plugin.... ] Vineet Reynolds edited comment on FORGE-192 at 7/15/13 9:45 PM: ---------------------------------------------------------------- Well, just so that it doesn't get lost somewhere, we should not forget about handling the keyed in characters correctly. Curerntly, the jline fork we use does not handle input characters greater than 0x128 correctly. The following error (or something similar, except for the byte value) is displayed when a unicode character is input: {noformat} [no project] vineet $ ***ERROR*** Exception encountered: Invalid UTF-8 first byte: -127 (type "set VERBOSE true" to enable stack traces) {noformat} The following jline commit: https://github.com/jline/jline2/commit/f728bf8ea9beb4f25c77fb11b54e485e34... has changed the behaviour. I haven't verified is completely, but it's worth looking into. Also worth looking into is SBT, since they're using jline in someway or another, and still manage to get Unicode support for REPL. On Windows, it would be better to use Jansi since it provides APIs to read wide-chars : https://github.com/fusesource/jansi-native/pull/1. was (Author: vineet.reynolds): Well, just so that it doesn't get lost somewhere, we should not forget about handling the keyed in characters correctly. Curerntly, the jline fork we use does not handle input characters greater than 0x128 correctly. The following error (or something similar, except for the byte value) is displayed when a unicode character is input: {noformat} [no project] vineet $ ***ERROR*** Exception encountered: Invalid UTF-8 first byte: -127 (type "set VERBOSE true" to enable stack traces) {noformat} The following jline commit: https://github.com/jline/jline2/commit/f728bf8ea9beb4f25c77fb11b54e485e34... has changed the behaviour. I haven't verified is completely, but it's worth looking into. Also worth looking into is SBT, since they've used jline2 or a fork. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira