User:PerfektesChaos/js/WikiSyntaxTextMod/flow/selective

WikiSyntaxTextMod → Syntax polishing → Step 5

The fifth step protects further areas (after nowiki, codes, and link targets etc.) against general modifications.

This is not always necessary and will be executed only if there is a reason.

Within protected areas nothing is searched, so nothing found or even worse: replaced.

Necessity of protection
There are two levels: Comments,  and These regions influence further interpretation and processing of wikitext. In the first case the referred ranges are always protected, while parts deserve to be protected only if later acivity has been scheduled.
 * 1) Hide from further analysis
 * 1) Protection against user defined modifications and some changes triggered internally.

Protection of sections with coded information
Ranges with coded information are to be skipped.

If in doubt the extension is spread in conservating direction; may be wider than actually intended. If end marks have not been found, since illegal nesting happened in source text, the range is extended at maximum, in extreme cases until end of the entire wikitext.

Keys for sorting of categories and the entire DEFAULTSORT are always protected against user defined modifications.

Since the processing order brings tags into standardised form first and consecutively protected regions are built from those tags, it is possible to show scaring examples for bad formatting of wikisyntax or similar ML only by  or enclosing by.

Protection of link targets
It is reasonable to modify changed URL and wikilinks of moved pages or disambiguation pages. In particular cases it is meaningful to modify link targets which have been protected before. However, these link targets have to be protected against spelling correction and typographic refinement.

Syntax elements of template transclusion (parameter names with  and  ) might be protected as well, but not the parameter values.

Remarks
&#91; German page &#93;