MediaWiki talk:Gadget-charinsert-core.js

Current sets
These are the current as of Apr. 17, 2015 additional sets included with the Character Insert gadget. Please refer to it when making suggestions or requests to add or remove characters from the default set(s).

+ 

Experts needed
As of this post, most (if not all) of the add-on character sets found in the old tool have been imported into the script for the new Character Insert gadget. Further "tweaking" is still needed however, as I am limited both by my lack of familiarity as well as my limited viewibility for some of the character sets added-in.

The hope is those familar with a particular set or sets will chime here and help adding the finishing layout & presentation questions as well as insure each set is indeed complete and/or valid moving forward. The most critical of areas needing attention are the Hebrew and IPA sets as the prior incarnations from the old tool used inline css attributes & stylings to accomplish rendering (or something else?) that I wouldn't dare port over to the new script without some 'beyond-my-pay-grade' re-writing of the code getting in the way. -- George Orwell III (talk) 03:22, 25 December 2013 (UTC)

Configuration of Character Insert gadget
// copied from mw:User:Alex Smotrov/edittools.js, modified for use on the English Wikipedia. // enableForAllFields feature from commons:MediaWiki:Edittools.js // combined and modified by w:User:Ilmari Karonen Configuration (to be set from Special:MyPage/common.js): .
 * 1) window.charinsertCustom – Object.
 * Merged into the default charinsert list. For example, adding this line and setting it to { Symbols: '‽' } will add the interrobang to the end of the Symbols section.
 * 1) window.editToolsRecall – Boolean. .js induced default = false
 * Add line and set to true for the creation of a recall-last switch  left of the drop down menu.
 * 1) window.charinsertDontMove – Boolean. .js induced default = false
 * Add line and set to true to leave the box in its default position, rather than moving it above the edit summary.
 * 1) window.charinsertMoveTop – Boolean. .js induced default = false
 * Add line and Set to true to move the box above the enhanced editing toolbar (WikiEditor).
 * 1) window.updateEditTools – Function.
 * Only add if needed. A call after updating window.charinsertCustom to regenerate the EditTools window

The last one (#5) seems to be enabled (already "on" or "is in effect") via the presence of the 'user' dependency in the Gadget's definitions and is no longer a requirement. -- George Orwell III (talk) 12:36, 24 December 2013 (UTC)

In general, you should add an option line w/setting to your Special:MyPage/common.js file ONLY if the desired functionality is opposite of the .js induced default state. Otherwise the simple presence of a line regardless of what it is set to, be it true or false by induced default or not, can interfere with the desired functionality by invalidating the option itself. -- George Orwell III (talk) 03:33, 21 October 2014 (UTC)

Anomalies observed when CharacterInsert is enabled
The primary issue with the old character set tool (EditTool) was two-fold
 * 1) The designed function of MediaWiki:Edittools was specifically for non-java enabled users and their browser sessions to "fail gracefully" and still have the basics (Insert [core templates] & Insert Wiki Mark-ups [most-common templates]) available to editors, who, - for whatever reason - found themselves contributing to wiki projects under such conditions over and over again. From what I've been able to gather, the additional character sets where added by individuals rather than by actual developers and, over time, came to be giggered into a pop-down selectable menu of both the basic and additional character sets along the way.  Those "improvements", however, made the feature less about being just a "back-up" that 'fails instead of crashes' your browser session whenever possible and more about exploiting the opening it provided for all sorts of customizations, add-ons and similar tripe by various well-intentioned contributors (ultimately achieving the opposite in the end by increasing the reliance on scripting, load order & resources and the like be enabled & working just to "maintain" the appearance of normallacy or the notion of a properly developed baseline).
 * 2) Second, eons have passed since someone actually furthered the development of the damn thing!! Sure, its been poked and proded by just about everyone to one degree or another over the years (including me) - but that hardly qualifies as "development". The fact its been fairly reliable all this time is not due to the genius of its fundamental coding or anything as grandeous as that - its merely the symptom of its long-ago abandonment, taken for granted without a second thought. Given all the advances in the wiki-code since its been primarily relegated to preserving dead, near dead or foreign languages than 'blue screens of death', its no wonder its mere presence is getting in the way of the latest and greatest advances coming down the pipe [thus, its been deprecated].

One of things (depending on your setup) that you might observe with CharInsert enabled is a lot that pop-up, floated edit preview stuff you read or heard about in passing actually works now. This is because the old tools setup inserted itself pretty much outside of the formal textarea form and way at the end of "the page" (resource &/or order sensitive), usurping or disabling other aspects enabled by other routines or the wiki code itself in the process (such as floating edit summaries appearing in different locations depending on if any changes were made between edit previews for example). Long story short, if you've made sure that you've only selected one gadget (CharInsert) or the other [EditTools] in your User preferences, and some new behavior or bug has started happening to you, please look through the remainder of your user preference settings for previous conflicts now cleared or unhidden by enabling charInsert. More later - post em' as you discover them. -- George Orwell III (talk) 13:30, 24 December 2013 (UTC)

Additional tweaks to improve layout
One of the things that immediately leaped out at me was the general "flaw" in the layout of the edit  field & the   check-bozes once the old EditTool was no longer fudging up what is suppose to be a hard-coded Form (html fieldset). The improper vs. proper way to implement Forms can be observed when editing any [//en.wikisource.org/w/index.php?title=Template:Support&action=edit template] hosted on WS and comparing the familiar   input field's layout with the much more recent   (using the template being edited) field layout located in the area just below the save, preview buttons.

The following adjustments have been applied to the sitewide .css tweaks file to make the Label->Field->Button form layout "more similar between" the old and the new approaches (even though the button(s) do not follow the field in Summary's case). The check-boxes are then padded left to more align with the Summary: input field instead of the Summary label. If the majority of folks do not like the way the "new" layout looks (or plain-old breaks something), report back and we'll go about making it a user applied tweak rather than a site wide setting. -- George Orwell III (talk) 14:50, 24 December 2013 (UTC)

Core
The following should reside at MediaWiki:Edittools instead of anything 'coded-for-more-not-less-javascripting' that might be there, past present or future. Removing the SyntaxHighlight wrapper should cause the content wrapped in the single DIV block to "disappear" upon a (re)preview afterwards. I only emphasised "should" because expected behavior vs. actual behavior really depends upon whether or not all the baseline components needed are present and proper (previously, a rare state of affairs when it came to this feature). In other words, only those who properly disable the ability to run JavaScript manually should ever see this variant of the body of character sets (if js is installed but crippled for whatever reason(s), your guess is as good as anybody's re: what renders & what does not) -- George Orwell III (talk) 08:20, 25 December 2013 (UTC)

Activating CharInsert break the edit page
If I activate the gadget, the edit view would not display properly. Bennylin (talk) 09:19, 6 August 2014 (UTC)
 * Please try again. I've added some additional settings in your common.js file that might help. Report back; thanks. -- George Orwell III (talk) 23:32, 6 August 2014 (UTC)

Proposed Bengali character list
অ আ ই ঈ উ ঊ ঋ ঌ এ ঐ ও ঔ া ি ী ু ূ ৃ ে ৈ ো ৌ ্য ৗ ক খ গ ঘ ঙ চ ছ জ ঝ ঞ ট ঠ ড ঢ ণ ত থ দ ধ ন প ফ ব ভ ম য র ল শ ষ স হ ড় ঢ় য় ৎ ং ঃ ঁ ্ ৷ ॥ ১ ২ ৩ ৪ ৫ ৬ ৭ ৮ ৯ ০ ঽ ় ৰ ৱ ৲ ৻ ৳ ৴ ৵ ৶ ৷ ৸ ৹ ৺ ৠ ৡ ৄ ৢ ৣ

Also to add: zero-width non-joiner (U+200C). Now can be added with code  but better to have it in the list. This is required for writing মিস্&zwnj;মি as in bn:মিস্‌মিদের কবচ. Without the non-joiner, it would be মিস্মি. Some deprecated characters are also included in the list which are required for proofreading old works like The History of the Bengali Language. Hrishikes (talk) 09:53, 17 April 2015 (UTC)
 * Thanks Saikat, for adding ্য. Hrishikes (talk) 09:08, 19 April 2015 (UTC)
 * Thanks Nahid, for adding the ganda mark. Hrishikes (talk) 12:51, 19 April 2015 (UTC)

For WikiEditor
Action proposed at 1, draft made at 2 and action taken vide 3, 4, 5, 6 for the following charset:

"bangla":["ঀ","অ","আ","ই","ঈ","উ","ঊ","ঋ","ঌ","এ","ঐ","ও","ঔ","া","ি","ী","ু","ূ","ৃ","ে","ৈ","ো","ৌ","্য","্র","ক","খ","গ","ঘ","ঙ","চ","ছ","জ","ঝ","ঞ","ট","ঠ","ড","ঢ","ণ","ত","থ","দ","ধ","ন","প","ফ","ব","ভ","ম","য","র","ল","শ","ষ","স","হ","ড়","ঢ়","য়","ৎ","ং","ঃ","ঁ","্","৷","॥","১","২","৩","৪","৫","৬","৭","৮","৯","০","ঽ","ৗ","়","ৰ","ৱ","৲","৻","৳","৴","৵","৶","৷","৸","৹","৺","ৠ","ৡ","ৄ","ৢ","ৣ","‘","’","“","”",["zws","​"],["zwnj","‌"],["zwj","‍"]],

Hrishikes (talk) 02:11, 23 April 2015 (UTC)

Change Ğ/ğ to Ǧ/ǧ
Under Other_diacritics -> caron, the letter g has a breve mark (ğ/Ğ) instead of a caron sign (Ǧ/ǧ).--Underlying lk (talk) 15:05, 27 July 2018 (UTC)
 * Done.— Mpaa (talk) 15:55, 27 July 2018 (UTC)

Removed &lt;code>
I have removed &lt;code> from the selection list as the preference is to use &lt;syntaxhighlight> to display coding effects (see mw:Extension:SyntaxHighlight.) To note that one can also use &lt;kbd> if just looking for the typographic monospace effect. — billinghurst  sDrewth  06:12, 12 May 2023 (UTC)