Differences between revisions 3 and 4
Revision 3 as of 2006-12-31 21:01:15
Size: 2876
Editor: KaiJaeger
Comment:
Revision 4 as of 2007-02-27 08:20:35
Size: 3781
Editor: KaiJaeger
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
== 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.
== Looking at special characters in this wiki ==
This wiki is a Unicode wiki. This means that you will see APL characters as long as your browser uses a Unicode font. This wiki suggests to your browser to use the "APL385 Unicode" font, but even if this font is not available on your machine, you should see the APL characters: Arial and Times New Roman are containing all APL characters nowadays. All this is true on Windows systems, however; it might be different on a UNIX/LINUX box or a Macintosh.

== 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 these special 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 some.

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 appropriate technology used by no other browser. That is the reason why this wiki is not using the same technique.

== Check out ==
Line 22: Line 32:
== 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 are 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 - it works. With versions prior to 11 this will not work, sorry!
Line 26: Line 36:
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. 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, but any Unicode font will do.
Line 30: Line 40:
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): 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):
Line 45: Line 55:
== 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.
== Entering special 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 48: Line 58:
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.
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. Microsoft Word for example does not pass Ctrl keys, UltraEdit and most browser do.

SpecialCharacters

TableOfContents

Looking at special characters in this wiki

This wiki is a Unicode wiki. This means that you will see APL characters as long as your browser uses a Unicode font. This wiki suggests to your browser to use the "APL385 Unicode" font, but even if this font is not available on your machine, you should see the APL characters: Arial and Times New Roman are containing all APL characters nowadays. All this is true on Windows systems, however; it might be different on a UNIX/LINUX box or a Macintosh.

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 these special 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 some.

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 appropriate 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:

attachment: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 are 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 - it works. With versions prior to 11 this will not work, sorry!

Marking code as such

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, but any Unicode font will do.

If neither of them is installed on your computer, "Courier New" or "Courier" is used.

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 BRwhich leads to this output: BR 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:

{{{ BR anycode BR }}}

which leads to this output:

anycode

Entering special 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. Microsoft Word for example does not pass Ctrl keys, UltraEdit and most browser do.

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