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
This is, as of today, still the case. It has to do with the fact that Morbig, once it has delimited a token, only knows the position of the delimiter, and not the token itself. It would require a form of "position-aware" token buffer.
The column numbers of starting position are still wrong, as demonstrated by the following example:
which produces the following JSON for the word
true
:The text was updated successfully, but these errors were encountered: