You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

hexadecimal unicode input broken

After updating from Catalina to Monterey (I skipped Big Sur) I'm not able anymore to enter the accented a (à acute) with unicode input. According to character viewer the code is U+00E0, which is the expected code for acute a, however if I try to type option + 00E0, with hexadecimal unicode input selected, nothing happens. All other accented characters work as before. I discovered it because I use several keyboards running QMK firmware which are programmed to use unicodemap to enter accented keys. If I enter the character by double clicking it on Character Viewer the letter is pasted in the target document so it seems it's really a problem in decoding the input from keyboard. I'm italian so accented keys are necessary to write in my own language.

Clearly, or something happened to my computer configuration during the update or the problem is due to a bug. Can someone running Monterey try to replicate the problem?

Thanks

MacBook Pro 13″, macOS 12.0

Posted on Dec 5, 2021 9:13 AM

Reply

Similar questions

9 replies

Dec 5, 2021 11:17 AM in response to Tom Gewecke

QMK is mainly used by custom keyboard builders. If you are curious, the official github repository can be found here: https://github.com/qmk/qmk_firmware . There is quite an active community around this system but maybe is not that known outside custom builders.

In fact, I built the keyboards I'm using by myself and I customized and built the firmware to my liking. I choose to use unicode as it can be used on all major systems (macos, win and linux). As I use different systems for work (win and linux) and home (macos) I can use the same keyboards with all my systems. It's possibile to configure the firmware to work with the option key shortcuts but that would only work on mac.

Dec 5, 2021 1:51 PM in response to a5o

Technically speaking, à is a grave accent. á is acute.


That Unicode hex input must be something invented for Windows users. That used to be (still is?) the only way that Windows users could enter high ASCII characters. Clearly, Apple seems to have broken this input method in Monterey. I was able to get it to work for other characters around that one, but not with that specific character. But curiously, I couldn't get any of it to work at all at first. It took some effort. And by the time I did get it to work, my emoji and symbols viewer was completely broken. It won't display at all anymore. I guess I'll have to restart to get it back. Sadly, this does not surprise me at all. Monterey is one of the buggiest Apple operating systems that I can remember. This is just one more oddball for the list.


My recommendation would be to avoid the Hex input method. As I said above, that is clearly something invented for Windows users. The traditional method for Mac users is as follows:


option c: cedilla ç

option `: grave accents à, è, ...

option e: acute accents á, é, ...

option u: umlaut/diaresis ü, ï, ...

option i: circumflex î, ô, ...

option n: tilda ñ

option q: œ

option ': æ

option s: ß

option/shift option \: «»


This is the old-school Mac way. It heavily favours European languages, but that should be fine for you. It may take a bit of time to develop the muscle memory, but once you do, it never goes away.


Later, Apple added the press and hold method, but people report that this people stops working half the time. This traditional method has never failed.

Your custom keyboards are a different problem. They shouldn't be dependent on this hex input method. They should use something a little lower level and generate the specific unicode characters using the correct USB API. This would be the "correct" solution. An easier solution for someone that only needed European languages would be to just change the mapping to use the traditional Mac mapping. Then you wouldn't need the Hex Input method at all.

Dec 5, 2021 10:42 PM in response to etresoft

I'm not completely sure it's something related to windows. Indeed, in order to capture extended hex codes on windows you need an extra piece of software (WinCompose) while on linux and macos the unicode input is supported natively. The option ` method is fine for the moment, however that means using different way of entering accented keys depending on the system I'm using at the moment. Regarding the reason why I'm not just sending the accented keys directly from the keyboard, the reason is I much prefer the ansi-US layout to the italian layout. In order to make place for accented keys many symbols have been scrambled around in the italian/european layouts and as a programmer I use a lot of symbols. The ansi layout unfortunately does not have accented keys; the only way to enter them is by using dead keys on us-international keyboard layout which works on all systems but is not very handy because, again, I use ", ', and ` a lot while programming, and having to type the space bar every time is a pain. What I did in fact is to map accented keys on a different layer on my keyboard. In practice when I hit a dedicated modifier key on my keyboard and e, a, u, i, o I get the corresponding accented character. I find it much better than the traditional european layouts where accented keys are usually placed at the right extreme of the alphas.

Dec 6, 2021 5:24 AM in response to a5o

a5o wrote:

in order to capture extended hex codes on windows you need an extra piece of software (WinCompose)

I haven’t used Windows in about 20 years, but I think it still works. The trick is that you have to use the numeric keypad. Hold down alt, press +, and then enter the value that you have memorized.

macos the unicode input is supported natively.

Apparently it isn’t supported. 😄

The option ` method is fine for the moment, however that means using different way of entering accented keys depending on the system I'm using at the moment.

This is the “native” method. It predates all of macOS. It dates from the original Macintosh circa 1984. I strongly advise using it. There is absolutely no faster method.

Regarding the reason why I'm not just sending the accented keys directly from the keyboard, the reason is I much prefer the ansi-US layout to the italian layout. … I use ", ', and ` a lot while programming, and having to type the space bar every time is a pain.

Even Canada has its own keyboard layout, at least for PCs.

Dec 6, 2021 6:58 AM in response to a5o

a5o wrote:

Regarding the reason why I'm not just sending the accented keys directly from the keyboard, the reason is I much prefer the ansi-US layout to the italian layout.

Thanks for that clarification. It's an interesting problem faced by a lot of users. If you put the Italian accented characters on the Caps Lock level of the "US" layout, would that work on all systems? Or is that level already required for programming input.

hexadecimal unicode input broken

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.