[Cuis-dev] [Ann] Unicode Text Editors

Luciano Notarfrancesco luchiano at gmail.com
Wed May 11 11:41:51 PDT 2022


On Wed, 11 May 2022 at 8:55 PM Juan Vuletich <JuanVuletich at zoho.com> wrote:

>
> Just pushed updates. now:
> (Utf8String fromUtf32: (16r1D538 to: 16r1D56B)) edit.
> works as expected.
>
> Due to ninecities of Unicode design, what you actually want is:
> (Utf8String fromUtf32: #(16r1D538 16r1D539 16r2102 16r1D53B 16r1D53C
> 16r1D53D 16r1D53E 16r210D 16r1D540 16r1D541 16r1D542 16r1D543 16r1D544
> 16r2115 16r1D546 16r2119 16r211A 16r211D 16r1D54A 16r1D54B 16r1D54C
> 16r1D54D 16r1D54E 16r1D54F 16r1D550 16r2124 16r1D552 16r1D553 16r1D554
> 16r1D555 16r1D556 16r1D557 16r1D558 16r1D559 16r1D55A 16r1D55B 16r1D55C
> 16r1D55D 16r1D55E 16r1D55F 16r1D560 16r1D561 16r1D562 16r1D563 16r1D564
> 16r1D565 16r1D566 16r1D567 16r1D568 16r1D569 16r1D56A 16r1D56B)) edit.
> Just had to check why the most important ones were missing!
>

Yeah, I was using those already because they are in plane 0 and were
already accessible in Cuis. I wonder if there is some sort of standard
table for these mappings and if all TTF fonts do the same.


> Btw, sorry to be obsessive about names again, but wouldn’t UTF8String and
>
> UTF32String be better names than StringUtf8 and StringUtf32?
>
> I struggled a bit trying to decide between those. I liked the fact that
> having prefix String means those classes may be listed together. But I
> agree with you. Just changed them. Still, I used 'Utf' prefix and not
> 'UTF'. I tend not to capitalize acronyms, and use caps only for camelCase.
> Names matter!
>

Cool, thanks!!

If you mean “together” in the Browser, maybe we can move Utf8String,
Utf32String and UnicodeCodePoint to the category ‘Kernel-Text’ together
with String and Character.

I noticed the image grew about 100MB after loading DejaVu Sans. Now we’re
loading all glyphs. But I don’t think this is going to be a problem for me
because I can easily remove all the glyphs I don’t use in my image (the
vast majority of them). We are not storing redundant contour data for all
the code points that don’t have a glyph like 16r1D53A, right? I took a
quick look at the instance of TTFontDescription and there seems to be data
for this code point, but probably I made a mistake because I’m not familiar
with this…

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20220512/89614c2c/attachment-0001.htm>


More information about the Cuis-dev mailing list