[forge-issues] [JBoss JIRA] (FORGE-192) Make Forge console i18n and L10n compatible

[Vineet Reynolds (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789813#comment-12789813 ] 

Vineet Reynolds commented on FORGE-192:
---------------------------------------

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/f728bf8ea9beb4f25c77fb11b54e485e3476bfdb 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.
                
> Make Forge console i18n and L10n compatible
> -------------------------------------------
>
>                 Key: FORGE-192
>                 URL: https://issues.jboss.org/browse/FORGE-192
>             Project: Forge
>          Issue Type: Feature Request
>          Components: Brainstorming, UI - Shell
>    Affects Versions: 1.0.6.Final
>            Reporter: George Gastaldi
>             Fix For: 2.x Future
>
>
> Forge should allow different languages to be used, so that the help messages and commands could be typed on the native speaker developer language.
> Example: When a Brazilian Portuguese developer is creating a new project, he would type: "novo-projeto" instead of "new-project".

--
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