VisualAPL for Visual Studio 2008: Font

General discussions related to APLNext's VisualAPL.

Moderators: Tech Support, phpbb_admin

VisualAPL for Visual Studio 2008: Font

Postby joe_blaze » March 20th, 2009, 5:03 pm

The attached "" file contains the "APLNext.ttf" Unicode font which has the APL glyphs implemented.

The attached "VisualAPL for Visual Studio 2008 Font.pdf" document illustrates how to customize your copy of Visual Studio 2008 to use the "APLNext.ttf" Unicode font.

An alternative font which is installed with recent versions of Microsoft Office products and supports most Unicode glyphs, including all the APL ones, is "Arial Unicode MS", which is described at: ... ?FMID=1081

The attached "" file contains a version of the "APLNext.ttf" Unicode font which eliminates the obsolete Macromedia Font Foundry restriction which prevented the previous version of the APLNext.ttf font from being embedded in an Adobe .pdf-format document.
(42.01 KiB) Downloaded 225 times
(43.24 KiB) Downloaded 199 times
VisualAPL for Visual Studio 2008 Font.pdf
(105.21 KiB) Downloaded 202 times
Last edited by joe_blaze on April 22nd, 2009, 11:41 pm, edited 1 time in total.
Posts: 383
Joined: February 11th, 2007, 3:09 am
Location: Box 361 Brielle, NJ 08730-0361

"Font is corrupted"?

Postby joe_blaze » April 22nd, 2009, 7:24 pm

Sometimes VisualAPL programmers report that the "font is corrupted" when displaying APL characters.

VisualAPL, just like any other .Net language, is entirely Unicode-based. The positions of the "APL" glyphs in a Unicode font used by VisualAPL are those which were established by internation standards prepared many years ago.

When APL characters appear to be "corrupted" it generally means that the rendering mechanism, e.g. text editor, printer, forum software, Windows configuration, Visual Studio configuration. etc. has been set by the user, or by default, to a font which does not have the APL glyphs implemented. This occurs even with fonts described as "Unicode fonts", because often a font is designed to support a limited number of the many glyphs defined in the international Unicode standards.

This is one of the reasons that VisualAPL provides the APLNext.ttf font to be sure that the VisualAPL programmer has available typography which implements the APL glyphs in the positions of the font defined by internation Unicode standards.

Legacy APL implementations generally did not have a Unicode basis. Instead they developed a proprietary font which usurped other glyphs in pre-existing, general-use fonts and replaced those glyphs with APL glyphs.

With a Unicode-based implementation, this usurpation is not necessary because internation Unicode standards have reserved a section of the Unicode code numbers and associated font positions for the complete set of APL glyphs.

Recently other Unicode fonts purporting to support APL glyphs have circulated on the Internet which do not follow the internation Unicode standards. These fonts are thus proprietary to a specific APL implementation.
Posts: 383
Joined: February 11th, 2007, 3:09 am
Location: Box 361 Brielle, NJ 08730-0361

Return to VisualAPL

Who is online

Users browsing this forum: Google [Bot] and 1 guest