wikimedia/mediawiki-extensions-WikiEditor
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/WikiEditor synced 2024-12-02 20:06:49 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-extensions-WikiEd.../modules/jquery.wikiEditor.toolbar.config.js

744 lines
23 KiB
JavaScript
Raw Normal View History

A bit of a reorganisation that fixes bug 27164. Basically the extensive configuration in the ext.wikieditor.* functions is moved to the jquery plugins, to be able to use these configurations in other extensions which don't have a #wpTextbox1. Please review this to check if this is the right way to do it!
2011-02-24 01:45:55 +00:00
/**
* Configuration of Toolbar module for wikiEditor
*/
Remove obsolete aliases from closures Bug: T208951 Change-Id: I0b2993912de221e810414e46708c19be163922f6
2018-11-12 22:28:40 +00:00
( function () {
A bit of a reorganisation that fixes bug 27164. Basically the extensive configuration in the ext.wikieditor.* functions is moved to the jquery plugins, to be able to use these configurations in other extensions which don't have a #wpTextbox1. Please review this to check if this is the right way to do it!
2011-02-24 01:45:55 +00:00
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
var configData = require( './data.json' ),
fileNamespace = mw.config.get( 'wgFormattedNamespaces' )[ 6 ],
specialCharacterGroups = require( 'mediawiki.language.specialCharacters' ),
toolbarConfig;
build: Test JS code with jshint and jscs via npm Change-Id: I039bc4c17fbba3c74a5050066b20af05434ca482
2015-11-15 14:30:18 +00:00
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
/**
* Replace link targets from example messages with hash
* after a message has been parsed.
*
* @param {jQuery} $message an mw.message().parseDom() object
* @return {string} HTML string
*/
function delink( $message ) {
// dummy div to append the message to
var $div = $( '<div>' );
$div.append( $message );
$div.find( 'a' ).attr( 'href', '#' );
return $div.html();
}
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
toolbarConfig = {
toolbar: {
// Main section
main: {
type: 'toolbar',
groups: {
format: {
tools: {
bold: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-bold' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'button',
oouiIcon: 'bold',
action: {
type: 'encapsulate',
options: {
pre: "'''",
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-bold-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: "'''"
build: Test JS code with jshint and jscs via npm Change-Id: I039bc4c17fbba3c74a5050066b20af05434ca482
2015-11-15 14:30:18 +00:00
}
A bit of a reorganisation that fixes bug 27164. Basically the extensive configuration in the ext.wikieditor.* functions is moved to the jquery plugins, to be able to use these configurations in other extensions which don't have a #wpTextbox1. Please review this to check if this is the right way to do it!
2011-02-24 01:45:55 +00:00
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
italic: {
section: 'main',
group: 'format',
id: 'italic',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-italic' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'button',
oouiIcon: 'italic',
action: {
type: 'encapsulate',
options: {
pre: "''",
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-italic-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: "''"
A bit of a reorganisation that fixes bug 27164. Basically the extensive configuration in the ext.wikieditor.* functions is moved to the jquery plugins, to be able to use these configurations in other extensions which don't have a #wpTextbox1. Please review this to check if this is the right way to do it!
2011-02-24 01:45:55 +00:00
}
}
}
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
insert: {
tools: {
signature: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-signature' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'button',
oouiIcon: 'signature',
action: {
type: 'encapsulate',
options: {
pre: configData.signature
build: Test JS code with jshint and jscs via npm Change-Id: I039bc4c17fbba3c74a5050066b20af05434ca482
2015-11-15 14:30:18 +00:00
}
A bit of a reorganisation that fixes bug 27164. Basically the extensive configuration in the ext.wikieditor.* functions is moved to the jquery plugins, to be able to use these configurations in other extensions which don't have a #wpTextbox1. Please review this to check if this is the right way to do it!
2011-02-24 01:45:55 +00:00
}
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
}
}
}
}
},
Add new 'secondary' toolbar section Add a new top-level section to the right side of the toolbar, containing a single (empty) 'default' group. Bug: T296447 Change-Id: If88789f20420f02c729122392e16509bbc5ae7d0
2021-12-01 03:07:39 +00:00
// Secondary section of the top toolbar (at right side when LTR).
secondary: {
type: 'toolbar',
groups: {
default: {
tools: {}
}
}
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
// Format section
advanced: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-section-advanced' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'toolbar',
groups: {
heading: {
tools: {
heading: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-heading' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'select',
list: {
'heading-2': {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-heading-2' ),
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
action: {
type: 'encapsulate',
options: {
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
pre: '== ',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-heading-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: ' ==',
regex: /^(\s*)(={1,6})(.*?)\2(\s*)$/,
regexReplace: '$1==$3==$4',
ownline: true
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
}
build: Test JS code with jshint and jscs via npm Change-Id: I039bc4c17fbba3c74a5050066b20af05434ca482
2015-11-15 14:30:18 +00:00
}
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
'heading-3': {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-heading-3' ),
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
action: {
type: 'encapsulate',
options: {
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
pre: '=== ',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-heading-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: ' ===',
regex: /^(\s*)(={1,6})(.*?)\2(\s*)$/,
regexReplace: '$1===$3===$4',
ownline: true
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
}
build: Test JS code with jshint and jscs via npm Change-Id: I039bc4c17fbba3c74a5050066b20af05434ca482
2015-11-15 14:30:18 +00:00
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
'heading-4': {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-heading-4' ),
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
action: {
type: 'encapsulate',
options: {
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
pre: '==== ',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-heading-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: ' ====',
regex: /^(\s*)(={1,6})(.*?)\2(\s*)$/,
regexReplace: '$1====$3====$4',
ownline: true
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
}
build: Test JS code with jshint and jscs via npm Change-Id: I039bc4c17fbba3c74a5050066b20af05434ca482
2015-11-15 14:30:18 +00:00
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
'heading-5': {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-heading-5' ),
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
action: {
type: 'encapsulate',
options: {
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
pre: '===== ',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-heading-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: ' =====',
regex: /^(\s*)(={1,6})(.*?)\2(\s*)$/,
regexReplace: '$1=====$3=====$4',
ownline: true
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
}
build: Test JS code with jshint and jscs via npm Change-Id: I039bc4c17fbba3c74a5050066b20af05434ca482
2015-11-15 14:30:18 +00:00
}
}
A bit of a reorganisation that fixes bug 27164. Basically the extensive configuration in the ext.wikieditor.* functions is moved to the jquery plugins, to be able to use these configurations in other extensions which don't have a #wpTextbox1. Please review this to check if this is the right way to do it!
2011-02-24 01:45:55 +00:00
}
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
}
}
},
format: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-group-format' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
tools: {
ulist: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-ulist' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'button',
oouiIcon: 'listBullet',
action: {
type: 'encapsulate',
options: {
pre: '* ',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-ulist-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: '',
ownline: true,
splitlines: true
}
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
olist: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-olist' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'button',
oouiIcon: 'listNumbered',
action: {
type: 'encapsulate',
options: {
pre: '# ',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-olist-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: '',
ownline: true,
splitlines: true
build: Test JS code with jshint and jscs via npm Change-Id: I039bc4c17fbba3c74a5050066b20af05434ca482
2015-11-15 14:30:18 +00:00
}
A bit of a reorganisation that fixes bug 27164. Basically the extensive configuration in the ext.wikieditor.* functions is moved to the jquery plugins, to be able to use these configurations in other extensions which don't have a #wpTextbox1. Please review this to check if this is the right way to do it!
2011-02-24 01:45:55 +00:00
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
nowiki: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-nowiki' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'button',
oouiIcon: 'noWikiText',
action: {
type: 'encapsulate',
options: {
pre: '<nowiki>',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-nowiki-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: '</nowiki>'
}
}
},
newline: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-newline' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'button',
oouiIcon: 'newline',
action: {
type: 'encapsulate',
options: {
pre: '<br>\n'
build: Test JS code with jshint and jscs via npm Change-Id: I039bc4c17fbba3c74a5050066b20af05434ca482
2015-11-15 14:30:18 +00:00
}
A bit of a reorganisation that fixes bug 27164. Basically the extensive configuration in the ext.wikieditor.* functions is moved to the jquery plugins, to be able to use these configurations in other extensions which don't have a #wpTextbox1. Please review this to check if this is the right way to do it!
2011-02-24 01:45:55 +00:00
}
}
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
size: {
tools: {
big: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-big' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'button',
oouiIcon: 'bigger',
action: {
type: 'encapsulate',
options: {
pre: '<big>',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-big-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: '</big>'
}
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
small: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-small' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'button',
oouiIcon: 'smaller',
action: {
type: 'encapsulate',
options: {
pre: '<small>',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-small-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: '</small>'
}
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
superscript: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-superscript' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'button',
oouiIcon: 'superscript',
action: {
type: 'encapsulate',
options: {
pre: '<sup>',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-superscript-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: '</sup>'
}
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
subscript: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-subscript' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'button',
oouiIcon: 'subscript',
action: {
type: 'encapsulate',
options: {
pre: '<sub>',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-subscript-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: '</sub>'
}
}
}
}
},
insert: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-group-insert' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
tools: {
gallery: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-gallery' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'button',
oouiIcon: 'imageGallery',
action: {
type: 'encapsulate',
options: {
pre: '<gallery>\n',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-gallery-example', fileNamespace ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: '\n</gallery>',
ownline: true
}
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
redirect: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-tool-redirect' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'button',
oouiIcon: 'articleRedirect',
action: {
type: 'encapsulate',
options: {
Use only the first item of various magic words Bug: T273231 Change-Id: I1f88eb3e043cb95f939a7e38ddaa3e39a49523fa Follows-Up: Ib03932d3d85a5540bea325f2717da3365756a90e
2021-01-29 02:32:13 +00:00
pre: configData.magicWords.redirect[ 0 ] + ' [[',
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
peri: mw.msg( 'wikieditor-toolbar-tool-redirect-example' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
post: ']]',
ownline: true
}
}
}
}
}
}
},
characters: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-section-characters' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'booklet',
deferLoad: true,
pages: {
latin: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-latin' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'characters',
characters: specialCharacterGroups.latin
},
latinextended: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-latinextended' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'characters',
characters: specialCharacterGroups.latinextended
},
ipa: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-ipa' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'characters',
characters: specialCharacterGroups.ipa
},
symbols: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-symbols' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'characters',
characters: specialCharacterGroups.symbols
},
greek: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-greek' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'characters',
language: 'el',
characters: specialCharacterGroups.greek
},
greekextended: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-greekextended' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'characters',
characters: specialCharacterGroups.greekextended
},
cyrillic: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-cyrillic' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'characters',
characters: specialCharacterGroups.cyrillic
},
// The core 28-letter alphabet, special letters for the Arabic language,
// vowels, punctuation, digits.
// Names of letters are written as in the Unicode charts.
arabic: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-arabic' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'characters',
language: 'ar',
direction: 'rtl',
characters: specialCharacterGroups.arabic
},
// Characters for languages other than Arabic.
arabicextended: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-arabicextended' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'characters',
language: 'ar',
direction: 'rtl',
characters: specialCharacterGroups.arabicextended
},
hebrew: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-hebrew' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'characters',
direction: 'rtl',
characters: specialCharacterGroups.hebrew
},
bangla: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-bangla' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
language: 'bn',
layout: 'characters',
characters: specialCharacterGroups.bangla
},
tamil: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-tamil' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
language: 'ta',
layout: 'characters',
characters: specialCharacterGroups.tamil
},
telugu: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-telugu' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
language: 'te',
layout: 'characters',
characters: specialCharacterGroups.telugu
},
sinhala: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-sinhala' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
language: 'si',
layout: 'characters',
characters: specialCharacterGroups.sinhala
},
devanagari: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-devanagari' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'characters',
characters: specialCharacterGroups.devanagari
},
gujarati: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-gujarati' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
language: 'gu',
layout: 'characters',
characters: specialCharacterGroups.gujarati
},
thai: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-thai' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
language: 'th',
layout: 'characters',
characters: specialCharacterGroups.thai
},
lao: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-lao' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
language: 'lo',
layout: 'characters',
characters: specialCharacterGroups.lao
},
khmer: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-khmer' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
language: 'km',
layout: 'characters',
characters: specialCharacterGroups.khmer
},
canadianaboriginal: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-canadianaboriginal' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
language: 'cr',
layout: 'characters',
characters: specialCharacterGroups.canadianaboriginal
Add runes to special characters Depends-On: I6c736563068a83f56990729ac6ef3be6c8a0f621 Change-Id: Ia5c43f5973ab512cc5f9e674063d47833eb9a6fc
2021-08-17 16:18:47 +00:00
},
runes: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'special-characters-group-runes' ),
Add runes to special characters Depends-On: I6c736563068a83f56990729ac6ef3be6c8a0f621 Change-Id: Ia5c43f5973ab512cc5f9e674063d47833eb9a6fc
2021-08-17 16:18:47 +00:00
layout: 'characters',
characters: specialCharacterGroups.runes
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
}
}
},
help: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-section-help' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
type: 'booklet',
deferLoad: true,
pages: {
format: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-help-page-format' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'table',
headings: [
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
{ html: mw.message( 'wikieditor-toolbar-help-heading-description' ).parse() },
{ html: mw.message( 'wikieditor-toolbar-help-heading-syntax' ).parse() },
{ html: mw.message( 'wikieditor-toolbar-help-heading-result' ).parse() }
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
],
rows: [
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-italic-description' ).parse()
},
syntax: {
html: "''" + mw.message( 'wikieditor-toolbar-help-content-italic-example' ).escaped() + "''"
},
result: {
html: '<em>' + mw.message( 'wikieditor-toolbar-help-content-italic-example' ).parse() + '</em>'
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-bold-description' ).parse()
},
syntax: {
html: "'''" + mw.message( 'wikieditor-toolbar-help-content-bold-example' ).escaped() + "'''"
},
result: {
html: '<strong>' + mw.message( 'wikieditor-toolbar-help-content-bold-example' ).parse() + '</strong>'
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-bolditalic-description' ).parse()
},
syntax: {
html: "'''''" + mw.message( 'wikieditor-toolbar-help-content-bolditalic-example' ).escaped() + "'''''"
},
result: {
html: '<strong><em>' + mw.message( 'wikieditor-toolbar-help-content-bolditalic-example' ).parse() + '</em></strong>'
}
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
}
]
},
link: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-help-page-link' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'table',
headings: [
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
{ html: mw.message( 'wikieditor-toolbar-help-heading-description' ).parse() },
{ html: mw.message( 'wikieditor-toolbar-help-heading-syntax' ).parse() },
{ html: mw.message( 'wikieditor-toolbar-help-heading-result' ).parse() }
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
],
rows: [
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-ilink-description' ).parse()
},
syntax: {
html: mw.message( 'wikieditor-toolbar-help-content-ilink-example' ).escaped()
},
result: {
html: '<span class="pre-wrap">' + delink( mw.message( 'wikieditor-toolbar-help-content-ilink-example' ).parseDom() ) + '</span>'
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-xlink-description' ).parse()
},
syntax: {
html: mw.message(
'wikieditor-toolbar-help-content-xlink-example1',
mw.msg( 'wikieditor-toolbar-help-content-xlink-example-url' ),
mw.msg( 'wikieditor-toolbar-help-content-xlink-example-label' )
).escaped()
},
result: {
html: '<span class="mw-parser-output pre-wrap">' +
delink( mw.message(
'wikieditor-toolbar-help-content-xlink-example2',
mw.msg( 'wikieditor-toolbar-help-content-xlink-example-url' ),
mw.msg( 'wikieditor-toolbar-help-content-xlink-example-label' ),
mw.language.convertNumber( 1 )
).parseDom() ) +
'</span>'
}
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
}
]
},
heading: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-help-page-heading' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'table',
headings: [
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
{ html: mw.message( 'wikieditor-toolbar-help-heading-description' ).parse() },
{ html: mw.message( 'wikieditor-toolbar-help-heading-syntax' ).parse() },
{ html: mw.message( 'wikieditor-toolbar-help-heading-result' ).parse() }
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
],
rows: [
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-heading2-description' ).parse()
},
syntax: {
html: '== ' + mw.message( 'wikieditor-toolbar-help-content-heading2-example' ).escaped() + ' =='
},
result: {
html: '<h2>' + mw.message( 'wikieditor-toolbar-help-content-heading2-example' ).parse() + '</h2>'
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-heading3-description' ).parse()
},
syntax: {
html: '=== ' + mw.message( 'wikieditor-toolbar-help-content-heading3-example' ).escaped() + ' ==='
},
result: {
html: '<h3>' + mw.message( 'wikieditor-toolbar-help-content-heading3-example' ).parse() + '</h3>'
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-heading4-description' ).parse()
},
syntax: {
html: '==== ' + mw.message( 'wikieditor-toolbar-help-content-heading4-example' ).escaped() + ' ===='
},
result: {
html: '<h4>' + mw.message( 'wikieditor-toolbar-help-content-heading4-example' ).parse() + '</h4>'
}
Add Canadian Aboriginal characters to the special characters toolbar Bug: T108626 Change-Id: I613e89a520f78bcf7b6640c3ed5b9f3cce351912 Depends-On: Ia337d42c6ef7f9645f1dd843ef0e7553857f6aa3
2017-04-05 08:20:05 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-heading5-description' ).parse()
},
syntax: {
html: '===== ' + mw.message( 'wikieditor-toolbar-help-content-heading5-example' ).escaped() + ' ====='
},
result: {
html: '<h5>' + mw.message( 'wikieditor-toolbar-help-content-heading5-example' ).parse() + '</h5>'
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
}
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
]
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
list: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-help-page-list' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'table',
headings: [
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
{ html: mw.message( 'wikieditor-toolbar-help-heading-description' ).parse() },
{ html: mw.message( 'wikieditor-toolbar-help-heading-syntax' ).parse() },
{ html: mw.message( 'wikieditor-toolbar-help-heading-result' ).parse() }
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
],
rows: [
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-ulist-description' ).parse()
},
syntax: {
html: '* ' + mw.message( 'wikieditor-toolbar-help-content-ulist-example' ).escaped() + '<br />' +
'* ' + mw.message( 'wikieditor-toolbar-help-content-ulist-example' ).escaped()
},
result: {
html: '<ul>' +
'<li>' + mw.message( 'wikieditor-toolbar-help-content-ulist-example' ).parse() + '</li>' +
'<li>' + mw.message( 'wikieditor-toolbar-help-content-ulist-example' ).parse() + '</li>' +
'</ul>'
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-olist-description' ).parse()
},
syntax: {
html: '# ' + mw.message( 'wikieditor-toolbar-help-content-olist-example' ).escaped() + '<br />' +
'# ' + mw.message( 'wikieditor-toolbar-help-content-olist-example' ).escaped()
},
result: {
html: '<ol>' +
'<li>' + mw.message( 'wikieditor-toolbar-help-content-olist-example' ).parse() + '</li>' +
'<li>' + mw.message( 'wikieditor-toolbar-help-content-olist-example' ).parse() + '</li>' +
'</ol>'
}
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
}
]
},
file: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-help-page-file' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'table',
headings: [
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
{ html: mw.message( 'wikieditor-toolbar-help-heading-description' ).parse() },
{ html: mw.message( 'wikieditor-toolbar-help-heading-syntax' ).parse() },
{ html: mw.message( 'wikieditor-toolbar-help-heading-result' ).parse() }
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
],
rows: [
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-file-description' ).parse()
},
syntax: {
html: mw.message(
'wikieditor-toolbar-help-content-file-syntax',
fileNamespace,
configData.magicWords.img_thumbnail[ 0 ],
mw.msg( 'wikieditor-toolbar-help-content-file-caption' )
).escaped()
},
result: {
html: '<div class="thumbinner" style="width: 102px;">' +
'<a class="image">' +
'<img alt="" src="' + $.wikiEditor.imgPath + 'toolbar/example-image.png" width="100" height="50" class="thumbimage"/>' +
'</a>' +
'<div class="thumbcaption"><div class="magnify">' +
'<a title="' + mw.message( 'thumbnail-more' ).escaped() + '" class="internal"></a>' +
'</div>' + mw.message( 'wikieditor-toolbar-help-content-file-caption' ).escaped() + '</div>' +
'</div>'
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
}
}
]
},
discussion: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
label: mw.msg( 'wikieditor-toolbar-help-page-discussion' ),
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
layout: 'table',
headings: [
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
{ html: mw.message( 'wikieditor-toolbar-help-heading-description' ).parse() },
{ html: mw.message( 'wikieditor-toolbar-help-heading-syntax' ).parse() },
{ html: mw.message( 'wikieditor-toolbar-help-heading-result' ).parse() }
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
],
rows: [
{
description: {
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
html: mw.message( 'wikieditor-toolbar-help-content-signaturetimestamp-description' ).parse()
},
syntax: {
html: mw.message( 'wikieditor-toolbar-help-content-signaturetimestamp-syntax' ).escaped()
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
},
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
result: {
html: delink( mw.message(
'wikieditor-toolbar-help-content-signaturetimestamp-example',
mw.config.get( 'wgFormattedNamespaces' )[ 2 ],
mw.config.get( 'wgFormattedNamespaces' )[ 3 ],
mw.config.get( 'wgUserName' ) || mw.msg( 'wikieditor-toolbar-help-content-signature-username' )
).parseDom() )
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-signature-description' ).parse()
},
syntax: {
html: mw.message( 'wikieditor-toolbar-help-content-signature-syntax' ).escaped()
},
result: {
html: delink( mw.message(
'wikieditor-toolbar-help-content-signature-example',
mw.config.get( 'wgFormattedNamespaces' )[ 2 ],
mw.config.get( 'wgFormattedNamespaces' )[ 3 ],
mw.config.get( 'wgUserName' ) || mw.msg( 'wikieditor-toolbar-help-content-signature-username' )
).parseDom() )
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
},
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
{
Stop using autoMsg and use mw.messages directly instead WikiEditor has a clever functionality where you can enter a message key directly by using [key]Msg syntax in the object definition. While that may have been a clever approach, it led to tons of messages in this extension having to be marked as RawHtmlMessages because they could potentially be parsed as HTML. Thus I am replacing all of these instances with using mw.message explicitly instead, with the necessary method attached. The autoMsg (and its cloned autoSafeMsg) functions have had FIXME comments attached since 2018 saying that these methods are unnecessarily complex and should be replaced with using mw.messages directly. This solves a lot of problems for translators in Translatewiki, and hopefully makes the code more straightforward and easier to understand for those reading it down the line. I would like to remove the autoMsg and autoSafeMsg functions altogether, but their functionality is still in use in a few extensions (and potentially on-wiki code), so we would have to clean up that first. Bug: T154891 Bug: T294760 Change-Id: I2835341867df85552579ea6927cd39a6f889fa6b
2023-06-29 22:29:20 +00:00
description: {
html: mw.message( 'wikieditor-toolbar-help-content-indent-description' ).parse()
},
syntax: {
html: mw.message( 'wikieditor-toolbar-help-content-indent1' ).escaped() +
'<br />:' +
mw.message( 'wikieditor-toolbar-help-content-indent2' ).escaped() +
'<br />::' +
mw.message( 'wikieditor-toolbar-help-content-indent3' ).escaped()
},
result: {
html: mw.message( 'wikieditor-toolbar-help-content-indent1' ).parse() +
'<dl><dd>' +
mw.message( 'wikieditor-toolbar-help-content-indent2' ).parse() +
'<dl><dd>' +
mw.message( 'wikieditor-toolbar-help-content-indent3' ).parse() +
'</dd></dl></dd></dl>'
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
}
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
]
build: Test JS code with jshint and jscs via npm Change-Id: I039bc4c17fbba3c74a5050066b20af05434ca482
2015-11-15 14:30:18 +00:00
}
A bit of a reorganisation that fixes bug 27164. Basically the extensive configuration in the ext.wikieditor.* functions is moved to the jquery plugins, to be able to use these configurations in other extensions which don't have a #wpTextbox1. Please review this to check if this is the right way to do it!
2011-02-24 01:45:55 +00:00
}
}
}
Replace jshint/jscs with eslint/stylelint Change-Id: Ife5e782bd5513e0496e384655b9b203de5c841a5
2016-11-20 17:13:39 +00:00
};
A bit of a reorganisation that fixes bug 27164. Basically the extensive configuration in the ext.wikieditor.* functions is moved to the jquery plugins, to be able to use these configurations in other extensions which don't have a #wpTextbox1. Please review this to check if this is the right way to do it!
2011-02-24 01:45:55 +00:00
Convert ext.wikiEditor module to packageFiles This allows us to bundle the wgWikiEditorMagicWords and mw.msg.wikiEditor(?!) config vars that were previously exported globally in the startup module. This code is old and crufty, so this is a somewhat minimal conversion: * Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js, and for jquery.wikiEditor.{dialogs,toolbar}.js * Don't attempt to convert jquery.wikiEditor.js to something require-based, instead just run it and let it set the $.wikiEditor and $.fn.wikiEditor globals * Consolidate ext.wikiEditor.{dialogs,toolbars}.js into ext.wikiEditor.js Bug: T222828 Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
2019-07-20 08:09:04 +00:00
// Remove the signature button on non-signature namespaces
if ( !mw.Title.wantSignaturesNamespace( mw.config.get( 'wgNamespaceNumber' ) ) ) {
delete toolbarConfig.toolbar.main.groups.insert.tools.signature;
}
module.exports = toolbarConfig;
Remove obsolete aliases from closures Bug: T208951 Change-Id: I0b2993912de221e810414e46708c19be163922f6
2018-11-12 22:28:40 +00:00
}() );
Reference in a new issue Copy permalink