SecureCRT 8 build 1055 and Norwegian special characters

[gan]

I i'm currently using SecureCRT 8 Build 1055 and seems like there are some issues with none standard characters. In Norway we got 3 characters that is unique for Norway and if i create a folder in session manager using any of these characters everything seems fine until i close scrt and restart the application. After the restart of the application it seems like all the characters are replaces with the hex value for the ascii code.

Attached is screenshot1.jpg that show a new folder under test which is fine. In screenshot2.jpg this is how it looks after i restarted scrt.

For the record i use a Mac with El Capitan 10.11.4 where everything is setup for English except the number, date/time formats and they keyboard which is Norwegian.

-gan

[bgagnon]

Hi gan,

What is the specific Mac OS SecureCRT is installed on?

What keyboard layout, specifically, do you use?

[gan]

Originally Posted by bgagnon

Hi gan,

What is the specific Mac OS SecureCRT is installed on?

What keyboard layout, specifically, do you use?

The OS is El Capitan 10.11.4 and the keyboard layout is Norwegian.

[bgagnon]

Hi gan,

Maybe it is something specific to El Capitan OS. I could not replicate it with Yosemite. I could create both sessions and folders with those characters and they remained after quit/restart. See attached.

Outside of SecureCRT, if you create folders using those special characters, what are the results?

[gan]

Originally Posted by bgagnon

Hi gan,

Maybe it is something specific to El Capitan OS. I could not replicate it with Yosemite. I could create both sessions and folders with those characters and they remained after quit/restart. See attached.

Outside of SecureCRT, if you create folders using those special characters, what are the results?

Outside of SecureCRT I have no problem with those characters and i neither have any problems with SecureCRT 7.3.7 and earlier releases using the same version of OS X. This problem started with 8.0 beta and tried with both beta 3, 4 and 5. When i went back to 7.3.7 the problem were gone.

-gan

[bgagnon]

Hi gan,

I have submitted this behavior for investigation by the development team. Should progress be made toward a resolution, or further information be requested, I will post in this thread.

If you prefer direct e-mail notification, contact support@vandyke.com and include "Bug Report - Forum Thread #12304" in the subject line.