Differences between revisions 2 and 17 (spanning 15 versions)
Revision 2 as of 2006-12-31 20:59:29
Size: 2876
Editor: KaiJaeger
Comment:
Revision 17 as of 2009-05-06 09:31:06
Size: 4442
Editor: KaiJaeger
Comment: Revisited
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
<<TableOfContents>>
Line 3: Line 4:
[[TableOfContents]] == Looking at special characters in this wiki ==
This wiki is a Unicode wiki. This means that you should see APL characters as long as your browser uses a Unicode font. This wiki suggests to your browser to use one of these fonts:
Line 5: Line 7:
== Looking at special characters in this Wiki ==
This Wiki is a Unicode Wiki. This means that you will see the special characters used by Dyalog (for historical reasons also known as APL characters) as long as you use a Unicode font. If you tell your browser explicitly to use a particular non-Unicode font regardless what sites tell the browser to use, you won't see these special characters, of course.
 * APL385 Unicode
 * APLX Upright
 * Courier APL2 Unicode
 * SImPL
 * SiMPL medium
 * Courier
 * Courier New
 * monospace
Line 8: Line 16:
=== Is all okay for you? === The order defines the priority.

If one of these fonts is to be found on your machine, you will see APL characters. If not, well, you might see APL chars.

Problem is that almost no Unicode font implements '''all''' characters. Unfortunately, all fonts available on a Windows system do '''not''' come with APL chars. When Microsoft Office or Microsoft Punlisher is installed on such a system you might or might not have a version of the Ariabl font which comes with the APL symbols, but this font it not free.

== Problems ==
 1. If you have told your browser explicitly to use a particular non-Unicode font regardless what a site is suggesting to the browser, you won't see the APL characters, of course.
 1. In case you use an old browser, you might encounter a problem. Since this wiki addresses IT professionals your are supposed to use a modern browser.
 1. If you use any version of the Internet Explorer you might have a problem. The same version of IE might work well on one machine but not on another, and nobody can explain why. Even the latest version, IE7, which is the first one defaulting to Unicode, is not displaying UTF characters correctly in all cases - but in most.

You might find that you are using a version of IE which is displaying APL characters perfectly well on Dyalog's pages related to dynamic functions but not with this wiki. This is because IE is the only browser which is able to do a "dynamic font download". The Dyalog pages tell the IE that a particular font is needed. If this font is not available on that machine, it is downloaded and installed by IE. When the IE is closed, the font will disappear. This is an proprietory technology used by no other browser. That is the reason why this wiki is not using the same technique.

== Check out ==
'''Is all okay for you?'''
Line 14: Line 37:
Line 17: Line 39:
attachment:Code_Prim.jpg {{attachment:Code_Prim.jpg}}
Line 21: Line 43:
== Copying code between a Dyalog session and this Wiki and vice versa ==
It's all about Unicode: Since version 11 you can copy code from the Dyalog session and paste it into this Wiki and vice versa - it works. With versions prior to 11 this cannot work, sorry!
== Copying code between an APL session and this wiki and vice versa ==
It's all about Unicode: If your APL is able to handle Unicode, it will work perfectly well. Dyalog APL, for example, is able to deal with Unicode since version 11. You can copy code from the Dyalog session and paste it into this wiki and vice versa and it works. With versions prior to 11 this will not work, sorry!

With APLX Version 3 or later it will work as well, but you have to select the "Copy as Unicode" or "Paste from Unicode" menu commands, or to use the keyboard shortcuts associated to these commands.

APL2 was the very first APL offering this feature.
Line 25: Line 51:
Also any Unicode font will display the special characters properly that does not mean that they will look nice! Normally you want have a monospaced font. This Wiki try to use the "Apl385 Unicode" font by default. If this font is not installed on your local machine, the Wiki tries to use "Causeway" instead. Both fonts comes with a standard Dyalog version 11 installation on your machine. Although a Unicode font might display the APL characters properly that does not mean that they will look nice! Normally you want to have a monospaced font.
Line 27: Line 53:
If neither of them is installed on your computer, "Courier New" or "Courier" is used. If you want include code in a wiki page you have to tell the wiki explicitly to process that piece of text as code. For this, prefix ''and'' postfix the code with 3 "curlies" (curly brackets):
Line 29: Line 55:
However, you have to tell the Wiki explicitly to process a piece of text as code. For this, prefix ''and'' postfix the code with 3 "curlies" (curly brackets):

This is: `{{{anycode}}}` an inline example [[BR]]which leads to this output: [[BR]] This is: {{{anycode}}} an inline example
This is: `{{{anycode}}}` an inline example <<BR>>which leads to this output: <<BR>> This is: {{{anycode}}} an inline example
Line 35: Line 59:
`{{{` [[BR]] `anycode` [[BR]] `}}}` `{{{` <<BR>> `anycode` <<BR>> `}}}`
Line 42: Line 66:
== Entering APL characters directly into this wiki ==
If Microsofts Input Method Editor is installed on your machine you should be able to enter APL characters into the wiki directly.
Line 43: Line 69:
However, most keyboard layouts uses the Ctrl key to create some of the special characters. That might conflict with the application hosting the [[http://www.microsoft.com/globaldev/handson/user/IME_Paper.mspx|Input Method Editor]], typically a text editor or a browser.
Line 44: Line 71:
== Entering special characters directly into this Wiki ==
If Microsofts Input Editor is installed on your machine in theory you should be able to enter Dyalog's special characters into the Wiki directly.
== Recommended Font ==
The font "APL385 Unicode" from Adrian Smith is recommended.This font is able to display all APL characters used in any of the modern dialects.
Line 47: Line 74:
However, most keyboard layouts uses the Ctrl key to create some of the special characters. That works fine within a Dyalog session but conflicts with your browser which apparently uses a number of them as shortcuts. Typical candidates are Ctrl+C, Ctrl+V, Ctrl+X, Ctrl+A, Ctrl+P more. And because the browser takes them first and do not let them thru to the Input Editor, all characters accessible by those keys only cannot be entered into this Wiki directly, of course. The same is true for application like Word, who use even more keys as shortcuts.

There *are* applications available acting more intelligent. For example, UltraEdit passes those shortcuts thru to the Input editor first. Don't know how they do it but it works.
[[attachment:APL385_Unicode.zip]]

SpecialCharacters

Looking at special characters in this wiki

This wiki is a Unicode wiki. This means that you should see APL characters as long as your browser uses a Unicode font. This wiki suggests to your browser to use one of these fonts:

  • APL385 Unicode
  • APLX Upright
  • Courier APL2 Unicode
  • SImPL
  • SiMPL medium
  • Courier
  • Courier New
  • monospace

The order defines the priority.

If one of these fonts is to be found on your machine, you will see APL characters. If not, well, you might see APL chars.

Problem is that almost no Unicode font implements all characters. Unfortunately, all fonts available on a Windows system do not come with APL chars. When Microsoft Office or Microsoft Punlisher is installed on such a system you might or might not have a version of the Ariabl font which comes with the APL symbols, but this font it not free.

Problems

  1. If you have told your browser explicitly to use a particular non-Unicode font regardless what a site is suggesting to the browser, you won't see the APL characters, of course.
  2. In case you use an old browser, you might encounter a problem. Since this wiki addresses IT professionals your are supposed to use a modern browser.
  3. If you use any version of the Internet Explorer you might have a problem. The same version of IE might work well on one machine but not on another, and nobody can explain why. Even the latest version, IE7, which is the first one defaulting to Unicode, is not displaying UTF characters correctly in all cases - but in most.

You might find that you are using a version of IE which is displaying APL characters perfectly well on Dyalog's pages related to dynamic functions but not with this wiki. This is because IE is the only browser which is able to do a "dynamic font download". The Dyalog pages tell the IE that a particular font is needed. If this font is not available on that machine, it is downloaded and installed by IE. When the IE is closed, the font will disappear. This is an proprietory technology used by no other browser. That is the reason why this wiki is not using the same technique.

Check out

Is all okay for you?

If this code:

Prim←{all/⍨2=+⌿0=all∘.|all←⍳⍵}

displays the same code as this image:

Code_Prim.jpg

everything should be okay.

Copying code between an APL session and this wiki and vice versa

It's all about Unicode: If your APL is able to handle Unicode, it will work perfectly well. Dyalog APL, for example, is able to deal with Unicode since version 11. You can copy code from the Dyalog session and paste it into this wiki and vice versa and it works. With versions prior to 11 this will not work, sorry!

With APLX Version 3 or later it will work as well, but you have to select the "Copy as Unicode" or "Paste from Unicode" menu commands, or to use the keyboard shortcuts associated to these commands.

APL2 was the very first APL offering this feature.

Marking code as such

Although a Unicode font might display the APL characters properly that does not mean that they will look nice! Normally you want to have a monospaced font.

If you want include code in a wiki page you have to tell the wiki explicitly to process that piece of text as code. For this, prefix and postfix the code with 3 "curlies" (curly brackets):

This is: {{{anycode}}} an inline example
which leads to this output:
This is: anycode an inline example

Another example with the same piece of code but with newline characters between the curlies and the code iself:

{{{
anycode
}}}

which leads to this output:

anycode

Entering APL characters directly into this wiki

If Microsofts Input Method Editor is installed on your machine you should be able to enter APL characters into the wiki directly.

However, most keyboard layouts uses the Ctrl key to create some of the special characters. That might conflict with the application hosting the Input Method Editor, typically a text editor or a browser.

The font "APL385 Unicode" from Adrian Smith is recommended.This font is able to display all APL characters used in any of the modern dialects.

APL385_Unicode.zip

SpecialCharacters (last edited 2009-05-06 09:31:06 by KaiJaeger)