non-ASCII characters not displaying correctly

[bpphi...@gmail.com]

Hello - should I expect unicode characters that display correctly in my browser (i.e. http://www.ltg.ed.ac.uk/~richard/unicode-sample.html) to display correctly in the secure shell chrome app?  Many characters display correctly but it looks like many of them have encoding issues (I've attached a screenshot).  Those characters all display correctly when connecting to the same host via gnome-terminal (with the exception of two characters which I'm guessing I just don't have glyphs for) so I don't think it's a server-side configuration issue.  Is there a setting in hterm that I can tweak to make this work?  Should I not expect this to work in hterm?

Thanks

[Robert Ginda]

It should work.  Are you using crosh or Secure Shell?  Crosh seems to have issues when UTF-8 bytes are sent quickly.  If you're using Secure Shell and it's still not working, check your LANG environment variable, it should end with a ".UTF-8" suffix, as in "en_US.UTF-8".

Here's a screenshot of Secure Shell rendering our test UTF-8 file:

Rob.

On Mon, Apr 7, 2014 at 6:14 AM, <bpphi...@gmail.com> wrote:

Hello - should I expect unicode characters that display correctly in my browser (i.e. http://www.ltg.ed.ac.uk/~richard/unicode-sample.html) to display correctly in the secure shell chrome app?  Many characters display correctly but it looks like many of them have encoding issues (I've attached a screenshot).  Those characters all display correctly when connecting to the same host via gnome-terminal (with the exception of two characters which I'm guessing I just don't have glyphs for) so I don't think it's a server-side configuration issue.  Is there a setting in hterm that I can tweak to make this work?  Should I not expect this to work in hterm?

Thanks

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/fb1b4250-a341-4e02-9a32-d79fe57211cd%40chromium.org.

[bpphi...@gmail.com]

Excellent!  That does indeed fix it for me (setting the LANG environment variable as you suggested).