Emoji Shortcodes now use keyboard layout for language

[realChesta]

Is your feature request related to a problem?

I've been using chat programs since they have existed and my habits are deeply ingrained.

The behaviour of emoji autocomplete has changed with a recent update (I'm using 11.5.269855 Stable) and the colon search now uses the keyboard layout origin's language instead of the system or even app language (english).

Now when I try to type :thinking: nothing happens, because my language is detected as German, since my keyboard layout (but not system language or spelling) is set to German QWERTZ. So I'd need to type :denken: - a thing I would never write in any context.

The exact same issue replicates across all emojis. I don't know what most emojis are called in german and in most cases I don't type in German, and still, the emoji names are translated.

This issue also propagates to emoji search for custom emojis (and seemingly stickers too? but there it's more inconsistent)

Describe the solution you'd like

Give users the option to revert back to the default english emoji names instead of forcing translation based on some undocumented rules (seemingly based on keyboard layout).

Describe alternatives you've considered

I tried changing system language, input language on macOS level, ap language, and more. Nothing changed this behaviour except for changing keyboard layout, which cannot be the solution here.

[arsenico13]

I have the same exact problem. My keyboard layout is set to Italian and now all my shortcodes are in italian and the english ones don't work anymore. I have no clue what they're called in italian (and I don't want to learn their names in Italian, I'd prefer to stick using english shortcodes).

I tested changing the keyboard layout from Italian to English and it worked so I think is directly tied to that.

I hope this get fixed soon. Thank you

[Heliosmaster]

This has been quite annoying in the last few days. FWIW i checked that with 11.3.1.269392 works fine, and with 11.4.1.269807 is already broken.

[lepinkainen]

Same problem here, but with Finnish:

Now when I try to type :shrug: nothing happens, because my language is detected as Finnish. So I'd need to type :kohautus: - a thing I would never write in any context.

The exact same issue is for all emojis. I have no clue what they're called in Finnish. I don't want to learn their names in Finnish. In most cases I don't type in Finnish and still the emoji names are translated.

Please give us the option to revert to english emoji names, preferably default to english.

[tokual]

Same issue with the Swiss German keyboard layout. What is even more annoying is that the search terms / keywords for the emojis aren't the same in each language so even translating the search term doesn't even bring up the same results that one would expect from the suggestions... very annoying and this behavior definitely was not like this just a couple of versions ago.

[jgmontoya]

This is also an issue for me using version 11.5.269857. Quite annoying.

[Siguza]

Running into this issue too, it's annoying as hell. And it should be noted that this is a newly introduced bug - a few months ago, this was not happening.

[oh4kpn]

Any news on this one? This current situation is unbearable - is there a keymap/language editor coming in app or some setting where one can choose english emojis instead of the languages I dont even know but have to use their keymaps to get the keyboard matching to physical keyboard?

[fbbdev]

This made the app unusable for me too. What about just allowing to search all languages at once instead of just one? A few keystrokes should be enough to disambiguate quickly.

[chlab]

Commenting to add my vote to this issue. Would love to see a fix. The easiest imho would be to use the system language instead of the keyboard layout. Alternatively, provide a setting to set the language.

It would be great if someone could look into this! ❤

[AlbertMontserrat]

Same on my side, super annoying. There's some schedule for the fix? Or at least aknowledge?

[DrCondor]

Commenting to add my vote to fix this as well

[TapioHautamaki]

Same issue here! I've been frustrated with this for months.

[josemigallas]

Same problem here! It's driving me mad!

[anperez]

I have no experience with Swift, but did some digging and it seems like this issue was introduced by this change: https://github.com/overtake/TelegramSwift/commit/4fabc33116d33f60d92eab1327b05ee73237f48d#diff-a2b310c12795b5f836d241c40dfd6c2191dda8697bf0e53e121eb6d301c583e2R22

I've created a revert PR to fix it in: https://github.com/overtake/TelegramSwift/pull/1252