[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-apl] Incorrect encoding in ATF files.

From: Kacper Gutowski
Subject: Re: [Bug-apl] Incorrect encoding in ATF files.
Date: Sat, 18 Jan 2014 05:42:24 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

>       ⎕FX 'test' '⋄'
I just realized that I entered ⋄ U+22C4 while GNU APL defaults
to ◊ U+25CA and the later is correctly encoded as d8 in ATF.
Looks like ∊/∈ also suffers the same problem while writing to ATF file.

So I must ask this (loosely related) question now.
Is there any specific reason why characters different than usual
were chosen as default? Or is just my notion of what's usual flawed?

For example both NARS2000 and Dyalog's APL/W (as I played only with
those two before) use U+22C4 for diamond; APL/W doesn't even accept
U+25CA as a valid token.  Likewise they both use ∊ U+220A and don't
accept U+2208.  The later character ∈ is also missing from popular
APL385 Unicode font.

Well, on the other hand I like that GNU APL uses ∼ and ⋆ rather than
plain ~ and * as this seems ‘more correct’ and in some fonts looks
better; even if it's less compatible.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]