APL Under-bar Characters
prosfilaes at gmail.com
Sun Aug 16 19:59:28 CDT 2015
The standard is set here. The Unicode Consortium has declared that it won't
encode precomposed characters that can be created from characters in the
standard, because that would be destabilizing and potentially introduce
security holes in programs depending on Unicode. If you want, we can have a
vote on whether or not APL should use characters with underlines, since I
was unfairly locked out of that vote by not being born yet.
On Sun, Aug 16, 2015 at 5:52 PM <alexweiner at alexweiner.com> wrote:
> You pose a very strong, and well worded response. The historical element
> really helps to illuminate what I thought was lost knowledge: "Why are
> there no under-bars". To this I can only ask one thing:
> Can we put this to a vote again? To put things in perspective, I was thee
> years old at the time of the ballot in 1993 and had much larger issues to
> deal with (comprehending speech, learning to walk, etc.), and was unable to
> participate in this internationally binding vote.
> Perhaps feelings about the under-bar characters have changed since then. I
> know that the APL landscape is *very* different than it was in 1993.
> I have a copy of one of those IBM books that has the italicized upper-case
> under-bars. If my proposal for a new vote is well received, maybe we should
> include those as well, for completeness sake.
> -------- Original Message --------
> Subject: Re: APL Under-bar Characters
> From: Ken Whistler <kenwhistler at att.net>
> Date: Sun, August 16, 2015 5:15 pm
> To: alexweiner at alexweiner.com
> Cc: unicode at unicode.org
> On 8/16/2015 12:41 PM, alexweiner at alexweiner.com wrote:
> As far as I know, APL definitely predates the Unicode consortium. Do you
> think that The Consortium possibly overlooked the pre-existing under-bar
> character set?
> The answer to that is no.
> Initially, Unicode 1.0 attempted to punt the entire APL complex functional
> problem by encoding U+2300 APL COMPOSE OPERATOR.
> The concept was essentially that any of the combined symbols -- the old
> rack of stuff that people complained about entering with
> keying, could simply be represented as sequences of existing symbols.
> Think of 2300 as an early attempt to introduce an APL "script"-specific
> conjunct-forming virama, a la much-later artificially introduced
> joiners. Cf. U+2D7F TIFINAGH CONSONANT JOINER.
> But U+2300 APL COMPOSE OPERATOR was an innovation that failed.
> It was fiercely opposed *by the APL community*, who wanted it
> out of 10646 and replaced with a explicit list of pre-formed complex
> functional symbols. Presumably for the same reason we are talking
> about here now: essentially that each symbol had to work as a "character",
> and in an APL context that meant fixed width and the same data size as
> all the other characters.
> The removal of Unicode 1.0 U+2300 APL COMPOSE OPERATOR is documented
> in Unicode 1.1 as of 1993:
> (see page 3)
> The addition of APL functional symbols is documented in Section 5.4.8, pp.
> The exact repertoire that ended up encoded in the standard was the result
> of meetings
> between some Unicode representatives and some folks from the APL
> community. The names
> escape me at the moment, although it might be possible to recover some
> information eventually. (Documentation regarding Unicode events in late
> 1991 is
> sparse these days.) At any rate the agreed upon additional repertoire is
> that included in:
> X3L2/92-035, Unicode Request for Additional Characters in ISO/IEC
> And the rest of the consequences and processing can be dug out of the
> ballot history record
> for the voting on 10646 in 1992.
> At any rate, a propos *this* discussion, we agreed that the repertoire
> would cover
> all the complex functional symbols, but *not* the letters
> with underscores. And it is not that they were simply overlooked.
> How do I know? Well, first, there were APL specialists involved in coming
> (and promoting) the repertoire that was carried into the 10646 balloting at
> the time. It isn't as if a bunch of ignorant Unicoders just grabbed one APL
> book off the shelf and coded up the table, not noticing that some stuff was
> Second, the text that is currently in the core specification about this
> to wit:
> " ... All other APL extensions can e encoded by composition of other
> Unicode characters. For example, the APL symbol a underbar can be
> represented by U+0061 LATIN SMALL LETTER A + U+0332 COMBINING LOW LINE."
> (Unicode 7.0, Section 22.7, p. 772)
> is *ancient* text. It was first printed on p. 6-83 of Unicode 2.0 in 1996,
> with exactly the same wording. And the only reason it took until 1996 to
> instead of 1993, was that the editing of Unicode 2.0 and its code charts
> was such a massive task at the time.
> So the clear intent in *1993* was to represent any APL letter with underbar
> as a combining character sequence -- as noted. The only problem I see there
> is that the text in the core spec mistakenly used U+0061 (the lowercase
> instead of U+0041 (the uppercase "A") for the exemplification.
> Third, I can attest that at least some of us at the time -- as early as
> 1989, had
> printed copies of IBM EBCDIC code page 293 for APL, which had
> the EBCDIC uppercase Latin letters with underscores (italicized, by the
> together with the regular EBCDIC upper and lowercase letters. [Dates from
> *And* IBM EBCDIC code page 310 for APL, which dropped all the
> regular upper- and lowercase letters but added more symbols.
> *And* IBM PC code page 907 (with the underscored uppercase Latin
> letters) and PC code page 909 (CP437 hacked up for APL, without the
> underscored uppercase Latin letters), which was quickly superseded by
> PC code page 910, which also did not use the uppercase Latin letters
> with underscores.
> So yeah, we knew about these. Encoding them as combining character
> sequences instead of as atomic characters was a deliberate decision
> taken in 1992. And that decision made it through both UTC and
> international balloting for publication in 1993.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Unicode