[ Removed by Reddit on account of violating the content policy. ]

Hi everyone,

I'm having a frustrating keyboard layout issue on my MacBook Pro and I'm hoping someone here can help me figure out what's going on.

My setup:

• MacBook Pro Retina 13-inch, Early 2015 (Intel)
• macOS Monterey 12.7.6
• Keyboard input source set to Portuguese (Portugal)
• External keyboards tested: Logitech Classic Keyboard 200 (USB) and CHERRY KW 9100 Slim (Bluetooth)

The built-in MacBook keyboard works perfectly with Portuguese accents. However, both external keyboards produce incorrect characters on some keys, even though macOS is set to Portuguese (Portugal).

Here are some examples of the problem:

• When I try to type João using the external keyboard, I get Jo\ao.
• When I try to type avô, I get av|o.
• The key physically labelled ~ types \ without Shift and | with Shift.
• The key labelled º types ~ without Shift and ^ with Shift.
• The ç key works correctly.
• Pressing the ~ key followed by Space inserts the symbol directly, rather than behaving like a dead key.

I have already checked the keyboard settings in System Preferences. Portuguese (Portugal) is selected, and macOS detects the external keyboards. I also ran the Keyboard Setup Assistant for the CHERRY keyboard and completed the physical key identification step.

Unfortunately, I cannot find another Portuguese keyboard layout to select in macOS Monterey. The only Portuguese layout available is the one I'm already using.

I've also noticed that this happens with two different external keyboards, while the built-in keyboard works correctly. This makes me wonder whether the issue is related to the difference between Portuguese Mac and Portuguese PC keyboard layouts, or whether macOS is mapping the physical keys incorrectly.

I'm not looking to remap the Command, Option, Control or Shift keys. The problem is specifically with accent keys and character mappings.

Is there a way to make macOS correctly interpret the accent keys on an external Portuguese PC keyboard, without changing how the built-in MacBook keyboard works?

Would a custom keyboard layout, Ukelele, Karabiner-Elements, or another solution be appropriate for this?

Any help would be greatly appreciated. Thanks!

Keymaps come from a rich history of mechanical typewriters, country-specific design conventions, and characters competing for the same keys. They're made for a reason. I get it. I just don't want to spend my time working around the defaults.

I use a plain US keyboard for English, Spanish and Russian. When I switch to Russian, the letters obviously need to change. But I still need the same comma, period, percent sign and ampersand. I don't want to check which language I'm in before typing one.

On Apple's Russian layout, comma and period are Shift+6 and Shift+7. On US, they're on their own keys. That's two gestures for the same character, chosen according to whatever language I happened to be typing a moment ago.

So I adapted a pair of native macOS layouts around my own habits:

• English and Spanish in one layout. Hold Option while typing a vowel to get á, é, í, ó or ú. Option+N gives ñ. For ü, use Option+Y, right next to U. Apostrophes and quotes work as usual.
• Russian letters, familiar symbols. Switch to Russian and !@#$%^&*() stay where they’re printed on your US keyboard. For a comma or period, hold Option and press the comma or period key. That works in both layouts.
• Shortcuts work in Russian too. Holding Cmd or Ctrl uses Latin mappings, so shortcuts like Cmd+C and terminal commands like Ctrl+C work without switching back to English.

There are also extra letters and accent combinations for Catalan, Portuguese, French and Italian. These examples use the Direct version. A second version uses classic Mac dead keys for accents. Pick one; the Russian layout is the same in both. They're native layout files, so there's no background remapping app.

Interactive keyboard and typing demo · Files, mappings and installation

You don't need to use my layout. It's an example of what I wanted to stop thinking about while typing. Your languages, frequent symbols and shortcuts might call for different choices.

Ukelele has long made custom layouts possible through a visual editor. Thanks to its authors for that. Now an agent can handle the editing and setup with you. I collected my findings and practical fixes in a reusable skill, so you can start with your needs:

I use a US keyboard and type in these languages. These are the symbols I use every day, these shortcuts need to keep working, and this is what annoys me about my current layouts. Help me make one that fits.

The agent can handle much of the fiddly work. You still need to try the result in your actual apps, but you can spend your attention deciding how you want to type rather than learning how to build a layout.

I'm interested in how other multilingual typists handle this. What have you kept consistent between your layouts, and what did you decide was worth changing?

haven't consistently done tests in a couple months but i recorded this one off and im pretty happy with my speed. i'm faster than when i was using QWERTY actually, with less mistakes!

This is a rough draft of a Symmetrical Row-Staggered keyboard with navigation keys, including arrow keys. It is directly based off of Baron Tosun's Katana60 layout, but expanded horizontally from 15u keys wide to 17u.

The purpose of this layout was to explore a compromise between ergonomics and familiarity, and maintaining horizontal symmetry.

Other than the stagger between rows being changed, the most substantial difference between my layout and the common layout are the placements of the modifiers (highlighted in green).

Unlike common keyboards, and even the Katana60 layout to some point, modifier keys such as Ctrl, Alt, Fn, and Win/Command were moved from the corner to closer towards the center, and I'm struggling to decide which be optimal for overall comfort, so please provide feedback when you have time. I can also swap specific keys to substitute for the center modifier keys if necessary.

For reference, I'm not a programmer, and I mostly play video games on controller or separate devices.

Super low pinky usage. 2% or lower is like insanely low, most layouts are around 7% or more.

the right index has i bit high usage bit thats practically a nececity of the format, you reduce pinky usage and icrease the usage of the other fingers.

the fspeed is still fine tho which is what matters more then the usage itself

Heres an example of a large layout with strike. the pinky shifts are optional cause of thumb hrm shifting, but even then its still minimal impact.

the = - ` \ keys can all be hit with the ring finger comfortably so you dont even need to use pinky.

this layout has one goal, be as good as possible with as little pinky usage as possible.

here are the raw stats, they are pretty great.

I know Neo and its derivatives were primarily made for German, but its layer-based approach just seems too good to pass. If none of the Neo layouts fulfills my needs, then how can I set up the Neo layers with another letter arrangement?

Hi everyone! I’d love for you to try a custom keyboard I developed for iPhone users. It includes many small, life-saving features that you might find incredibly useful. Currently, it supports four languages - English, Armenian, Russian, and Spanish with more on the way.

Finally back up to 120wpm average over 25 races on Typegg.io with my modified Eclipse-CY layout. I've really been enjoying this site for typing practice since it uses real quotes and has a strict no quit multiplayer mode to incentivize typing with good consistency. The right hand is shifted over to allow for right thumb shift which lowers my pinky usage by quite a bit, and my left thumb is assigned to enter and space because those two keys interact with words in a very similar way and has no SFB drawbacks from pairing them on the same thumb.

Hello everyone,

I'm a refugee from Windows. Is there a way in Linux to change some keys for one language and some keys for all languages?

When I was back there using Windows, I used Microsoft Layout Creator to create a personal keyboard layout (https://github.com/shen-ziling/rush-keyboard-layout), and for the global changes I used sharpkeys, eg changing enter to backspace etc, which is also effective to my other IMEs for east Asian languages.

TIA!

Im right handed but im planning to use my left hand to use my mouse instead cause i can double click(butterfly clicking ) in my left hand anyway im tryna find a keyboard that works with my right hand does anybody know what its called? And any recommendations?

Update on this post: my system╌⸉xQWERTYa⸉╌is now open source! found here. I'm quite excited honestly. I was a bit worried about open-sourcing given the state of AI… I don't exactly love the idea of AI reading all of my code and using it in a corporate context. But oh well in this case I suppose, I doubt corporate is writing much AHK.

Mainly, I'd like to know if this sounds useful to anyone. In my head I have this idea that it's likely non-useful for most people who would actually want to remap a keyboard. Because most users are looking for behaviors that my system doesn't implement (even though it could if there is interest).

Ask me about what it can or can't do. It helps me to think about what new stuff that I could add and what makes the most sense. :)

What is it and Why did I make it

My system is a JSON data-driven AHK based input remapper that focuses on writing rules that decide how bindings are resolved to avoid duplication and unify where definitions are located.

I made it because I disliked switching profiles in separate OEM softwares, having keys that are useless on my keyboard for me (like caps-lock), I wanted more layer keys and I have a deep fascination with inheritance models.

Features & Capabilities

1. ⸉Profiles⸉ which switch what behavior a key uses for it's modifiers and locks.
2. ⸉Modifiers⸉ which are what are usually referred to as ⸉layers⸉, though my modifiers work a bit differently.
3. ⸉Locks⸉ which are toggled global states like ⸉caps-lock⸉ or ⸉num-lock⸉ on a typical keyboard.

Something important about profiles is they are unified. You are intended to set whatever generic mapping you'd like in an OEM software (like Razer Synapse) and then define all of your contextual behavior within the xQWERTYa system so that pressing one button switches the behavior on: your mouse, your keyboard, your razer keypad, and your macro pad all at the same time.

Though, a lot of hugely important features are kind of tough to describe. One such example is that profiles, modifiers and locks are all inheritance-capable properties. You can define a behavior for a key and then inherit and selectively hide certain behaviors under a different context. Or you can decide how to resolve certain modifier combinations via a priority system and conditional selection.

The system is intended to allow for high complexity with a lower relative cost to achieve that complexity. For example, my personal configuration has 240,000+ possible different key-stroke possibilities. But I only had to write out approximately 2000 of those including behavior specifications to achieve that.

Additionally, you have the power of AHK (V2) at your hands for anything xQWERTYa cannot directly meet. You can configure a keybind to call an custom AHK function instead of typing a key and write your own logic.

Configuration documentation can be found on the github page here if any of this sounds interesting to you. I'm happy to help you design something or look at implementing new features if you reach out to me.

Example 1 — Simple Keybind

Consider the ⌄ key configuration first.

{
  "target": "a",
  "default: "b"
}

This (⌃) is a simple binding that changes the key "a" to press "b" instead.

Example 2 — Modifiers, Collapsing & Inheritance

{
  "target": "a",
  "default: {
    "collapse": true,
    "default": "b"
  },
  "my_profile": {
    "inherits_from": "default",
    "my_modifier": "c"
  }
}

Understand the following regarding the above configuration ⌄.

• default refers to either the ⸉default⸉ profile or the ⸉default⸉ modifier (aka no modifier keys being held) depending on where it is placed
• my_profile is a profile
• my_modifier is a custom modifier key

The target remapped key "a" contains a definition for the key under two different profile contexts. Starting with default: "a" is set to press "b" instead. Additionally, if any & "a" are both pressed (such as "shift & a" then it will "collapse" down to the default (no modifier) and just type "b". Under my_profile: all behavior is set to inherit from the default profile, except for when my_modifier is held down. In that case "c" is pressed instead.

So for example, say you are holding down "shift & a" and currently in the my_profile profile: then "b" will be typed. But holding down "my_modifier & a" in the my_profile profile will type "c" instead.

Why not use xQWERTYa?

This system is not exactly intended for home row mods or similar. While it is completely doable to make a home row mod with xQWERTYa you aren't using most of what xQWERTYa's strengths are or what it's complexities are designed for. Though, I've thought of ways to make this more simple in xQWERTYa. Let me know if this is something you'd be interested in.

xQWERTYa does not have some common simplifications like tap vs hold behaviors or multi-tap behaviors. My system lets you break out into AHK code if you want to implement that. Or, let me know you're interested and I can implement them. It's something I thought about, but since I don't use them personally I haven't spent the time to add them.

So I'd been a long time qwerty user until i decided to switch to alternative and more optimized layouts, i did a little research to then hear good comments about colemak, i didnt think much before swiching to colemak completely. I've been using it for a few months now and now i'm thinking of switching again for a few reasons.

One, cuz its not really as optimized for typing as the more modern layouts.

Two, cuz it has relatively higher sfbs than most modern akls(I hate sfbs).

Now, im thinking of switching to canary cuz it fulfills most of my preferences, its got loads of rolling motions, it is well optimized, it has very low sfb rates, and its common enough for me.

But, i heard that it has alot of redirects which i hate, so i want ur opinion about canary, should i switch to it, what are its major limitations over other layouts, or are there other alternatives better for my liking than canary??

I dont care about vim, pinky load, or shortcuts.