[Cuis-dev] UTF-8 Unicode editors

Andres Valloud ten at smallinteger.com
Sun May 1 09:44:22 PDT 2022


Be careful not to confuse sequences of code points (integers) with their 
encoding (UTF-*, and others).  Those two are not the same.

On 4/30/22 12:56 AM, Luciano Notarfrancesco via Cuis-dev wrote:
> This is super cool. I’d like to have unicode symbols at some point, not 
> sure if we’ll need WideStrings in UTF-32, or how big will be the impact 
> in memory use if we make all strings wide (not only memory use, but also 
> speed, because we have primitives for String). Anyway we’ll see once we 
> start experimenting. Thank you for doing this!
> 
> On Sat, 30 Apr 2022 at 8:55 AM Juan Vuletich <JuanVuletich at zoho.com 
> <mailto:JuanVuletich at zoho.com>> wrote:
> 
>     __
>     Class StringUtf8 is a bytes object (like ByteArray). It implements
>     #byteSize, #byteAt:, #byteAt:put:. #at: is rather expensive. It
>     doesn't support #at:put:. It has several iteration messages in
>     CodePoints. Performance seems OK for reasonably small stuff.
> 
>     In any case, it is always possible to change the data structure, as
>     long as it is polymorphic.
> 
>     I haven't used it for Smalltalk source code yet, only for stand
>     alone editors. Parser would see instances of UnicodeCodePoint, maybe
>     mixed with Characters (for code points that fit in a Cuis Character).
> 
>     So far this is experimental, so we can adapt it while we learn the
>     details of what we need.
> 
> 
>     On 4/29/2022 6:24 PM, Luciano Notarfrancesco via Cuis-dev wrote:
>>     How do you represent strings? You’re avoiding random access like
>>     #at:? The parser can read them and see unicode characters instead
>>     of byte characters?
>>
>>     On Thu, 28 Apr 2022 at 1:35 AM Juan Vuletich via Cuis-dev
>>     <cuis-dev at lists.cuis.st <mailto:cuis-dev at lists.cuis.st>> wrote:
>>
>>         Hi Folks,
>>
>>         I've been working on making Cuis text editors work well with
>>         UTF-8
>>         Unicode contents. It is not ready, but you can see how it goes
>>         in the
>>         attach,
>>
>>         Cheers,
>>
>>         -- 
>>         Juan Vuletich
>>         www.cuis-smalltalk.org <http://www.cuis-smalltalk.org>
>>         https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev
>>         <https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev>
>>         https://github.com/jvuletich <https://github.com/jvuletich>
>>         https://www.linkedin.com/in/juan-vuletich-75611b3
>>         <https://www.linkedin.com/in/juan-vuletich-75611b3>
>>         https://independent.academia.edu/JuanVuletich
>>         <https://independent.academia.edu/JuanVuletich>
>>         https://www.researchgate.net/profile/Juan-Vuletich
>>         <https://www.researchgate.net/profile/Juan-Vuletich>
>>         https://patents.justia.com/inventor/juan-manuel-vuletich
>>         <https://patents.justia.com/inventor/juan-manuel-vuletich>
>>         https://twitter.com/JuanVuletich
>>         <https://twitter.com/JuanVuletich>
>>
>>         -- 
>>         Cuis-dev mailing list
>>         Cuis-dev at lists.cuis.st <mailto:Cuis-dev at lists.cuis.st>
>>         https://lists.cuis.st/mailman/listinfo/cuis-dev
>>         <https://lists.cuis.st/mailman/listinfo/cuis-dev>
>>
> 
> 
>     -- 
>     Juan Vuletich
>     www.cuis-smalltalk.org  <http://www.cuis-smalltalk.org>
>     https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev  <https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev>
>     https://github.com/jvuletich  <https://github.com/jvuletich>
>     https://www.linkedin.com/in/juan-vuletich-75611b3  <https://www.linkedin.com/in/juan-vuletich-75611b3>
>     https://independent.academia.edu/JuanVuletich  <https://independent.academia.edu/JuanVuletich>
>     https://www.researchgate.net/profile/Juan-Vuletich  <https://www.researchgate.net/profile/Juan-Vuletich>
>     https://patents.justia.com/inventor/juan-manuel-vuletich  <https://patents.justia.com/inventor/juan-manuel-vuletich>
>     https://twitter.com/JuanVuletich  <https://twitter.com/JuanVuletich>
> 
> 


More information about the Cuis-dev mailing list