Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

korean support issue. #1210

Closed
cybertramp opened this issue Feb 12, 2019 · 6 comments
Closed

korean support issue. #1210

cybertramp opened this issue Feb 12, 2019 · 6 comments
Labels

Comments

@cybertramp
Copy link
Contributor

@cybertramp cybertramp commented Feb 12, 2019

Operating system

  • Windows
  • macOS
  • Linux
  • Android
  • iOS

Application

  • Desktop
  • Mobile
  • Terminal

Hi!
I found a korean input bug.
Strange special characters are displayed like this when I type.
Could it be an UTF-8 encoding problem?
Please check this bug.

Alt text

Thank you for providing a good program.

@thereblight

This comment has been minimized.

Copy link

@thereblight thereblight commented Feb 26, 2019

I'm having the exact same issue with Joplin 1.0.127 on Windows 10 and Kubuntu 18.04 with Plasma 5 DE. (FYI, Debian Buster with Xfce doesn't have this issue.) And this happens on the editor area only. On the search box or the note title box, Korean input works without any glitch.

As I understand it, The note edit area in Joplin is embeded Ace editor. So I tested it on the Ace editor demo site(https://ace.c9.io/build/kitchen-sink.html), and Korean input works as it should. So maybe this issue ocurrs in the course of implementing the editor to Joplin.

I assume that CJK issues like this is quite low in priority and I understand that, and this doesn't make the app totally unusable, but to a Korean user like me this is quite an annoying show stopper. I hope that it's dealt with someday.

@Icy-Breath

This comment has been minimized.

Copy link

@Icy-Breath Icy-Breath commented Mar 27, 2019

I have the same issue on Windows 10 while it works fine on Linux Mint 19 (Cinnamon desktop).

@stale

This comment has been minimized.

Copy link

@stale stale bot commented Sep 22, 2019

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "backlog" and I will leave it open. Thank you for your contributions.

@stale stale bot added the stale label Sep 22, 2019
@Icy-Breath

This comment has been minimized.

Copy link

@Icy-Breath Icy-Breath commented Sep 25, 2019

Problem still exists.

@stale stale bot removed the stale label Sep 25, 2019
@stale

This comment has been minimized.

Copy link

@stale stale bot commented Dec 24, 2019

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@stale stale bot added the stale label Dec 24, 2019
@stale

This comment has been minimized.

Copy link

@stale stale bot commented Dec 31, 2019

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

@stale stale bot closed this Dec 31, 2019
@lock lock bot locked and limited conversation to collaborators Jan 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.