I used to be a macOS user and had a “Keychron Q3 QMK Custom Mechanical Keyboard ISO Layout” keyboard. I was very satisfied with this keyboard. Now I have sold my Apple equipment and migrated to Linux.
Keychron currently cannot deliver keyboards with a Swiss German layout (all sold out). The Swiss German layout is very important to me. What alternative for Linux? It should be as close to 1:1 as possible to the Keychron.
Have you considered getting another ISO board and searching for ISO-CH keycaps? Keychron seems to have at least one set in stock, and if Digitec is a reputable store (I don’t know; dumb American here), they have some too.
Part of the reason why @wjrii suggests that is because ISO layout keyboards are uncommon in general and so searching for a particular one will limit your choices even further. And, of the DIY stuff to do, swapping keycaps isn’t too bad. If you really want to buy one with zero customization, you may be searching awhile.
AFAIK, ISO keyboards are just sending ANSI scan codes anyway – there’s two extra ones, KC_NUBS and KC_NUHS, for the keys ANSI lacks, but everything else is ANSI. The OS then does the remapping based on its settings for the language. E.g., in ISO-CH, this means that the Z key on the top row is actually sending the key code for KC_Y, but the OS is translating it to Z. Meanwhile, the Y on the bottom row is actually sending KC_Z and then getting translated to Y.
In poking around a little more, it appears Digitec is a pretty well known online retailer in Switzerland, and they seem to have some swiss boards in stock. Nothing super special, but I saw several Keychrons.
As others have mentioned, and you’re finding, ISO beyond UK or DE can be a challenge to find with pre-made keycaps. That really is the only difference though, and changing caps is not messy or risky. Even the Mac versus Linux difference only really lives in Software. Anything with a mature remapping utility should be able to be made to work.
Re “I don’t want to do any DIY at all”: You can not avoid that with a Keychron keyboard (unless you get one of the few gamer-oriented Keychron keyboards with ‘ISO’ variants, without Mac support)
The Mac keycaps are installed by default, so for Linux you would have to change some keycaps.
The Windows/Mac switch is also in the Mac position by default, so you have to change that as well. If it isn’t, it is a sign the reseller or Keychron is trying to sell a return and/or a faulty keyboard as a new keyboard.
Gamer keyboard or not, the context menu key is (by default) also in the wrong position (occupied by the Fn key), a sin not only committed by Keychron. It fact, it is completely absent. A workaround is to repurpose the right Windows key as the context menu key (the keycode is KC_APP, notKC_MENU). And swap the keymappings and the keycaps. The Mac Option key can be used as a suitable keycap for the context menu key.
What is it used for? For example, invoking the context menu in Nemo, FileZilla, Archive Manager, etc, to avoid having to use the mouse. It is usually also faster, though the required Tab’bing has become excessive; one workaround is two macro keys issuing four Tabs and four Shift + Tabs, respectively, suitable for switching between the left and right panels in FileZilla.
References
Documentation for the old keycodes from 2019. In general, these are the ones accepted by Via and possibly the Via clone (in most cases only an alias and only one of the aliases if there is more than one). Note: It does not cover Keychron’s custom keycodes.
Re “Even the Mac versus Linux difference only really lives in Software”: The position of the keycodes for Win/Alt and Option/Command are swapped, both left and right
Which is why Keychron keyboards have a Windows/Mac mode switch (unless it is a gamer-oriented Keychron keyboard, without Mac support).
True, but MacOS has a built in setting to remap mod row keycodes, there are utilities for Linux that do the same, and proper custom firmwares can change the actual code that’s sent (if you pardon the slight expansion of the definition of “software” to include firmware). IMO it’s just not the hill to die on when picking hardware. If OP is particular enough to come asking for help from the likes of us, I think they’ll be much happier accepting that they’ll need to change a couple of keycaps and/or remap a couple of keys.
Re “…proper custom firmwares can change the actual code that’s sent”: That is what I do (for example, I just migrated 10 of my stable and tested Via macros to my QMK macro engine), but very few users will ever do that
Even flashing (premade) keyboard firmware is usually too much of a barrier (for example, from SRGBmods). Not to speak of setting up QMK. Though it is possible to do in one or two command lines (near “it isn’t any more complicated than”), even for Keychron’s fork (and any other fork and nonstandard branch), without the need for anyGit or Make gyrations. Even for Vial, treating it as any other fork of QMK.
The most they will ever do is using dynamic keyboard configuration. There are exceptions, of course.
Since you want a finished keyboard without DIY, the in-stock Swiss boards mentioned above are probably the best place to check first. As a fallback, look for an ISO barebone that supports QMK or VIA and a separate Swiss German keycap set. Ask the seller whether they can assemble it for you, and check that the keycap set fits the board’s layout. VIA can also help you map modifier or context-menu keys without compiling firmware.
If you’re offering to build something, the key question is whether it can be full ISO with Swiss German legends and QMK/VIA support. A hybrid ANSI/ISO layout won’t really match the Q3 ISO or give OP the Swiss German key labels they need. If you can do that, it’s a useful alternative; otherwise the barebone-plus-Swiss-keycaps route is more realistic.