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 line suggests the engine API is exposing our internal UTF-16 string representation. Though cognizant of the performance hit, I think we need an API where all string content is ordinary char*'s of UTF-8 (maybe not the only one, but certainly the one that code like @adang1345's would use)
The text was updated successfully, but these errors were encountered:
We refer to literals via offsets in the text (and not making a copy as we used to do), that text is supposed to be of a fixed character size (UCS-2), if we convert to (multibye) utf8, we should also convert to byte offset.
Python also used UCS-2 as it's internal text representation, for all string - offset combinations to work in more exotic languages. But for emitting tracing strings, that surely can be utf8 encoded.
iknow/modules/iknowpy/engine.pxd
Line 30 in 60b1c74
This line suggests the engine API is exposing our internal UTF-16 string representation. Though cognizant of the performance hit, I think we need an API where all string content is ordinary char*'s of UTF-8 (maybe not the only one, but certainly the one that code like @adang1345's would use)
The text was updated successfully, but these errors were encountered: