-
Notifications
You must be signed in to change notification settings - Fork 226
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
Crash when processing a file with multibyte characters #35
Labels
Comments
Yay grapheme clusters vs bytes! |
jpsim
added a commit
that referenced
this issue
Mar 26, 2015
This is now fixed in the |
This is now fixed in master. |
SteffenL
pushed a commit
to SteffenL/SourceKitten
that referenced
this issue
Feb 13, 2019
update for jazzy-issue-333-pt2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I tried to run jazzy with multibyte texts and
I found it doesn't work with multibyte texts.
It can be reproduced by parsing this code.
I’ve investigated a little bit and I seems like below.
In values from sourcekitd(?) like offset or bodyoffset, a Japanese character is counted as 3.
But NSRange in filteredSubstring counts a multibyte character as 1.
As a result, the range index will be out of bounds.
The text was updated successfully, but these errors were encountered: