Can't enter special characters

[Boris Samardžija]

Hello,

I can't enter special characters (e.g. \ | @{}§ and so on...). I am from Croatia and I use Croatian keyboard setup.

Some international keyboards like South Slavic Latin, Croatia, Slovenia, Bosnia and Herzegovina and Serbia use AltGr key to get some characters.

• AltGr+v @
  
• AltGr+b {
  
• AltGr+n }
  
• AltGr+m §
  
• AltGr+, <
  
• AltGr+. >
  
• ...

You can find more about this on Wikipedia

http://en.wikipedia.org/wiki/AltGr_key#South_Slavic_Latin

Is there a way for this to work?

Thanks,

Boris.

[Robert Ginda]

What is your LANG environment variable set to?  hterm only works with the UTF-8 variants, so you'll run into problems if you're using to a different encoding.

There are also issues with composed characters as described in http://code.google.com/p/chromium/issues/detail?id=218382.

Rob.

--
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/aeb428d3-028d-4bad-9321-fea062257f33%40chromium.org.

[Boris Samardžija]

I tried to put {"LANG":"en_US.UTF-8"} for environment in options, but with no effect...

Is there any way to check that?

Sorry, forgot to mention, I am on Windows 8.1, Chrome 32

Boris.

[Robert Ginda]

I don't think the LANG setting gets passed over ssh.  Instead, once you're logged in to the remote host type "echo $LANG" to see what it's set to, and "export LANG=en_US.UTF-8" to set it.

If that fixes the problem you'll want to modify your ~/.bashrc or similar.

Rob.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/ebe2517c-c28b-4355-8181-2c5de4f348fa%40chromium.org.

[Boris Samardžija]

No, unfortunately it's the same. Thanks for the effort.

I would really really want to replace PuTTY (special characters work fine there) with Secure Shell, but this is dealbreaker for me :( 

[Harald Glatt]

I've got the same problem. It's extremely annoying and makes the shell nearly unuseable. For example I can't enter the pipe sign | but I can easily paste it in. This means I always type the character I want to type into Spotlight, copy it there and patse it into the shell. Directly typing it in isn't possible. I'm on Mac OS X 10.9 and the latest Chrome Dev. However it doesn't work in the Beta or Stable builds of Chrome either. My keyboard layout in Mac OS X is German and the remote shell is set to the UTF LANG. If you need further info to track this down, let me know.

[Robert Ginda]

Which OS?

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/25752288-0c4f-4ddd-a7dc-8671f75bb687%40chromium.org.

[Harald Glatt]

Are you asking me??? I wrote in my original post: 'I'm on Mac OS X 10.9 and the latest Chrome Dev. '

[Darcy Parker]

You should probably also mention the OS you are ssh'ing into.

Also, don't just check $LANG on the OS your ssh'ing into... sometimes it can be set to a value with ".UTF8" at the end, but this locale is not actually installed on the OS you are ssh'ing into.  So you should also run `locale -a` on the machine you are ssh'ing into and check that the $LANG value is listed by `locale -a`.  If not, then you need to install that locale.  In general the locale should be the UTF8 variant of what you want.

Darcy

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/05b9b322-86f1-446c-b1b0-3757b35acbd7%40chromium.org.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-hter...@chromium.org.

[Harald Glatt]

The lang and locale -a is fine. The OS im sshing into is Ubuntu / Gentoo / Debian / Arch Linux. All fail the same way but it works fine with the OS X ssh.

[erik...@google.com]

The LANG and UTF-8 locale stuff looks like a red herring. Most of the problematic characters are ASCII.

On MacOS it worked for me to type term_.prefs_.set('alt-sends-what', 'browser-key')  in the JS console. This fixes it in all windows, not just the one that I type it in.

This probably affects both Alt keys, whereas it's only needed for the right Alt key.  But I never use the left Alt key in terminals, so it's fine for me.

[Boris Samardžija]

I can confirm this has been fixed in 0.8.32.1 release

Thank you!

[di...@dambra.dk]

Still an issue with 0.8.34.

You need to edit "Options" -> "alt-sends-what" from "escape" to "browser-key".