<div>Yes, I was planning to add commands like the \hat your tried. The problem I see is if some user uses a different input method, for example a keyboard configured in international English. In that case, Cuis with a\hat would generate two code points, while entering â with ctrl+shift+^ followed by a would generate a single code point (I guess). If we use ambiguous unicode like this for selectors sooner or later some user will encounter a MNU. One way to get rid of ambiguity is to make sure a\hat generates normalized unicode, but perhaps a better and more general solution is to make sure that symbols are normalized. Also I noticed some of the diacritical marks are rendered slightly misaligned, a bit too much to the right in some cases (depending on the modified character). For example x followed with u+0307 should show a dot on the top of x, aligned horizontally with the center of x, but it shows it a bit to the right.</div><div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 2 Dec 2022 at 01:14 Juan Vuletich <<a href="mailto:juan@cuis.st">juan@cuis.st</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Hi Luciano, On 12/1/2022 10:24 AM, Luciano Notarfrancesco via Cuis-dev wrote: > Here's an improvement of the commands to input untypeable characters. > > I simplified the method in SmalltalkEditor>>normalCharacter: and > changed the table of named characters in UnicodeCodePoint class from > an array to a dictionary. I added some missing characters, including > subscripts and superscripts for digits (for example type \^2 or \_2 > followed by space or any non-letter). Very nice. Thanks! Now at GitHub. > The list of commands is not complete yet, but it's easy to add more. > I'm trying to use the same names that are used in LaTeX. Leandro > Caniglia is doing the same in Bee Smalltalk and we plan to unify the > list of commands soon. Updating the list of commands only > requires changing the method > UnicodeCodePoint>>initializeNamedCharactersMap. > > It would be nice to support diacritical marks too, but I didn't > implement it yet because it's a bit more complicated and requires > dealing with normalization. Dealing with normalization is desirable, but not absolutely required IMO. Just tried adding , { {#hat. `UnicodeCodePoint codePoint: 16r0302`} } to your array, and typing `a\hat ` works as expected. > The methods for #arrowUp, #arrowDown, #arrowLeft and #arrowRight in > Character and UnicodeCodePoint seem unnecessary. I didn't remove them > just in case someone is using them, but probably we should remove them. > Yes. We can remove them. Same with #euro. Thanks, -- Juan Vuletich <a href="http://cuis.st" rel="noreferrer" target="_blank">cuis.st</a> <a href="http://github.com/jvuletich" rel="noreferrer" target="_blank">github.com/jvuletich</a> <a href="http://researchgate.net/profile/Juan-Vuletich" rel="noreferrer" target="_blank">researchgate.net/profile/Juan-Vuletich</a> <a href="http://independent.academia.edu/JuanVuletich" rel="noreferrer" target="_blank">independent.academia.edu/JuanVuletich</a> <a href="http://patents.justia.com/inventor/juan-manuel-vuletich" rel="noreferrer" target="_blank">patents.justia.com/inventor/juan-manuel-vuletich</a> <a href="http://linkedin.com/in/juan-vuletich-75611b3" rel="noreferrer" target="_blank">linkedin.com/in/juan-vuletich-75611b3</a> <a href="http://twitter.com/JuanVuletich" rel="noreferrer" target="_blank">twitter.com/JuanVuletich</a> </blockquote></div></div>