User talk:Remember the dot/Archive/2014

ICO (file format)
Your edit seemed to violate WP:NPOV to me. I have removed the MIME type altogether from the infobox and let the reader judge. ï¿½ (talk) 08:58, 28 February 2014 (UTC)

Featured article removal candidate for Opera (web browser)
I have nominated Opera (web browser) for a featured article review here. Please join the discussion on whether this article meets featured article criteria. Articles are typically reviewed for two weeks. If substantial concerns are not addressed during the review period, the article will be moved to the Featured Article Removal Candidates list for a further period, where editors may declare "Keep" or "Delist" the article's featured status. The instructions for the review process are here. Huang (talk in public in private &#124; contribs) 11:10, 11 March 2014 (UTC)

Support for Firefox ESR versions?
You recently dropped support for Firefox other than the bleeding-edge latest. However some users (myself included) prefer stability, and don't necessarily want to run the latest version of the browser. Would you consider including support for the Extended Support Release version of Firefox, currently 24.5.0? Thanks, Mitch Ames (talk) 02:15, 11 May 2014 (UTC)


 * I'm not going to penalize highlighting performance for everyone else in order to support old Firefox bugs. If you update your browser you'll see the performance improvement immediately, but if you don't want to update for another 3 months, you can turn off the gadget and import the old version into your personal common.js until then:


 * I know that sounds really harsh, but I honestly believe it's for the best. You can take comfort knowing that with the Firefox and Chrome bugs resolved (or so I hope), the syntax highlighter's development has finally reached a point of stability. And feel free to message me with any other concerns. —Remember the dot (talk) 04:01, 11 May 2014 (UTC)


 * I did update to Firefox 29, and the specific problem that I was having (with the syntax highlighter tool and the earlier Firefox) disappeared. However, Mozilla continues to add more bloat to their browser, so I'm looking at alternatives. Pale Moon looks to be a good replacement - but apparently has the same bug as earlier Firefox, because the syntax highlighter doesn't work reliably! I respect your right to not support earlier versions of Firefox or (the current version of) Pale Moon, but ask for your assistance so that I can report the problem accurately to Pale Moon developers, in the hope that they will fix the bug in their browser.
 * The specific problem, was that the syntax highlighting did not line up with the text in some cases. An example is shown at http://tinypic.com/r/2ag93ih/8 - the image on the left is Pale Moon 24.6.2, the image on the right is Firefox 30. I've added the red rectangle to show one instance of the problem.
 * I presume from what you removed from the script (which caused the problem to appear in my earlier Firefox) that the bug https://bugzilla.mozilla.org/show_bug.cgi?id=157846 has not been fixed in the current Pale Moon. Is this likely to be the case? Thanks Mitch Ames (talk) 08:43, 26 July 2014 (UTC)


 * As far as I can tell, Pale Moon is based on Firefox 24. This means that it has almost all the same bugs that Firefox 24 had. When Pale Moon is updated to a base of Firefox 29 or newer, the current version of the syntax highlighter will work in it. —Remember the dot (talk) 17:24, 26 July 2014 (UTC)

A barnstar for you!

 * You're very welcome! Happy editing! —Remember the dot (talk) 05:58, 24 May 2014 (UTC)

Syntax highlighter not working
Hello, Since about 0700 UTC today, I've had no colors on my editing screen in English Wikipedia. I've become quite dependent on this script and miss it greatly. Syntax highlighter is still selected on my preferences panel. I am using a PC with a cable modem and FireFox 31.0. It seems to work with Chrome 36.0.1985.143 m, but that's not my preferred browser. It doesn't work on Internet Explorer 11.0.9600.17239 and that's no one's preferred browser. My User Agent is: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 and I use the default Vector skin.

If this is helpful, it seems that the vertical spacing of lines is greater than usual. When I go to preferences for MediaWiki and enable Syntax highlighter, it works in MediaWiki, but still not in English Wikipedia. When I go to preferences for Wiktionary and enable Syntax highlighter, it does not work there. I had already posted this on MediaWiki before I saw that this is where you want to be informed. Thank you. SchreiberBike talk 19:33, 21 August 2014 (UTC)

TemplateScript
Hello Remember the dot. I updated your common.js page to the latest version of TemplateScript. This is just to enable automatic updates, so you shouldn't see much difference. If you notice any problems or have questions, let me know! :) — Pathoschild 02:21, 24 August 2014 (UTC)

Syntax highlighter
(Sorry for my bad english)

Hi !

I started some discussions on french wikipedia to opt-out the Syntax highlighter. People are enthusiastic but some points were raised :
 * Is it possible to make the list of tags recognized configurable ? Or at least add.
 * Is it possible to add a button somewhere to turn off highlighting ?
 * Is it possible to allow the ability to resize the editing area ?
 * Is it possible to have an automatic deactivation for mobile and unsupported browsers ?

Can you add the error message in french : "La coloration syntaxique a été désactivée sur cette page en raison d'un temps de chargement trop important ($2ms). Le temps maximum autorisé est $1ms."

For more you can read (in french) :
 * Discussion Projet:Aide et accueil#Coloration syntaxique du wikitexte
 * Discussion utilisateur:Arkanosis#Syntax highlighter
 * Discussion utilisateur:Dr Brains#Syntax highlighter

P.S.: I tried some browsers but with the lastest version of chrome (37) it seems not work well.

Best regards, --Mattho69 (talk) 20:02, 3 September 2014 (UTC)


 * Your English is fine :-)
 * Anything that looks like a tag is highlighted as a tag, including.
 * The syntax highlighter can be disabled in your preferences. I don't really want to add another way to disable it.
 * Vertically resizing the edit box is now supported. For horizontal resizing, resize your browser window.
 * Internet Explorer is the only blacklisted browser. Firefox < 29, Opera < 15, and pre-2014 versions of Safari and Chrome (I'm not sure exactly which versions) also have a little trouble, but still mostly work, and hopefully few people use them any more.
 * The mobile edition of Wikipedia does not activate the syntax highlighter. However, if you switch back to the desktop edition, syntax highlighting works fine--even on a mobile device.
 * Please translate the error message fully--you're missing a couple of sentences. If you're going to make the syntax highlighter opt-out then it would also be a good idea to translate the user manual into French.
 * I have had no problems with Chromium 36. What trouble did you run into with Chrome 37?
 * —Remember the dot (talk) 21:31, 3 September 2014 (UTC)


 * By the way, I noticed a complaint about the mishighlighting of . You might consider turning off bold and italic highlighting by default on the French Wikipedia. —Remember the dot (talk) 23:43, 3 September 2014 (UTC)
 * Tkanks for your answers.
 * For tags is it possible to remove one from the detection list, especially  ?
 * I have consider turning off bold and italic highlighting.
 * The translation of the error message is "La coloration syntaxique a été désactivée sur cette page en raison d'un temps de chargement trop important ($2ms). Le temps maximum autorisé est $1ms. Vous pouvez essayer de fermer certains onglets et programmes et cliquez sur Prévisualisation ou Voir mes modifications. Si cela ne fonctionne pas, essayez un autre navigateur web, et si cela ne fonctionne toujours pas, essayez un ordinateur plus rapide."
 * I have started to translate the the user manual into French.
 * For Chrome 37 there was a mismatch between the colors and text but it seems fixed now.
 * Regards, --Mattho69 (talk) 19:53, 5 September 2014 (UTC)


 * You can only enable or disable tag highlighting. You can't choose which tags are highlighted.
 * I've integrated your translation. Thanks for working on the manual too.
 * I'm glad that Chrome is working now. Let me know if you have any more trouble with it.
 * —Remember the dot (talk) 07:08, 8 September 2014 (UTC)

Syntax highlighter issue
Hey Dot. It's been a while since the highlighter has been working for me. I recall I had it turned on as a gadget for a time when I noticed it under preferences several months ago, but I do not remember exactly when after that point it stopped working for me. Here is the information you requested: Let me know if you have other questions. I also noticed another user mentioned that their Adblock software was interfering. I have disabled my own (Adblock Plus), but there was no change and did not appear to affect the syntax highlighter. I, JethroBT drop me a line 03:10, 28 October 2014 (UTC)
 * Detail about the circumstances: No highlighting occurs for me under any circumstances, regardless of whether it is turned on as a gadget or the relevant syntax put under User:I JethroBT/common.js.  I've considered it might be possible that some other piece of code there might be interfering with the highlighter, but I'm not skilled enough to know what to look for.
 * User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0
 * Mediawiki Skin: Monobook.


 * One guess: MediaWiki does not support ctype=application/javascript, even though this is the official standard. So, MediaWiki was defaulting to text/x-wiki instead, which Chrome (and possibly now Firefox too) rejects. Last May I updated the documentation to recommend ctype=text/javascript instead, and last July I dropped the smaxage and maxage parameters . Just now I made those changes in your own common.js . If the problem persists, try disabling your other scripts to see if any of them might be interfering. —Remember the dot (talk) 06:35, 19 November 2014 (UTC)
 * Thanks-- the change from ctype=application/javascript did not do the trick, unfortunately. I'll see if there are other scripts that are interfering and get back to you. Thanks for letting me know about the dropped parameters as well.  I, JethroBT  drop me a line 07:08, 19 November 2014 (UTC)
 * Seems like disabling this script here from User:Writ Keeper/Scripts/SearchNamespace.js appeared to allow the highlighter to function normally again.  Not sure why this would interfere on the face of it, but there you have it.  I, JethroBT  drop me a line 07:28, 19 November 2014 (UTC)


 * That script is not compatible with MonoBook. In the browser console, you can see "TypeError: searchDiv is null". This error causes the browser to abort before loading the syntax highlighter. —Remember the dot (talk) 09:19, 20 November 2014 (UTC)
 * Indeed it's not; User:Writ_Keeper/Scripts/SearchNamespaceMono.js should be, though. Writ Keeper &#9863;&#9812; 09:44, 20 November 2014 (UTC)

br tag in DotsSyntaxHighlighter
Hello, thank you for your code which is now a gadget on the French WP, I like it and I have a suggestion concerning this tag, which I often see on talk pages as  coloring all that follows : would it be possible to treat   as  , since both really do the same thing ? Thank you. Oliv0 (talk) 17:29, 5 November 2014 (UTC)


 * This has been discussed many times. The answer is no. —Remember the dot (talk) 06:35, 19 November 2014 (UTC)
 * OK, I found it: mw:User talk:Remember the dot/Syntax highlighter "For performance reasons, the highlighter requires all tags to be valid XML." Oliv0 (talk) 07:10, 20 November 2014 (UTC)

ending span bug
My info:
 * Vector skin
 * Mozilla/5.0 (Windows NT 6.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.111 Safari/537.36

's signature ends a span outside of a piped link, which makes all text following it purple in the syntax highlighter. Putting the span end inside the double square brackets solves the problem. The signature itself doesn't cause problems with the page, just the highlighter. Chris Troutman ( talk ) 04:07, 18 November 2014 (UTC)


 * The problem here is Biblioworm's sloppy syntax, which is difficult to understand with or without the syntax highlighter. You'll have to convince Biblioworm to put the  in the right place. —Remember the dot (talk) 06:35, 19 November 2014 (UTC)

Syntax Higlighter broken on jawiki
Hello Remember the dot, the highlighting's position is off on jawiki. Probably some custom font styling they use there, but maybe you can adapt the script to respect those customizations. Regards, --Patrick87 (talk) 23:31, 1 December 2014 (UTC)


 * I can't reproduce the problem. Could you provide me with the details listed at mw:User:Remember the dot/Syntax highlighter? —Remember the dot (talk) 00:59, 2 December 2014 (UTC)
 * Ah sorry, thought this was an obvious one (note to self: it never is ). Actually it happens when you set the language to English on jawiki (see this link for an example). If the language is set to Japanese everything looks as expected. (Browser is Firefox 33.1.1 on Windows 7; Vector Skin; all custom JS/CSS disabled). --Patrick87 (talk) 01:37, 2 December 2014 (UTC)


 * Thanks! This actually resolves an issue on the Arabic Wikipedia as well. —Remember the dot (talk) 05:21, 2 December 2014 (UTC)
 * Great! --Patrick87 (talk) 10:08, 2 December 2014 (UTC)

Proposal: enable "Syntax highlighter" gadget by default for all editors
Hey there! If you look through my contributions (especially my recent ones in my user space), you'll see that I'm fairly proficient with JavaScript. I figured I'd pop by here to see if we can start collaborating on getting this ready to be a better proposal. Based on what I'm reading on your talk page here, I see there have been a lot of problems with the script, and it apparently collides with some other scripts in some use cases. I also see that it is being used on multiple wikis. Let's see if we can fix the incompatibilities, and get some research, and maybe even get enabled as a default gadget on one or more of the other wikis.

As far as the IEG thing goes, maybe we can get some help on that from, , , or as they have all either gone through the process or are part of the process.

, (I'll leave a "please see" TB too), I still believe the best course of action is to withdraw the current proposal as something like I am withdrawing this proposal at this time as the comments up til this point has indicated to me that it is too soon for this and the script isn't quite as ready as I had originally thought. I'd like to thank everyone for their time and comments and look forward to possibly changing some minds when the issues indicated in this discussion have been resolved. Happy Holidays! — or at VERY least changing the proposal to: RfC: What it would take to get the "Syntax highlighter" gadget "default enabled" for new editors.

Happy editing and happy holidays to everyone! :) — &#123;&#123;U&#124;Technical 13&#125;&#125; (e • t • c) 22:57, 5 December 2014 (UTC)
 * Hm. Well, I certainly love the syntax highlighter and think it's pretty amazing.  That said, I don't have any strong opinions about whether it should be turned on by default; also, what's the IEG idea that T13 is talking about?  Is it to find evidence that the syntax highlighter is a strong benefit to all editors, which would support turning it onto default?   I, JethroBT  drop me a line 23:07, 5 December 2014 (UTC)
 * All editors, sure, although my main curiosity is whether it would be a benefit to editors who are new or only edit once or twice in their life as anon IPs. All of us "old coots" who have been around forever and know what we are doing can simply disable it if we don't like it.  Seeing what the data to that comes back as will help us determine if it is a good idea to enable it by default or not.  I also just remembered, I saw  say that there were technical restrictions that forced it to be a background color changer instead of a text color/styling changer, what are those restrictions?  Am I missing something?  Thanks! — &#123;&#123;U&#124;Technical 13&#125;&#125; (e • t • c) 23:24, 5 December 2014 (UTC)
 * I like the syntax highlighter too. Before exposing it to the masses, it would be helpful to clear up some minor UI problems, like the lack of vertical space between lines of text (compared to the default editor) and the incompatibility with unclosed br tags. It also chokes on large pages. I'm sure these problems have all been brought up before, but they are the sort of problems that people can live with when using an opt-in tool developed by a volunteer but that cause annoyance in an opt-out tool. Fixing them may involve fixing things other than the highlighter itself (i.e. fixing unclosed br tags could be done by a bot). – Jonesey95 (talk) 23:50, 5 December 2014 (UTC)
 * Putting vertical space between lines of text creates stripes in multiline templates and makes them look awful.
 * Making the text change color is impossible because I would have to make the real text invisible and the fake text visible, and if I make the real text invisible, the caret disappears too. But if I make the real text visible and the fake text invisible (except for its colored background), there's no problem. See mw:User:Remember the dot/Syntax highlighter. I found some discussion about making it possible to style the caret separately from the text, but nothing seems to have come of it.
 * Any wiki that turns the syntax highlighter on by default would also have to decide to use only the subset of markup that the syntax highlighter understands, e.g.  and  . The syntax highlighter can only work as fast as it does because it requires a bit stricter syntax than usual, but getting any wiki to agree to that will be the biggest obstacle to be overcome.
 * —Remember the dot (talk) 02:26, 6 December 2014 (UTC)

I have had syntax highlighter installed but it has never worked, I get a red warning message about excessive load times. I like the idea of this tool, but I think it needs some more development before it could be rolled out more broadly. Thanks for your work and cheers! Ocaasit &#124; c 13:19, 6 December 2014 (UTC)

In hindsight I should've talked to you first before proposing this on Village Pump... I thought it would be an easy pass - I forget sometimes how resistant to even a minor change has Wikipedia became. I hope that the resulting discussion will make the tool better, and lead to a successful round two - but I promise I won't start it without consulting you this time :) --Piotr Konieczny aka Prokonsul Piotrus&#124; reply here 04:45, 8 December 2014 (UTC)