seeseemelk/cool-retro-term
1
0
Fork 0
Code Issues 449 Pull Requests 12 Actions Packages Projects Releases 8 Wiki Activity

Problem AZERTY french keyboard layout #523

New Issue
Open
opened 2019-04-04 11:39:21 +02:00 by taldeguer · 19 comments
taldeguer commented 2019-04-04 11:39:21 +02:00 (Migrated from github.com)
Copy Link

There is a problem with the AZERTY french disposition. the A key gives Q, but Q also gives Q. Same for M key, M = M , ?/, = M.
It seems both QWERTY/AZERTY are mixed. Is it possible to choose another layout and how ?

There is a problem with the AZERTY french disposition. the A key gives Q, but Q also gives Q. Same for M key, M = M , ?/, = M. It seems both QWERTY/AZERTY are mixed. Is it possible to choose another layout and how ?
👍 24
taldeguer commented 2019-04-04 11:44:00 +02:00 (Migrated from github.com)
Copy Link

Also, I forgot to mention that I'm running OSX Mojave

Also, I forgot to mention that I'm running OSX Mojave
Jefwillems commented 2019-04-24 14:55:54 +02:00 (Migrated from github.com)
Copy Link

Same problem here

Same problem here
dairaine commented 2019-04-28 17:18:15 +02:00 (Migrated from github.com)
Copy Link

+1

+1
mblarsen commented 2019-04-30 08:13:55 +02:00 (Migrated from github.com)
Copy Link

I'm experiencing this with Colemak as well.

I'm experiencing this with Colemak as well.
👍 2
Alvaro-AT commented 2019-06-08 01:26:48 +02:00 (Migrated from github.com)
Copy Link

Same with Spanish QWERTY. Only happens in Mac OS using any version above v1.0.1. I've tried v1.1.1 in Linux and all is working properly.

Same with Spanish QWERTY. Only happens in Mac OS using any version above v1.0.1. I've tried v1.1.1 in Linux and all is working properly.
solsticedhiver commented 2019-06-10 18:18:49 +02:00 (Migrated from github.com)
Copy Link

Isn't the issue simply that QWERTY is the only layout whatever the one already set in your desktop ?

You could change your layout in your desktop, it will always be QWERTY in CRT

Isn't the issue simply that QWERTY is the only layout whatever the one already set in your desktop ? You could change your layout in your desktop, it will always be QWERTY in CRT
Alvaro-AT commented 2019-06-10 18:24:52 +02:00 (Migrated from github.com)
Copy Link

Yes, I think that's the problem, but only happens in Mac OS.

Yes, I think that's the problem, but only happens in Mac OS.
👍 1
solsticedhiver commented 2019-06-12 07:43:10 +02:00 (Migrated from github.com)
Copy Link

No, no. If I am talking about desktop, it's because I am using linux. Ubuntu 19.04/wayland.

So that defintivly does not happen only in MacOS

No, no. If I am talking about desktop, it's because I am using linux. Ubuntu 19.04/wayland. So that defintivly does not happen only in MacOS
Jefwillems commented 2019-06-12 09:00:24 +02:00 (Migrated from github.com)
Copy Link

Isn't the issue simply that QWERTY is the only layout whatever the one already set in your desktop ?

You could change your layout in your desktop, it will always be QWERTY in CRT

That's the problem, would you change your keyboard layout for every app you use? There should just be support for azerty and other layouts in this app, hence the issue.

> Isn't the issue simply that QWERTY is the only layout whatever the one already set in your desktop ? > > You could change your layout in your desktop, it will always be QWERTY in CRT That's the problem, would you change your keyboard layout for every app you use? There should just be support for azerty and other layouts in this app, hence the issue.
lraulin commented 2019-06-28 18:36:51 +02:00 (Migrated from github.com)
Copy Link

There should just be support for azerty and other layouts in this app, hence the issue.

The app should use the OS-selected keyboard layout like every single other app, and like CRT apparently did until the most recent update.

Interesting that there's a report of it happening in Linux too... Like others, I can't use any *non-QWERTY layout in OSX Mojave, but have never seen this problem on Linux.

*Edit: Correction: Hangul (the Korean alphabet) seems to work fine. Dvorak and Programmer Dvorak do not. I haven't tried any others myself.

>There should just be support for azerty and other layouts in this app, hence the issue. The app should use the OS-selected keyboard layout like every single other app, and like CRT apparently did until the most recent update. Interesting that there's a report of it happening in Linux too... Like others, I can't use any *non-QWERTY layout in OSX Mojave, but have never seen this problem on Linux. *Edit: Correction: Hangul (the Korean alphabet) seems to work fine. Dvorak and Programmer Dvorak do not. I haven't tried any others myself.
👍 3
nicolas-b12 commented 2019-09-01 12:07:30 +02:00 (Migrated from github.com)
Copy Link

Same here, OSX Mojave, AZERTY Keyboard

Same here, OSX Mojave, AZERTY Keyboard
👍 1
ghost commented 2019-09-20 17:24:13 +02:00 (Migrated from github.com)
Copy Link

Same issue, with more informations.

My config is OSX Mojave and AZERTY Keyboard.

The first and third rows are QWERTY, they render qwertyuiop^$ and zxcvbnm;:=.
Whereas the second row renders qsdfghjklmù' which is the AZERTY configuration.

So I can't type the letter a ... 😞

Same issue, with more informations. My config is OSX Mojave and AZERTY Keyboard. The first and third rows are QWERTY, they render `qwertyuiop^$` and `zxcvbnm;:=`. Whereas the second row renders `qsdfghjklmù'` which is the AZERTY configuration. So I can't type the letter `a` ... 😞
👍 2
jbltx commented 2019-11-13 05:30:09 +01:00 (Migrated from github.com)
Copy Link

Same problem here on OSX Mojave, AZERTY French keyboard layout.

EDIT : I saw qmltermwidget has a mac-vkcode.h file with ANSI virtual keys from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/Headers/Events.h

In this file there's an interesting comment above these keys :

/*
 *  Summary:
 *    Virtual keycodes
 *  
 *  Discussion:
 *    These constants are the virtual keycodes defined originally in
 *    Inside Mac Volume V, pg. V-191. They identify physical keys on a
 *    keyboard. Those constants with "ANSI" in the name are labeled
 *    according to the key position on an ANSI-standard US keyboard.
 *    For example, kVK_ANSI_A indicates the virtual keycode for the key
 *    with the letter 'A' in the US keyboard layout. Other keyboard
 *    layouts may have the 'A' key label on a different physical key;
 *    in this case, pressing 'A' will generate a different virtual
 *    keycode.
 */

As far as I understand, only US keyboard can work as intended with these virtual keys, no ?

Same problem here on OSX Mojave, AZERTY French keyboard layout. EDIT : I saw qmltermwidget has a **mac-vkcode.h** file with ANSI virtual keys from `/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/Headers/Events.h` In this file there's an interesting comment above these keys : ```cpp /* * Summary: * Virtual keycodes * * Discussion: * These constants are the virtual keycodes defined originally in * Inside Mac Volume V, pg. V-191. They identify physical keys on a * keyboard. Those constants with "ANSI" in the name are labeled * according to the key position on an ANSI-standard US keyboard. * For example, kVK_ANSI_A indicates the virtual keycode for the key * with the letter 'A' in the US keyboard layout. Other keyboard * layouts may have the 'A' key label on a different physical key; * in this case, pressing 'A' will generate a different virtual * keycode. */ ``` As far as I understand, only US keyboard can work as intended with these virtual keys, no ?
khl3o commented 2019-11-14 17:50:41 +01:00 (Migrated from github.com)
Copy Link

same here, macOS Mojave ands AZERTY keyboard.

Also:

  • The cmd + c / cmd + v doesn't work
  • Touch a returns a 'q' and touch q return also a 'q'
  • Drag and drop (file or directory) doesn't work
  • Open a script with cool-retro-term doesn't work

I'm sad, it looks so nice...

same here, macOS Mojave ands AZERTY keyboard. Also: - The cmd + c / cmd + v doesn't work - Touch a returns a 'q' and touch q return also a 'q' - Drag and drop (file or directory) doesn't work - Open a script with cool-retro-term doesn't work I'm sad, it looks so nice...
laubster commented 2020-01-19 03:31:19 +01:00 (Migrated from github.com)
Copy Link

Steps to demonstrate the problem (these work under the linux neon distro - may need tweaking for others):

  1. leave desktop environment keyboard settings at the default
  2. in terminal run "setxkbmap dvorak" (or maybe some azerty if it's installed)
  3. start the cool-retro-term AppImage
  4. notice that typing reflects qwerty instead of the requested alternate keyboard
Steps to demonstrate the problem (these work under the linux neon distro - may need tweaking for others): 1) leave desktop environment keyboard settings at the default 2) in terminal run "setxkbmap dvorak" (or maybe some azerty if it's installed) 3) start the cool-retro-term AppImage 4) notice that typing reflects qwerty instead of the requested alternate keyboard
BuonOmo commented 2020-02-14 09:59:37 +01:00 (Migrated from github.com)
Copy Link

With bépo (French Dvorak) I end end having a qwerty Keyboard... (Mojave as well)

With bépo (French Dvorak) I end end having a qwerty Keyboard... (Mojave as well)
👍 1
diedummydie commented 2020-02-23 02:07:10 +01:00 (Migrated from github.com)
Copy Link

Same problem with Colemak on macOS 10.14 Mojave

Same problem with Colemak on macOS 10.14 Mojave
👍 1
ChristopherJdL commented 2020-11-23 12:58:12 +01:00 (Migrated from github.com)
Copy Link

Same problem with macOS Catalina in 2020 with AZERTY

Same problem with macOS Catalina in 2020 with AZERTY
ImLilDev commented 2021-11-11 00:19:15 +01:00 (Migrated from github.com)
Copy Link

Same Big Sur 2021 ! how to fix it ?

Same Big Sur 2021 ! how to fix it ?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bounty
bug
duplicate
enhancement
help wanted
invalid
priority
high
priority
low
question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
seeseemelk
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#523
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?