Markup spec/BNF/Inline text

"Inline text" is the guts of Wikitext formatting. It covers every situation where "normal" text is allowed, such as image captions, table data, and to an extent (yet to work out how to enforce this restriction...), headings and link text.

Code
Detail:
 * noparse-block: ../Noparse-block
 * link: ../Links/
 * magic-link: ../Magic links/

The parser should try the options in order, with  matching if all else fails. In particular, &lt;category-link> should be matched before &lt;link> because a category is a special type of link, and we don't want the normal parsing to occur.

HTML entity
The parser recognises validly constructed HTML entities and leaves them alone.

Rendering

 * The whole sequence is output literally.
 * The current parser does very complicated things with escaping and de-escaping. So maybe there are places where something more complicated needs to happen.

HTML unsafe symbol
These "unsafe" symbols are turned into HTML entities if they haven't matched part of a valid HTML entity above. It's probably not too efficient having single-character level matching rules...perhaps should be combined with "text".

Rendering

 * &lt;unescaped-ampersand> →
 * &lt;unescaped-less-than> →
 * &lt;unescaped-greater-than> →

Text
Harmless-characters mean characters that couldn't be anything else. I'm not sure how useful this is as a distinction, but perhaps it will help speed things up?

A "random character" is any character which hasn't matched anything else.

Rendering
Both types are written literally.

This section from the "fundamental elements" section...time to mangle!

Formatting
Bold/italics is the biggest problem with switching to a consume-parse-render parser. It will not be possible to describe the current, extremely esoteric rules in simple (E)BNF. The best we can hope for is to store tokens representing the apostrophe clumps and do a second pass to make more sense of them. It would be very useful to define a second, unambiguous set of formatting syntax (most likely // and **), and encourage people to use those wherever apostrophes and bold/italics meet.

Some rules for parsing bold/italics as recognised by the current parser. These must be implemented (Brion said so). In increasing order of complexity:
 * 1) italics, bold, bold-italics
 * italics, bold, bold-italics
 * 1) bold-italics just italics normal
 * bold-italics just italics normal
 * 1) Some text about l'Arc de triomphe.
 * Some text about l'Arc de triomphe.
 * 1) However: bold is l'Arc de triomphe'''.
 * However: bold is l'Arc de triomphe'''.

Optimistic view:

Reality:

Rendering

 * Once the parser has decided which way the toggles go:
 * bold-toggle-on -> &lt;b>
 * bold-toggle-off -> &lt;/b>
 * italic-toggle-on -> &lt;i>
 * italic-toggle-off -> &lt;/i>
 * bold-italic-toggle-on -> &lt;b> &lt;i>
 * bold-italic-toggle-off-> &lt;/i> &lt;/b>

Determining the behaviour of apostrophes
The following describes the behaviour of repeated apostrophes. "Bold" means "toggle bold", rather than "turn bold on". "Bold, italics" means "Toggle bold and italics independently", rather than "turn bold and italics on" or "toggle bold and italics the same way".


 * One : Always a single apostrophe.
 * e.g.  → hello ' blah
 * Two : Always italics on or off
 * e.g.  → hello '' blah
 * Three :
 * Bold (default)
 * e.g.  → hello ''' blah
 * Apostrophe, italics
 * If there is otherwise an odd number of both bold and italics
 * If the preceding characters are  (and there are no earlier such sequences)
 * e.g.  → hello lamour louest' blah
 * Else if the preceding characters are  (and there are no earlier such sequences)
 * e.g.  → hello mon'amour blah
 * Else (the preceding character is ) (and there are no earlier such sequences)
 * e.g.  → hello amour blah 'blah
 * Italics, apostrophe (never)
 * Four :
 * Bold, apostrophe (never)
 * Apostrophe, bold (default, if either bold or italics ends up balanced)
 * e.g.  → hello 'amour now ''italics unbalanced, but that's ok
 * e.g.  → hello 'amour now, '''bold unbalanced, but that's ok
 * Apostrophe, apostrophe, italics
 * If the default treatment leads to an odd number of bold and italics then this can meet condition 1 under the second case of three italics, above.
 * e.g.  → hello 'amour' now bold and italics unbalanced, so invoke this special case
 * Five :
 * Bold, italics; or italics, bold (default, the two cases are equivalent)
 * e.g.  → hello ' blah
 * Italics, apostrophe, italics (never)
 * More than five:
 * Apostrophes, bold+italics (default)
 * e.g.  → hello  blah
 * e.g.  → hello '''bold  blah
 * Bold+italics, apostrophes (never)

Inline HTML
The parser recognises and cleans a large number of HTML tags, as defined in Sanitizer.php.

A decision has to be made here on whether to attempt to parse these things as a matched set, or whether to leave that to a later pass.

A loose definition assuming they are treated individually:

Remarks

 * The range of "word-boundary-char" seems to be an artefact of the regular expression:
 * The range of "word-boundary-char" seems to be an artefact of the regular expression:

The list of "tags that must be closed" :

 * block elements
 * p, span, table, div,


 * lists
 * ol, ul, dl,


 * paragraph formatting
 * h1, h2, h3, h4, h5, h6, cite, center, blockquote, caption, pre,


 * character formatting
 * b, del, i, ins, u, font, big, small, sub, sup, code, em, s,
 * strike, strong, tt, var, u


 * Ruby
 * rt, rb, rp, ruby,

Tags that can appear singly, and possibly paired

 * br, hr, li, dt, dd

Tags that must not be paired

 * br, hr

Tags that can be nested (source code is dubious on this)

 * table, tr, td, th, div, blockquote, ol, ul, dl, font, big, small, sub, sup, span

Tags that can only appear inside a table

 * td, th, tr,

Tags that make lists

 * ul,ol,

And tags that can appear inside lists

 * li

The significance of these groupings is shown as follows: A "B C" D E Here, blockquote and span are both "nesting" tags. When the close-blockquote tag is found inside the span block, it is escaped.

This doesn't work: Some text But this does: '''Some text

Rendering

 * Tags that have to be paired are forced closed according to some sort of logic.
 * &lt;extra-characters> are "sanitized", strip all but pre-approved attributes and styles on a whitelist.
 * Tags are then written out literally:  etc.
 * HTML comments are completely discarded, with some whitespace massaging: (sanitizer.php)
 * To avoid leaving blank lines, when a comment is both preceded and followed by a newline (ignoring spaces), trim leading and trailing spaces and one of the newlines.

Non-breaking spaces
This is pretty trivial and used basically to improve the appearance of punctuation in French, which always places a space before certain punctuation, and places spaces inside guillemets. Other languages use these characters, but without the spaces. Currently performed directly in the parse method.

Rendering

 * In both cases, the space is converted to a  string.

Behaviour switches
Not to be confused with magic links. These seem to be able to be used virtually anywhere: a table of contents in an image caption even works. See Help:Magic words.

Notes:
 * These are the "default" strings to be matched. They can be modified in  where Xx is the language.
 * Each magicword can have more than one string associated with it.
 * The magic words are by default case insensitive but this can be changed in the file.
 * Plenty of other "magic words" exist, including "magic variables" (eg August ) which will be handled by the preprocessor. However it looks like all sorts of other "magic words" exist and are processed in different places.

Semantics

 * behaviourswitch-toc: a miniature contents page will be rendered and inserted at the first instance of this token.
 * behaviourswitch-forcetoc: a contents box will be rendered even if the normal criteria (typically, 4 sections) have not been met. Irrelevant if magicword-toc is present.
 * behaviourswitch-notoc: no miniature contents pages will be rendered. Only takes effect if neither magicword-toc nor magicword-forcetoc are present.
 * behaviourswitch-noeditsection: no edit links are to be displayed for any sections.
 * behaviourswitch-nogallery: unclear. According to the code (parser::stripNoGallery): if the string __NOGALLERY__ (not case-sensitive) occurs in the HTML, do not add TOC. Perhaps it only has an effect in certain namespaces.

Images, media, gallery
Links to images and media should be handled as normal links. It's inline images and media that are being dealt with here.

Originally from MetaWiki.

Semantics

 * Renders an image inline using the  tag.
 * It is not an error to specify multiple alignment parameters; the first specified is the one used.
 * It is not an error to specify multiple captions; the last specified is the one used.
 * The caption has no effect if ThumbImageParameter is not given.

Gallery
Remarks:
 * The gallery block can technically be used in the middle of a sentence so is not a "special block". It doesn't render particularly nicely when you do that though.