Extensão: SyntaxHighlight
 Estado de lançamento: estável |
|
|---|---|
 |
|
| Implementação | Etiqueta |
| Descrição | Allows source code to be syntax highlighted on wiki pages |
| Autor(es) |
|
| Última versão | atualizações contínuas |
| Política de compatibilidade | Original mantém a compatibilidade com versões anteriores. |
| MediaWiki | 1.25+ |
| Alterações à base de dados | Não |
|
|
<syntaxhighlight> |
|
| Licence | GNU - Licença Pública Geral 2.0 ou superior |
| Transferência | README |
| Traduza a extensão SyntaxHighlight | |
| Problemas | Tarefas em aberto · Reportar um erro |
A extensão SyntaxHighlight, anteriormente conhecida como SyntaxHighlight_GeSHi, fornece formatação rica do código fonte utilizando a etiqeuta <syntaxhighlight>.
It is powered by the Pygments library and supports hundreds of different programming languages and file formats.
Like the <pre> and <poem> tags, the text is rendered exactly as it was typed, preserving any white space.
The SyntaxHighlight extension does not work on wiki installations hardened using Hardened-PHP due to the lack of proc_open, shell_exec and other functions.
Consulte T250763.
The <syntaxhighlight> tag has become expensive since 1.39 for 5 000 or some other extreme amount of syntaxhighlight tags in a single page such as for Wikibooks.
Increase webserver timeout value in environments in extreme cases.
(Consulte T316858.)
Utilização
Once installed, you can use "syntaxhighlight" tags on wiki pages. For example,
def quick_sort(arr):
less = []
pivot_list = []
more = []
if len(arr) <= 1:
return arr
else:
pass
is the result of the following wikitext markup:
<syntaxhighlight lang="python" line>
def quick_sort(arr):
less = []
pivot_list = []
more = []
if len(arr) <= 1:
return arr
else:
pass
</syntaxhighlight>
To use on source code that is transcluded, for example from a module call, use the #tag parser and safesubst::[1]
{{#tag:syntaxhighlight|{{safesubst:Module:Sandbox/userName/myModule}}|lang=lua}}
Prior to MediaWiki 1.16, the extension used the tag <source>.
This is still supported, but is deprecated. <syntaxhighlight> should always be used.
Estilo
If the displayed code is too big, you can adjust it by putting the following into the MediaWiki:Common.css page in your wiki (create it if it does not exist):
/* CSS placed here will be applied to all skins */
.mw-highlight pre {
font-size: 90%;
/* Insert additional CSS styling here */
}
Encasing code blocks in borders can be done by inserting a line like border: 1px dashed blue; in the section above.
Control over font family used can also be exercised by inserting a line like font-family: "Courier New", monospace; into the section above.
A practical method to generate CSS code in bulk that corresponds to one of the color schemes supported by Pygments is to run the following command from within the MediaWiki installation folder.
This example is for the stata-dark color scheme:
./extensions/SyntaxHighlight_GeSHi/pygments/pygmentize -S stata-dark -f html | sed 's/^/.mw-highlight /'
This will output a large chunk of CSS that looks something like:
.mw-highlight pre { line-height: 125%; }
.mw-highlight td.linenos .normal { color: inherit; background-color: transparent; padding-left: 5px; padding-right: 5px; }
.mw-highlight span.linenos { color: inherit; background-color: transparent; padding-left: 5px; padding-right: 5px; }
.mw-highlight td.linenos .special { color: #000000; background-color: #ffffc0; padding-left: 5px; padding-right: 5px; }
.mw-highlight span.linenos.special { color: #000000; background-color: #ffffc0; padding-left: 5px; padding-right: 5px; }
.mw-highlight .hll { background-color: #49483e }
.mw-highlight .c { color: #777; font-style: italic } /* Comment */
.mw-highlight .err { color: #A61717; background-color: #E3D2D2 } /* Error */
.mw-highlight .esc { color: #CCC } /* Escape */
/* ... and so on ... */
These CSS lines can then be copy-pasted into a site-wide CSS page such as MediaWiki:Common.css, or a skin-specific one such as MediaWiki:Vector.css.
Categoria de erro de realce de sintaxe
The extension adds pages that have a bad lang attribute in a <syntaxhighlight> tag to a tracking category.
The message key MediaWiki:syntaxhighlight-error-category determines the category name; on this wiki it is Category:Pages with syntax highlighting errors.
The most common error that leads to pages being tagged with this category is a <syntaxhighlight> tag with no lang attribute at all, because older versions of this extension supported the definition of $wgSyntaxHighlightDefaultLang.
These can typically either be replaced with <pre>, or lang="text" can be added to the tag.
Por exemplo:
<syntaxhighlight lang="text">
...
</syntaxhighlight>
The category may also be added, and the content will not be highlighted, if there are more than 1 000 lines or more than 100 kB text.[2]
Parâmetros
lang
O atributo lang="name" define a lexicografia que deverá ser utilizada.[3]
O idioma afeta como a extensão realça o código fonte.
Consulte #Idiomas suportados para detalhes dos idiomas suportados.
def quick_sort(arr):
less = []
<syntaxhighlight lang="python">
...
</syntaxhighlight>
Specifying an invalid or unknown name will tag the page with a tracking category. See the section #Syntax highlighting error category in this page for details.
line
The line attribute enables line numbers.
def quick_sort(arr):
less = []
<syntaxhighlight lang="python" line>
...
</syntaxhighlight>
start
The start attribute (in combination with line) defines the first line number of the code block.
For example, line start="55" will make line numbering start at line 55.
def quick_sort(arr):
less = []
<syntaxhighlight lang="python" line start="55">
...
</syntaxhighlight>
linelinks
| Versão MediaWiki: | ≥ 1.36 Gerrit change 653142 |
The linelinks attribute (in combination with line) adds link anchors to each line of the code block.
You can click on the line numbers to get a link that highlights the selected line, and use them in internal and external links.
You can also hold ⇧ Shift and click on another line number to get a link that highlights the selected range of lines (Since MediaWiki 1.42 • change 1007640).
When JavaScript is disabled, single-line highlights can be created and existing ones jump to the right location, but the highlight is missing; however, range highlights don’t work at all, so consider using single-line highlights only for accessibility if meaningfully possible.
The value of the attribute is used as a prefix for the anchors, to distinguish multiple code blocks on one page.
Click here to jump to and highlight line 3 in the code block above. Click here to jump to and highlight lines 2-4 in the code block above.
<syntaxhighlight lang="python" line linelinks="example">
...
</syntaxhighlight>
[[#example-3|...]]
[[#example-2--example-4|...]]
highlight
The highlight attribute specifies one or more lines that should be marked (by highlighting those lines with a different background color).
You can specify multiple line numbers separated by commas (for example, highlight="1,4,8") or ranges using two line numbers and a hyphen (for example, highlight="5-7").
start attribute.def quick_sort(arr):
less = []
pivot_list = []
more = []
if len(arr) <= 1:
return arr
É o resultado de:
<syntaxhighlight lang="python" line start="3" highlight="1,5-7">
...
</syntaxhighlight>
inline
| Versão MediaWiki: | ≥ 1.26 |
The attribute indicates that the source code should be inline as part of a paragraph (as opposed to being its own block). (introduzido(a) na 1.26)
class="nowrap" (on those wikis that support it; see below) or style="white-space:nowrap".Por exemplo:
The following lambda x: x * 2 is a lambda expression in Python.
É o resultado de:
The following <syntaxhighlight lang="python" inline>lambda x: x * 2</syntaxhighlight> is a [[w:Lambda (programming)|lambda expression]] in Python.
class
When inline is used, class="nowrap" (on those wikis that support it; not on MediaWiki itself) specifies that line breaks should not occur at spaces within the code block.
Por exemplo:
Sem class="nowrap":
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxlambda x: x * 2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Com style="white-space:nowrap":
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxlambda x: x * 2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
style
The style attribute allows CSS attributes to be included directly.
This is equivalent to enclosing the block in a <div> (not <span>) tag.
The tab‑size attribute cannot be specified this way; it requires an enclosing <span> tag as described below under Advanced.
Por exemplo:
def quick_sort(arr):
less = []
pivot_list = []
more = []
if len(arr) <= 1:
return arr
else:
pass
É o resultado de:
<syntaxhighlight lang="python" style="border: 3px dashed blue;">
def quick_sort(arr):
less = []
pivot_list = []
more = []
if len(arr) <= 1:
return arr
else:
pass
</syntaxhighlight>
copy
| Versão MediaWiki: | ≥ 1.43 |
The copy attribute adds a button link that copies the content to the clipboard when clicked.
inline attribute. If both are specified, copy will be ignored.Por exemplo:
def quick_sort(arr):
less = []
É o resultado de:
<syntaxhighlight lang="python" copy>
def quick_sort(arr):
less = []
</syntaxhighlight>
Idiomas suportados
Pygments library provides syntax-highlighting for hundreds of programming languages and file formats through its built-in regex-based lexing mechanism termed lexers.
Generally, lang uses the lowercase version of the language name, but many languages also have aliases or "short names" as they are called in the Pygments documentation; see Pygments lexers and SyntaxHighlight.lexers.php.
Languages previously supported by GeSHi have been mapped to equivalent Pygments lexers, see SyntaxHighlightGeSHiCompat.php.
As of January 2020, the list of programming languages supported by Pygments is:
Linguagens de programação
- ActionScript
- Ada
- Agda (incl. literate)
- Alloy
- AMPL
- ANTLR
- APL
- AppleScript
- Assembly (various)
- Asymptote
- Augeas
- AutoIt
- Awk
- BBC Basic
- Befunge
- BlitzBasic
- Boa
- Boo
- Boogie
- BrainFuck
- C, C++ (incl. dialects like Arduino)
- C#
- Chapel
- Charm++ CI
- Cirru
- Clay
- Clean
- Clojure
- CoffeeScript
- ColdFusion
- Common Lisp
- Component Pascal
- Coq
- Croc (MiniD)
- Cryptol (incl. Literate Cryptol)
- Crystal
- Cypher
- Cython
- D
- Dart
- DCPU-16
- Delphi
- Dylan (incl. console)
- Eiffel
- Elm
- Emacs Lisp
- Erlang (incl. shell sessions)
- Ezhil
- Factor
- Fancy
- Fantom
- Fennel
- FloScript
- Forth
- Fortran
- FreeFEM++
- F#
- GAP
- Gherkin (Cucumber)
- GLSL shaders
- Golo
- Gosu
- Groovy
- Haskell (incl. Literate Haskell)
- HLSL
- HSpec
- Hy
- IDL
- Idris (incl. Literate Idris)
- Igor Pro
- Io
- Jags
- Java
- JavaScript
- Jasmin
- Jcl
- Julia
- Kotlin
- Lasso (incl. templating)
- Limbo
- LiveScript
- Logtalk
- Logos
- Lua
- Mathematica
- Matlab
- Modelica
- Modula-2
- Monkey
- Monte
- MoonScript
- Mosel
- MuPad
- NASM
- Nemerle
- NesC
- NewLISP
- Nimrod
- Nit
- Notmuch
- NuSMV
- Objective-C
- Objective-J
- Octave
- OCaml
- Opa
- OpenCOBOL
- ParaSail
- Pawn
- PHP
- Perl 5
- Pike
- Pony
- PovRay
- PostScript
- PowerShell
- Praat
- Prolog
- Python (incl. console sessions and tracebacks)
- QBasic
- Racket
- Raku a.k.a. Perl 6
- REBOL
- Red
- Redcode
- Rexx
- Ride
- Ruby (incl. irb sessions)
- Rust
- S, S-Plus, R
- Scala
- Scdoc
- Scheme
- Scilab
- SGF
- Shell scripts (Bash, Tcsh, Fish)
- Shen
- Silver
- Slash
- Slurm
- Smalltalk
- SNOBOL
- Snowball
- Solidity
- SourcePawn
- Stan
- Standard ML
- Stata
- Swift
- Swig
- SuperCollider
- Tcl
- Tera Term language
- TypeScript
- TypoScript
- USD
- Unicon
- Urbiscript
- Vala
- VBScript
- Verilog, SystemVerilog
- VHDL
- Visual Basic.NET
- Visual FoxPro
- Whiley
- Xtend
- XQuery
- Zeek
- Zephir
- Zig
Linguagens de modelo
- Modelos angulares
- Cheetah templates
- ColdFusion
- Django / Jinja templates
- ERB (Ruby templating)
- Evoque
- Genshi (the Trac template language)
- Handlebars
- JSP (Java Server Pages)
- Liquid
- Myghty (the HTML::Mason based framework)
- Mako (the Myghty successor)
- Slim
- Smarty templates (PHP templating)
- Tea
- Twig
- WikiText
Outra marcação
- Ficheiros de configuração Apache
- Apache Pig
- BBCode
- CapDL
- Cap'n Proto
- CMake
- Csound scores
- CSS
- Debian control files
- Diff files
- Dockerfiles
- DTD
- EBNF
- Cabeçalhos de E-mail
- Extempore
- Flatline
- Catálogos de Gettext
- Script Gnuplot
- Marcação Groff
- Hexdumps
- HTML
- Sessões de HTTP
- IDL
- Inform
- INI-style config files
- IRC logs (irssi style)
- Isabelle
- JSGF notation
- JSON, JSON-LD
- Lean theorem prover
- Lighttpd config files
- Linux kernel log (dmesg)
- LLVM assembly
- LSL scripts
- Makefiles
- MoinMoin/Trac Wiki markup
- MQL
- MySQL
- NCAR command language
- Nginx config files
- Linguagem Nix
- Scripts NSIS
- Notmuch
- POV-Ray scenes
- Puppet
- QML
- Ragel
- Redcode
- ReST
- Roboconf
- Robot Framework
- RPM spec files
- Rql
- RSL
- Scdoc
- SPARQL
- SQL, also MySQL, SQLite
- Squid configuration
- TADS 3
- Terraform
- TeX
- Thrift
- TOML
- Treetop grammars
- USD (Universal Scene Description)
- Varnish configs
- VGL
- Vim Script
- WDiff
- Windows batch files
- XML
- XSLT
- YAML
- Windows Registry files
- ansys
- apdl
- asc
- gcode
- golang === go
- gsql
- jslt
- julia-repl
- kuin
- meson
- nestedtext
- nodejsrepl
- nt
- omg-idl
- output
- pem
- procfile
- pwsh
- smithy
- teal
- thingsdb
- ti
- wast
- wat
Lexers previously supported by GeSHi
Below is a partial list of languages that GeSHi could highlight, with strike-through for languages no longer supported after the switch to Pygments.
| Lexers previously supported by GeSHi | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Instalação
- Exporte e coloque o ficheiro, ou ficheiros, num diretório chamado
SyntaxHighlight_GeSHi, na sua pastaextensions/.
Developers and code contributors should install the extension from Git instead, using:cd extensions/ git clone https://gerrit.wikimedia.org/r/mediawiki/extensions/SyntaxHighlight_GeSHi
- Only when installing from Git, run Composer to install PHP dependencies, by issuing
composer install --no-devin the extension directory. (See T173141 for potential complications.) - Acrescente o seguinte código ao fundo do ficheiro $LocalSettings:
wfLoadExtension( 'SyntaxHighlight_GeSHi' );
- In Linux, set execute permissions for the pygmentize binary.
You can use an FTP client or the following shell command to do so:
chmod a+x /path/to/extensions/SyntaxHighlight_GeSHi/pygments/pygmentize
Pronto – Na página especial Special:Versionda sua wiki verifique se a extensão foi instalada.
Vagrant installation:
- Se estiver a utilizar Vagrant, instale com
vagrant roles enable syntaxhighlight --provision
So, after installation from Git change to the directory containing the extension e.g.
"../extensions/SyntaxHighlight_GeSHi/" and run composer install --no-dev, or when updating: composer update --no-dev.Alternatively as well as preferably add the line
"extensions/SyntaxHighlight_GeSHi/composer.json" to the "composer.local.json" file in the root directory of your wiki like e.g.
{
"extra": {
"merge-plugin": {
"include": [
"extensions/SyntaxHighlight_GeSHi/composer.json"
]
}
}
}
Now run composer update --no-dev.
 Aviso: | When uploading the extension via FTP be sure to upload the pygments/pygmentize file with the transfer type binary. |
Configuração
$wgSyntaxHighlightMaxLines, $wgSyntaxHighlightMaxBytes
|
Optional | For performance reasons, blobs or pages (JS, Lua and CSS pages) larger than these values will not be highlighted. (introduzido(a) na 1.40) |
- Linux
$wgPygmentizePath
|
Optional | Absolute path to pygmentize of the Pygments package. The extension bundles the Pygments package and $wgPygmentizePath points to the bundled version by default, but you can point to a different version, if you want to. Por exemplo: $wgPygmentizePath = "/usr/local/bin/pygmentize";.
|
- Windows
- If you are hosting your MediaWiki on a Windows machine, you have to set the path for the Pygmentize.exe
$wgPygmentizePath = "c:\\Python27\\Scripts\\pygmentize.exe";- If there is no
pygmentize.exeruneasy_install Pygmentsfrom command line inside theScriptsfolder to generate the file.
- If there is no
If you are using the bundled pygmentize binary (extensions/SyntaxHighlight_GeSHi/pygments/pygmentize), make sure your webserver is permitted to execute it.
If your host does not allow you to add executables to your web directory, install python-pygments and add $wgPygmentizePath = pygmentize to LocalSettings.php.
- Resolução de problemas
After updating to MediaWiki v1.26 and above, some users started reporting problems with the extension.
There could be cases, when some languages, such as Lua might not get highlighted and by turning on debugging, MediaWiki would throw out the error, Notice: Failed to invoke Pygments: /usr/bin/env: python3: No such file or directory.
- Try pointing
$wgPygmentizePathinLocalSettings.phptowards an external pygmentize binary.
- In shared hosting environments with cPanel, this can be done by setting up a new Python application through the "Setup Python App" menu, and activating the virtual environment for the app through SSH (
source /virtualenv/python/3.5/bin/activate). After this, the Pygments module can be added to the Python app, for which navigate to the virtual environment path (cd virtualenv/python/3.5/bin/), download and install Pygments (./pip install Pygments) and then activate the module by adding "Pygments" under the "Existing applications" section of the "Setup Python App" menu. This will create the required file at path:virtualenv/python/3.5/bin/pygmentize
- In shared hosting environments with cPanel, this can be done by setting up a new Python application through the "Setup Python App" menu, and activating the virtual environment for the app through SSH (
- See phab:T128993 on this for further suggestions and information.
- SELinux can also prevent the extension from running with an error similar to
type=AVC msg=audit(1609598265.169:225924): avc: denied { execute } for pid=2360888 comm="bash" name="pygmentize" dev="dm-0" ino=50814399 scontext=system_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:httpd_user_content_t:s0 tclass=file permissive=0in your audit.log. This can be allowed withsetsebool -P httpd_unified 1 - In earlier versions of this extension, Windows would sometimes fail with an _Py_HashRandomization_Init error. This was a bug with the Windows environment not being passed to python executions. A fix was released in 1.40, with backports to 1.38 and 1.39.
Integração do Editor Visual
The plugin enables direct editing with VisualEditor.
A popup is opened when a user wants to edit syntaxhighlight sections.
For this to work, VisualEditor must be installed and configured from the latest Git version, same for Parsoid.
The feature may not work with older Parsoid versions.
Cosnulte Extension:SyntaxHighlight/VisualEditor para detalhes.
Using with MediaWiki-Docker
See MediaWiki-Docker/Extension/SyntaxHighlight for instructions on configuring a MediaWiki-Docker environment for SyntaxHighlight usage, development, and testing.
Avançado
- Unlike the
<pre>and<code>tags, HTML character entities such as need not (and should not) have the&character escaped as&. - Like the
<pre>tag but unlike the<code>tag, tags within the range (other than its own closing tag) need not have the<symbol escaped as<, nor does Texto Wiki (Wikitext) need to be escaped with a<nowiki>tag. - Furthermore, while
<pre>assumes tab stops every 8 characters and renders tabs using actual spaces when the rendered text is copied,<syntaxhighlight>uses 4-space tab stops (except Internet Explorer, which uses 8) and preserves the tab characters in the rendered text.- Tab stop length for
<syntaxhighlight>may be adjusted by assigning it to a CSS class (e.g.<syntaxhighlight class="syntaxhighlight-tab-size-8">), which may be specified using Global CSS stylesheets or TemplateStyles, that specifies thetab-size(its own style attribute cannot be used to specify the tab stops):.syntaxhighlight-tab-size-nn pre {-moz-tab-size: nn; -o-tab-size: nn; tab-size: nn;"} - The
-moz-prefix is required for older versions of Firefox (from version 4.0 to version 90), and the-o-prefix is required for older versions of Opera (from version 10.60 to version 15).[4]
- Tab stop length for
Consultar também
- Instructions on updating the pygments version used by SyntaxHighlight
- Instructions on setting up SyntaxHighlight in a MediaWiki-Docker development environment
- Pygments – Python syntax highlighter
- Extensões dependentes desta:
- Extension:SyntaxHighlightPages – realça as páginas baseadas em sufixos de título.
- Extensões alternativas:
- Extension:Highlightjs Integration – syntax highlighter that uses HighlightJS library (includes support for some languages that are missing from Pygments, such as Maxima).
- Extension:ExternalContent – embed external content, such as code from GitHub, GitLab, and Bitkeeper repos with automatic rendering of Markdown files; and using syntax highlighting via the Prism.js library for nearly 300 supported languages. Content indexed by CirrusSearch
Notas de rodapé
- ↑ See topic "problem of syntaxhighlight vs code transclusion"
- ↑ phab:T104109#3879800
- ↑ lexicografia: divide a fonte em códigos, fragmentos da fonte que têm um tipo de código que determina o que o texto representa semânticamente (por exemplo, palavra-chave, string, ou comentário). There is a lexer for every language or markup format that Pygments supports. Consulte https://pygments.org/docs/quickstart/
- ↑ devmo:Web/CSS/tab-size
 | Este extensão está a ser utilizado em um ou mais projetos da Wikimedia. Isso provavelmente significa que a extensão é estável e funciona bem o suficiente para ser usada por esses sites de alto tráfego. Procure o nome desta extensão nos arquivos de configuração CommonSettings.php e InitialiseSettings.php da Wikimedia para ver onde está instalado. Uma lista completa das extensões instaladas em um determinado wiki pode ser vista na página Special:Version do wiki. |
 | This extension is included in the following wiki farms/hosts and/or packages: |
- Extensions bundled with MediaWiki 1.21/pt
- Stable extensions/pt
- Tag extensions/pt
- ParserFirstCallInit extensions/pt
- ResourceLoaderRegisterModules extensions/pt
- SoftwareInfo extensions/pt
- GPL licensed extensions/pt
- Extensions in Wikimedia version control/pt
- All extensions/pt
- Extensions requiring Composer with git/pt
- Extensions used on Wikimedia/pt
- Extensions included in BlueSpice/pt
- Extensions included in Canasta/pt
- Extensions available as Debian packages/pt
- Extensions included in Fandom/pt
- Extensions included in Miraheze/pt
- Extensions included in MyWikis/pt
- Extensions included in ProWiki/pt
- Extensions included in semantic::core/pt
- Extensions included in ShoutWiki/pt
- Extensions included in Telepedia/pt
- Extensions included in Weird Gloop/pt
- Extensions included in wiki.gg/pt
- Syntax highlighting extensions/pt
- GeSHi extensions/pt
- Extensions with VisualEditor support/pt