DDO wiki:AutoWikiBrowser/Typos/header

These are the typo for RegExTypoFix  (Regular Expression Typographical error Fixer, or RETF).

Please add to or improve these regular expressions!

Description
These find and fix common misspellings and grammatical errors. The primary advantage of RegExTypoFix over other possible spellchecking engines and approaches is accuracy and the return of only one possible replacement. The rules below are developed to give as few false positives as possible. Errors should be encountered only in extremely rare usages or when parsing other languages (though even then if there are too many false positives the expression will be modified). On everyday English, accuracy should hit 100%.

RegExTypoFix derivatives can be leveraged in other software. This leads to a massively tested, well-vetted set of automatic corrections.

Syntax of the expressions is described in full on the MSDN website, though for the purposes of this page the Well House summary is likely easier to use.

Usage
Everyone using RegExTypoFix should use it responsibly. '''Check every edit before you make it. If in doubt, SKIP'''.

AutoWikiBrowser (AWB)
AWB purposely avoids fixing typos in certain areas of the wiki-text. Typo fixing is prevented within: image names, template names and parameters, wikilink targets, text in quotations and italics, and any text that follows a colon or asterisk. If a typo rule matches a wikilink target, this rule will be ignored on the whole page.

When using AWB, you can refresh the typo list by selecting "File → Refresh status/typos" (CTRL). This is useful when you are modifying the typo list on Wikipedia while using AWB to test/process the modification (but basic testing should first be done offline—e.g. by using AWB's Regex Tester or "Find and replace").

Adding/changing a misspelling
The syntax for each rule is the following (according to AWB source code): The "word" parameter is optional and any additional spaces between the parameters are ignored.

Before editing this page

 * Note that all typo rules are case-sensitive. This affects how they are written and tested.
 * Test your proposed change by using an ordinary search or an AWB Google Search with a "Find and Replace" configured. This may reveal that your rule will sometimes damage correct text, or may sometimes make the wrong correction. In these cases do not add the rule here; instead, consider adding it to the List of common misspellings.
 * If you do not know how to make a change, suggest it here, where a knowledgeable user will add it for you.
 * Keep in mind that every addition/possibility of a word uses more CPU and slows scanning.
 * Note that only words outside wikimarkup are fixed, so a rule to fix, say, a wiki template will not work on AWB.

Writing typo rules

 * Aim to have a single rule for each root word, prefix, and suffix.
 * Avoid having a rule detect a spelling outside its intended scope (for example, a rule that fixes housa to house must not detect thousand or house). Add word boundaries to both ends of the regex unless you are matching errors in parts of words or multiple words.
 * Do not expect rules to be applied in the order they appear.
 * Write fast rules:
 * Beginnings are expensive, so be specific in the matching of the first few characters to eliminate possibilities quickly.
 * If possible don't use the quantifiers  and   with anything but a single character. Avoid them entirely if possible, as they put extra strain on CPU and are apt to do other than what you expect.
 * Each rule must be completely independent.
 * Update the rule name if you change something that affects it.
 * Because the typo rules are case-sensitive, be sure to handle all reasonable case possibilities.

Testing typo rules

 * With the AWB Regular Expression tester, AWB's "Find and replace", or something similar before adding here. If you use AWB's "Find and replace", make sure "Case sensitive" is checked for each rule tested.
 * With AWB or WikEd immediately after you add them. If they do not work, remove first, analyze later.

To do

 * Identify and improve rules to avoid false positives.
 * Keep lists sorted alphabetically by word= value.