2015-05-20 21:36:13 +00:00
|
|
|
{
|
|
|
|
|
"name": "SyntaxHighlight",
|
Highlight using Pygments rather than Geshi
GeSHi is unmaintained, lacks support for many popular modern languages, and
suffers from deep architectural flaws, chief among them the inconsistent
tokenization of different languages, each of which requires a custom
stylesheet.
Pygments is a well-maintained alternative. It is, by my count, the most popular
syntax highlighting library around. It is BSD-licensed, actively maintained,
and is widely used in PHP projects.
To keep this easy to review, this change does not include update for l10n
files, and it does not delete the geshi/ directory. I will do those in a
separate patch.
The chief change between this and the previous implementation is that errors
result in the code block not being highlighted, as opposed to not being printed
at all, having been replaced by an angry red error message. I think that is the
right user experience. If you go to StackOverflow or GitHub and try to mark up
your code block as being written in some language that their highlighter
doesn't know about, you don't get an error message -- the code simply doesn't
get highlighted.
Because we don't recursively load dependencies for extensions, to test this,
you will need to create a composer.local.json in $IP and add:
{
"extra": {
"merge-plugin": {
"include": [
"extensions/SyntaxHighlight_GeSHi/composer.json"
]
}
}
}
Then run `composer update`.
Bug: T85794
Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
|
|
|
"version": "2.0",
|
2015-05-20 21:36:13 +00:00
|
|
|
"author": [
|
|
|
|
|
"Brion Vibber",
|
|
|
|
|
"Tim Starling",
|
|
|
|
|
"Rob Church",
|
Highlight using Pygments rather than Geshi
GeSHi is unmaintained, lacks support for many popular modern languages, and
suffers from deep architectural flaws, chief among them the inconsistent
tokenization of different languages, each of which requires a custom
stylesheet.
Pygments is a well-maintained alternative. It is, by my count, the most popular
syntax highlighting library around. It is BSD-licensed, actively maintained,
and is widely used in PHP projects.
To keep this easy to review, this change does not include update for l10n
files, and it does not delete the geshi/ directory. I will do those in a
separate patch.
The chief change between this and the previous implementation is that errors
result in the code block not being highlighted, as opposed to not being printed
at all, having been replaced by an angry red error message. I think that is the
right user experience. If you go to StackOverflow or GitHub and try to mark up
your code block as being written in some language that their highlighter
doesn't know about, you don't get an error message -- the code simply doesn't
get highlighted.
Because we don't recursively load dependencies for extensions, to test this,
you will need to create a composer.local.json in $IP and add:
{
"extra": {
"merge-plugin": {
"include": [
"extensions/SyntaxHighlight_GeSHi/composer.json"
]
}
}
}
Then run `composer update`.
Bug: T85794
Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
|
|
|
"Niklas Laxström",
|
2015-05-27 16:15:00 +00:00
|
|
|
"Ori Livneh",
|
|
|
|
|
"Ed Sanders"
|
2015-05-20 21:36:13 +00:00
|
|
|
],
|
|
|
|
|
"url": "https://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi",
|
|
|
|
|
"descriptionmsg": "syntaxhighlight-desc",
|
|
|
|
|
"license-name": "GPL-2.0+",
|
|
|
|
|
"type": "parserhook",
|
|
|
|
|
"MessagesDirs": {
|
|
|
|
|
"SyntaxHighlight_GeSHi": [
|
|
|
|
|
"i18n"
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
"AutoloadClasses": {
|
|
|
|
|
"SyntaxHighlight_GeSHi": "SyntaxHighlight_GeSHi.class.php",
|
2015-05-27 16:15:00 +00:00
|
|
|
"GeSHi": "SyntaxHighlight_GeSHi.compat.php",
|
2015-06-24 23:34:11 +00:00
|
|
|
"ResourceLoaderGeSHiVisualEditorModule": "ResourceLoaderGeSHiVisualEditorModule.php"
|
Highlight using Pygments rather than Geshi
GeSHi is unmaintained, lacks support for many popular modern languages, and
suffers from deep architectural flaws, chief among them the inconsistent
tokenization of different languages, each of which requires a custom
stylesheet.
Pygments is a well-maintained alternative. It is, by my count, the most popular
syntax highlighting library around. It is BSD-licensed, actively maintained,
and is widely used in PHP projects.
To keep this easy to review, this change does not include update for l10n
files, and it does not delete the geshi/ directory. I will do those in a
separate patch.
The chief change between this and the previous implementation is that errors
result in the code block not being highlighted, as opposed to not being printed
at all, having been replaced by an angry red error message. I think that is the
right user experience. If you go to StackOverflow or GitHub and try to mark up
your code block as being written in some language that their highlighter
doesn't know about, you don't get an error message -- the code simply doesn't
get highlighted.
Because we don't recursively load dependencies for extensions, to test this,
you will need to create a composer.local.json in $IP and add:
{
"extra": {
"merge-plugin": {
"include": [
"extensions/SyntaxHighlight_GeSHi/composer.json"
]
}
}
}
Then run `composer update`.
Bug: T85794
Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
|
|
|
},
|
2015-06-20 01:04:36 +00:00
|
|
|
"ExtensionFunctions": [
|
|
|
|
|
"SyntaxHighlight_GeSHi::onSetup"
|
|
|
|
|
],
|
Highlight using Pygments rather than Geshi
GeSHi is unmaintained, lacks support for many popular modern languages, and
suffers from deep architectural flaws, chief among them the inconsistent
tokenization of different languages, each of which requires a custom
stylesheet.
Pygments is a well-maintained alternative. It is, by my count, the most popular
syntax highlighting library around. It is BSD-licensed, actively maintained,
and is widely used in PHP projects.
To keep this easy to review, this change does not include update for l10n
files, and it does not delete the geshi/ directory. I will do those in a
separate patch.
The chief change between this and the previous implementation is that errors
result in the code block not being highlighted, as opposed to not being printed
at all, having been replaced by an angry red error message. I think that is the
right user experience. If you go to StackOverflow or GitHub and try to mark up
your code block as being written in some language that their highlighter
doesn't know about, you don't get an error message -- the code simply doesn't
get highlighted.
Because we don't recursively load dependencies for extensions, to test this,
you will need to create a composer.local.json in $IP and add:
{
"extra": {
"merge-plugin": {
"include": [
"extensions/SyntaxHighlight_GeSHi/composer.json"
]
}
}
}
Then run `composer update`.
Bug: T85794
Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
|
|
|
"ResourceFileModulePaths": {
|
|
|
|
|
"localBasePath": "modules",
|
|
|
|
|
"remoteExtPath": "SyntaxHighlight_GeSHi/modules"
|
2015-05-20 21:36:13 +00:00
|
|
|
},
|
|
|
|
|
"ResourceModules": {
|
Highlight using Pygments rather than Geshi
GeSHi is unmaintained, lacks support for many popular modern languages, and
suffers from deep architectural flaws, chief among them the inconsistent
tokenization of different languages, each of which requires a custom
stylesheet.
Pygments is a well-maintained alternative. It is, by my count, the most popular
syntax highlighting library around. It is BSD-licensed, actively maintained,
and is widely used in PHP projects.
To keep this easy to review, this change does not include update for l10n
files, and it does not delete the geshi/ directory. I will do those in a
separate patch.
The chief change between this and the previous implementation is that errors
result in the code block not being highlighted, as opposed to not being printed
at all, having been replaced by an angry red error message. I think that is the
right user experience. If you go to StackOverflow or GitHub and try to mark up
your code block as being written in some language that their highlighter
doesn't know about, you don't get an error message -- the code simply doesn't
get highlighted.
Because we don't recursively load dependencies for extensions, to test this,
you will need to create a composer.local.json in $IP and add:
{
"extra": {
"merge-plugin": {
"include": [
"extensions/SyntaxHighlight_GeSHi/composer.json"
]
}
}
}
Then run `composer update`.
Bug: T85794
Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
|
|
|
"ext.pygments": {
|
2015-05-26 10:28:02 +00:00
|
|
|
"position": "top",
|
2015-06-23 11:17:03 +00:00
|
|
|
"targets": [
|
|
|
|
|
"desktop",
|
|
|
|
|
"mobile"
|
|
|
|
|
],
|
Highlight using Pygments rather than Geshi
GeSHi is unmaintained, lacks support for many popular modern languages, and
suffers from deep architectural flaws, chief among them the inconsistent
tokenization of different languages, each of which requires a custom
stylesheet.
Pygments is a well-maintained alternative. It is, by my count, the most popular
syntax highlighting library around. It is BSD-licensed, actively maintained,
and is widely used in PHP projects.
To keep this easy to review, this change does not include update for l10n
files, and it does not delete the geshi/ directory. I will do those in a
separate patch.
The chief change between this and the previous implementation is that errors
result in the code block not being highlighted, as opposed to not being printed
at all, having been replaced by an angry red error message. I think that is the
right user experience. If you go to StackOverflow or GitHub and try to mark up
your code block as being written in some language that their highlighter
doesn't know about, you don't get an error message -- the code simply doesn't
get highlighted.
Because we don't recursively load dependencies for extensions, to test this,
you will need to create a composer.local.json in $IP and add:
{
"extra": {
"merge-plugin": {
"include": [
"extensions/SyntaxHighlight_GeSHi/composer.json"
]
}
}
}
Then run `composer update`.
Bug: T85794
Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
|
|
|
"styles": [
|
2015-06-26 00:15:40 +00:00
|
|
|
"pygments.generated.css",
|
|
|
|
|
"pygments.wrapper.css"
|
Highlight using Pygments rather than Geshi
GeSHi is unmaintained, lacks support for many popular modern languages, and
suffers from deep architectural flaws, chief among them the inconsistent
tokenization of different languages, each of which requires a custom
stylesheet.
Pygments is a well-maintained alternative. It is, by my count, the most popular
syntax highlighting library around. It is BSD-licensed, actively maintained,
and is widely used in PHP projects.
To keep this easy to review, this change does not include update for l10n
files, and it does not delete the geshi/ directory. I will do those in a
separate patch.
The chief change between this and the previous implementation is that errors
result in the code block not being highlighted, as opposed to not being printed
at all, having been replaced by an angry red error message. I think that is the
right user experience. If you go to StackOverflow or GitHub and try to mark up
your code block as being written in some language that their highlighter
doesn't know about, you don't get an error message -- the code simply doesn't
get highlighted.
Because we don't recursively load dependencies for extensions, to test this,
you will need to create a composer.local.json in $IP and add:
{
"extra": {
"merge-plugin": {
"include": [
"extensions/SyntaxHighlight_GeSHi/composer.json"
]
}
}
}
Then run `composer update`.
Bug: T85794
Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
|
|
|
]
|
2015-05-27 16:15:00 +00:00
|
|
|
},
|
|
|
|
|
"ext.geshi.visualEditor": {
|
2015-06-24 23:34:11 +00:00
|
|
|
"class": "ResourceLoaderGeSHiVisualEditorModule",
|
2015-05-27 16:15:00 +00:00
|
|
|
"scripts": [
|
|
|
|
|
"VisualEditor/ve.dm.MWSyntaxHighlightNode.js",
|
|
|
|
|
"VisualEditor/ve.ce.MWSyntaxHighlightNode.js",
|
|
|
|
|
"VisualEditor/ve.ui.MWSyntaxHighlightInspector.js",
|
|
|
|
|
"VisualEditor/ve.ui.MWSyntaxHighlightInspectorTool.js"
|
|
|
|
|
],
|
|
|
|
|
"styles": [
|
|
|
|
|
"VisualEditor/ve.ui.MWSyntaxHighlightInspector.css"
|
|
|
|
|
],
|
|
|
|
|
"dependencies": [
|
2015-06-24 23:34:11 +00:00
|
|
|
"ext.visualEditor.mwcore"
|
2015-05-27 16:15:00 +00:00
|
|
|
],
|
|
|
|
|
"messages": [
|
|
|
|
|
"syntaxhighlight-visualeditor-mwsyntaxhighlightinspector-code",
|
|
|
|
|
"syntaxhighlight-visualeditor-mwsyntaxhighlightinspector-language",
|
|
|
|
|
"syntaxhighlight-visualeditor-mwsyntaxhighlightinspector-title"
|
|
|
|
|
],
|
|
|
|
|
"targets": [ "desktop", "mobile" ]
|
2015-05-20 21:36:13 +00:00
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
"Hooks": {
|
|
|
|
|
"ParserFirstCallInit": [
|
Highlight using Pygments rather than Geshi
GeSHi is unmaintained, lacks support for many popular modern languages, and
suffers from deep architectural flaws, chief among them the inconsistent
tokenization of different languages, each of which requires a custom
stylesheet.
Pygments is a well-maintained alternative. It is, by my count, the most popular
syntax highlighting library around. It is BSD-licensed, actively maintained,
and is widely used in PHP projects.
To keep this easy to review, this change does not include update for l10n
files, and it does not delete the geshi/ directory. I will do those in a
separate patch.
The chief change between this and the previous implementation is that errors
result in the code block not being highlighted, as opposed to not being printed
at all, having been replaced by an angry red error message. I think that is the
right user experience. If you go to StackOverflow or GitHub and try to mark up
your code block as being written in some language that their highlighter
doesn't know about, you don't get an error message -- the code simply doesn't
get highlighted.
Because we don't recursively load dependencies for extensions, to test this,
you will need to create a composer.local.json in $IP and add:
{
"extra": {
"merge-plugin": {
"include": [
"extensions/SyntaxHighlight_GeSHi/composer.json"
]
}
}
}
Then run `composer update`.
Bug: T85794
Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
|
|
|
"SyntaxHighlight_GeSHi::onParserFirstCallInit"
|
2015-05-20 21:36:13 +00:00
|
|
|
],
|
|
|
|
|
"ContentGetParserOutput": [
|
Highlight using Pygments rather than Geshi
GeSHi is unmaintained, lacks support for many popular modern languages, and
suffers from deep architectural flaws, chief among them the inconsistent
tokenization of different languages, each of which requires a custom
stylesheet.
Pygments is a well-maintained alternative. It is, by my count, the most popular
syntax highlighting library around. It is BSD-licensed, actively maintained,
and is widely used in PHP projects.
To keep this easy to review, this change does not include update for l10n
files, and it does not delete the geshi/ directory. I will do those in a
separate patch.
The chief change between this and the previous implementation is that errors
result in the code block not being highlighted, as opposed to not being printed
at all, having been replaced by an angry red error message. I think that is the
right user experience. If you go to StackOverflow or GitHub and try to mark up
your code block as being written in some language that their highlighter
doesn't know about, you don't get an error message -- the code simply doesn't
get highlighted.
Because we don't recursively load dependencies for extensions, to test this,
you will need to create a composer.local.json in $IP and add:
{
"extra": {
"merge-plugin": {
"include": [
"extensions/SyntaxHighlight_GeSHi/composer.json"
]
}
}
}
Then run `composer update`.
Bug: T85794
Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
|
|
|
"SyntaxHighlight_GeSHi::onContentGetParserOutput"
|
2015-05-20 21:36:13 +00:00
|
|
|
],
|
|
|
|
|
"ApiFormatHighlight": [
|
Highlight using Pygments rather than Geshi
GeSHi is unmaintained, lacks support for many popular modern languages, and
suffers from deep architectural flaws, chief among them the inconsistent
tokenization of different languages, each of which requires a custom
stylesheet.
Pygments is a well-maintained alternative. It is, by my count, the most popular
syntax highlighting library around. It is BSD-licensed, actively maintained,
and is widely used in PHP projects.
To keep this easy to review, this change does not include update for l10n
files, and it does not delete the geshi/ directory. I will do those in a
separate patch.
The chief change between this and the previous implementation is that errors
result in the code block not being highlighted, as opposed to not being printed
at all, having been replaced by an angry red error message. I think that is the
right user experience. If you go to StackOverflow or GitHub and try to mark up
your code block as being written in some language that their highlighter
doesn't know about, you don't get an error message -- the code simply doesn't
get highlighted.
Because we don't recursively load dependencies for extensions, to test this,
you will need to create a composer.local.json in $IP and add:
{
"extra": {
"merge-plugin": {
"include": [
"extensions/SyntaxHighlight_GeSHi/composer.json"
]
}
}
}
Then run `composer update`.
Bug: T85794
Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
|
|
|
"SyntaxHighlight_GeSHi::onApiFormatHighlight"
|
2015-06-23 20:46:35 +00:00
|
|
|
],
|
|
|
|
|
"RejectParserCacheValue": [
|
|
|
|
|
"SyntaxHighlight_GeSHi::onRejectParserCacheValue"
|
2015-05-20 21:36:13 +00:00
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
"SyntaxHighlightModels": {
|
|
|
|
|
"css": "css",
|
|
|
|
|
"javascript": "javascript"
|
|
|
|
|
},
|
2015-05-27 16:15:00 +00:00
|
|
|
"VisualEditorPluginModules": [
|
|
|
|
|
"ext.geshi.visualEditor"
|
|
|
|
|
],
|
2015-05-20 21:36:13 +00:00
|
|
|
"config": {
|
2015-06-25 01:11:54 +00:00
|
|
|
"PygmentizePath": false
|
2015-05-29 03:39:54 +00:00
|
|
|
},
|
2015-06-23 04:41:39 +00:00
|
|
|
"ParserTestFiles": [
|
|
|
|
|
"tests/parserTests.txt"
|
|
|
|
|
],
|
2015-05-29 03:39:54 +00:00
|
|
|
"manifest_version": 1
|
2015-05-20 21:36:13 +00:00
|
|
|
}
|