I will explore, thank you for your thoughts. I tell myself you have to better, yet the task list is long and somewhat disorganized. And the are only so many seconds each decade.
- Alan
On Sep 18, 2017, at 12:29, tim Rowledge tim@rowledge.org wrote:
We do have assorted string encoding stuff in the current image but the actual UTF8 results of #squeakToUtf8 (for example) are just ByteStrings. Which is actually rather confusing and annoying because now you have no way to know what encoding is relevant other than be carefully keeping track manually. Normally of course, within the image we have perfectly usable strings because any time a unicode character that is outside the 1-byte range is used the string becomes a WideString.
We need to do better. Look at TextEncoder and its hierarchy for more info.
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: RLBM: Ruin Logic Board Multiple