Using greek fonts ISO-8859-7:1987 (Latin/Greek)

[GoogleCodeExporter]

What steps will reproduce the problem?
Use of openVista (this is a EHR system under GT.M, which
is a MUMPS database)

What is the expected output? What do you see instead?
Switching in greek alphabet when using SIAB under Firefox
with alt+shift should display greek characters when typing
greek.  Instead of this nothing is showing, but it seems that
input has been accepted i.e following is shown :

ASTRON>
%GTM-E-CMD, Command expected but not found
ΣΔΦΣΔΦ
^----- 

What version of the product are you using? On what operating system?
shellinabox-2.10.tar.gz under ubuntu server 10.03

Please provide any additional information below.
Inputing latin characters works ok.  Everything else seems to work ok.

Original issue reported on code.google.com by ssu.e...@gmail.com on 27 Jul 2011 at 8:33

[GoogleCodeExporter]

After experimenting and comparing to putty I came to the
conclusion that the problme is related to the encoding
used when initiating SIAB, which is utf8.  So, reformulating
my question : 
Is it possible to start SIAB in ISO-8859-7 encoding ?
Can you please provide a call if possible ?

Also : How can SIAB started automatically on Ubuntu ?
I knwo this is a general question belonging to other
fora, but I would appreciate a quick answer.

Thank you!

Original comment by ssu.e...@gmail.com on 28 Jul 2011 at 7:04

[GoogleCodeExporter]

I would make this critical; it's not a charset specific bug. 

*No* UTF-8 input is supported.  

Displaying UTF-8 is fine thanks to shellinabox running in modern browsers; but 
I can't input Japanese via IME on OSX at all.  I can't even make a workaround 
by copying and pasting UTF-8 from another source since there's no paste support 
in shellinabox, 

This making shellinabox unusable in non-ascii environments; I would love to 
ditch local terminal apps, but this is a blocker.  

That said, don't feel bad!  graphterm & even Google's own hterm also fail at 
UTF-8 input for now (and I've filed bugs with those projects as well), still, 
getting this fixed would be a huge win! ^.^ がんばって！

Original comment by artki...@gmail.com on 4 Nov 2012 at 8:41

[GoogleCodeExporter]

Actually: while in Firefox 3.5 I have no charset issues (for instance typing 
"á"), I do have issues on Firefox 10.0.11 and later (trying to type "á" types 
"áA"). I'm not sure in which Firefox version (between 3.5 and 10) this started 
happening, but I can try to find out if there's an interest.

Original comment by mindboos...@gmail.com on 22 Nov 2012 at 3:55