ACM Home Page
Please provide us with feedback. Feedback
Extending the APL character set
Full text PdfPdf (504 KB)
Source International Conference on APL archive
Proceedings of the international conference on APL table of contents
Toronto, Ontario, Canada
Pages: 41 - 46  
Year of Publication: 1993
ISBN:0-89791-612-3
Also published in ...
Authors
Sponsor
SIGAPL: ACM Special Interest Group on APL Programming Language
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 1,   Downloads (12 Months): 7,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/166197.166203
What is a DOI?

ABSTRACT

APL is often presented as a notation that is independent of national language because of its symbolic nature. Paradoxically its unique character set has led to APL being treated as if it were itself a national language. This has meant, in many practical situations, that the APL character set is incompatible with national language character sets.IBM's APL2 attempted to avoid these problems by defining a set of extended (31 bit) characters, and this has indeed been helpful in handling Asian languages such as Kanji. But the character mappings adopted have not been adequate to support all European and Middle Eastern language characters, nor have they been consistent across platforms.With the advent of international standards for character assignment, there is an opportunity to create APL systems that handle the character sets of the world in an efficient and elegant manner. While at first the solution appears to require only a recitation of code point assignments, an analysis of the problem leads to interesting and disturbing questions about a number of APL system functions, system variables, commands, and file facilities. This paper explores problems with internal conversions, external representations, migration, compatibility, and interplatform portability.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
IBM Corporation. ,,t PL Pr(~gramming Language C-I{ 3-9()45-1)()1 (1)ecembcr 1977)


Collaborative Colleagues:
James A. Brown: colleagues
Brent Hawks: colleagues
Ray Trimble: colleagues

Peer to Peer - Readers of this Article have also read: