<div dir="auto">Hi Juan,</div><div dir="auto">I like the idea to make everything Unicode and get rid of old code!</div><div dir="auto"><br></div><div dir="auto">About removing support for $^ and $_ I’m not so sure… depends how we do it. The first question that comes to my mind is how are we going to input other arrows for assignment and for return. The LaTeX commands like \oplus are very convenient for my math stuff, but seem too much typing for something that we can do with one keystroke (two keys actually with SHIFT). Also, I see that removing support for assignment with $_ has the benefit of making available that character for something else, but removing support for $^ doesn’t seem to bring any benefits (since we can already use it as binary selector).</div><div dir="auto"><br></div><div dir="auto">Probably you gave more thought to this, and I’d like to know. In the meantime I throw this idea: get rid of $_, in the actual source and changes files use ‘:=‘ and $^, and make the syntax highlighter show assignment and return as any Unicode that the user chooses (with some arrows as default). Does this make sense? I’m not sure how this would work when you save a method that was syntax highlighter, do we need to convert back the Unicode arrows to ‘:=‘ and $^ ? It we never insert real Unicode arrows in the text and just display them with the arrow glyphs, like we do with useST80Glyphs?</div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 19 Oct 2022 at 02:02 Juan Vuletich via Cuis-dev <<a href="mailto:cuis-dev@lists.cuis.st">cuis-dev@lists.cuis.st</a>> wrote:<br></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)"><u></u>
<div bgcolor="#ffffff" text="#000000">
Hi Luciano,<br>
<br>
I also think it would be good to make this configurable. It is also
bad that I hardcoded this in the plugin, making it harder to change.<br>
<br>
Still, this opens a different discussion. Something I have been
thinking about, but hadn't talked about in the list.<br>
<br>
Now that the VectorEnginePlugin is in the official VMs, it means we
can count on it. So, what I want to do is to make the "Use Unicode"
preference the default and only behavior, and actually remove
support for ISO 8859 files (and StrikeFonts, and a lot of the older
stuff). And if everything is Unicode, then there's no need to have
these special glyphs for $_ and $^. We could use instead a real
Unicode left arrow for assignment, and just remove support for $_
for assignment. (Using := would still be possible). All this
"Smalltalk-80 glyphs" kludge would go away.<br>
<br>
What do you think?<br>
<br>
If we decide to go in this direction, it may make sense to
temporarily disable the "Smalltalk-80 glyphs", at least if you want
to use the Unicode arrows for something else.<br>
<br>
Opinions?<br>
<br>
On 10/17/2022 6:20 AM, Luciano Notarfrancesco via Cuis-dev wrote:
<blockquote type="cite">
<div dir="auto">Perhaps instead of the useST80Glyphs boolean in
Tahoe displayUtf32: method we could pass a translation table, a
WordArray with pairs of code points to replace when displaying.
Juan, what do you think?</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, 17 Oct 2022 at 13:06
Luciano Notarfrancesco <<a href="mailto:luchiano@gmail.com" target="_blank">luchiano@gmail.com</a>>
wrote:<br>
</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)">
<div dir="auto">I changed those methods but still couldn’t
get it to work. Now I see this is hardcoded in the
VectorEngine plugin. Juan, could we make this
configurable?</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, 17 Oct 2022 at
04:23 Gerald Klix <<a href="mailto:cuis.01@klix.ch" target="_blank">cuis.01@klix.ch</a>>
wrote:<br>
</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)">On 16.10.22 22:54, Luciano
Notarfrancesco wrote:<br>
> I don’t mean to change the current behavior. I
just would like that the<br>
> user could easily choose the code points of the
glyphs to be used for those<br>
> characters. Right now they are hardcoded in
TTFFontReader and VectorEngine.<br>
> As a preference they would be more flexible, but
I can just change those<br>
> methods in my image for now. I’m using all DejaVu
Sans and the thick arrows<br>
> look nice.<br>
Yes, that was my initial impression; I even started<br>
to write an encouraging E-mail.<br>
Then I tried some other fonts and discovered that the
fonts<br>
mentioned below do not have the necessary glyphs.<br>
<br>
Perhaps a dictionary that maps the font-name to
code-point<br>
substitution mapping, would be a general solution.<br>
Actually we also have to look at the syntactic context
...<br>
<br>
Anyway, I like the thicker arrows that DejaVu provides<br>
and I am willing to help to find a solution.<br>
> <br>
> On Mon, 17 Oct 2022 at 03:38 Gerald Klix <<a href="mailto:cuis.01@klix.ch" target="_blank">cuis.01@klix.ch</a>> wrote:<br>
> <br>
>> Luciano,<br>
>><br>
>> I see your problem,<br>
>> but these Characters only have glyphs in the<br>
>> DejaVu, JetBrainsMono, KiwiMaru and
KurintoSans fonts.<br>
>><br>
>> To make this work properly, we need some
means<br>
>> to discover the aforementioned situation<br>
>> and switch back to the current behavior.<br>
>><br>
>><br>
>> Sorry and HTH,<br>
>><br>
>> Gerald<br>
>><br>
>><br>
>> On 06.10.22 12:55, Luciano Notarfrancesco via
Cuis-dev wrote:<br>
>>> What do you think about adding two
preferences to set the unicode<br>
>>> characters to be used for displaying ^
and _? The problem I’m having is<br>
>>> that the arrows that we currently use are
the same that are commonly used<br>
>>> in mathematics for morphisms, and the
code gets a bit confusing in my<br>
>>> system, so I’d like to use the thick
arrow 16r2B05 for _ and 16r2B06 for<br>
>> ^,<br>
>>> and to avoid annoying people who like the
current arrows I think we could<br>
>>> make this a preference. Is this
reasonable?<br>
>>><br>
>>><br>
>><br>
> <br>
<br>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
<br>
<pre cols="72" style="font-family:monospace">--
Juan Vuletich
<a href="http://cuis.st" target="_blank" style="font-family:monospace">cuis.st</a>
<a href="http://github.com/jvuletich" target="_blank" style="font-family:monospace">github.com/jvuletich</a>
<a href="http://researchgate.net/profile/Juan-Vuletich" target="_blank" style="font-family:monospace">researchgate.net/profile/Juan-Vuletich</a>
<a href="http://independent.academia.edu/JuanVuletich" target="_blank" style="font-family:monospace">independent.academia.edu/JuanVuletich</a>
<a href="http://patents.justia.com/inventor/juan-manuel-vuletich" target="_blank" style="font-family:monospace">patents.justia.com/inventor/juan-manuel-vuletich</a>
<a href="http://linkedin.com/in/juan-vuletich-75611b3" target="_blank" style="font-family:monospace">linkedin.com/in/juan-vuletich-75611b3</a>
<a href="http://twitter.com/JuanVuletich" target="_blank" style="font-family:monospace">twitter.com/JuanVuletich</a></pre></div><div bgcolor="#ffffff" text="#000000">
</div>
-- <br>
Cuis-dev mailing list<br>
<a href="mailto:Cuis-dev@lists.cuis.st" target="_blank">Cuis-dev@lists.cuis.st</a><br>
<a href="https://lists.cuis.st/mailman/listinfo/cuis-dev" rel="noreferrer" target="_blank">https://lists.cuis.st/mailman/listinfo/cuis-dev</a><br>
</blockquote></div></div>