You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They are all multibyte characters(except eol). The original display result is
And when I use s, the result is like below:
Some characters become encode number(?) like 谓 becomes <93>. The later ones occupy 4 grid. I believe they are direct match labels. Is there any rendering bug?
Besides, when I enter 生 after s shortcut, the result is
The display lines seems weird.
The f label on the first display line seems to be misaligned, which should be after 生 char.
The next to last char 义 on the second display line does not show up. Maybe a render bug?
etc
Is multibyte chars not taken into consideration during rendering?
Besides, with multibyte chars, position calculation may be more complicated I think.
Interestingly, I cannot reproduce the first example (the unique chars are highlighted normally for me in Lightspeed). Try these with Leap, because there I fixed a bug related to multibyte characters, if that works, I'll just apply the same fix here. I can reproduce the alignment issue (in Leap it works as it should).
I use Chinese a lot, so frequently I want to jump to a position between Chinese characters.
For example, with the content of
They are all multibyte characters(except eol). The original display result is
And when I use
s
, the result is like below:Some characters become encode number(?) like
谓
becomes<93>
. The later ones occupy 4 grid. I believe they are direct match labels. Is there any rendering bug?Besides, when I enter
生
afters
shortcut, the result isThe display lines seems weird.
f
label on the first display line seems to be misaligned, which should be after生
char.义
on the second display line does not show up. Maybe a render bug?Is multibyte chars not taken into consideration during rendering?
Besides, with multibyte chars, position calculation may be more complicated I think.
Updated:
Environments
Minimal configurations
The text was updated successfully, but these errors were encountered: