I am personally finding the same issue with Japanese actually (not my daily driver, just tested out for situation confirmation). Also, the underline issue does not appear on the stock app for me either.
On the other hand, I see the underline even when searching for fonts in Bear settings.
Another finding: Bear works as intended when I first boot the app (no blue underline, [[ works as intended ). Then the problem starts as I start trying to input a Korean hashtag. From then on all Korean inputs starts to have blue underline.
Another finding: Bear works as intended when I first boot the app (no blue underline, [[ works as intended ). Then the problem starts as I start trying to input a Korean hashtag. From then on all Korean inputs starts to have blue underline.
Oh, I see what you mean.
Although for me, there is the underline thing but it gives me the tag straightaway. Are you updated to the lates Macos version (sequoia 15.3.1).
Also, try to go to app store, and when you go into the updates section, it sometimes doesnāt appear. Type in searchbar bear, and clikc on it. There may be the update. button if you havent updated to the latest.
It shows the tag straight away. Is there any chance you couldnāt see it? Or could you send me a video or pic so I can see whats happening straight away?
Thanks! (hope i can help you)
No problem.
So what is happening is that you create a korean hashtag for a new tag, but then it gives the blue underlines, and only when you restart the app it doesnāt work?
Iāll try to see what the problem is but good luck finding a solution!
I think this could be because when you type the Korean letters, your Mac automatically thinks that you have made a spelling error (because you usually type more than 1 character for a whole character set in Korean). This is the blue underline I think that could be doing this. Also, the tag only works at the end, because Bear (and Mac) is trying to decide whether to render it as a new tag or automatically show this as the korean tag you already have. I donāt know if there is a way to fix this, but I will dig deeper