Re: An APL Archive

phil chastney wrote:
Morten Kromberg wrote:

There ARE still a few glitches when viewing APL encoded as UNICODE in
some web browsers

Morten -- are those glitches down to the browsers, or simply
the result of HTML specifying fonts the user hasn't installed?

I have not yet had time to study the problems in detail, but have been
following experiments performed by other from a distance. "Full Unicode
Support" is a target for Dyalog Version 11.1, so we will be taking a
close look at these issues over the summer, and will be aiming to be
ready to make statements about the details of what we intend to do and
how we expect browsers and other components to deal with it, at our
User Conference in October.

make that "followed by two bytes for each Unicode character
in the Basic Multilingual Plane (BMP)"

Yes, that is more correct.


will you store your APL code using the ISO codepoints or near
equivalents from ASCII?

This is a tricky issue and I know that there are some cases which are
very hard to decide on, like | and the various quotes. Very roughly,
our goal will be to be as compatible as possible with what other APL
vendors have done or are planning to do. Note that for each unique
256-element []AV (or 512, if you are still runnning DEC APLSF :-), a
mapping needs to be defined to Unicode. There is not a single mapping
for any particular APL system, as a Czech Dyalog user is likely to be
using a different 256-element subset of Unicode from someone in the UK.
Making the process of migrating transparently from existing systems to
a system which supports Unicode is going to be an interesting
challenge.

(as an aside: among other things, Lee
Dickey and the other APL standards people persuaded Unicode to
include all the symbols used by past, present ->and proposed<-
APL systems)

I know, there are lots of interesting symbols to pick from once we get
there!

By the way, with respect to sharing binary data between systems, there
IS a standard for this, which is used by quite a few people - but
remains relatively unknown. It is possible that the functions are not
quite accessible enough in the systems which support it. There is
support for the SCAR (Self-Contained ARay) format in APL2, APL+Win and
Dyalog APL. This format was designed for Insight Systems more than 10
years ago, is based on Unicode translate tables, and is now in the
public domain. For more information, see
http://www.insight.dk/scardesign

It may be worth doing something to make SCAR functions more accessible
- the format is highly efficient - but my feeling is that we will get
better long term mileage out of adopting something more standard, and
using an XML array representation based on Unicode. This way, we can
share our arrays with non-APL systems as well.

Morten

.

Relevant Pages

  • Re: An APL Archive
    ... As far as the format of an archive is concerned, ... past and present APL systems, and allows us to put APL code into files ... Dyalog aims to support loading from and saving APL code in Unicode ...
    (comp.lang.apl)
  • Re: An APL Archive
    ... As far as the format of an archive is concerned, I think UNICODE has ... past and present APL systems, and allows us to put APL code into files ... Dyalog have an "Input Mode Editor" application, ...
    (comp.lang.apl)
  • Re: Thesaurus Problem
    ... files by using text editor tools, the files must be saved in Unicode format ... RelevantNoise.com - dedicated to mining blogs for business intelligence. ... be saved as a Unicode file. ... FROM FullDocuments ...
    (microsoft.public.sqlserver.fulltext)
  • Re: SBS 2003 Standard/Exchange Server issue
    ... To enforce Unicode mode in Outlook ... load the Outlook 2003 template. ... Double-click Exchange Unicode Mode - Ignore Archive Format. ... Double-click Exchange Unicode Mode - Ignore OST Format. ...
    (microsoft.public.windows.server.sbs)
  • Re: Thesaurus Problem
    ... files by using text editor tools, the files must be saved in Unicode format ... (ANSI, Unicode, Big Endian, and UTF-8). ... I then downloaded an XML editor and saved it from there. ...
    (microsoft.public.sqlserver.fulltext)