[Maxima] bug report, or am I doing something wrong?

[Stavros Macrakis]

------=_Part_10055_30516952.1139596367212
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

>
> Her paper uses \uparrow and
> \downarrow, but this can be translated into CAS syntax as follows.
>
> a^b as ususal.
>
> a_b will be log_a(b).
>

So... is anyone actually using this convention?  I haven't seen it.

But it brings up another issue, which is that Unicode has a very rich
collection of operator symbols which it would be nice to be able to use.  I
don't know what the current situation is on Unicode support in our Lisps.
Actually, the Unicode support doesn't even need to be very "deep", just
something done in the front ends. After all, UTF-8 looks just like any othe=
r
sequence of 8-bit codes, and only i/O and string operations care.  I would
be happy even if string operations were ignorant of Unicode.

Any news on that front?  (Of course, there is then the problem of input
methods, and teaching Displa about these characters...)

            -s

------=_Part_10055_30516952.1139596367212
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(=
204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Her paper us=
es \uparrow and<br>\downarrow, but this can be translated into CAS syntax a=
s follows.
<br><br>a^b as ususal.<br><br>a_b will be log_a(b).<br></blockquote></div><=
br>So... is anyone actually <span style=3D"font-style: italic;">using</span=
> this convention?&nbsp; I haven't seen it.<br><br>But it brings up another=
 issue, which is that Unicode has a very rich collection of operator symbol=
s which it would be nice to be able to use.&nbsp; I don't know what the cur=
rent situation is on Unicode support in our Lisps.&nbsp; Actually, the Unic=
ode support doesn't even need to be very &quot;deep&quot;, just something d=
one in the front ends. After all, UTF-8 looks just like any other sequence =
of 8-bit codes, and only i/O and string operations care.&nbsp; I would be h=
appy even if string operations were ignorant of Unicode.
<br><br>Any news on that front?&nbsp; (Of course, there is then the problem=
 of input methods, and teaching Displa about these characters...)<br><br>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -s<br>

------=_Part_10055_30516952.1139596367212--