One persistent issue with this stems from a chicken-and-egg problem. The last layer in the presentation of APL characters is the font. Everything below that, from the application to the transport to the character encoding (& the reverse) could fully & robustly support APL, but if the font doesn't support it, then all's for naught.
The chicken-and-egg problem is that common fonts are only going to support APL characters if those characters are commonly used; otherwise they won't. But APL characters won't be commonly used until we can rely on them being transmitted faithfully, which can't happen until common fonts support them... Unless rendering engines can "fall back" on universal (-ish) fonts for glyphs not in the desired font? That might explain Joey's "ransom note" experience. If that's the case, then we just have to identify the fall-back universal fonts, and convince their maintainers to support APL characters. -Dan ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
