Extension:SyntaxHighlight/ko

SyntaxHighlight 확장 기능은 이전에는 SyntaxHighlight_GeSHi라는 이름이었으며 태그를 사용했을 때 소스 코드를 강조해 줍니다. Pygments 라이브러리를 사용하였고 100개가 넘는 프로그래밍 언어, 마크업 언어, SQL, 쉘 스크립트 같은 다양한 언어를 지원합니다.

나  태그처럼 텍스트를 정확히 입력한 그대로 렌더링됩니다.

사용법
설치하면 위키 페이지에서 "syntaxhighlight" 태그 사용할 수 있습니다. 예를 들어

미디어 위키 마크업의 결과입니다.

MediaWiki 1.16이전의 구버전에서는 태그로 입력해야 합니다. 아직은 지원되지만 추천하지는 않습니다. 로 작성해야합니다.

서식
보여지는 코드가 너무 크다면 MediaWiki:Common.css 페이지로 설정하세요.

위 섹션에 와 같은 줄을 삽입하여 코드 블록을 테두리로 묶을 수 있습니다. 위의 섹션에 와 같은 코드를 삽입하여 사용 된 폰트를 조정할 수도 있습니다.

구문 강조에 오류가 있는 문서
태그에 잘못된  속성값을 가지는 문서들을 추적용 분류에 분류합니다. The message key MediaWiki:syntaxhighlight-error-category determines the category name; on this wiki it is Category:.

The most common error that leads to pages being tagged with this category is a tag with no   attribute at all, because older versions of this extension supported the definition of. These can typically either be replaced with, or  or   can be added to the tag.

The category may also be added, and the content will not be highlighted, if there are more than 1000 lines or more than 100 kB text.

lang
The  attribute defines what lexer should be used. The language affects how the extension highlights the source code. See the section Supported languages for details of supported languages.

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  attribute enables line numbers.

start
The  attribute (in combination with  ) defines the first line number of the code block. For example,  will make line numbering start at 55.

highlight
The  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, ) or ranges using two line numbers and a hyphen (for example,  ).

is the result of

inline
The attribute indicates that the source code should be inline as part of a paragraph (as opposed to being its own block). This option is available starting with MediaWiki 1.26. For backwards-compatibility, an  attribute results in the same behavior.

For example:

The following  is a lambda expression in Python.

Is the result of:

class
When  is used,   (on those wikis that support it; not on MediaWiki itself) specifies that line breaks should not occur at spaces within the code block.

For example:

Without :

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx With : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

style
The  attribute allows CSS attributes to be included directly. This is equivalent to enclosing the block in a (not ) tag. The  attribute cannot be specified this way; it requires an enclosing  tag as described below under Advanced.

For example:

Is the result of:

지원되는 언어들
Pygments 라이브러리는 백개가 넘는 컴퓨터 언어나 파일 형식을 지원합니다. 2020년 1월 기준 목록입니다

프로그래밍 언어
1=

ActionScript

Ada

Agda

Alloy

AMPL

ANTLR

APL

AppleScript

Assembly (여러 형식)

Asymptote

Augeas

AutoIt

Awk

BBC Basic

Befunge

BlitzBasic

Boa

Boo

Boogie

BrainFuck

C, C++ (Arduino같은 방언 포함)

C#

Chapel

Charm++ CI

Cirru

Clay

Clean

Clojure

CoffeeScript

ColdFusion

Common Lisp

Component Pascal

Coq

Croc (MiniD)

Cryptol (Literate Cryptol 포함)

Crystal

Cypher

Cython

D

Dart

DCPU-16

Delphi

Dylan (콘솔 포함)

Eiffel

Elm

Emacs Lisp

Email

Erlang (셸 세션 포함)

Ezhil

Factor

Fancy

Fantom

Fennel

FloScript

Forth

Fortran

FreeFEM++

F#

GAP

Gherkin (Cucumber)

GLSL 셰이더

Golo

Gosu

Groovy

Haskell (Literate Haskell 포함)

HLSL

HSpec

Hy

IDL

Idris (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

Template languages
1=

Angular templates

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

Other markup
1=

Apache config files

Apache Pig

BBCode

CapDL

Cap'n Proto

CMake

Csound scores

CSS

Debian control files

Diff files

Dockerfiles

DTD

EBNF

E-mail headers

Extempore

Flatline

Gettext catalogs

Gnuplot script

Groff markup

Hexdumps

HTML

HTTP sessions

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

Nix language

NSIS scripts

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

For accurate language codes, see complete details in the Pygments document and there are some mappings for some language names which were supported by GeSHi (full list).

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.



설정

 * Linux:


 * (optional): Absolute path to pygmentize of the Pygments package. The extension bundles the Pygments package and points to the bundled version by default, but you can point to a different version, if you want to. For example:.
 * : Configure the default lexer for some wiki pages. By default this will highlight javascript and css pages. Additional content models can be configured by extensions (e.g. Lua, JSON, ..). Example:


 * Windows:


 * If you are hosting your MediaWiki on a Windows machine, you have to set the path for the Pygmentize.exe
 * If there is no  run   from command line inside the   folder to generate the file.

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 to LocalSettings.php.


 * Troubleshooting :

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,.


 * Try pointing in LocalSettings.php towards 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 . After this, the Pygments module can be added to the Python app, for which navigate to the virtual environment path, download and 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:


 * See T128993 on this for further suggestions and information.
 * SELinux can also prevent the extension from running with an error similar to  in your audit.log This can be allowed with

VisualEditor integration
The plugin enables direct editing with VisualEditor. A popup is opened when a user wants to edit  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. See for details

고급 사용
Unlike the and  tags, HTML character entities such as   need not (and should not) have the   character escaped as. Like the tag but unlike the  tag, tags within the range (other than its own closing tag) need not have the   symbol escaped as , nor does wikitext need to be escaped with a  tag.

Furthermore, while assumes tab stops every 8 characters and renders tabs using actual spaces when the rendered text is copied,  uses 4-space tab stops (except Internet Explorer, which uses 8) and preserves the tab characters in the rendered text; the latter may be changed using an enclosing  tag (not, and not using its own   attribute). The  prefix is required for Firefox (from version 4.0), and the   prefix is required for Opera (from version 10.60 to version 15). ( Note that the wiki editing box assumes 8-space tabs. ) This applies only to actual saved pages; previews generated through an edit box or Special:ExpandTemplates may differ.

같이 보기

 * Pygments — Python syntax highlighter
 * Extensions dependent on this one:
 * — highlights pages based on title suffixes.
 * Alternative extensions:
 * — syntax highlighter that uses HighlightJS library (includes support for some languages that are missing from Pygments, such as Maxima).
 * — syntax highlighter that uses Google Code Prettify library.
 * — syntax highlighter that uses SyntaxHighlighter library.