Few issues regarding Korean

Hello.
Although Discord is generally a very good platform, it has some weird issues regarding Korean.

When you type a Hangul character right after rich text feature with visual cue(e.g. right after opening/closing of ```, right after user/channel mention, right after closing part of strikethrough, or even right after unicode/server emojis), the hangul typing system completely breaks and produces bunch of garbages.
One Hangul character consists of different alphabets(jamo), assembled by sequence of inputs. A Hangul character 밝 is typed by sequential inputs of ㅂ, ㅏ, ㄹ, and ㄱ.
Now, if I type exact same input right after ```(no space), instead of 밝 which should be typed, this happens.

```ㄱㄹㅏㅂ

Notice how sequence of input is reversed. After each input, it should hold the data previously typed until moving to next syllable, but it just forgets what I was typing and spits raw jamos. It happens pretty often considering the condition for reproduction is just some rich text and Hangul keyboard, and it's extra annoying because after ```ㄱㄹㅏㅂ was typed, the cursor stays between ``` and ㄱㄹㅏㅂ, and pressing backspace after realized you typed bunch of garbage doesn't help because you need to press DELETE since cursor is in front of the garbages. It harms the experience pretty badly, and I want to see this issue fixed as soon as possible.
I wonder other languages that does not uses latin script has same issues.

Wasn't tested anywhere else, but it happens on Windows 7/10. It doesn't happen on android, probably because it doesn't have visual cue for rich text feature.

And one more thing, searching with Korean keyword is absolute dogshit. It's horrible beyond measure. Keyword searching in Discord doesn't detects word 'partly contained' in one big word, and it makes searcing with Korean keyword a nightmare.
It has some link to structure of the modern Hangul, so I'll explain it briefly. English isn't my native tongue, and I don't know technical terms for linguistics even with Korean, but I will try my best to explain it.

Hangul uses space as word divider, but the way it is used is quite different compared to latin script based languages.
Hangul does not uses space in between each and every words, good portion of particle is rather combined with base word and move around as one single block. In example, 'human' is translated to '사람'. 'of human' is translated to '사람의', 'at human' is '사람에', 'to human' is '사람으로'. Notice that the postposition particles didn't separated from base word. And, although it's not 'orthodox' usage, spacing is often skipped, or ignored and not used at all, because it's still readable.

AND BECAUSE OF THIS, searcing for Korean word is vomit-inducing word guessing game, with hundreads of possibilities you couldn't think. Let's say you have a faint memories with one chat message, and it had a word 'cake'. Now, in English, it probably contains 'cake' in whole word so searching for it is not a problem. But in Korean, if the word without postposition particle(i.e. 'pure' word) doesn't have a desired result, you would have to search with random stupid particles such as 'of cake', 'to cake', or something else. And good chance you'll never find the chat message. Remember I said spacing is often skipped or ignored? Korean for 'eat the goddamn cake' is can be roughly translated to '제발 케이크 좀 먹어'. But during middle of the conversation, I could type things like '제발 케이크좀먹어'. And it's completely readable. Current searching doesn't detect '케이크' out of this, so you are out of luck and the funny moments are gone.

I propose the option for searcing 'any occurrence' or simply 'any', meaning it matches input of certain text regardless of word block. In this searcing mode, 'pain' and 'aint' would both match for the message containing 'paint'. It not only greatly helps Korean users, some other foreign language speakers/latin-script language speakers will have its benefit.

Thank you for listening so far, have a great day.