-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Updating Slate editor to support Korean #1347
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Reopening as I still have the same issue with the current editor. I'm Japanese and having problem in inputing text on both rich-text and markdown editor via Japanese IME. There is a report that updating slate from 0.47.0 to 0.57.1 solved the problem to some extent. The test above is done on netlify cms v2.10.51. |
Hi @acomagu updating to the latest version of slate is not a simple task. See https://docs.slatejs.org/concepts/xx-migrating. |
Could we consider moving to other editors such as Quill.js? It seems like Slate's CJK support is still far from perfect even in latest versions. |
Will the efforts describe here: https://decapcms.org/blog/2023/03/march-23-status-update address this (and other related issues described in ianstormtaylor/slate#2368)? |
The latest Slate version should fix most problems with the editor, and probably this one too. |
@aywander can you test if Korean is better supported now in Decap 3? |
@BasixKOR are you maybe willing to test if this works now? |
I'm Japanese and I'm having trouble typing in Japanese. Can someone help me? |
I'm not sure if it is only for Korean, the current editor doesn't work well with Korean. Whenever typing characters, it omits some words. More details here: ianstormtaylor/slate#1701
There are some other issues left but this particular problem has been solved in the latest version of Slate. Could you make the Slate version up to date for Netlify?
The text was updated successfully, but these errors were encountered: