Localisation updates from http://translatewiki.net.

Change-Id: I839107fd43dc0d88c2eff924007e5ecfaaeca816
(bug 45669) Fix highly recursive number highlighting regex

The regular expression used for number highlighting in GeSHi is highly
recursive, and easily overflows the low PCRE recursion limit on WMF
sites (and, on sites where the recursion limit isn't low, it can easily
crash PHP).

Fortunately, it's easy to fix for the common case.

This is also reported upstream at
https://sourceforge.net/p/geshi/bugs/223/

Bug: 45669
Bug: 36839
Change-Id: I27203c767d1d3f2f0999b1b1d8a06e8cf68c19ed
Localisation updates from http://translatewiki.net.

Change-Id: Ia73796f6c61e4a4f86a7dbc2ce5f7ce4c7fb3241
Localisation updates from http://translatewiki.net.

Change-Id: I2f469034d0a51f97cdd2e5a4f1183c814d484f18
Localisation updates from http://translatewiki.net.

Change-Id: Ied5c30b5659c25f8effba18035c81cf800b3bd85
Remove contrib directory and add gitignore to ignore it

Change-Id: I0a4bcfb54abe9d98b37d87912ee23ec17cea11ac
Localisation updates from http://translatewiki.net.

Change-Id: I8727666c874f1a0393353a58fc4d68a6840fea72
Localisation updates from http://translatewiki.net.

Change-Id: I50420a7ed85872ba072fffca85b02f642a727780
Localisation updates from http://translatewiki.net.

Change-Id: Icab1dac6c13146d6198cb0345a618cf23e4184d2
Localisation updates from http://translatewiki.net.

Change-Id: I512afaf3fc61d85c8eb3cec7ca4108cffc1c0aa9
Add Option to Enable Keyword Links

Patch by Bryan Petty

Bug: 53787
Change-Id: I8c818859df8240cfcfef94d06d5d12a848cc76dc
Haskell syntax: omit single quotes from QUOTEMARKS

Single quotes in Haskell may be used to delimit character literals, but they
can also be used in identifiers. GeSHi's syntax highlighter only recognizes the
former usage. When Haskell source uses "'" as part of an identifier, GeSHi
treats it as the start of a literal string, which screws up syntax
highlighting.

Upstream bug report and proposed patch have been ignored for more than a year,
so I am applying the proposed fix here, and changing the version identifier to
reflect a WMF modification.

Upstream bug report: <http://sourceforge.net/p/geshi/bugs/217/>
Upstream proposed patch: <http://sourceforge.net/p/geshi/bugs/219/>

Bug: 52509
Change-Id: I210832c4b272b5c03bbc4623d73fb821092e5ef4
Localisation updates from http://translatewiki.net.

Change-Id: I3147b110244f3854c01abdd49291880f4c3c1e21
Localisation updates from http://translatewiki.net.

Change-Id: I1d973d94b73b0760a0cdd6c12bc7cf574f1035e8
Merge "Localisation updates from http://translatewiki.net."
Localisation updates from http://translatewiki.net.

Change-Id: I7841ab7af5e7c2ec280f9f1f9d3894a8d1de4c86
Merge "Haskell syntax: omit single quotes from QUOTEMARKS"
Localisation updates from http://translatewiki.net.

Change-Id: Ic3c6b4f62f6bfd0e7d8d78d17ffbc6175653defa
Protect tabs from HTML Tidy

HTML Tidy doesn't care for tabs, and likes to always output spaces. This
can break the syntax-highlighted output, since Tidy converts tabs to
spaces on the source-code level instead of on the rendered HTML level,
even inside <pre> tags where it really shouldn't (this is probably a bug
in Tidy).

r97300 fixed the bad indenting by converting tabs to spaces before
highlighting, which works around Tidy's bug but breaks highlighting of
languages where tabs are significant (e.g. Whitespace).

It turns out that Tidy's tab mangling occurs while it's reading the
source file, before the conversion of entities such as &#9; to tab. So
GeSHi can armor its <pre>-wrapped output against Tidy's bug by encoding
all tabs as &#9;.

Bug: 30930
Bug: 57826
Change-Id: Id541e2712bd3f94446442ccf2e1e2f214e2801ba
Localisation updates from https://translatewiki.net.

Change-Id: I37b572a144dfb7deca997b2383d8f5c2b8eff015