APL Wiki:Formatting

APL Wiki is a standard MediaWiki, so the MediaWiki documentation for applies. In particular, the following are useful:


 * Links
 * Formatting

However, please familiarise yourself with the below APL Wiki-specific guidelines before making any major edits.

Mentioning subjects that have their own page
It is fine for a page to have a section about a subject that also has its own page. When that happens, begin the section with  where   is the target page title. Don't include double brackets (as a page link) — it is done for you.

Yes/No tables
For tables comparison tables, use the,  , and   templates, e.g.: gives:

Custom options
You can customise the text by supplying an argument: gives:

Mathematical notation
MathJax is enabled, so you can insert mathematical notation (for example for Iverson notation) inline using included the expression $$⊥p_{32,33}:+/\alpha^2/I^0$$ in its description which results in: included the expression $$⊥p_{32,33}:+/\alpha^2/I^0$$ in its description For multiple and larger mathematical expressions, use included the expression
 * $$i←O^{⊥I^0_{0,1,2,3}}_{⊥I^0_{4,5,6,7}}$$

in its description which results in: included the expression
 * $$i←O^{⊥I^0_{0,1,2,3}}_{⊥I^0_{4,5,6,7}}$$

in its description

Equivalence
It is quite common to state equivalences. Please use a proper equivalence arrow, which is easy to insert with the template: "this that" which results in: "this that"

Inline code
Inline code is used for single primitives and short expressions and uses the format

"" which results in ""

Code blocks
For session transcripts, function definitions and longer expressions, use code blocks like

""

which results in:

""

Optionally, you can indicate one or more APL dialects which are able to run the code by using a special template immediately after the source tag, like

which results in:

You can also include a permalink to TryAPL, Try It Online, repl.it, or n9n.gitlab.io right before the source tag, for example

Try it now!

which results in:

Try it now!

Very long code blocks
Use }

which results in:

Primitives and other built-ins
When creating a page for a primitive function, operator, or quad name, begin the page with the following template:

""

This inserts the text

""

and also inserts a nice big illustration of the glyph on the page:

At the bottom such pages, include  and [ edit that template's content] if the page you're creating isn't already listed there.

Dialects
Begin your page about an APL dialect with the Infobox array language info box. These are all the optional parameters it supports:

Have a look at the existing dialect pages, e.g. Dyalog APL, to see how these values are used, Try to fill in as many as you can (but use only one of each singular/plural pair). You only need to use  if the language title differs from the page title (e.g. for technical reason like the inability to create a page that begins with a lowercase letter). In that case, you may also want to begin the page with  where   should be the proper name of the dialect.

At the bottom of the page, include  and [ edit that template's content] if the dialect you're creating a page about isn't already listed there.

People, organisations, and what they do
Insert   at the very bottom of the page, and [ edit that template's content] if the page you're creating isn't already listed there.