When entering Chinese punctuation (such as 。 ， ！ ？ ¥) on the Mac platform, it will become English punctuation.

[HughLink]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. macOS 11.4]
• Neovide Version [e.g. 0.6.0]
• Neovim Version [e.g. 0.5.0]

Please run neovide --log and paste the contents of the .log file created in the current directory here:

Additional context
Add any other context about the problem here.

[fredizzimo]

I see some problems in KDE Plasma 6 Wayland with fcitx5 too.

It looks like neovide_input_ime now defaults to false for some reason. Can you try to set it after Neovim has started, and see if that fixes the problem?
https://neovide.dev/configuration.html#ime

Meanwhile I will try to fix the defaults.

[fredizzimo]

I hope this fixes it:

• fix: Broken IME enable and popup position #2571

[HughLink]

Thank you, but setting neovide_input_ime = true did not solve the problem

as follows:
Use nvim in Neovide to enter Chinese punctuation as English punctuation
Use nvim in iTerm2 to enter Chinese punctuation as Chinese punctuation.

@fredizzimo

[HughLink]

I hope this fixes it:

• fix: Broken IME enable and popup position #2571

I have also compiled and used this version, which fixed the position problem👍, but did not fix the Chinese punctuation problem.

[fredizzimo]

Ok, can you run neovide --log then type something with that punctuation and then close neovide. Then attach the log file here. I don't have a macOS machine myself so I have to rely on the log file to debug it.

[fredizzimo]

I checked this on Linux Wayland with the fctix5, fcitx5-chinese-addons, pinyin combination. And the punctuation is correctly Chinese with that. So it's probably a macOS specific problem.

[fredizzimo]

I think this might be related to this:

• Character separation issue when typing in Korean #2014, which has been reported to winit Character separation issue when typing in Korean rust-windowing/winit#3095

But we need a log file in order to confirm. @falcucci was able to repeat it so I think he can provide one.