Bug 3707 - Impossible to type @ in the Italian version
Summary: Impossible to type @ in the Italian version
Status: RESOLVED WORKSFORME
Alias: None
Product: Claws Mail (Windows)
Classification: Unclassified
Component: default (show other bugs)
Version: 3.14.1
Hardware: PC Windows 10
: P3 major
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2016-10-07 21:04 UTC by nicola-marras
Modified: 2017-01-12 15:32 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description nicola-marras 2016-10-07 21:04:19 UTC 
I have Claws Mail (Italian Version)in three computers: Windows XP, Windows 7 and Windows 10. In all it is impossible to type @ when I write the mail address. Only possibility is copy and paste. A VERY annoing bug that I do not had using an English version. A question: it is possiblee to export the settings to another computer?
Best regards, Nicola Marras
Comment 1 Andrej Kacian 2016-10-09 01:15:55 UTC 
Since there is no Italian version of Claws Mail, I assume you mean Claws Mail on Windows system set to Italian locale.

I do not have Italian Windows available, but I tried to reproduce it on English Windows (7) by choosing Italian language for Claws Mail, and Italian keyboard layout in Windows. Typing @ (AltGr plus key where English layout has a semicolon), but it worked fine.

Can you do following two tests?

1. Does typing @ work when you have English keyboard layout active?

2. Open cmd.exe window and enter following commands:

 cd "c:\Program Files (x86)\Claws Mail"
 set LC_ALL=en_US
 claws-mail.exe

Claws Mail should start in English language. Does typing @ work now with Italian or English keyboard layout?
Comment 2 Andrej Kacian 2016-10-09 01:17:41 UTC 
Another question: Does typing @ work outside of the Compose window? For example, hit / to get a quicksearch bar. Are you able to type @ in the search entry?
Comment 3 Andrej Kacian 2017-01-12 15:32:33 UTC 
Closing due to lack of feedback. Feel free to reopen once you respond to my question.
Note You need to log in before you can comment on or make changes to this bug.