This is an archive of past discussions with User:Mgiganteus1. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
Hello, Mgiganteus1/Archive 5, and welcome to Wikipedia! Thank you for your contributions. I hope you like the place and decide to stay. Here are a few good links for newcomers:
I hope you enjoy editing here and being a Wikipedian! Please sign your name on talk pages using four tildes (~~~~); this will automatically produce your name and the date. If you need help, check out Wikipedia:Where to ask a question, ask me on my talk page, or place {{helpme}} on your talk page and someone will show up shortly to answer your questions. Again, welcome! --Bachrach4423:19, 18 January 2006 (UTC)
Orphaned non-free media (File:Alien (1986) - Alien queen.jpg)
Thanks for uploading File:Alien (1986) - Alien queen.jpg. The media description page currently specifies that it is non-free and may only be used on Wikipedia under a claim of fair use. However, it is currently orphaned, meaning that it is not used in any articles on Wikipedia. If the media was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that media for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
If you have uploaded other unlicensed media, please check whether they're used in any articles or not. You can find a list of 'file' pages you have edited by clicking on the "my contributions" link (it is located at the very top of any Wikipedia page when you are logged in), and then selecting "File" from the dropdown box. Note that all non-free media not used in any articles will be deleted after seven days, as described on criteria for speedy deletion. Thank you. Hazard-Bot (talk) 04:05, 24 June 2012 (UTC)
Hello Mgiganteus; apologies, those edits to the pronunciation were initiated by me, I didn't realise that I was logged out on my laptop. It has been many months since I checked the entries, but I notice that some very odd pronunciations are creeping in, whether by American or British English standards. Any objections to my running through and tweaking? Whilst I originally included the IPA as a guide - and it should only be seen as such given regional differences - some of the names have shifted to pronunciations that I've never heard used on either side of the Atlantic. I also need to add in some missing ones. Let me know, and I'll see to it. Cheers, Attenboroughii (talk) 04:18, 24 July 2012 (UTC)
Not to worry; I'd probably have done the same had I been so attentive. Only a couple of them have been tweaked since 2007, something I didn't notice until I started working on a lightweight iPhone app that will include pronunciation guides for all the species, among other things. I'll add the missing IPA as I go. The one thing that still bugs me is that the pronunciation for Nepenthes is still given as NIH-pen-theez, rather then NUH- or NEH-; there's an old discussion further up my wall (item 3) where the resolution was for NUH- (i.e. using schwa: ə ), but I have no experience with bots and am not about to change them all manually. I wonder what your thoughts are, and perhaps Rkitko will have an opinion also. I speak with RP, do passable estuary/cockney, Aussie and Saffa, and half my family speaks with an American accent. None of them say NIH-, but personal experience of speaking aside, the poster (see last 3 posts by Kwami in item 3 on my talk page) admits that ə makes a difference to speakers of non-American English, but not American English. I'm not saying that we *should* change it, but would prefer some democratic consensus on that matter that involves those who care most. Cheers Attenboroughii (talk) 11:36, 25 July 2012 (UTC)
Saw a note regarding this discussion on Rkitko's talk page, and will offer what I can. By way of introduction, I'm trained as a botanist and I've worked on Wiktionary a lot, spending a lot of time dealing with pronunciation of both English and Classical Latin. The problem is that the pronunciation of the initial syllable is expected to be variable. I've checked the pronunciation of "Nepal" in the Cambridge English Pronouncing Dictionary, and for both the UK and US, both /nɪ-/ and /nə-/ are given as pronunciations of the initial unstressed syllable. I would expect the same to be true of Nepenthes. So, I see three options: (1) we make an arbitary choice to use one or the other pronunciation, (2) we give both prounciations at the start of the article, or (3) we give one pronunciation at the outset of the article, with a footnote placed there describing and explaining the alternative. --EncycloPetey (talk) 01:53, 26 July 2012 (UTC)
Thank you for your input, EncycloPetey. Looking at your options, 2) seems less neat as the pronunciation for the genus appears on all Nepenthes pages; 1) "arbitrary" perhaps isn't quite the right word, as any action on our part can only be considered; whether we favour one or the other, we'll have done so for a variety of reasons. Anyway, taking into account your citation of Nepal as an example, perhaps the currently employed /ɨ/ is the least problematic after all? /ɪ/ would miss the mark for most RP speakers, while /ə/ would be fine for RP and make little difference to GA speakers since they don't articulate their vowels quite so markedly; though /ɨ/ is a reduced vowel, which it certainly isn't in Nepal, or indeed some pronunciations of Nepenthes, in the latter the stress is most commonly on the -PEN- and /ɨ/ offers some flexibility where /ɪ/ and /ə/ do not. RP speakers still draw a short straw in terms of accuracy, but it's closer than /ɪ/. 3) may be overkill for an audience who probably don't care too much about how it is pronounced (and it is a trivial point after all) since it's a straightforward word. So concentrating on point 1), I want to establish what the consensus would be on the use of -ɪ, -ə, or -ɨ over the alternatives. Attenboroughii (talk) 01:27, 27 July 2012 (UTC)
Thinking about this some more, I'm leaning towards option 3. How about this: we keep /ɨ/ as the only pronunciation in the intro to Nepenthes and throughout all the daughter articles (for the reasons stated above), but include a footnote in Nepenthes explaining the nuances. All three pronunciations can then be sourced to popular dictionaries (most of which apparently favour /ɪ/, per kwami). I don't think it would be overkill to include a sentence or two on this, hidden away as it would be at the bottom of the page. If a reader isn't interested they can skip over the footnote. mgiganteus1 (talk) 16:21, 27 July 2012 (UTC)
I'm content with option 3 also. I can't spare the time to see to it at present (not that it's urgent), but if you do think of a suitable footnote, please feel free. And IPA is a whole series of delicious beers - alas, Greene King is hard to find outside of the UK.Attenboroughii (talk) 01:16, 30 July 2012 (UTC)
Hi, all. Thanks for thinking of me in this discussion, but I must confess my complete ignorance of IPA (isn't that some kind of beer?). I'm also accustomed to meeting others at conferences and instantly comparing pronunciations, usually brought on by talking about our favorite organisms. Subsequently, I have a rather lax attitude toward pronunciations. I'll leave the decision in your capable hands :-) Rkitko(talk)02:20, 27 July 2012 (UTC)
Hello, Mgiganteuus1.
I would like to contact to you for copyright issue.
Kindly let me know how I can talk with you.
Chikiemon
Is there anything that can be done about this user? He is on a template removal rampage this week, and refuses to format taxoboxes correctly. --Kevmin§22:24, 15 August 2012 (UTC)
Unfortunately at this point he refuses to even engage in dialog with me, and continues his disruptive editing.--Kevmin§00:18, 21 August 2012 (UTC)
File:Nepenthes x trusmadiensis distribution.png listed for deletion
Hello, Mgiganteus1, and thank you for welcoming me in English section!
I changed the formulation in Gladius (cephalopod) because it looked like "Vampyroteuthis is the sole recent member of Octopodiformes". Yes, my formulation isn't very exact in relation to extinct species. Maybe, you could find better formulation. With best regards, Stas000D (talk) 17:05, 8 October 2012 (UTC)
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Nepenthes macrophylla, you added a link pointing to the disambiguation page Mutualism (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Epitonium, you added a link pointing to the disambiguation page Spiral staircase (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Why are lengthy references, as you reverted back to, better than more concise references such as I changed. While the extra wording probably wouldn't matter, except for providing nothing essential, when the reference appeared only at the bottom of the page, with in-line references now popping up on pages it seems they should be as short as reasonably possible. Just my perspective.J.H.McDonnell (talk) 23:56, 16 November 2012 (UTC)
Nice mollusk contributions
Hello Mgiganteus1, nice to see your excellent contributions to WikiProject Gastropods and WikiProject Bivalves. Any and all contributions you can make, and continue to make, keeping with the projects' style are greatly appreciated. I look forward to spending more time making contributions myself, as I have been absent a few months due to work matters. Take care and keep up the great work! Shellnut (talk) 01:46, 17 November 2012 (UTC)
I've noticed your edits on pages relating to Bivalves; perhaps you'd be interested in joining WikiProject Bivalves. If you would like more information please visit the project page.
Thank you for all of your valuable contributions on marine fauna articles! Your edits have greatly added to the wealth and integrity of the articles on Cephalopods, Gastropods, Bivalves, and other marine mollusks. Shellnut (talk) 16:20, 17 November 2012 (UTC)
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that you've added some links pointing to disambiguation pages. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Nepenthes surigaoensis, you added a link pointing to the disambiguation page Danao (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that you've added some links pointing to disambiguation pages. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited List of giant squid specimens and sightings, you added a link pointing to the disambiguation page Epidermis (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Cephalopod dermal structures, you added a link pointing to the disambiguation page Epidermis (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Rafflesia arnoldii, you added a link pointing to the disambiguation page Corpse flower (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that you've added some links pointing to disambiguation pages. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that you've added some links pointing to disambiguation pages. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that you've added some links pointing to disambiguation pages. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Electronegativity, you added a link pointing to the disambiguation page Fourth period (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Charles Brewer-Carías, you added a link pointing to the disambiguation page Table mountain (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Thank you for contributing to Wikipedia. We always appreciate when users upload new images. However, it appears that one or more of the images you have recently uploaded or added to an article may fail our non-free image policy. Most often, this involves editors uploading or using a copyrighted image of a living person. For other possible reasons, please read up on our Non-free image criteria. If you have any questions please ask them at the Media copyright questions page. Werieth (talk) 11:12, 8 March 2013 (UTC)
Disambiguation link notification for March 12
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Sierra de Lema, you added a link pointing to the disambiguation page Upland (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Phytotelma, you added a link pointing to the disambiguation page Treehole (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Apical ectodermal ridge, you added links pointing to the disambiguation pages Wnt, Fingers and Ectopic (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Do you mind elaborating on why you created the redirect page of Spirulina (suborder) to the cephalopod page? There seems to be no support for the use of that term anywhere else on Wikipedia, and Spirulina does have an actual specific meaning regarding cyanobacteria. ScottHW (talk) 21:32, 15 June 2013 (UTC)
The link you cited for the use of "spirulina" as a suborder of cephalopod actually states that spirulina was an acceptable Homonym in 1827. And that it was listed as a suborder in 1912.
The conflict comes from the fact that the word Spirulina is currently, modernly, and actively used to describe a significantly taxonomy, specifically a genus of cyanobacteria. Derived from that scientific realm, the name Spirulina is often used to refer to the nutritional supplement derived from the cyanobacteria. A very brief web search will quickly show that this is the OVERWHELMING use of the word. I'm struggling to find additional sources confirming modern use of the suborder "Spirulina".
I guess you're right. The Spirulina cephalopod suborder is unambiguous. I was just annoyed to find out that a hundred years ago some guys decided to use the exact same word to name such drastically different things.
I also agree that the Spriulina disambiguation should be addressed. As a scientist, I would rather that that cyanobacteria be given the default position, since that's how the nutritional supplement derives it's name. But I recognize (and in fact just pointed out above) that to a general audience, the word most often refers to the supplements.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Preservation of biopolymers, you added a link pointing to the disambiguation page Anaerobic (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Author citation dates in plant taxoboxes (above genera)
I have been adding dates to taxobox authorities for plant families and orders. I had seen this done in a few taxoboxes, and I am working on citing all of the authorities for plant families and orders. A discussion had taken place about this before, here, although the focus of this discussion was on all taxa, inlcuding genera and species. As you participated in a past discussion, and are actively editing Wikipedia now, I am posting this link in case you wish to comment.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Myopsina, you added a link pointing to the disambiguation page Adductor muscle (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Nepenthes hemsleyana, you added a link pointing to the disambiguation page Lamina (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hey Mgiganteus1! We've just deployed some fixes to the VisualEditor. These include:
"Edit" will load the latest version, not the version you're looking at (bug 49943)
"Edit" will load the latest version, not the version you edited last time if this is your second edit (bug 50441)
VE edit section links will load the latest, not original, version in diff view preview (bug 50925)
<big><big>Foo</big></big> and similar repeated tags will not get corrupted any more (bug 49755)
In the meantime, testing is proceeding well, and hopefully we can get some more fixes out over the next couple of days. If you're interested in helping out, we have a set of open tasks we'd really appreciate your assistance with :). Thanks, Okeyes (WMF) (talk) 08:04, 9 July 2013 (UTC)
Parameter names in the template dialogue now word-wrap (50800)
The link inspector will not show in the top left if you hit the return key while opening it (49941)
Hitting return twice in the link editor will no longer introduce a new line that overwrites the link (51075)
Oddly-named categories no longer cause corruption (50702)
The toolbar no longer occasionally covers the cursor (48787)
Changing the formatting of text no longer occasionally scrolls you upwards (50792)
Not specific bugs, but other things; cacheing is now improved, so people should stop seeing temporary breaking when the VisualEditor updates, and RTL support has received some patches. I hope this newsletter is helpful to people; I'll send out another one with the next deployment :). Thanks, Okeyes (WMF) (talk) 10:14, 11 July 2013 (UTC)
Hey Mgiganteus1! Another set of patches :). Today we have:
Required template parameters are now automatically added to new templates (50747)
Templates with piped links now display correctly when you alter them (50801)
If your edit token expires, you're now informed of it (50424).
You still won't be able to save - that's due to be fixed on Monday :).
More on Monday, I suspect. Hope you have a good weekend :). I should also have some news about the IP launch pretty soon. Thanks, Okeyes (WMF) (talk) 13:23, 12 July 2013 (UTC)
(if you're seeing this and aren't the newsletter recipient - please do sign up here)
VE newsletter
Hey Mgiganteus1; hope you had a decent weekend :). We've got a pile of patches, some of which went out on Monday, some yesterday:
If you insert wikitext such as links or section headers, you get a notice in the top right corner (over the save button). It doesn't go away until click, though once dismissed you don't get another one that edit. (49820)
If your edit token expires, VE fetches a new one for you so you can save. (50424)
If the page is empty of content but does have something non-content (like a category or an HTML comment), VE no longer crashes on load - (50289)
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Drosera glanduligera, you added a link pointing to the disambiguation page Fruit fly (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Links now don't extend over space/punctuation/workbreaks when you type (bugzilla:51463)
Users with the "minoredit" preference set get working functionality (bugzilla:51515)
You can tab to buttons in dialogs, including the save dialog (bugzilla:50047)
We now show the <newarticletext> (or <newarticletextanon>) message as an edit notice (bugzilla:51459)
You can scroll dialog panels like in transclusions' templates' parameter listings (bugzilla:51739)
Templates that only create meta-data and no display content at all (like Template:Use dmy dates) now can't be deleted accidentally or deliberately, but still don't show up (bugzilla:51322)
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited John Dominy, you added a link pointing to the disambiguation page Chelsea (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Quick tip: Need to wikilink a word in VisualEditor? Select the word and type Control+k or ⌘ Command+k to enter VisualEditor's link tool without taking your hands off the keyboard. See Wikipedia:VisualEditor/Keyboard shortcuts for more time-saving keyboard shortcuts.
It's been almost two weeks since the last newsletter, and a lot of improvements have been made during that time. The main things that people have noticed are significant improvements to speed for typing into long pages (T54012), scrolling (T54014) and deleting (T54013) on large pages. There have also been improvements to references, with the latest being support for list-defined references, which are <ref>s defined inside a <references> block (T53741). Users of Opera 12 and higher have had their web browser removed from the browser black-list, mostly as a result of work by a volunteer developer (T38000). Opera has not been fully white-listed yet, so these users will get an additional warning and request to report problems.
Significant changes were made to the user interface to de-emphasize VisualEditor. This has cut the use of VisualEditor by approximately one-third. You can read about these at Wikipedia:VisualEditor/Updates/August 1, 2013, but they include:
Re-ordering links to the editors to put "Edit source" first and VisualEditor second
Renaming the link for VisualEditor to "Editbeta"
Disabling the animation for section editing.
Changing all labels for the classic wikitext editor to say "Edit source", regardless of namespace.
There have also been many smaller fixes, including these:
Horizontal alignment of images working correctly on more pages (T53995)
Magic JavaScript gadgets and tools like sortable tables will now work once the page is saved (T53565)
Keyboard shortcut for "clear annotations" - now Control+\ or ⌘ Command+\ (T53507)
Fixed corruption bugs that led to duplicate categories (T54238) and improper collapsing when multiple new references were added in a row (T54228).
Improvements to display elements: The save dialog in Monobook is restored to normal size (T52058), pop-up notices on save now look the same in VisualEditor as in wikitext editor (T41632), and the popup about using wikitext has a link to the definition of wikitext that now opens in a new window (T54093)
Most of the Wikimedia Foundation staff is traveling this week and next, so no updates are expected until at least August 15th. If you're going to be in Hong Kong for Wikimania 2013, say hello to James Forrester, Philippe Beaudette, and the other members of the VisualEditor team.
Hi Mgiganteus1, I've edited the date section of article DWKX because I've seen that you've reversed the date. I made the typos for you since it is stated that 103.5 Wow FM was launched on July 22, 2013 and 103.5 K-Lite 2nd Iteration was launched on August 23, 2010 which is clearly a typo. Hope you're still considered this edit, thanks and cheers . Hamham31Heke!00:59, 10 August 2013 (UTC)
Hello, Mgiganteus1. You have new messages at Hamham31's talk page. You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Wedge (mechanical device), you added a link pointing to the disambiguation page Taper (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Did you know?Parsoid is a tool that translates between the raw wikitext that Wikipedia articles are stored in, and the HTML/RDFa that VisualEditor uses on your screen. If you see chess pawn (♙) or snowman (☃) icons in an article, it usually means that Parsoid has encountered something confusing in the wikitext markup. Please report these problems to Wikipedia:VisualEditor/Feedback.
Both VisualEditor and MediaWiki were upgraded recently. For VisualEditor, this is the long-awaited post-Wikimania update with many bug fixes and enhancements. Work also continues on speed at opening and during use, as well as on the bugs reported here and at other Wikipedias. The full report is at Mediawiki.
References are displaying properly, even when nested (T52749) or in image captions (T2000. Reference lists are now always fully populated with references (bug 50094). Firefox users can insert an existing reference in the first paragraph (T54159). Opera users no longer see corruption of categories when a reference was added (bug 50385).
Stray spaces are being stripped from the start of paragraphs to end one of the common <nowiki> problems (T53462). We also fixed a round-tripping bug that caused desirable whitespace in templates (used to make templates more legible, e.g., by putting each parameter in an infobox on a separate line) to get corrupted (bug 51150).
Wikilink handling was improved. Users are not allowed to create internal links to invalid titles (titles that are actually impossible due to limits on acceptable character combinations in titles, not redlinks) (T35094). You can extend wikilinks, but it won't do so over a wordbreak (like a space) (bugs 49931 and 51463).
A handful of fixes to the user interface were made. The toolbar doesn't float over personal tools after opening a dialog or the inspector (T54441). Toolbars were also re-written to be collapsible/expandable, with room for more icons. Buttons in dialogs can now be activated using the Tab ↹ and ⇧ Shift+Tab ↹ key commands (bug 50047). This saves time for editors, because you don't need to take your hands off the keyboard to click a button. We fixed a handful of bugs that affected only certain articles or certain browsers, including toolbar buttons in Firefox (bug 51986) and dialog panels that didn't always scroll correctly (bug 51739). Bugs with undo/redo getting confused have been fixed (T54113).
Images, in addition to getting references displaying correctly, also saw improvements with a set-empty |link= parameter no longer corrupted (51963). We corrected thumbnail images' display so that they look don't wrong in some contexts (bug 51995). Inserted images no longer explicitly set their alignment, but instead inherit the default position in compliance with the Manual of Style (bug 51851).
More edit notices, warnings, and metadata like information about Pending Changes on an article now appear as appropriate (bug 49699). When new articles are created, users are now shown the <newarticletext> message (bug 51459). VisualEditor now handles templates that set "meta" items (like a category) and nothing else better (bug 51322). If the database is locked when a user tries to save with VisualEditor, they now get a message telling them as such and an opportunity to try again, rather than a silent failure (bug 51636).
When you save the page, having the default preference set to "mark all my edits as minor by default" no longer overrides the setting in the save dialog (bug 51515). If you open VisualEditor from a section edit link, the section's title will be pre-filled in in the edit summary box when you go to save it (bug 50872). The size of the save dialog box in the Monobook skin has been fixed (bug 50058). Also, wikipage content handlers like sortable tables are re-run automatically after saving (T53565).
A very early version of the mathematics equation editor is now available for testing on mw:Mediawiki. If you would like to help improve the user interface for math editor, please test out the extension at mw:Mediawiki:Sandbox and leave your comments directly at the discussion page for the Math Node User Interface at Mediawiki. You should be able to use your regular username and password should to login to Mediawiki.
Hello, it looks like you made many contributions to this page, Do you have any information on the lifespan of these little Sprogs and what kind of elements they are made up of that extends their life faculty so much and makes them as rough as a bag of nails.--Prestigiouzman (talk) 10:16, 28 August 2013 (UTC)
Disambiguation link notification for August 29
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited List of Nepenthes species, you added a link pointing to the disambiguation page Negros (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Thank you for welcoming me. You're the first to talk to me. How do I find pictures I can use in an article? The picture in Cucurbita pepo is not that good. There's bound to be a better one around. Another question, I'm using a JSTOR article to update c. pepo and Cucurbita. I do I "recycle" that reference without copying all the syntax for the reference every time?
I've noticed that when I use cite jstor and create fill in the info, it creates a file called "template cite doi....." and that the doi numbers it makes seem to be bad. I'll just keep using cite jstor as you suggested. Thank you for being so helpful and I hope I don't bug you too much. I'm also trying to figure how to combine the two species lists. I made the second one but I don't like how it came out, too much repeated info.HalfGig (talk) 12:53, 1 September 2013 (UTC)
Good tips. I like using academic/university level references. And the coding/syntax/markup isn't that hard for me to learn. HalfGig (talk) 16:09, 1 September 2013 (UTC)
I started my first article, a little know curcubit species. If you have tips, just let me know on my talk. If you want to edit it yourself, feel free. Thanks for all you help so far. HalfGig (talk) 21:05, 1 September 2013 (UTC)
Can you keep an eye on my talk page? That way we don't keep switching between your page and mine. I have another response for you there. HalfGig (talk) 11:53, 2 September 2013 (UTC)
Hi. I just made an edit here to remove erroneous info and its errant reference. I put in more accurate info with a better reference. Is this ok to do? See Cucurbita for more details on why this prior info was erroneous. Please respond here. It's that other stuff I wanted to keep in one spot. HalfGig (talk) 23:56, 3 September 2013 (UTC)
Thanks for the help. I learned from looking at decent articles, their style, format, etc and copying how they were done and the tips you've given have really helped. HalfGig (talk) 01:57, 5 September 2013 (UTC) Oh, I've still working on Cucurbita, I'll probably spend a few more weeks on it. I have more JSTOR articles to read. If you have tips on that article, it'd be appreciated.HalfGig (talk) 01:59, 5 September 2013 (UTC)
VisualEditor newsletter for September 5
Did you know?
You can search for images directly in VisualEditor. Click the media icon, which looks like this:
Then type a few keywords into the search box. VisualEditor will search Commons for images or other files whose titles or descriptions contain those words, and will display thumbnail pictures of them for your review. Click one time on the image you want to insert in the article.
This Thursday's VisualEditor update was mostly about stability and performance improvements, and some preparatory work for major planned improvements, along with bug fixes for non-English language support and right-to-left text. Everything that the English Wikipedia received today has been running on Mediawiki for a week already.
Officially, the problem with the link inspector not linking to a specific section on a page (bug 53219) was fixed in this release, although that critical patch actually appeared here earlier.
A number of bugs related to copy-and-paste functionality were fixed (48604, bug 50043, bug 53362, bug 51538, among others). Full rich copy-and-paste from external sources into VisualEditor is expected "soon".
In other fixes, you can no longer add empty ref tags (<ref/>) (bug 53345). Selecting both an image and some text, and then trying to add a link, previously deleted the selected image and the text. This was fixed in bug 50127. There was another problem related to using arrow keys to move the cursor next to an inline image that was fixed (bug 53507).
Looking ahead: The next planned upgrade is scheduled for next Thursday, and you should expect to find a redesigned toolbar with drop-down menus that include room for references, templates, underline, strikethrough, superscript, subscript, and code formatting. There will also be keyboard shortcuts for setting the format (paragraph vs section headings).
If you are active at other Wikipedias, the next group of Wikipedias to have VisualEditor offered to all users is being determined at this time. Generally speaking, languages that depend on the input method editor are not going to receive VisualEditor this month. The current target date is Tuesday, September 24 for logged-in users only. You can help with translating the documentation. In several cases, most of the translation is already done, and it only needs to be copied over to the relevant Wikipedia. If you are interested in finding out whether a particular Wikipedia is currently on the list, you can leave a message for me at my talk page.
I'm done with my initial work on Cucurbita fraterna. It's my biggest one yet of the new ones. I've dumped a lot of facts in it but I think it doesn't read well. Could you look at it and help make it a better read? HalfGig (talk) 01:27, 7 September 2013 (UTC)
On my other new articles I did not find photos of the freely licensed type you told me about. My next article will be C. texana. I found 10 images (1 USDA, 9 forestryimages.org) that i think are freely licensed. I made an account on Wikipedia Commons and instantly got a talk page message about how to do things. It had a link with a form to fill out to upload images. It was not too hard but I am sure I goofed a few things. 1) I had trouble with the texana category I made. It shows up under the cucurbita category, but should show up under the c. pepo category 2) can you kindly look over the uploads and see if I need to fix anything. The images are in two places: https://commons.wikimedia.org/wiki/User_talk:HalfGig and https://commons.wikimedia.org/wiki/Category:Cucurbita_texana . If I repeated a mistake, let me know and I'll fix it. Which image do you think is best on the soon to be new article? HalfGig (talk) 21:57, 7 September 2013 (UTC)
Yep, those images are all fine license-wise. You included all the necessary information in your uploads (source, author, permission, etc.) but strictly speaking all images should have a license template (which I've added). Some of these templates can be quite obscure and difficult to find, but here's a more-or-less complete list: https://commons.wikimedia.org/wiki/Commons:Copyright_tags.
I think placing C. texana within C. pepo would be confusing as they are both at the same taxonomic rank (that of species). If the category was named Cucurbita pepo var. texana then it would make sense for it to be subordinate to Cucurbita pepo. I'm not sure which combination (if any) has greater currency in the literature?
Thank you again for being so helpful. Yes, there's inconsistency in how the various species/varieties relate to one another, not uncommon in the taxa world. They're either separate and equal, subspecies, or varieties. Maybe for now I'll leave it as and think about it. There's no doubt fraterna, texana, and pepo are related. If we make the Commons category subordinate to pepo, we should probably rename the wiki articles on fraterna and texana. Note the fruit photos have melons on the right and texana on the left. HalfGig (talk) 01:29, 8 September 2013 (UTC)
Note this part "As most recently defined (Decker-Walters, et al., 1993), free-living gourds that occur in Texas are classified as C. pepo ssp. ovifera var. texana. Similar, free-living plants that occur in the U.S. beyond Texas (Illinois, Missouri, Arkansas, Oklahoma, and Louisiana) are placed in C. pepo ssp. ovifera var. ozarkana." There still seems to be disagreement on what to call and the relations between pepo, texana, and fraterna. That 1993 ref is 20 years. I'm looking for newer stuff. And "However, primary areas of disagreement among those working with the C. pepo 'problem' do not center on the pattern of genetic differentiation that has produced the entities defined as subspecies and varieties in Fig. 1. These have been relatively well defined by a series of comparative studies that show considerable congruence. The 'Texas Gourd' has not been treated as a distinct species by specialists since the formal name change in 1988 (Decker, 1988;Decker-Walters, 1990;Decker-Walters et al., 1990;Decker-Walters et al., 1993;Harlan, 1992;Heiser, 1989;Smith, 1992;Cowan and Smith, 1993;Wilson, 1989;1990). There are, however, several competing hypotheses regarding phylogenetic linkage between both free-living and domesticated elements of C. pepo. " HalfGig (talk) 12:41, 8 September 2013 (UTC)
Looking good. The only thing I could find to edit was to move the stub tags below the categories. This is so the auto-generated stub category (in this case Category:Cucurbitales stubs) appears after, and not before, the more important, non-maintenance categories. Anyway, keep up the good work! mgiganteus1 (talk) 02:06, 10 September 2013 (UTC)
Following some tips and hint to nominate for "good" status, I've nominated Cucurbita for "good" status. If you have suggestions, please make the edits or let me know and I'll make the edits. If you want to review it for "good", that's okay too. HalfGig (talk) 23:28, 10 September 2013 (UTC), and a new one: Cucurbita andreanaHalfGig (talk) 23:51, 10 September 2013 (UTC)
Moorei may have the same problem C. gracilior. Nee counts them as species but this Plant List site doesn't. Not unusual to have disagreement. But the issue at hand is how to deal with this in the genus level Cucurbita article. Nee counts 27 species in 13 groups. But the Plant List has 19 species. What should we do here? HalfGig (talk) 01:18, 12 September 2013 (UTC)
I think a peer-reviewed paper such as Nee's should take precedence over The Plant List, especially as their determinations for this genus only have a "medium confidence level" (explained here). Having said this, it would be good to mention competing taxonomic treatments, either stating that The Plant List recognises 19 species and providing a link to their page, or including their list of species in the article. mgiganteus1 (talk) 15:55, 12 September 2013 (UTC)
Excellent points. I'll be working on that over the next couple days. There are other taxonomy proposals too. I'lll poke around more. Thank you! I also started Cayaponia. I felt since it is the largest genus in the tribe, it should at least be a stub. HalfGig (talk) 20:45, 12 September 2013 (UTC)
I'm pretty much done. Mostly I'm waiting for the reviewer for "good" status to pick up the nomination. A copyedit would be greatly appreciated! HalfGig (talk) 02:34, 15 September 2013 (UTC)
You can edit a page's categories in VisualEditor. Click the "Page settings" button (next to Cancel/Save) in the toolbar to open the category tool. It will show you a list of the current categories for that page.
To add a category, type the name of the category you want to add in the search field. To remove an existing category, click on the category in the list and then, in the dialog that opens, click on the "Remove" icon (trash can). "Options" will allow you to set a default sorting key.
VisualEditor has been updated twice in the last two weeks. As usual, what is now running on the English Wikipedia had a test run at Mediawiki during the previous week.
As announced, the toolbar was redesigned to be simpler, shorter, and to have the ability to have drop-down groups with descriptions. What you see now is the initial configuration and is expected to change in response to feedback from the English Wikipedia and other Wikipedias. The controls to add <u> (underline), <sub> (subscript), and <sup> (superscript), <s> (strikethrough) and <code> (computer code/monospace font) annotations to text are available to all users in the drop-down menu. At the moment, all but the most basic tools have been moved into a single drop-down menu, including the tools for inserting media, references, reference lists, and templates. The current location of all of the items in the toolbar is temporary, and your opinions about the best order are needed! Please offer suggestions at Wikipedia:VisualEditor/Feedback/Toolbar.
In an eagerly anticipated upgrade to the reference dialog, newly added references or reference groups no longer need the page to be saved before they can be re-used (bugs 51689 and 52000). The 'Use existing reference' button is now disabled on pages which don't yet have any references (bug 51848). The template parameter filter in the transclusion dialog now searches both parameter name and label (bug 51670).
In response to several requests, there are some new keyboard shortcuts. You can now set the block/paragraph formatting from the keyboard: Ctrl+0 sets a block as a regular paragraph; Ctrl+1 up to Ctrl+6 sets it as a Heading 1 ("Page title") to Heading 6 ("Sub-heading 4"); Ctrl+7 sets it as pre-formatted (bug 33512). Ctrl+2, which creates level 2 section headings, may be the most useful.
Some improvements were made to capitalization for links, so typing in "iPhone" will offer a link to "iPhone" as well as "IPhone" (bug 50452).
Copying and pasting within the same document should work better as of today's update, as should copying from VisualEditor into a third-party application (bug 53364, bug 52271, bug 52460). Work on copying and pasting between VisualEditor instances (for example, between two articles) and retaining formatting when copying from an external source into VisualEditor is progressing.
Major improvements to editing with input method editors (IMEs; mostly used for Indic and East Asian languages) are being deployed today. This is a complex change, so it may produce unexpected errors. On a related point, the names of languages listed in the "languages" (langlinks) panel in the Page settings dialog now display as RTL when appropriate (bug 53503).
Looking ahead: The help/'beta' menu will soon expose the build number next to the "Leave feedback" link, so users can give more specific reports about issues they encounter (bug 53050). This change will make it easier for developers to identify any cacheing issues, once it starts reporting the build number (currently, it says "Version false"). Also, inserting a link, reference or media file will put the cursor after the new content again (bug 53560). Next week’s update will likely improve how dropdowns and other selection menus behave when they do not fit on the screen, with things scrolling so the selected item is always in view.
If you are active at other Wikipedias, the next group of Wikipedias to have VisualEditor offered to all users is being finalized. About two dozen Wikipedias are on the list for Tuesday, September 24 for logged-in users only, and on Monday, September 30 for unregistered editors. You can help with translating the documentation. In several cases, most of the translation is already done, and it only needs to be copied over to the relevant Wikipedia. If you are interested in finding out whether a particular Wikipedia is currently on the list, you can leave a message for me at my talk page.
Hi, not sure if you've seen that I'm reviewing Cucurbita - looks as if you have been helping nom with the article and can advise on list/table formats to make references clear, I've a couple of small queries there which formatting might iron out. Overall it's a lovely article and it was a pleasure to read it. All the best, Chiswick Chap (talk) 15:23, 20 September 2013 (UTC)
Chiswick Chap said "It may require care with lists and medical claims, and a separate section on constituents, for progress to FA." I asked for more info on his talk page because I'm not sure about the constituents parts. What do you see we need to do to get it to FA? I would need a helping start with tables. I worked on medical claims, but perhaps more is needed. I'll readily share credit as I couldn't do this without you. The article is definitely better now. HalfGig (talk) 10:13, 21 September 2013 (UTC)
If you have time, I could use help on this new article: Lewis Leonard Forman. See ref 5, I need title and author name. I'm having trouble getting proper info (and hence format) on refs 4 and 6. Ref 8 is shaky as it says year 1942 but Forman would have been 13 years old then. I got this rough info from es.wiki and went through it to verify it. This is what's left at this point. Thank you. HalfGig (talk) 00:21, 30 September 2013 (UTC)
Stemonitis picked up on it from WT:Plants and fixed it. I wonder where he found the stuff. I'm ready for you, if you don't mind, to look at Cucurbita#Chemical_constituents. I think we're close to the peer review ready other users mentioned. HalfGig (talk) 01:00, 1 October 2013 (UTC)
Hello Mgiganteus, It looks as though you are busy in other areas right now, but I just wanted to point out that I was told that this kind of template, since it is intended to be a navigational aid, should probably not contain red links (except maybe for a brief period of time). The red links in the cephalopod anatomy template have been there for nearly a year. In the MoS it says about these navigational templates: "Red links should be avoided ... editors are encouraged to write the article first." I do totally understand why these are listed though; I was tempted to do the same thing in the templates for Gastropod anatomy and Bivalve anatomy, but in the end I left them incomplete without any red links. Red links are a useful reminder for us, the writers, but they are not useful for the readers or consumers of WP. Hope you don't mind my pointing this out. All best wishes, Invertzoo (talk) 13:36, 12 October 2013 (UTC)
VisualEditor newsletter on 16 October 2013
Did you know?
You can create and edit multi-level lists in VisualEditor. The first two icons let you set or remove list formatting.
The last two are used to increase or decrease the indentation level. This can also be done from the keyboard, by using Tab ↹ to indent the list and ⇧ Shift+Tab ↹ to outdent it.
VisualEditor is still being updated every Thursday. As usual, what is now running on the English Wikipedia had a test run at Mediawiki during the previous week. If you haven't done so already, you can turn on VisualEditor by going to your preferences and choosing the item, "MediaWiki:Visualeditor-preference-enable".
The reference dialog for all Wikipedias, especially the way it handles citation templates, is being redesigned. Please offer suggestions and opinions at mw:VisualEditor/Design/Reference Dialog. (Use your Wikipedia username/password to login there.) You can also drag and drop references (select the reference, then hover over the selected item until your cursor turns into the drag-and-drop tool). This also works for some templates, images, and other page elements (but not yet for text or floated items). References are now editable when they appear inside a media item's caption (bug 50459).
There were a number of miscellaneous fixes made: Firstly, there was a bug that meant that it was impossible to move the cursor using the keyboard away from a selected node (like a reference or template) once it had been selected (bug 54443). Several improvements have been made to scrollable windows, panels, and menus when they don't fit on the screen or when the selected item moves off-screen. Editing in the "slug" at the start of a page no longer shows up a chess pawn character ("♙") in some circumstances (bug 54791). Another bug meant that links with a final punctuation character in them broke extending them in some circumstances (bug 54332). The "page settings" dialog once again allows you to remove categories (bug 54727). There have been some problems with deployment scripts, including one that resulted in VisualEditor being broken for an hour or two at all Wikipedias (bug 54935). Finally, snowmen characters ("☃") no longer appear near newly added references, templates and other nodes (bug 54712).
Looking ahead: Development work right now is on rich copy-and-paste abilities, quicker addition of citation templates in references, setting media items' options (such as being able to put images on the left), switching into wikitext mode, and simplifying the toolbar. A significant amount of work is being done on other languages during this month. If you speak a language other than English, you can help with translating the documentation.
I was wondering if you could help me expand this by, oh, 50% or so. There are 10 references right now but choosing what to add has stymied me. FYI, User:Sasata has given some great feedback on the Cucurbita peer review that I am working through. (talk) 00:20, 27 October 2013 (UTC)
Greetings Wikipedia Library members! Welcome to the inaugural edition of Books and Bytes, TWL’s monthly newsletter. We're sending you the first edition of this opt-in newsletter, because you signed up, or applied for a free research account: HighBeam, Credo, Questia, JSTOR, or Cochrane. To receive future updates of Books and Bytes, please add your name to the subscriber's list. There's lots of news this month for the Wikipedia Library, including new accounts, upcoming events, and new ways to get involved...
New positions: Sign up to be a Wikipedia Visiting Scholar, or a Volunteer Wikipedia Librarian
Wikipedia Loves Libraries: Off to a roaring start this fall in the United States: 29 events are planned or have been hosted.
New subscription donations: Cochrane round 2; HighBeam round 8; Questia round 4... Can we partner with NY Times and Lexis-Nexis??
New ideas: OCLC innovations in the works; VisualEditor Reference Dialog Workshop; a photo contest idea emerges
News from the library world: Wikipedian joins the National Archives full time; the Getty Museum releases 4,500 images; CERN goes CC-BY
Announcing WikiProject Open: WikiProject Open kicked off in October, with several brainstorming and co-working sessions
New ways to get involved: Visiting scholar requirements; subject guides; room for library expansion and exploration
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Nepenthes viridis, you added links pointing to the disambiguation pages Dinagat, Lamina and Stewart McPherson (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
VisualEditor's toolbar has a new feature (currently working only in some browsers), "Switch to source editing". By choosing this item, you can move directly into the wikitext source editor without saving. This is particularly useful if you need to make significant changes to tables, image galleries, or other elements that are not currently supported.
Since the last newsletter, the VisualEditor team has worked on some feature changes, major infrastructure improvements to make the system more stable, dependable and extensible, some minor toolbar improvements, and fixing bugs.
A new form parsing library for language characters in Parsoid caused the corruption of pages containing diacritics for about an hour two weeks ago. Relatively few pages at the English Wikipedia were affected, but this created immediate problems at some other Wikipedias, sometimes affecting several dozen pages. The development teams for Parsoid and VisualEditor apologize for the serious disruption and thank the people who reported this emergency at Wikipedia:VisualEditor/Feedback and on the public IRC channel, #mediawiki-visualeditor.
There have been dozens of changes since the last newsletter. Here are some of the highlights:
Accidental deletion of infoboxes and other items: You now need to press the Delete or ← Backspace key twice to delete a template, reference or image. The first time, the item becomes selected, and the second time, it is removed. The need to press the delete key twice should make it more obvious what you are doing and help avoid accidental removals of infoboxes and similar (bug 55336).
Switch from VisualEditor to the wikitext editor: A new feature lets you make a direct, one-way editing interface change, which will preserve your changes without needing to save the page and re-open it in the wikitext editor (bug 50687). It is available in a new menu in the action buttons by the Cancel button (where the "Page Settings" button used to be). Note that this new feature is not currently working in Firefox.
Categories and Languages are also now directly available in that menu. The category suggestions drop-down was appearing in the wrong place rather than below its input box, which is now fixed. An incompatibility between VisualEditor and the deployed Parsoid service that prevented editing categories and language links was fixed.
File:, Help: and Category: namespaces: VisualEditor was enabled for these namespaces the on all wikis (bug 55968), the Portal: and Viquiprojecte: namespaces on the Catalan Wikipedia (bug 56000), and the Portal: and Book: namespaces on the English Wikipedia (bug 56001).
Media item resizing: We improved how files are viewed in a few ways. First, inline media items can now be resized in the same way that has been possible with block ones (like thumbnails) before. When resizing a media item, you can see a live preview of how it will look as you drag it (bug 54298). While you are dragging an image to resize it, we now show a label with the current dimensions (bug 54297). Once you have resized it, we fetch a new, higher resolution image for the media item if necessary (bug 55697). Manual setting of media item sizes in their dialog is nearly complete and should be available next week. If you hold down the ⇧ Shift key whilst resizing an image, it will now snap to a 10 pixel grid instead of the normal free-hand sizing. The media item resize label now is centered while resizing regardless of which tool you use to resize it.
Undo and redo: A number of improvements were made to the transactions system which make undoing and redoing more reliable during real-time collaboration (bug 53224).
Save dialogue: The save page was re-written to use the same code as all other dialogs (bug 48566), and in the process fixed a number of issues. The save dialog is re-accessible if it loses focus (bug 50722), or if you review a null edit (bug 53313); its checkboxes for minor edit, watch the page, and flagged revisions options now layout much more cleanly (bug 52175), and the tab order of the buttons is now closer to what users will expect (bug 51918). There was a bug in the save dialog that caused it to crash if there was an error in loading the page from Parsoid, which is now fixed.
Links to other articles or pages sometimes sent people to invalid pages. VisualEditor now keeps track of the context in which you loaded the page, which lets us fix up links in document to point to the correct place regardless of what entry point you launched the editor from—so the content of pages loaded through /wiki/Foobar?veaction=edit and /w/index.php?title=Foobar&veaction=edit both now have text links that work if triggered (bug 48915).
Toolbar links: A bug that caused the toolbar's menus to get shorter or even blank when scrolled down the page in Firefox is now fixed (bug 55343).
Numbered external links: VisualEditor now supports Parsoid's changed representation of numbered external links (bug 53505).
Removed empty templates: We also fixed an issue that meant that completely empty templates became impossible to interact with inside VisualEditor, as they didn't show up (bug 55810).
Mathematics formulae: If you would like to try the experimental LaTeX mathematics tool in VisualEditor, you will need to opt-in to Beta Features. This is currently available on Meta-wiki, Wikimedia Commons, and Mediawiki.org. It will be available on all other Wikimedia sites on 21 November.
Browser testing support: If you are interested in technical details, the browser tests were expanded to cover some basic cursor operations, which uncovered an issue in our testing framework that doesn't work with cursoring in Firefox; the Chrome tests continue to fail due to a bug with the welcome message for that part of the testing framework.
Load time: VisualEditor now uses content language when fetching Wikipedia:TemplateData information, so reducing bandwidth use, and users on multi-language or multi-script wikis now get TemplateData hinting for templates as they would expect (bug 50888).
Reuse of VisualEditor: Work on spinning out the user experience (UX) framework from VisualEditor into oojs-ui, which lets other teams at Wikimedia (like Flow) and gadget authors re-use VisualEditor UX components, is now complete and is being moved to a shared code repository.
Support for private wikis: If you maintain a private wiki at home or at work, VisualEditor now supports editing of private wikis, by forwarding the Cookie: HTTP header to Parsoid ($wgVisualEditorParsoidForwardCookies set to true) (bug 44483). (Most private wikis will also need to install Parsoid and node.js, as VisualEditor requires them.)
Looking ahead:
VisualEditor will be released to some of the smaller Wikipedias on 02 December 2013. If you are active at one or more smaller Wikipedias where VisualEditor is not yet generally available, please see the list at VisualEditor/Rollouts.
Public office hours on IRCto discuss VisualEditor with Product Manager James Forrester will be held on Monday, 2 December, at 1900 UTC and on Tuesday, 3 December, at 0100 UTC. Bring your questions. Logs will be posted on Meta after each office hour completes.
In terms of feature improvements, one of the major infrastructure projects affects how inserting characters works, both using your computer's built-in Unicode input systems and through a planned character inserter tool for VisualEditor. The forthcoming rich copying and pasting feature was extended and greater testing is currently being done. Work continues to support the improved reference dialog to quickly add citations based on local templates.
whether Superspecies and Artenkreis should be merged. I'm not very familiar with these terms that are mostly used in zoology. There are dictionary definitions accessible online that seem to say that Ring species and Artenkreis are the same, but I wonder if Artenkreis is supposed to be a ring of species, and consequently a superspecies but not a ring species. More investigation needed. I'll look for original sources, since later ones might have muddled things. Sminthopsis84 (talk) 13:00, 5 December 2013 (UTC)
The Wikipedia Library's Books and Bytes newsletter (#2)
Welcome to the second issue of The Wikipedia Library's Books & Bytes newsletter! Read on for updates about what is going on at the intersection of Wikipedia and the library world.
See my post on Zad68's talk page. I want to deeply thank you for all your help and kindness. Too bad there is so much bickering on wikipedia. HalfGigtalk22:04, 12 December 2013 (UTC)
VisualEditor's toolbar has a new drop-down menu that contains all character formatting: bold, italics, subscript, superscript, strikethrough, computer code, underline, and the ability to remove all formatting from text.
For more information about how to use VisualEditor, read the user guide.
Since the last newsletter, the VisualEditor team has worked on some toolbar improvements, fixing bugs, and improving support for Indic languages as well as other languages with complex characters. The current focus is on improving the reference dialog and expanding the new character inserter tool.
There have been dozens of changes since the last newsletter. Here are some of the highlights:
Rich copying and pasting is now available. If you copy text from another website, then character formatting and some other HTML attributes are preserved. This means, for example, that if you copy a pre-formatted suggested citation from a source like this, then VisualEditor will preserve the formatting of the title in the citation. Keep in mind that copying the formatting may include formatting that you don't want (like section headings). If you want to paste plain, unformatted text onto a page, then use Control+⇧ Shift+V or ⌘ Command+⇧ Shift+V (Mac).
Auto-numbered external links like [1] can now be edited just like any other link. However, they cannot be created in VisualEditor easily.
Several changes to the toolbar and dialogs have been made, and more are on the way. The toolbar has been simplified with a new drop-down text styles menu and an "insert" menu. Your feedback on the toolbar is wanted here. The transclusion/template dialog has been simplified. If you have enabled mathematical formula editing, then the menu item is now called the formula editor instead of LaTeX.
There is a new character inserter, which you can find in the new "insert" menu, with a capital Omega ("Ω"). It's a very basic set of characters. Your feedback on the character inserter is wanted here.
Saving the page should seem faster by several seconds now.
It is now possible to access VisualEditor by manually editing the URL, even if you are not logged in or have not opted in to VisualEditor normally. To do so, append ?veaction=edit to the end of the page name. For example, change https://en.wikipedia.org/wiki/Special:Random to https://en.wikipedia.org/wiki/Special:Random?veaction=edit to open a random page in VisualEditor. This is intended to support bug testing across multiple browsers, without requiring editors to login repeatedly.
Looking ahead: The transclusion dialog will see further changes in the coming weeks, with a simple mode for single templates and an advanced mode for more complex transclusions. The new character formatting menu on the toolbar will get an arrow to show that it is a drop-down menu. The reference dialog will be improved, and the Reference item will become a button in the main toolbar, rather than an item in the Insert menu.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Nepenthes robcantleyi, you added a link pointing to the disambiguation page Lamina (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Nepenthes hemsleyana, you added a link pointing to the disambiguation page Parabolic (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
I've decided to try again to make Cucurbita as good as we can. I'll start by going back over the peer review. Any help is greatly appreciated. Thank you again for your long support and superb guidance. Best wishes to you on the New Year. HalfGigtalk13:00, 11 January 2014 (UTC)
Happy New Year, and welcome to a special double issue of Books & Bytes. We've included a retrospective on the changes and progress TWL has seen over the last year, the results of the survey TWL participants completed in December, some of our plans for the future, a second interview with a Wiki Love Libraries coordinator, and more. Here's to 2014 being a year of expansion and innovation for TWL!
The Wikipedia Library completed the first 6 months of its Individual Engagement grant last week. Here's where we are and what we've done:
Increased access to sources: 1500 editors signed up for 3700 free accounts, individually worth over $500,000, with usage increases of 400-600%
Deep networking: Built relationships with Credo, HighBeam, Questia, JSTOR, Cochrane, LexisNexis, EBSCO, New York Times, and OCLC
New pilot projects: Started the Wikipedia Visiting Scholar project to empower university-affiliated Wikipedia researchers
Developed community: Created portal connecting 250 newsletter recipients, 30 library members, 3 volunteer coordinators, and 2 part-time contractors
Tech scoped: Spec'd out a reference tool for linking to full-text sources and established a basis for OAuth integration
Broad outreach: Wrote a feature article for Library Journal's The Digital Shift; presenting at the American Library Association annual meeting
To add templates, go to the "Insert" menu and choose the "Transclusion" (puzzle piece) item. Enter the name of the template and click "Add template". If TemplateData exists for the template, then a list of possible parameters will appear. If not, you can add parameters yourself by typing the parameter name under "Add parameter". For unnamed parameters, use numbers ("1" for the first unnamed parameter).
Since the last newsletter, the VisualEditor team has worked mostly minor features and fixing bugs. A few significant bugs include working around a bug in CSSJanus that was wrongly flipping images used in some templates in right-to-left (RTL) environments (bug 50910) a major bug that meant inserting any template or other transclusion failed (bug 59002), a major but quickly resolved problem due to an unannounced change in MediaWiki core, which caused VisualEditor to crash on trying to save (bug 59867). This last bugs did not appear on any Wikipedia. Additionally, significant work has been done in the background to make VisualEditor work as an independent editing system.
As of today, VisualEditor is now available as an opt-out feature to all users at 149 active Wikipedias.
The character inserter tool in the "Insert" menu has a very basic set of characters. The character inserter is especially important for languages that use Latin and Cyrillic alphabets with unusual characters or frequent diacritics. Your feedback on the character inserter is requested. In addition to feedback from any interested editor, the developers would particularly like to hear from anyone who speaks any of the 50+ languages listed under Phase 5 at mw:VisualEditor/Rollouts, including Breton, Mongolian, Icelandic, Welsh, Afrikaans, Macedonian, and Azerbaijani.
meta:Office hours on IRC have been heavily attended recently. The next one will be held this coming Wednesday, 22 January at 23:00 UTC.
You can now edit some of the page settings in the "options" dialog – __NOTOC__ and __FORCETOC__ as selection (forced on, forced off, or default setting; bugs 56866 and 56867) and __NOEDITSECTION__ as a checkbox (bug 57166).
The automated browser tests were adjusted to speed them up and bind more correctly to list items in lists, and updated to a newer version of their ruby dependencies. You can monitor the automated browser tests' results (triggered every twelve hours) live on the server.
Looking ahead: The character formatting menu on the toolbar will get a drop-down indicator next Thursday. The reference and media items will be the first two listed in the Insert menu. The help menu will get a page listing the keyboard shortcuts. Looking further out, image handling will be improved, including support for alignment (left, right, and center) and better control over image size (including default and upright sizes). The developers are also working on support for editing redirects and image galleries.
See User_talk:Sasata#Cucurbita.23Production_tables. Can you or someone you know help with: An intro to the two new tables (I wrote one but it can probably be improved), removing the source column (I tried and it didn't work), and if and how to combine the tables (note the same 10 countries are not in the tables). HalfGigtalk11:41, 20 January 2014 (UTC)
Congratulations on winning the Natural History Shield
The Natural History Shield
For great service to Wikipedia in the area of Natural History. Your efforts in improving these areas and helping other users is greatly needed and appreciated! HalfGigtalk15:54, 2 February 2014 (UTC)
Thank you! I've been a bit quiet lately but hope to get back into the swing of things soon enough. Great to see you editing again, btw. :-) mgiganteus1 (talk) 23:41, 3 February 2014 (UTC)
You can easily re-use references by going to the Insert menu, choosing "Reference", and clicking on "Use an existing reference" in the lower left corner. A list of all references, their numbers, and their ref names (if any) will be shown. You can search the list for any author, title, date, or other keyword. Read the user guide for more information.
Since the last newsletter, the VisualEditor team has worked on some small changes to the user interface, such as moving the reference item to the top of the Insert menu, as well as some minor features and fixing bugs, especially for rich copying and pasting of references.
The biggest change was the addition of more features to the image dialog, including the ability to set alignment (left, right, center), framing options (thumbnail, frame, frameless, and none), adding alt text, and defining the size manually. There is still some work to be done here, including a quick way to set the default size.
A few bugs in the existing reference dialog were fixed. The toolbar was simplified to remove galleries and lists from the reference dialog. When you re-use references, it now correctly displays the references again, rather than just the number and name. If you paste content into a dialog that can't fit there (e.g. ==section headings== in references), it now strips out the inappropriate HTML.
You can now edit image galleries inside VisualEditor. At this time, the gallery tool is a very limited option that gives you access to the wikitext. It will see significant improvements at a later date.
Any community can ask to test a new tool to edit TemplateData by leaving a note at T53734.
Looking ahead: The link tool will tell you when you're linking to a disambiguation or redirect page. The warning about wikitext will hide itself after you remove the wikitext markup in that paragraph. Support for creating and editing redirects is in the pipeline. Looking further out, image handling will be improved, including default and upright sizes. The developers are also working on support for viewing and editing hidden HTML comments, some behavioral magic words like DISPLAYTITLE, and in-line language setting (dir="rtl").
Donations drive: news on TWL's partnership efforts with publishers
Open Access: Feature from Ocaasi on the intersection of the library and the open access movement
American Library Association Midwinter Conference: TWL attended this year in Philadelphia
Royal Society Opens Access To Journals: The UK's venerable Royal Society will give the public (and Wikipedians) full access to two of their journal titles for two days on March 4th and 5th
Going Global: TWL starts work on pilot projects in other language Wikipedias
The template dialog has been simplified to make it faster and easier to add parameter data. Read the user guide for more information.
Since the last newsletter, the VisualEditor team has mostly worked on changes to the template and image dialogs.
The biggest change in the last few weeks was the redesign of the template dialog. The template dialog now opens in a simplified mode that lists parameters and their descriptions. (The complex multi-item transclusion mode can be reached by clicking on "Show options" from inside the simplified template dialog.) Template parameters now have a bigger, auto-sizing input box for easier editing. With today's update, searching for template parameters will become case-insensitive, and required template parameters will display an asterisk (*) next to their edit boxes. In addition to making it quicker and easier to see everything when you edit typical templates, this work was necessary to prepare for the forthcoming simplified citation dialog. The main priority in the coming weeks is building this new citation dialog, with the ultimate goal of providing autofill features for ISBNs, URLs, DOIs and other quick-fills. This will add a new button on the toolbar, with the citation templates available picked by each wiki's community. Concept drawings can be seen at mw:VisualEditor/Design/Reference Dialog. Please share your ideas about making referencing quick and easy with the designers.
The link tool now tells you when you're linking to a disambiguation or redirect page. Pages that exist, but are not indexed by the search engine, are treated like non-existent pages (T56361).
Wikitext warnings will now hide when you remove wikitext from the paragraph you are editing.
The page options menu (three bars, next to the Cancel button) has expanded. You can create and edit redirect pages, set page options like __STATICREDIRECT__, __[NO]INDEX__ and __[NO]NEWEDITSECTION__, and more. New keyboard shortcuts are listed there, and include undoing the last action, clearing formatting, and showing the shortcut help window. If you switch from VisualEditor to wikitext editing, your edit will now be tagged.
It is easier to edit images. There are more options and they are explained better. If you add new images to pages, they will also be default size. You can now set image sizes to the default, if another size was previously specified. Full support for upright sizing systems, which more readily adapt image sizes to the reader's screen size, is planned.
VisualEditor adds fake blank lines so you can put your cursor there. These "slugs" are now smaller than normal blank lines, and are animated to be different from actual blank lines.
You can use the Ctrl+Alt+S or ⌘ Command+⌥ Option+Sshortcuts to open the save window, and you can preview your edit summary when checking your changes in the save window.
After community requests, VisualEditor has been deployed to the Interlingual Occidental Wikipedia, the Portuguese Wikibooks, and the French Wikiversity.
Any community can ask for custom icons for their language in the character formatting menu (bold, italic, etc.) by making a request on Bugzilla or by contacting Product Manager James Forrester.
The developers apologize for a regression bug with the deployment on 6 March 2014, which caused the incorrect removal of |upright size definitions on a handful of pages on the English Wikipedia, among others. The root cause was fixed, and the broken pages were fixed soon after.
Looking ahead: Several template dialogs will become more compact. Looking further out, the developers are also working on support for viewing and editing hidden HTML comments. You will be able to see the Table of Contents change live as you edit the page, rather than it being hidden. In-line language setting (dir="rtl") may be offered to a few Wikipedias soon.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Selective laser sintering, you added a link pointing to the disambiguation page Sinter (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
You can use VisualEditor to make redirects. First, remove any unwanted content from the page. Then go to the "Page options" menu (next to "⧼visualeditor-toolbar-cancel⧽") and choose the "Page settings" item. Click the box to "Redirect this page to". In the box, type in the name of the page that you want to redirect this page to.
You can also set or remove categories for the redirect in the "Page options" menu. Read the user guide for more information.
Since the last newsletter, the VisualEditor team has mostly worked on performance improvements, image settings, and preparation for a simplified citation template tool in its own menu.
In an oft-requested improvement, VisualEditor now displays red links (links to non-existent pages) in the proper color. Links to sister projects and external URLs are still the same blue as local links.
You can now open templates by double-clicking them or by selecting them and pressing Return. This also works for references, images, galleries, mathematical equations, and other "nodes".
VisualEditor has been disabled for pages that were created as translations of other pages using the Translate extension (common at Meta and MediaWiki.org). If a page has been marked for translation, you will see a warning if you try to edit it using VisualEditor.
When you try to edit protected pages with VisualEditor, the full protection notice and most recent log entry are displayed. Blocked users see the standard message for blocked users.
The developers fixed a bug that caused links on sub-pages to point to the wrong location.
The size-changing controls in the advanced settings section of the media or image dialog were simplified further. VisualEditor's media dialog supports more image display styles, like borderless images.
If there is not enough space on your screen to display all of the tabs (for instance, if your browser window is too narrow), the second edit tab will now fold into the drop-down menu (where the "Move" item is currently housed). On the English Wikipedia, this moves the "Edit beta" tab into the menu; on most projects, it moves the "Edit source" tab. This is only enabled in the default Vector skin, not for Monobook users. See this image for an example showing the "Edit source" and "View history" tabs after they moved into the drop-down menu.
After community requests, VisualEditor has been deployed as an opt-in feature at Meta and on the French Wikinews.
The drop-down menu is on the right, next to the search box.
Looking ahead: A new, locally controlled menu of citation templates will put citations immediately in front of users. You will soon be able to see the Table of Contents while editing. Support for upright image sizes (preferred for accessibility) is being developed. In-line language setting (dir="rtl") will be offered as a Beta Feature soon. Looking further out, the developers are also working on support for viewing and editing hidden HTML comments. It will be possible to upload images to Commons from inside VisualEditor.
The cite menu offers quick access to up to five citation templates. If your wiki has enabled the "⧼visualeditor-toolbar-cite-label⧽" menu, press "⧼visualeditor-toolbar-cite-label⧽" and select the appropriate template from the menu.
Existing citations that use these templates can be edited either using the "⧼visualeditor-toolbar-cite-label⧽" tool or by selecting the reference and choosing the "⧼visualeditor-dialogbutton-reference-tooltip⧽" item in the "Insert" menu.
Since the last newsletter, the VisualEditor team has mostly worked on the new citation tool, improving performance, reducing technical debt, and other infrastructure needs.
The biggest change in the last few weeks is the new citation template menu, labeled "⧼visualeditor-toolbar-cite-label⧽". The new citation menu offers a locally configurable list of citation templates on the main toolbar. It adds or opens references using the simplified template dialog that was deployed last month. This tool is in addition to the "⧼visualeditor-dialogbutton-reference-tooltip⧽" item in the "Insert" menu, and it is not displayed unless it has been configured for that wiki. To enable this tool on your wiki, see the instructions at VisualEditor/Citation tool.
There is a new Beta Feature for setting content language and direction. This allows editors who have opted in to use the "Language" tool in the "Insert" menu to add HTML span tags that label text with the language and as being left-to-right (LTR) or right-to-left (RTL), like this: <span lang="en" dir="ltr">English</span>. This tool is most useful for pages whose text combines multiple languages with different directions, common on Right-to-Left wikis.
The tool for editing mathematics formulae in VisualEditor has been slightly updated and is now available to all users, as the "⧼math-visualeditor-mwmathinspector-title⧽" item in the "Insert" menu. It uses LaTeX like in the wikitext editor.
The layout of template dialogs has been changed, putting the label above the field. Parameters are now called "fields", to avoid a technical term that many editors are unfamiliar with.
TemplateData has been expanded: You can now add "suggested" parameters in TemplateData, and VisualEditor will display them in the template dialogs like required ones. "Suggested" is recommended for parameters that are commonly used, but not actually required to make the template work. There is also a new type for TemplateData parameters: wiki-file-name, for file names. The template tool can now tell you if a parameter is marked as being obsolete.
Some templates that previously displayed strangely due to absolute CSS positioning hacks should now display correctly.
Several messages have changed: The notices shown when you save a page have been merged into those used in the wikitext editor, for consistency. The message shown when you "⧼visualeditor-toolbar-cancel⧽" out of an edit is clearer. The beta dialog notice, which is shown the first time you open VisualEditor, will be hidden for logged-in users via a user preference rather than a cookie. As a result of this change, the beta notice will show up one last time for all logged-in users on their next VisualEditor use after Thursday's upgrade.
Adding a category that is a redirect to another category prompts you to add the target category instead of the redirect.
In the "Images and media" dialog, it is no longer possible to set a redundant border for thumbnail and framed images.
There is a new Template Documentation Editor for TemplateData. You can test it by editing a documentation subpage (not a template page) at Mediawiki.org: edit mw:Template:Sandbox/doc, and then click "Manage template documentation" above the wikitext edit box. If your community would like to use this TemplateData editor at your project, please contact product manager James Forrester or file an enhancement request in Bugzilla.
There have been multiple small changes to the appearance: External links are shown in the same light blue color as in MediaWiki. This is a lighter shade of blue than the internal links. The styling of the "Style text" (character formatting) drop-down menu has been synchronized with the recent font changes to the Vector skin. VisualEditor dialogs, such as the "⧼visualeditor-toolbar-savedialog⧽" dialog, now use a "loading" animation of moving lines, rather than animated GIF images. Other changes were made to the appearance upon opening a page in VisualEditor which should make the transition between reading and editing be smoother.
The developers merged in many minor fixes and improvements to MediaWiki interface integration (e.g., edit notices), and made VisualEditor handle Education Program pages better.
At the request of the community, VisualEditor has been deployed to Commons as an opt-in. It is currently available by default for 161 Wikipedia language editions and by opt-in through Beta Features at all others, as well as on several non-Wikipedia sites.
Looking ahead: The toolbar from the PageTriage extension will no longer be visible inside VisualEditor. More buttons and icons will be accessible from the keyboard. The "Keyboard shortcuts" link will be moved out of the "Page options" menu, into the "Help" menu. Support for upright image sizes (preferred for accessibility) and inline images is being developed. You will be able to see the Table of Contents while editing. Looking further out, the developers are also working on support for viewing and editing hidden HTML comments. VisualEditor will be available to all users on mobile devices and tablet computers. It will be possible to upload images to Commons from inside VisualEditor.
In this edit of Petiole (botany), you inserted {{for|the moth genus|Phyllodes (moth)}}. Why? Is there a citation for this genus having ever been known as Petiole? (A Google search reveals that it is Eublemma amoena that has the common name "petiole moth"). Why did you not instead use {{for|the constricted segment in some ant species|Petiole (insect anatomy)}}? I will look for your response here. —Anomalocaris (talk) 23:09, 5 June 2014 (UTC)
The Wikipedia Library: New Account Coordinators Needed
Hi Books & Bytes recipients: The Wikipedia Library has been expanding rapidly and we need some help! We currently have 10 signups for free account access open and several more in the works... In order to help with those signups, distribute access codes, and manage accounts we'll need 2-3 more Account Coordinators.
It takes about an hour to get up and running and then only takes a couple hours per week, flexible depending upon your schedule and routine. If you're interested in helping out, please drop a note in the next week at my talk page or shoot me an email at: jorlowitzgmail.com. Thanks and cheers, Jake Ocaasi via MediaWiki message delivery (talk) 23:41, 20 June 2014 (UTC)
The character formatting menu, or "Style text" menu lets you set bold, italic, and other text styles. "Clear formatting" removes all text styles and removes links to other pages.
Do you think that clear formatting should remove links? Are there changes you would like to see for this menu? Share your opinion at MediaWiki.org.
The user guide has information about how to use VisualEditor.
The VisualEditor team is mostly working to fix bugs, improve performance, reduce technical debt, and other infrastructure needs. You can find on Mediawiki.org weekly updates detailing recent work.
They have moved the "Keyboard shortcuts" link out of the "Page options" menu, into the "Help" menu. Within dialog boxes, buttons are now more accessible (via the Tab key) from the keyboard.
You can now see the target of the link when you click on it, without having to open the inspector.
The team also expanded TemplateData: You can now add a parameter type "date" for dates and times in the ISO 8601 format, and "boolean" for values which are true or false. Also, templates that redirect to other templates (like {{citeweb}} → {{cite web}}) now get the TemplateData of their target (bug 50964). You can test TemplateData by editing mw:Template:Sandbox/doc.
Category: and File: pages now display their contents correctly after saving an edit (bug 65349, bug 64239)
They have also improved reference editing: You should no longer be able to add empty citations with VisualEditor (bug 64715), as with references. When you edit a reference, you can now empty it and click the "use an existing reference" button to replace it with another reference instead.
It is now possible to edit inline images with VisualEditor. Remember that inline images cannot display captions, so existing captions get removed. Many other bugs related to images were also fixed.
You can now add and edit {{DISPLAYTITLE}} and __DISAMBIG__ in the "Page options" menu, rounding out the full set of page options currently planned.
The tool to insert special characters is now wider and simpler.
Looking ahead
The VisualEditor team has posted a draft of their goals for the next fiscal year. You can read them and suggest changes on MediaWiki.org.
The team posts details about planned work on VisualEditor's roadmap. You will soon be able to drag-and-drop text as well as images. If you drag an image to a new place, it won't let you place it in the middle of a paragraph. All dialog boxes and windows will be simplified based on user testing and feedback. The VisualEditor team plans to add autofill features for citations. Your ideas about making referencing quick and easy are still wanted. Support for upright image sizes is being developed. The designers are also working on support for viewing and editing hidden HTML comments and adding rows and columns to tables.
Supporting your wiki
Please read VisualEditor/Citation tool for information on configuring the new citation template menu, labeled "⧼visualeditor-toolbar-cite-label⧽". This menu will not appear unless it has been configured on your wiki.
If you speak a language other than English, we need your help with translating the user guide. The guide is out of date or incomplete for many languages, and what's on your wiki may not be the most recent translation. Please contact me if you need help getting started with translation work on MediaWiki.org.
VisualEditor can be made available to most non-Wikipedia projects. If your community would like to test VisualEditor, please contact product manager James Forrester or file an enhancement request in Bugzilla.
Please share your questions, suggestions, or problems by posting a note at mw:VisualEditor/Feedback or by joining the office hours on Saturday, 19 July 2014 at 21:00 UTC (daytime for the Americas and Pacific Islands) or on Thursday, 14 August 2014 at 9:00 UTC (daytime for Europe, Middle East, Asia).
The VisualEditor team is currently working mostly to fix bugs, improve performance, reduce technical debt, and other infrastructure needs. You can find on Mediawiki.org weekly updates detailing recent work.
Dialog boxes in VisualEditor have been re-designed to use action words instead of icons. This has increased the number of items that need to be translated. The user guide is also being updated.
The biggest visible change since the last newsletter was to the dialog boxes. The design for each dialog box and window was simplified. The most commonly needed buttons are now at the top. Based on user feedback, the buttons are now labeled with simple words (like "Cancel" or "Done") instead of potentially confusing icons (like "<" or "X"). Many of the buttons to edit links, images, and other items now also show the linked page, image name, or other useful information when you click on them.
Hidden HTML comments (notes visible to editors, but not to readers) can now be read, edited, inserted, and removed. A small icon (a white exclamation mark on a dot) marks the location of each comments. You can click on the icon to see the comment.
You can now drag and drop text and templates as well as images. A new placement line makes it much easier to see where you are dropping the item. Images can no longer be dropped into the middle of paragraphs.
All references and footnotes (<ref> tags) are now made through the "⧼visualeditor-toolbar-cite-label⧽" menu, including the "⧼visualeditor-dialogbutton-reference-tooltip⧽" (manual formatting) footnotes and the ability to re-use an existing citation, both of which were previously accessible only through the "Insert" menu. The "⧼visualeditor-dialogbutton-referencelist-tooltip⧽" is still added via the "Insert" menu.
When you add an image or other media file, you are now prompted to add an image caption immediately. You can also replace an image whilst keeping the original caption and other settings.
All tablet users visiting the mobile web version of Wikipedias will be able to opt-in to a version of VisualEditor from 14 August. You can test the new tool by choosing the beta version of the mobile view in the Settings menu.
The link tool has a new "Open" button that will open a linked page in another tab so you can make sure a link is the right one.
The "Cancel" button in the toolbar has been removed based on user testing. To cancel any edit, you can leave the page by clicking the Read tab, the back button in your browser, or closing the browser window without saving your changes.
Looking ahead
The team posts details about planned work on the VisualEditor roadmap. The VisualEditor team plans to add auto-fill features for citations soon. Your ideas about making referencing quick and easy are still wanted. Support for upright image sizes is being developed. The designers are also working on support for adding rows and columns to tables. Work to support Internet Explorer is ongoing.
Feedback opportunities
The Editing team will be making two presentations this weekend at Wikimania in London. The first is with product manager James Forrester and developer Trevor Parscal on Saturday at 16:30. The second is with developers Roan Kattouw and Trevor Parscal on Sunday at 12:30.
Please share your questions, suggestions, or problems by posting a note at the VisualEditor feedback page or by joining the office hours discussion on Thursday, 14 August 2014 at 09:00 UTC (daytime for Europe, Middle East and Asia) or on Thursday, 18 September 2014 at 16:00 UTC (daytime for the Americas; evening for Europe).
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited List of giant squid specimens and sightings, you added a link pointing to the disambiguation page Buccal. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
I don't think it was necessary to undo the hyphenation change. WP:QUOTE says "Exceptions are trivial spelling or typographical errors that obviously do not affect the intended meaning; these may be silently corrected ..." Happy editing! Christhe spelleryack14:07, 25 August 2014 (UTC)
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Nepenthes abgracilis, you added a link pointing to the disambiguation page Type locality. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
VisualEditor newsletter—September and October 2014
Did you know?
TemplateData is a separate program that organizes information about the parameters that can be used in a template. VisualEditor reads that data, and uses it to populate its simplified template dialogs.
With the new TemplateData editor, it is easier to add information about parameters, because the ones you need to use are pre-loaded.
Since the last newsletter, the Editing team has reduced technical debt, simplified some workflows for template and citation editing, made major progress on Internet Explorer support, and fixed over 125 bugs and requests. Several performance improvements were made, especially to the system around re-using references and reference lists. Weekly updates are posted on Mediawiki.org.
There were three issues that required urgent fixes: a deployment error that meant that many buttons didn't work correctly (bugs 69856 and 69864), a problem with edit conflicts that left the editor with nowhere to go (bug 69150), and a problem in Internet Explorer 11 that caused replaced some categories with a link to the system message, MediaWiki:Badtitletext (bug 70894) when you saved. The developers apologize for the disruption, and thank the people who reported these problems quickly.
Increased support for devices and browsers
Internet Explorer 10 and 11 users now have access to VisualEditor. This means that about 5% of Wikimedia's users will now get an "Edit" tab alongside the existing "Edit source" tab. Support for Internet Explorer 9 is planned for the future.
Tablet users browsing the site's mobile mode now have the option of using a mobile-specific form of VisualEditor. More editing tools, and availability of VisualEditor on smartphones, is planned for the future. The mobile version of VisualEditor was tweaked to show the context menu for citations instead of basic references (bug 68897). A bug that broke the editor in iOS was corrected and released early (bug 68949). For mobile tablet users, three bugs related to scrolling were fixed (bug 66697, bug 68828, bug 69630). You can use VisualEditor on the mobile version of Wikipedia from your tablet by clicking on the cog in the top-right when editing a page and choosing which editor to use.
TemplateData editor
A tool for editing TemplateData will be deployed to more Wikipedias soon. Other Wikipedias and some other projects may receive access next month. This tool makes it easier to add TemplateData to the template's documentation. When the tool is enabled, it will add a button above every editing window for a template (including documentation subpages). To use it, edit the template or a subpage, and then click the "Edit template data" button at the top. Read the help page for TemplateData. You can test the TemplateData editor in a sandbox at Mediawiki.org. Remember that TemplateData should be placed either on a documentation subpage or on the template page itself. Only one block of TemplateData will be used per template.
Other changes
Several interface messages and labels were changed to be simpler, clearer, or shorter, based on feedback from translators and editors. The formatting of dialogs was changed, and more changes to the appearance will be coming soon, when VisualEditor implements the new MediaWiki theme from Design. (A preview of the theme is available on Labs for developers.) The team also made some improvements for users of the Monobook skin that improved the size of text in toolbars and fixed selections that overlapped menus.
VisualEditor-MediaWiki now supplies the mw-redirect or mw-disambig class on links to redirects and disambiguation pages, so that user gadgets that colour in these in types of links can be created.
Templates' fields can be marked as 'required' in TemplateData. If a parameter is marked as required, then you cannot delete that field when you add a new template or edit an existing one (bug 60358).
Language support improved by making annotations use bi-directional isolation (so they display correctly with cursoring behaviour as expected) and by fixing a bug that crashed VisualEditor when trying to edit a page with a dir attribute but no lang set (bug 69955).
The team is also working on support for adding rows and columns to tables, and early work for this may appear within the month. Please comment on the design at Mediawiki.org.
In the future, real-time collaborative editing may be possible in VisualEditor. Some early preparatory work for this was recently done.
Supporting your wiki
At Wikimania, several developers gave presentations about VisualEditor. A translation sprint focused on improving access to VisualEditor was supported by many people. Deryck Chan was the top translator. Special honors also go to संजीव कुमार (Sanjeev Kumar), Robby, Takot, Bachounda, Bjankuloski06 and Ата. A summary of the work achieved by the translation community has been posted here. Thank you all for your work.
VisualEditor can be made available to most non-Wikipedia projects. If your community would like to test VisualEditor, please contact product manager James Forrester or file an enhancement request in Bugzilla.
Please join the office hours on Saturday, 18 October 2014 at 18:00 UTC (daytime for the Americas; evening for Africa and Europe) and on Wednesday, 19 November at 16:00 UTC on IRC.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Nepenthes viridis, you added a link pointing to the disambiguation page Dinagat. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Highbeam: 100+ remaining accounts for newspaper and magazine archives
Questia: 100+ remaining accounts for journal and social science articles
JSTOR: 100+ remaining accounts for journal archives
Do better research and help expand the use of high quality references across Wikipedia projects: sign up today!
--The Wikipedia Library Team 23:25, 5 November 2014 (UTC)
You can host and coordinate signups for a Wikipedia Library branch in your own language. Please contact Ocaasi (WMF).
VisualEditor is also available on the mobile version of Wikipedia. Login and click the pencil icon to open the page you want to edit. Click on the gear-shaped settings in the upper-right corner, to pick which editor to use. Choose "Edit" to use VisualEditor, or "Edit source" to use the wikitext editor.
It will remember whether you used wikitext or VisualEditor, and use the same editor the next time you edit an article.
The user guide has information about how to use VisualEditor. Not all features are available in Mobile Web.
Since the last newsletter, the Editing Team has fixed many bugs and requests, and worked on support for editing tables and for using non-Latin languages. Their weekly updates are posted on Mediawiki.org. Informal notes from the recent quarterly review were posted on Meta.
Recent improvements
The French Wikipedia should see better search results for links, templates, and media because the new search engine was turned on for everyone there. This change is expected at the Chinese and German Wikipedias next week, and eventually at the English Wikipedia.
The "pawn" system has been mostly replaced. Bugs in this system sometimes added a chess pawn character to wikitext. The replacement provides better support for non-Latin languages, with full support hopefully coming soon.
VisualEditor is now provided to editors who use Internet Explorer 10 or 11 on desktop and mobile devices. Internet Explorer 9 is not supported yet.
The keyboard shortcuts for items in the toolbar's menus are now shown in the menus. VisualEditor will replace the existing design with a new theme from the User Experience / Design group. The appearance of dialogs has already changed in one Mobile version. The appearance on desktops will change soon. (You can see a developer preview of the old "Apex" design and the new "MediaWiki" theme which will replace it.)
Several bugs were fixed for internal and external links. Improvements to MediaWiki's search solved an annoying problem: If you searched for the full name of the page or file that you wanted to link, sometimes the search program could not find the page. A link inside a template, to a local page that does not exist, will now show red, exactly as it does when reading the page. Due to a error, for about two weeks this also affected all external links inside templates. Opening an auto-numbered link node like [2] with the keyboard used to open the wrong link tool. These problems have all been fixed.
TemplateData
The tool for quickly editing TemplateData will be deployed to all Wikimedia Foundation wikis on Thursday, 6 November. This tool is already available on the biggest 40 Wikipedias, and now all wikis will have access to it. This tool makes it easier to add TemplateData to the template's documentation. When the tool is enabled, it will add a button above every editing window for a template (including documentation subpages). To use it, edit the template or a subpage, and then click the "Edit template data" button at the top. Read the help page for TemplateData. You can test the TemplateData editor in a sandbox at Mediawiki.org. Remember that TemplateData should be placed either on a documentation subpage or on the template page itself. Only one block of TemplateData will be used per template.
You can use the new autovalue setting to pre-load a value into a template. This can be used to substitute dates, as in this example, or to add the most common response for that parameter. The autovalue can be easily overridden by the editor, by typing something else in the field.
In TemplateData, you may define a parameter as "required". The template dialog in VisualEditor will warn editors if they leave a "required" parameter empty, and they will not be able to delete that parameter. If the template can function without this parameter, then please mark it as "suggested" or "optional" in TemplateData instead.
Looking ahead
Basic support for inserting tables and changing the number of rows and columns in tables will appear next Wednesday. Advanced features, like dragging columns to different places, will be possible later. The VisualEditor team plans to add auto-fill featuresfor citations soon. To help editors find the most important items more quickly, some items in the toolbar menus will be hidden behind a "More" item, such as "underlining" in the styling menu. The appearance of the media search dialog will improve, to make picking between possible images easier and more visual. The team posts details about planned work on the VisualEditor roadmap.
The user guide will be updated soon to add information about editing tables. The translations for most languages except Spanish, French, and Dutch are significantly out of date. Please help complete the current translations for users who speak your language. Talk to us if you need help exporting the translated guide to your wiki.
You can influence VisualEditor's design. Tell the VisualEditor team what you want changed during the office hours via IRC. The next sessions are on Wednesday, 19 November at 16:00 UTC and on Wednesday 7 January 2015 at 22:00 UTC. You can also share your ideas at mw:VisualEditor/Feedback.
Also, user experience researcherAbbey Ripstra is looking for editors to show her how they edit Wikipedia. Please sign up for the research program if you would like to hear about opportunities.
If you would like to help with translations of this newsletter, please subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Subscribe or unsubscribe at Wikipedia:VisualEditor/Newsletter. Thank you!
Hi. I started editing again yesterday. I made 2 new short articles, started a third, and then User:Sminthopsis84 asked me if I wanted to help get Cucurbita to FA. She and User:CorinneSD are helping. I'd like Sminthopsis84 to get official credit for it. I was wondering if you could help too. I guess some sort of precheck would be warranted. Nice to chat again and hope you can help out. CorinneSD is a very good copyeditor. I suggested she ask Sasata for input on what to look for. Let's coordinate the talk at Talk:Cucurbita. HalfGigtalk13:43, 9 November 2014 (UTC)
Other partnerships with accounts available are listed on our partners page. Do better research and help expand the use of high quality references across Wikipedia projects: sign up today!
--The Wikipedia Library Team.00:25, 18 December 2014 (UTC)
You can host and coordinate signups for a Wikipedia Library branch in your own language. Please contact Ocaasi (WMF).
Basic table editing is now available in VisualEditor. You can add and remove rows and columns from existing tables at the click of a button.
The user guide has more information about how to use VisualEditor.
Since the last newsletter, the Editing Team has fixed many bugs and worked on table editing and performance. Their weekly status reports are posted on Mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.
VisualEditor was deployed to several hundred remaining wikis as an opt-in beta feature at the end of November, except for most Wiktionaries (which depend heavily upon templates) and all Wikisources (which await integration with ProofreadPage).
Recent improvements
Basic support for editing tables is available. You can insert new tables, add and remove rows and columns, set or remove a caption for a table, and merge cells together. To change the contents of a cell, double-click inside it. More features will be added in the coming months. In addition, VisualEditor now ignores broken, invalid rowspan and colspan elements, instead of trying to repair them.
You can now use find and replace in VisualEditor, reachable through the tool menu or by pressing ⌃ Ctrl+F or ⌘ Cmd+F.
You can now create and edit simple <blockquote> paragraphs for quoting and indenting content. This changes a "Paragraph" into a "Block quote".
Some new keyboard sequences can be used to format content. At the start of the line, typing "* " will make the line a bullet list; "1. " or "# " will make it a numbered list; "==" will make it a section heading; ": " will make it a blockquote. If you didn't mean to use these tools, you can press undo to undo the formatting change. There are also two other keyboard sequences: "[[" for opening the link tool, and "{{" for opening the template tool, to help experienced editors. The existing standard keyboard shortcuts, like ⌃ Ctrl+K to open the link editor, still work.
If you add a category that has been redirected, then VisualEditor now adds its target. Categories without description pages show up as red.
You can again create and edit galleries as wikitext code.
Looking ahead
VisualEditor will replace the existing design with a new theme designed by the User Experience group. The new theme will be visible for desktop systems at MediaWiki.org in late December and at other sites early January. (You can see a developer preview of the old "Apex" theme and the new "MediaWiki" one which will replace it.)
The Editing team plans to add auto-fill featuresfor citations in January. Planned changes to the media search dialog will make choosing between possible images easier.
Translations of the user guide for most languages are oudated. Ukrainian, Portuguese, Spanish, French, and Dutch translators are nearly current. Please help complete the current translations for users who speak your language.
Talk to the Editing team during the office hours via IRC. The next session is on Wednesday, 7 January 2015 at 22:00 UTC.
File requests for language-appropriate "Bold" and "Italic" icons for the character formatting menu in Phabricator.
If you would like to help with translations of this newsletter, please subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Subscribe or unsubscribe at Meta.
Replaceable fair use File:Fischeripollis pollen.jpg
Thanks for uploading File:Fischeripollis pollen.jpg. I noticed that this file is being used under a claim of fair use. However, I think that the way it is being used fails the first non-free content criterion. This criterion states that files used under claims of fair use may have no free equivalent; in other words, if the file could be adequately covered by a freely-licensed file or by text alone, then it may not be used on Wikipedia. If you believe this file is not replaceable, please:
Go to the file description page and add the text {{di-replaceable fair use disputed|<your reason>}}below the original replaceable fair use template, replacing <your reason> with a short explanation of why the file is not replaceable.
On the file discussion page, write a full explanation of why you believe the file is not replaceable.
If you have uploaded other non-free media, consider checking that you have specified how these media fully satisfy our non-free content criteria. You can find a list of description pages you have edited by clicking on this link. Note that even if you follow steps 1 and 2 above, non-free media which could be replaced by freely licensed alternatives will be deleted 2 days after this notification (7 days if uploaded before 13 July 2006), per the non-free content policy. If you have any questions, please ask them at the Media copyright questions page. Thank you. Stefan2 (talk) 23:13, 28 December 2014 (UTC)
It is finally there! Your input and review would be greatly appreciated. I can never thank you enough for helping me get started here. The main reason I got serious about editing was to improve this article. HalfGigtalk00:16, 1 January 2015 (UTC)
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that you've added some links pointing to disambiguation pages. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
New donations, including real-paper-and-everything books, e-books, science journal databases, and more
New TWL coordinators, conference news, a new open-access journal database, summary of library-related WMF grants, and more
Spotlight: "Global Impact: The Wikipedia Library and Persian Wikipedia" - a Persian Wikipedia editor talks about their experiences with database access in Iran, writing on the Persian project and the JSTOR partnership
Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's appearance, the coming Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.
The Wikimedia Foundation has named its top priorities for this quarter (January to March). The first priority is making VisualEditor ready for deployment by default to all new users and logged-out users at the remaining large Wikipedias. You can help identify these requirements. There will be weekly triage meetings which will be open to volunteers beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC). Tell Vice President of Engineering Damon Sicore, Product Manager James Forrester and other team members which bugs and features are most important to you. The decisions made at these meetings will determine what work is necessary for this quarter's goal of making VisualEditor ready for deployment to new users. The presence of volunteers who enjoy contributing MediaWiki code is particularly appreciated. Information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins.
Due to some breaking changes in MobileFrontend and VisualEditor, VisualEditor was not working correctly on the mobile site for a couple of days in early January. The teams apologize for the problem.
Recent improvements
The new design for VisualEditor aligns with MediaWiki's Front-End Standards as led by the Design team. Several new versions of the OOjs UI library have also been released, and these also affect the appearance of VisualEditor and other MediaWiki software extensions. Most changes were minor, like changing the text size and the amount of white space in some windows. Buttons are consistently color-coded to indicate whether the action:
starts a new task, like opening the ⧼visualeditor-toolbar-savedialog⧽ dialog: blue ,
takes a constructive action, like inserting a citation: green ,
might remove or lose your work, like removing a link: red , or
is neutral, like opening a link in a new browser window: gray.
The TemplateData editor has been completely re-written to use a different design (T67815) based on the same OOjs UI system as VisualEditor (T73746). This change fixed a couple of existing bugs (T73077 and T73078) and improved usability.
Search and replace in long documents is now faster. It does not highlight every occurrence if there are more than 100 on-screen at once (T78234).
Editors at the Hebrew and Russian Wikipedias requested the ability to use VisualEditor in the "Article Incubator" or drafts namespace (T86688, T87027). If your community would like VisualEditor enabled on another namespace on your wiki, then you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
Looking ahead
The Editing team will soon add auto-fill featuresfor citations. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to contribute to the Citoid service's definitions for each website, to improve precision and reduce the need for manual corrections.
We will need editors to help test the new design of the special character inserter, especially if you speak Welsh, Breton, or another language that uses diacritics or special characters extensively. The new version should be available for testing next week. Please contact User:Whatamidoing (WMF) if you would like to be notified when the new version is available. After the special character tool is completed, VisualEditor will be deployed to all users at Phase 5 Wikipedias. This will affect about 50 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh. The date for this change has not been determined.
Join the weekly bug triage meetings beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC). Information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins. Contact James F. for more information.
Talk to the Editing team during the office hours via IRC. The next session is on Thursday, 19 February 2015 at 19:00 UTC.
Thanks for uploading File:Alien 2 poster.jpg. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
With Citoid in VisualEditor, you click the 'book with bookmark' icon and paste in the URL for a reliable source:
Citoid looks up the source for you and returns the citation results. Click the green "Insert" button to accept its results and add them to the article:
After inserting the citation, you can change it. Select the reference, and click the "Edit" button in the context menu to make changes.
The user guide has more information about how to use VisualEditor.
Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's performance, the Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.
The weekly task triage meetings continue to be open to volunteers, each Wednesday at 11:00 (noon) PDT (18:00 UTC). You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug. Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal.
Recent improvements
VisualEditor is now substantially faster. In many cases, opening the page in VisualEditor is now faster than opening it in the wikitext editor. The new system has improved the code speed by 37% and network speed by almost 40%.
The Editing team is slowly adding auto-fill featuresfor citations. This is currently available only at the French, Italian, and English Wikipedias. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to improve precision and reduce the need for manual corrections by contributing to the Citoid service's definitions for each website.
Citoid requires good TemplateData for your citation templates. If you would like to request this feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
The special character inserter has been improved, based upon feedback from active users. After this, VisualEditor was made available to all users of Wikipedias on the Phase 5 list on 30 March. This affected 53 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh.
Work continues to support languages with complex requirements, such as Korean and Japanese. These languages use input method editors ("IMEs”). Recent improvements to cursoring, backspace, and delete behavior will simplify typing in VisualEditor for these users.
The design for the image selection process is now using a "masonry fit" model. Images in the search results are displayed at the same height but at variable widths, similar to bricks of different sizes in a masonry wall, or the "packed" mode in image galleries. This style helps you find the right image by making it easier to see more details in images.
You can now drag and drop categories to re-arrange their order of appearance on the page.
The pop-up window that appears when you click on a reference, image, link, or other element, is called the "context menu". It now displays additional useful information, such as the destination of the link or the image's filename. The team has also added an explicit "Edit" button in the context menu, which helps new editors open the tool to change the item.
Invisible templates are marked by a puzzle piece icon so they can be interacted with. Users also will be able to see and edit HTML anchors now in section headings.
Users of the TemplateData GUI editor can now set a string as an optional text for the 'deprecated' property in addition to boolean value, which lets you tell users of the template what they should do instead (T90734).
Looking ahead
The special character inserter in VisualEditor will soon use the same special character list as the wikitext editor. Admins at each wiki will also have the option of creating a custom section for frequently used characters at the top of the list. Instructions for customizing the list will be posted at mediawiki.org.
The team is discussing a test of VisualEditor with new users, to see whether they have met their goals of making VisualEditor suitable for those editors. The timing is unknown, but might be relatively soon.
Can you translate from English into any other language? Please check this list to see whether more interface translations are needed for your language. Contact us to get an account if you want to help!
File requests for language-appropriate "Bold" and "Italic" icons for the character formatting menu in Phabricator.
Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
Hello Books & Bytes subscribers. There is a new Visual Editor reference feature in development called Citoid. It is designed to "auto-fill" references using a URL or DOI. We would really appreciate you testing whether TWL partners' references work in Citoid. Sharing your results will help the developers fix bugs and improve the system. If you have a few minutes, please visit the testing page for simple instructions on how to try this new tool. Regards, MediaWiki message delivery (talk) 18:47, 10 April 2015 (UTC)
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Nepenthes ramos, you added a link pointing to the disambiguation page Surigao. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
When you click on a link to an article, you now see more information:
The link tool has been re-designed:
There are separate tabs for linking to internal and external pages.
The user guide has more information about how to use VisualEditor.
Since the last newsletter, the Editing Team has created new interfaces for the link and citation tools, as well as fixing many bugs and changing some elements of the design. Some of these bugs affected users of VisualEditor on mobile devices. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.
A test of VisualEditor's effect on new editors at the English Wikipedia has just completed the first phase. During this test, half of newly registered editors had VisualEditor automatically enabled, and half did not. The main goal of the study is to learn which group was more likely to save an edit and to make productive, unreverted edits. Initial results will be posted at Meta later this month.
Recent improvements
Auto-fill featuresfor citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now created inside a single tool. Inside that tool, choose the tab you want (⧼citoid-citeFromIDDialog-mode-auto⧽, ⧼citoid-citeFromIDDialog-mode-manual⧽, or ⧼citoid-citeFromIDDialog-mode-reuse⧽). The cite button is now labeled with the word "⧼visualeditor-toolbar-cite-label⧽" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "⧼Citoid-citeFromIDDialog-lookup-button⧽", for the submit button.
The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and/or appropriate icons for disambiguation pages, redirect pages and empty pages. Search results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appeared over the first match in the link inspector (T98085).
The special character inserter in VisualEditor now uses the same special character list as the wikitext editor. Admins at each wiki can also create a custom section for frequently used characters at the top of the list. Please read the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing each character in the special character inserter (T70425).
Several improvements have been made to templates. When you search for a template to insert, the list of results now contains descriptions of the templates. The parameter list inside the template dialog now remains open after inserting a parameter from the list, so that users don’t need to click on "⧼visualeditor-dialog-transclusion-add-param⧽" each time they want to add another parameter (T95696). The team added a new property for TemplateData, "Example", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter (T53049).
The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design feature is being used for the cite button on wikis where the Citoid service is enabled.
The team has released a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.
The weekly task triage meetings continue to be open to volunteers, each Wednesday at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal. You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug.
If your Wikivoyage, Wikibooks, Wikiversity, or other community wants to have VisualEditor made available by default to contributors, then please contact James Forrester.
If you would like to request the Citoid automatic reference feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you! Whatamidoing (WMF) (talk) 17:31, 6 June 2015 (UTC)
The Wikipedia Library is expanding, and we need your help! With only a couple of hours per week, you can make a big difference in helping editors get access to reliable sources and other resources. Sign up for one of the following roles:
Account coordinators help distribute research accounts to editors.
Partner coordinators seek donations from new partners.
Outreach coordinators reach out to the community through blog posts, social media, and newsletters or notifications.
Technical coordinators advise on building tools to support the library's work.
Replaceable fair use File:St augustine monster locations.jpg
Thanks for uploading File:St augustine monster locations.jpg. I noticed that this file is being used under a claim of fair use. However, I think that the way it is being used fails the first non-free content criterion. This criterion states that files used under claims of fair use may have no free equivalent; in other words, if the file could be adequately covered by a freely-licensed file or by text alone, then it may not be used on Wikipedia. If you believe this file is not replaceable, please:
Go to the file description page and add the text {{di-replaceable fair use disputed|<your reason>}}below the original replaceable fair use template, replacing <your reason> with a short explanation of why the file is not replaceable.
On the file discussion page, write a full explanation of why you believe the file is not replaceable.
If you have uploaded other non-free media, consider checking that you have specified how these media fully satisfy our non-free content criteria. You can find a list of description pages you have edited by clicking on this link. Note that even if you follow steps 1 and 2 above, non-free media which could be replaced by freely licensed alternatives will be deleted 2 days after this notification (7 days if uploaded before 13 July 2006), per the non-free content policy. If you have any questions, please ask them at the Media copyright questions page. Thank you. Josh Milburn (talk) 18:00, 23 June 2015 (UTC)
You can add quotations marks before and after a title or phrase with a single click.
Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar).
Click the button. VisualEditor will add the quotation marks on either side of the text you selected.
You can read and help translate the user guide, which has more information about how to use VisualEditor.
Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.
Wikimania
The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.
Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.
For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).
For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).
We published some graphs showing the effect of the event on the Translathon page. Thank you to the translators for participating and the translatewiki.net staff for facilitating this initiative.
Recent improvements
Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.
Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top.
In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.
Future changes
The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.
On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.
Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help.
If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
Please file requests for language-appropriate "Bold" and "Italic" icons for the styling menu in Phabricator.
The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Nepenthes halmahera, you added a link pointing to the disambiguation page Isotype. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
The location of the visual editor's preference has been changed from the "Beta" tab to the "Editing" section of your preferences on this wiki. The setting now says Temporarily disable the visual editor while it is in beta.
This aligns en.wiki with almost all the other WMF wikis; it doesn’t mean the visual editor is complete, or that it is no longer “in beta phase” though.
This action has not changed anything else for editors: it still honours editors’ previous choices about having it on or off; logged-out users continue to only have access to wikitext; the “Edit” tab is still after the “Edit source” one. You can learn more at the visual editor’s talk page.
We don’t expect this to cause any glitches, but in case your account no longer has the settings that you want, please accept our apologies and correct it in the Editing tab of Special:Preferences. Thank you for your attention, Elitre (WMF) -16:32, 7 October 2015 (UTC)
Disputed non-free use rationale for File:Megalocranchia fisheri.jpg
Thank you for uploading File:Megalocranchia fisheri.jpg. However, there is a concern that the rationale provided for using this file on Wikipedia may not meet the criteria required by Wikipedia:Non-free content. This can be corrected by going to the file description page and adding or clarifying the reason why the file qualifies under this policy. Adding and completing one of the templates available from Wikipedia:Non-free use rationale guideline is an easy way to ensure that your file is in compliance with Wikipedia policy. Please be aware that a non-free use rationale is not the same as an image copyright tag; descriptions for files used under the non-free content policy require both a copyright tag and a non-free use rationale.
You can use the visual editor on smartphones and tablets.
Click the pencil icon to open the editor for a page. Inside that, use the gear menu in the upper right corner to "Switch to visual editing".
The editing button will remember which editing environment you used last time, and give you the same one next time. The desktop site will be switching to a system similar to this one in the coming months.
You can read and help translate the user guide, which has more information about how to use the visual editor.
Since the last newsletter, the VisualEditor Team has fixed many bugs, added new features, and made some small design changes. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving support for languages like Japanese and Arabic, making it easier to edit on mobile devices, and providing rich-media tools for formulæ, charts, galleries and uploading.
Recent improvements
Educational features: The first time you use the visual editor, it now draws your attention to the Link and ⧼visualeditor-toolbar-cite-label⧽ tools. When you click on the tools, it explains why you should use them. (T108620) Alongside this, the welcome message for new users has been simplified to make editing more welcoming. (T112354) More in-software educational features are planned.
Links: It is now easier to understand when you are adding text to a link and when you are typing plain text next to it. (T74108, T91285) The editor now fully supports ISBN, PMID or RFC numbers. (T109498, T110347, T63558) These "magic links" use a custom link editing tool.
Uploads: Registered editors can now upload images and other media to Commons while editing. Click the new tab in the "Insert Images and media" tool. You will be guided through the process without having to leave your edit. At the end, the image will be inserted. This tool is limited to one file at a time, owned by the user, and licensed under Commons's standard license. For more complex situations, the tool links to more advanced upload tools. You can also drag the image into the editor. This will be available in the wikitext editor later.
Mobile: Previously, the visual editor was available on the mobile Wikipedia site only on tablets. Now, editors can use the visual editor on any size of device. (T85630) Edit conflicts were previously broken on the mobile website. Edit conflicts can now be resolved in both wikitext and visual editors. (T111894) Sometimes templates and similar items could not be deleted on the mobile website. Selecting them caused the on-screen keyboard to hide with some browsers. Now there is a new "Delete" button, so that these things can be removed if the keyboard hides. (T62110) You can also edit table cells in mobile now.
Rich editing tools: You can now add and edit sheetmusic in the visual editor. (T112925) There are separate tabs for advanced options, such as MIDI and Ogg audio files. (T114227 and T113354) When editing formulæ and other blocks, errors are shown as you edit. It is also possible to edit some types of graphs; adding new ones, and support for new types, will be coming.
On the English Wikipedia, the visual editor is now automatically available to anyone who creates an account. The preference switch was moved to the normal location, under Special:Preferences.
Future changes
You will soon be able to switch from the wikitext to the visual editor after you start editing. (T49779) Previously, you could only switch from the visual editor to the wikitext editor. Bi-directional switching will make possible a single edit tab. (T102398) This project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab, similar to the system already used on the mobile website. The "Edit" tab will open whichever editing environment you used last time.
Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).
The weekly task triage meetings are open to volunteers. Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.
A new, simpler system for editing will offer a single Edit button. Once the page has opened, you can switch back and forth between visual and wikitext editing.
If you prefer having separate edit buttons, then you can set that option in your preferences, either in a pop-up dialog the next time you open the visual editor, or by going to Special:Preferences and choosing the setting that you want:
The current plan is for the default setting to have the Edit button open the editing environment you used most recently.
You can read and help translate the user guide, which has more information about how to use the visual editor.
Since the last newsletter, the VisualEditor Team has fixed many bugs and expanded the mathematics formula tool. Their workboard is available in Phabricator. Their current priorities are improving support for languages such as Japanese and Arabic, and providing rich-media tools for formulæ, charts, galleries and uploading.
Recent improvements
You can switch from the wikitext editor to the visual editor after you start editing.
The LaTeX mathematics formula editor has been significantly expanded. (T118616) You can see the formula as you change the LaTeX code. You can click buttons to insert the correct LaTeX code for many symbols.
Future changes
The single edit tab project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab, like the system already used on the mobile website. (T102398) Initially, the "Edit" tab will open whichever editing environment you used last time. Your last editing choice will be stored as a cookie for logged-out users and as an account preference for logged-in editors. Logged-in editors will be able to set a default editor in the Editing tab of Special:Preferences in the drop-down menu about "Editing mode:".
In 2016, the feedback pages for the visual editor on many Wikipedias will be redirected to mediawiki.org. (T92661)
Testing opportunities
Please try the new system for the single edit tab on test2.wikipedia.org. You can edit while logged out to see how it works for logged-out editors, or you can create a separate account to be able to set your account's preferences. Please share your thoughts about the single edit tab system at the feedback topic on mediawiki.org or sign up for formal user research (type "single edit tab" in the question about other areas you're interested in). The new system has not been finalized, and your feedback can affect the outcome. The team particularly wants your thoughts about the options in Special:Preferences. The current choices in Special:Preferences are:
Remember my last editor,
Always give me the visual editor if possible,
Always give me the source editor, and
Show me both editor tabs. (This is the current state for people using the visual editor. None of these options will be visible if you have disabled the visual editor in your preferences at that wiki.)
Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Cephalopod size, you added links pointing to the disambiguation pages Dorsal and Onondaga. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Among experienced editors, the visual editor's table editing is one of the most popular features. If you select the top of a column or the end of a row, you can quickly insert and remove columns and rows.
Now, you can also rearrange columns and rows. Click "Move before" or "Move after" to swap the column or row with its neighbor.
You can read and help translate the user guide, which has more information about how to use the visual editor.
Since the last newsletter, the VisualEditor Team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Japanese, Korean, Arabic, Indic, and Han scripts, and improving the single edit tab interface.
Recent changes
You can switch from the wikitext editor to the visual editor after you start editing. This function is available to nearly all editors at most wikis except the Wiktionaries and Wikisources.
Many local feedback pages for the visual editor have been redirected to mw:VisualEditor/Feedback.
You can now re-arrange columns and rows in tables, as well as copying a row, column or any other selection of cells and pasting it in a new location.
The formula editor has two options: you can choose "Quick edit" to see and change only the LaTeX code, or "Edit" to use the full tool. The full tool offers immediate preview and an extensive list of symbols.
Future changes
The single edit tab project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab. This is similar to the system already used on the mobile website. (T102398) Initially, the "Edit" tab will open whichever editing environment you used last time. Your last editing choice will be stored as an account preference for logged-in editors, and as a cookie for logged-out users. Logged-in editors will have these options in the Editing tab of Special:Preferences:
Remember my last editor,
Always give me the visual editor if possible,
Always give me the source editor, and
Show me both editor tabs. (This is the state for people using the visual editor now.)
The visual editor uses the same search engine as Special:Search to find links and files. This search will get better at detecting typos and spelling mistakes soon. These improvements to search will appear in the visual editor as well.
Please try out the newest version of the single edit tab on test2.wikipedia.org. You may need to restore the default preferences (at the bottom of test2wiki:Special:Preferences) to see the initial prompt for options. Were you able to find a preference setting that will work for your own editing? Did you see the large preferences dialog box when you started editing an article there?
Can you read and type in Korean, Arabic, Japanese, Indic, or Han scripts? Language engineer David Chan needs help from people who often type in these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help. Report your results on wiki (Korean – Japanese – all languages).
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thanks!
Do you want one Edit tab, or two? It's your choice
How to switch between editing environments
Click the [[ ]] to switch to the wikitext editor.
Click the pencil icon to switch to the visual editor.
The editing interface will be changed soon. When that happens, editors who currently see two editing tabs – "Edit" and "Edit source" – will start seeing one edit tab instead. The single edit tab has been popular at other Wikipedias. When this is deployed here, you may be offered the opportunity to choose your preferred appearance and behavior the next time you click the Edit button. You will also be able to change your settings in the Editing section of Special:Preferences.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Cephalopod size, you added a link pointing to the disambiguation page National Geographic. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that you've added some links pointing to disambiguation pages. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited List of giant squid specimens and sightings, you added a link pointing to the disambiguation page Uchinoura. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Place the cursor where you want to display the references list (usually at the bottom of the page). Open the "Insert" menu and click the "References list" icon (three books).
If you are using several groups of references, which is relatively rare, you will have the opportunity to specify the group. If you do that, then only the references that belong to the specified group will be displayed in this list of references.
Finally, click "Insert" in the dialog to insert the References list. This list will change as you add more footnotes to the page.
You can read and help translate the user guide, which has more information about how to use the visual editor.
Since the last newsletter, the VisualEditor team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Arabic and Indic scripts, and adapting the visual editor to the needs of the Wikivoyages and Wikisources.
Recent changes
The visual editor is now available to all users at most Wikivoyages. It was also enabled for all contributors at the French Wikinews.
The single edit tab feature combines the "Edit" and "Edit source" tabs into a single "Edit" tab. It has been deployed to several Wikipedias, including Hungarian, Polish, English and Japanese Wikipedias, as well as to all Wikivoyages. At these wikis, you can change your settings for this feature in the "Editing" tab of Special:Preferences. The team is now reviewing the feedback and considering ways to improve the design before rolling it out to more people.
Future changes
The "Save page" button will say "Publish page". This will affect both the visual and wikitext editing systems. More information is available on Meta.
The team is working with the volunteer developers who power Wikisource to provide the visual editor there, for opt-in testing right now and eventually for all users. (T138966)
The team is working on a modern wikitext editor. It will look like the visual editor, and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices around September 2016. You can read about this project in a general status update on the Wikimedia mailing list.
Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Watch the Tech Talk by Sebastian Karcher for more information.
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
Did you know that you can easily re-arrange columns and rows in the visual editor?
Select a cell in the column or row that you want to move. Click the arrow at the start of that row or column to open the dropdown menu (shown). Choose either "Move before" or "Move after" to move the column, or "Move above" or "Move below" to move the row.
You can read and help translate the user guide, which has more information about how to use the visual editor.
Since the last newsletter, the VisualEditor Team has mainly worked on a new wikitext editor. They have also released some small features and the new map editing tool. Their workboard is available in Phabricator. You can find links to the list of work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, releasing the 2017 wikitext editor as a beta feature, and improving language support.
Invisible templates have been shown as a puzzle icon. Now, the name of the invisible template is displayed next to the puzzle icon.[4] A similar feature will display the first part of hidden HTML comments.[5]
Categories are displayed at the bottom of each page. If you click on the categories, the dialog for editing categories will open.[6]
At many wikis, you can now add maps to pages. Go to the Insert menu and choose the "Maps" item. The Discovery department are adding more features to this area, like geoshapes. You can read more on MediaWiki.org.[7]
The "Save" button now says "Save page" when you create a page, and "Save changes" when you change an existing page.[8] In the future, the "Save page" button will say "Publish page". This will affect both the visual and wikitext editing systems. More information is available on Meta.
Image galleries now use a visual mode for editing. You can see thumbnails of the images, add new files, remove unwanted images, rearrange the images by dragging and dropping, and add captions for each image. Use the "Options" tab to set the gallery's display mode, image sizes, and add a title for the gallery.[9]
Future changes
The visual editor will be offered to all editors at the remaining 10 "Phase 6" Wikipedias during the next month. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including Thai, Burmese and Aramaic.
The team is working on a modern wikitext editor. The 2017 wikitext editor will look like the visual editor and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices in October 2016. You can read about this project in a general status update on the Wikimedia mailing list.
Hello, Mgiganteus1. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Did you know that you can review your changes visually?
When you are finished editing the page, type your edit summary and then choose "Review your changes".
In visual mode, you will see additions, removals, new links, and formatting highlighted. Other changes, such as changing the size of an image, are described in notes on the side.
Click the toggle button to switch between visual and wikitext diffs.
The wikitext diff is the same diff tool that is used in the wikitext editors and in the page history.
You can read and help translate the user guide, which has more information about how to use the visual editor.
A new wikitext editing mode is available as a Beta Feature on desktop devices. The 2017 wikitext editor has the same toolbar as the visual editor and can use the citoid service and other modern tools. Go to Special:Preferences#mw-prefsection-betafeatures to enable the ⧼Visualeditor-preference-newwikitexteditor-label⧽.
A new visual diff tool is available in VisualEditor's visual mode. You can toggle between wikitext and visual diffs. More features will be added to this later. In the future, this tool may be integrated into other MediaWiki components. [10]
You can now use your web browser's function to switch typing direction in the new wikitext mode. This is particularly helpful for RTL language users like Urdu or Hebrew who have to write JavaScript or CSS. You can use Command+Shift+X or Control+Shift+X to trigger this. [12]
The way to switch between the visual editing mode and the wikitext editing mode is now consistent. There is a drop-down menu that shows the two options. This is now the same in desktop and mobile web editing, and inside things that embed editing, such as Flow. [13]
The Categories item has been moved to the top of the Page options menu (from clicking on the icon) for quicker access. [14] There is also now a "Templates used on this page" feature there. [15]
You can now create <chem> tags (sometimes used as <ce>) for chemical formulas inside the visual editor. [16]
Tables can be set as collapsed or un-collapsed. [17]
The Special character menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) . The team thanks the volunteer developer, Tpt. [18]
A bug caused some section edit conflicts to blank the rest of the page. This has been fixed. The team are sorry for the disruption. [19]
There is a new keyboard shortcut for citations: Control+Shift+K on a PC, or Command+Shift+K on a Mac. It is based on the keyboard shortcut for making links, which is Control+K on a PC or Command+K on a Mac. [20]
Future changes
The VisualEditor team is working with the Community Tech team on a syntax highlighting tool. It will highlight matching pairs of <ref> tags and other types of wikitext syntax. You will be able to turn it on and off. It will first become available in VisualEditor's built-in wikitext mode, maybe late in 2017. [21]
The kind of button used to Show preview, Show changes, and finish an edit will change in all WMF-supported wikitext editors. The new buttons will use OOjs UI. The buttons will be larger, brighter, and easier to read. The labels will remain the same. You can test the new button by editing a page and adding &ooui=1 to the end of the URL, like this: https://www.mediawiki.org/wiki/Project:Sandbox?action=edit&ooui=1 The old appearance will no longer be possible, even with local CSS changes. [22]
Hello, Mgiganteus1. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Hi. Thank you for your recent edits. An automated process has detected that when you recently edited Cephalopod size, you added a link pointing to the disambiguation page German (check to confirm | fix with Dab solver). Such links are usually incorrect, since a disambiguation page is merely a list of unrelated topics with similar titles. (Read the FAQ • Join us at the DPL WikiProject.)
The change you made here is actually unbalancing brackets and adding double brackets to external links and reverting typos which I fixed. It was helpful to added the tag to the quote but the other reversions weren't correct. Pkbwcgs (talk) 17:40, 24 January 2018 (UTC)
Books and Bytes - Issue 26
The Wikipedia Library
Books & Bytes
Issue 26, December – January 2018
#1Lib1Ref
User Group update
Global branches update
Spotlight: What can we glean from OCLC’s experience with library staff learning Wikipedia?
Did you know that you can now use the visual diff tool on any page?
Sometimes, it is hard to see important changes in a wikitext diff. This screenshot of a wikitext diff (click to enlarge) shows that the paragraphs have been rearranged, but it does not highlight the removal of a word or the addition of a new sentence.
If you enable the Beta Feature for "⧼visualeditor-preference-visualdiffpage-label⧽", you will have a new option. It will give you a new box at the top of every diff page. This box will let you choose either diff system on any edit.
Click the toggle button to switch between visual and wikitext diffs.
In the visual diff, additions, removals, new links, and formatting changes will be highlighted. Other changes, such as changing the size of an image, are described in notes on the side.
This screenshot shows the same edit as the wikitext diff. The visual diff highlights the removal of one word and the addition of a new sentence. An arrow indicates that the paragraph changed location.
You can read and help translate the user guide, which has more information about how to use the visual editor.
The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools. The team have been comparing the performance of different editing environments. They have studied how long it takes to open the page and start typing. The study uses data for more than one million edits during December and January. Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor. Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits. More information will be posted at mw:Contributors/Projects/Editing performance.
The visual diff tool was developed for the visual editor. It is now available to all users of the visual editor and the 2017 wikitext editor. When you review your changes, you can toggle between wikitext and visual diffs. You can also enable the new Beta Feature for "Visual diffs". The Beta Feature lets you use the visual diff tool to view other people's edits on page histories and Special:RecentChanges. [24]
The citoid service automatically translates URLs, DOIs, ISBNs, and PubMed id numbers into wikitext citation templates. This tool has been used at the English Wikipedia for a long time. It is very popular and useful to editors, although it can be tricky for admins to set up. Other wikis can have this service, too. Please read the instructions. You can ask the team to help you enable citoid at your wiki.
Wikibooks, Wikiversity, and other communities may have the visual editor made available by default to contributors. If your community wants this, then please contact Dan Garry.
The <references /> block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. This has already been enabled at the English Wikipedia. If you want columns for a long list of footnotes on this wiki, you can use either <references /> or the plain (no parameters) {{reflist}} template. If you edit a different wiki, you can request multi-column support for your wiki. [26]
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Thank you!
From a single image to more images of the same object
@ you Major Giant :)
Many if not most of the sporadic visitors of Wikipedia do not know that from any single image they can get to more images of the same object, if they are available in WM Commons. Nor they know the link from the category to the Wikidata object.
If we want to address not only giants and nerts, but also muggles, we have to show them their chances.
In this very long list that allows only few exeptions fom the limit of one photo per object, the initial hint in the box is necessary.
Thanks for uploading File:Aliens- Colonial Marines.jpg. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
Orphaned non-free image File:Insectivorous Plant Society logo.jpg
⚠
Thanks for uploading File:Insectivorous Plant Society logo.jpg. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
Hi, I'm RonBot, a script that checks new non-free file uploads. I have found that the subject image that you recently uploaded was more than 5% in excess of the Non-free content guideline size of 100,000 pixels. I have tagged the image for a standard reduction, which (for jpg/gif/png/svg files) normally happens within a day. Please check the reduced image, and make sure that the image is not excessively corrupted. Other files will be added to Category:Wikipedia non-free file size reduction requests for manual processing. There is a full seven-day period before the original oversized image will be hidden; during that time you might want to consider editing the original image yourself (perhaps an initial crop to allow a smaller reduction or none at all). A formula for calculation the desired size can be found at WP:Image resolution, along with instructions on how to tag the image in the rare cases that it requires an oversized image (typically about 0.2% of non-free uploads are tagged as necessarily oversized). Please contact the bot owner if you have any questions, or you can ask them at Wikipedia talk:Non-free content. RonBot (talk) 17:07, 29 September 2018 (UTC)
Hi, I'm RonBot, a script that checks new non-free file uploads. I have found that the subject image that you recently uploaded was more than 5% in excess of the Non-free content guideline size of 100,000 pixels. I have tagged the image for a standard reduction, which (for jpg/gif/png/svg files) normally happens within a day. Please check the reduced image, and make sure that the image is not excessively corrupted. Other files will be added to Category:Wikipedia non-free file size reduction requests for manual processing. There is a full seven-day period before the original oversized image will be hidden; during that time you might want to consider editing the original image yourself (perhaps an initial crop to allow a smaller reduction or none at all). A formula for calculation the desired size can be found at WP:Image resolution, along with instructions on how to tag the image in the rare cases that it requires an oversized image (typically about 0.2% of non-free uploads are tagged as necessarily oversized). Please contact the bot owner if you have any questions, or you can ask them at Wikipedia talk:Non-free content. RonBot (talk) 17:08, 29 September 2018 (UTC)
Hi, I'm RonBot, a script that checks new non-free file uploads. I have found that the subject image that you recently uploaded was more than 5% in excess of the Non-free content guideline size of 100,000 pixels. I have tagged the image for a standard reduction, which (for jpg/gif/png/svg files) normally happens within a day. Please check the reduced image, and make sure that the image is not excessively corrupted. Other files will be added to Category:Wikipedia non-free file size reduction requests for manual processing. There is a full seven-day period before the original oversized image will be hidden; during that time you might want to consider editing the original image yourself (perhaps an initial crop to allow a smaller reduction or none at all). A formula for calculation the desired size can be found at WP:Image resolution, along with instructions on how to tag the image in the rare cases that it requires an oversized image (typically about 0.2% of non-free uploads are tagged as necessarily oversized). Please contact the bot owner if you have any questions, or you can ask them at Wikipedia talk:Non-free content. RonBot (talk) 17:12, 1 October 2018 (UTC)
Hi, I'm RonBot, a script that checks new non-free file uploads. I have found that the subject image that you recently uploaded was more than 5% in excess of the Non-free content guideline size of 100,000 pixels. I have tagged the image for a standard reduction, which (for jpg/gif/png/svg files) normally happens within a day. Please check the reduced image, and make sure that the image is not excessively corrupted. Other files will be added to Category:Wikipedia non-free file size reduction requests for manual processing. There is a full seven-day period before the original oversized image will be hidden; during that time you might want to consider editing the original image yourself (perhaps an initial crop to allow a smaller reduction or none at all). A formula for calculation the desired size can be found at WP:Image resolution, along with instructions on how to tag the image in the rare cases that it requires an oversized image (typically about 0.2% of non-free uploads are tagged as necessarily oversized). Please contact the bot owner if you have any questions, or you can ask them at Wikipedia talk:Non-free content. RonBot (talk) 17:24, 6 October 2018 (UTC)
Hi, I'm RonBot, a script that checks new non-free file uploads. I have found that the subject image that you recently uploaded was more than 5% in excess of the Non-free content guideline size of 100,000 pixels. I have tagged the image for a standard reduction, which (for jpg/gif/png/svg files) normally happens within a day. Please check the reduced image, and make sure that the image is not excessively corrupted. Other files will be added to Category:Wikipedia non-free file size reduction requests for manual processing. There is a full seven-day period before the original oversized image will be hidden; during that time you might want to consider editing the original image yourself (perhaps an initial crop to allow a smaller reduction or none at all). A formula for calculation the desired size can be found at WP:Image resolution, along with instructions on how to tag the image in the rare cases that it requires an oversized image (typically about 0.2% of non-free uploads are tagged as necessarily oversized). Please contact the bot owner if you have any questions, or you can ask them at Wikipedia talk:Non-free content. RonBot (talk) 18:06, 7 October 2018 (UTC)
Books & Bytes, Issue 30
The Wikipedia Library
Books & Bytes
Issue 30, August – Septmeber 2018
Library Card translation
Spotlight: 1Lib1Ref spreads to the Southern Hemisphere and beyond
The Editing team has begun a design study of visual editing on the mobile website. New editors have trouble doing basic tasks on a smartphone, such as adding links to Wikipedia articles. You can read the report.
The Editing team wants to improve visual editing on the mobile website. Please read their ideas and tell the team what you think would help editors who use the mobile site.
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Thank you!
Hi, I'm RonBot, a script that checks new non-free file uploads. I have found that the subject image that you recently uploaded was more than 5% in excess of the Non-free content guideline size of 100,000 pixels. I have tagged the image for a standard reduction, which (for jpg/gif/png/svg files) normally happens within a day. Please check the reduced image, and make sure that the image is not excessively corrupted. Other files will be added to Category:Wikipedia non-free file size reduction requests for manual processing. There is a full seven-day period before the original oversized image will be hidden; during that time you might want to consider editing the original image yourself (perhaps an initial crop to allow a smaller reduction or none at all). A formula for calculation the desired size can be found at WP:Image resolution, along with instructions on how to tag the image in the rare cases that it requires an oversized image (typically about 0.2% of non-free uploads are tagged as necessarily oversized). Please contact the bot owner if you have any questions, or you can ask them at Wikipedia talk:Non-free content. See User:RonBot for info on how to not get these messages. RonBot (talk) 18:00, 7 November 2018 (UTC)
ArbCom 2018 election voter message
Hello, Mgiganteus1. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
The mobile visual editor is a simpler editing tool, for smartphones and tablets using the mobile site. The Editing team has recently launched two new features to improve the mobile visual editor:
The purpose is to help contributors focus on their edits.
The team studied this with an A/B test. This test showed that contributors who could use section editing were 1% more likely to publish the edits they started than people with only full-page editing.
The purpose is to smooth the transition between reading and editing.
Section editing and the new loading overlay are now available to everyone using the mobile visual editor.
New and active projects
This is a list of our most active projects. Watch these pages to learn about project updates and to share your input on new designs, prototypes and research findings.
Edit cards: This is a clearer way to add and edit links, citations, images, templates, etc. in articles. You can try this feature now. Go here to see how:📲Try Edit Cards.
Mobile toolbar refresh: This project will learn if contributors are more successful when the editing tools are easier to recognize.
Mobile visual editor availability: This A/B test asks: Are newer contributors more successful if they use the mobile visual editor? We are collaborating with 20 Wikipedias to answer this question.
Usability improvements: This project will make the mobile visual editor easier to use. The goal is to let contributors stay focused on editing and to feel more confident in the editing tools.
Looking ahead
Wikimania: Several members of the Editing Team will be attending Wikimania in August 2019. They will lead a session about mobile editing in the Community Growth space. Talk to them about how editing can be improved.
Talk Pages: In the coming months, the Editing Team will begin improving talk pages and communication on the wikis.
Learning more
The VisualEditor on mobile is a good place to learn more about the projects we are working on. The team wants to talk with you about anything related to editing. If you have something to say or ask, please leave a message at Talk:VisualEditor on mobile.
Hi, in 2006 you created an impressive number of articles on species of Cyathea, such as this one. Many of the species are now placed in the genus Alsophila in the PPG I classification, as reflected in Checklist of Ferns and Lycophytes of the World, Plants of the World Online, GBIF, etc. So I've been working on moving those affected.
One issue is that you always gave as a general reference "Braggins, John E. & Large, Mark F. 2004. Tree Ferns. Timber Press, Inc. ISBN 0881926302". However, as reflected here and in some of the in text references you made to the book (e.g. in the text here), it appears to have the authors in the opposite order, i.e. as per the citation:
Large, Mark F.; Braggins, John E. (2004), Tree Ferns, Timber Press, ISBN978-0-88192-630-9{{citation}}: Unknown parameter |lastauthoramp= ignored (|name-list-style= suggested) (help)
Do you remember why you have the names the other way round?
Another issue is that some of the articles have been flagged as needing more inline citations. So I'm inclined to add the Tree Ferns book ref to the end of each general paragraph, as I've done at Alsophila acanthophora. Is this right from how you created the articles?
The article will be discussed at Wikipedia:Articles for deletion/Journal of Biological Sciences until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article. Headbomb {t · c · p · b}22:30, 22 September 2019 (UTC)
What talk page interactions do you remember? Is it a story about how someone helped you to learn something new? Is it a story about how someone helped you get involved in a group? Something else? Whatever your story is, we want to hear it!
Please tell us a story about how you used a talk page. Please share a link to a memorable discussion, or describe it on the talk page for this project. The team would value your examples. These examples will help everyone develop a shared understanding of what this project should support and encourage.
Talk Pages
The Talk Pages Consultation was a global consultation to define better tools for wiki communication. From February through June 2019, more than 500 volunteers on 20 wikis, across 15 languages and multiple projects, came together with members of the Foundation to create a product direction for a set of discussion tools. The Phase 2 Report of the Talk Page Consultation was published in August. It summarizes the product direction the team has started to work on, which you can read more about here: Talk Page Project project page.
The team needs and wants your help at this early stage. They are starting to develop the first idea. Please add your name to the "Getting involved" section of the project page, if you would like to hear about opportunities to participate.
Mobile visual editor
The Editing team is trying to make it simpler to edit on mobile devices. The team is changing the visual editor on mobile. If you have something to say about editing on a mobile device, please leave a message at Talk:VisualEditor on mobile.
In September, the Editing team updated the mobile visual editor's editing toolbar. Anyone could see these changes in the mobile visual editor.
One toolbar: All of the editing tools are located in one toolbar. Previously, the toolbar changed when you clicked on different things.
New navigation: The buttons for moving forward and backward in the edit flow have changed.
Seamless switching: an improved workflow for switching between the visual and wikitext modes.
Feedback: You can try the refreshed toolbar by opening the mobile VisualEditor on a smartphone. Please post your feedback on the Toolbar feedback talk page.
Talk Pages Project: The team is thinking about the first set of proposed changes. The team will be working with a few communities to pilot those changes. The best way to stay informed is by adding your username to the list on the project page: Getting involved.
Testing the mobile visual editor as the default: The Editing team plans to post results before the end of the calendar year. The best way to stay informed is by adding the project page to your watchlist: VisualEditor as mobile default project page.
Measuring the impact of Edit Cards: The Editing team hopes to share results in November. This study asks whether the project helped editors add links and citations. The best way to stay informed is by adding the project page to your watchlist: Edit Cards project page.
Hello, new pictures of Nepenthes mapuluensis were uploaded yesterday in the corresponding category of wikimedia commons ; as a newcomer, I don't know how to make them appear in the N. mapuluensis en.wikipedia page - I fear making a mess. As I see that you did most of the work on this page, albeit some time ago, could you do it ? thank you !Ethyle64 (talk) 09:30, 17 November 2019 (UTC)
Thank you for doing it ! Ethyle64 (talk) 20:00, 17 November 2019 (UTC)
Thanks for uploading File:Nepenthes mapuluensis.jpg. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
The article will be discussed at Wikipedia:Articles for deletion/Four Mile Globster until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article. –dlthewave☎03:21, 10 December 2019 (UTC)
The article will be discussed at Wikipedia:Articles for deletion/Hebrides blob until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article. –dlthewave☎21:37, 15 December 2019 (UTC)
The article will be discussed at Wikipedia:Articles for deletion/Newfoundland Blob until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article. –dlthewave☎22:32, 15 December 2019 (UTC)
Thanks for uploading File:Four Mile Globster.jpg. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
Thanks for uploading File:Newfoundland Blob.jpg. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
The team is planning some upcoming changes. Please review the proposed design and share your thoughts on the talk page. The team will test features such as:
an easy way to mention another editor ("pinging"),
a rich-text visual editing option, and
other features identified through user testing or recommended by editors.
You may prevent the proposed deletion by removing the {{proposed deletion/dated files}} notice, but please explain why in your edit summary or on the file's talk page.
Reply tool: This is available as a Beta Feature at the four partner wikis (Arabic, Dutch, French, and Hungarian Wikipedias). The Beta Feature will get new features soon. The new features include writing comments in a new visual editing mode and pinging other users by typing @. You can test the new features on the Beta Cluster. Some other wikis will have a chance to try the Beta Feature in the coming months.
New requirements for user signatures: Soon, users will not be able to save invalid custom signatures in Special:Preferences. This will reduce signature spoofing, prevent page corruption, and make new talk page tools more reliable. Most editors will not be affected.
Research on the use of talk pages: The Editing team worked with the Wikimedia research team to study how talk pages help editors improve articles. We learned that new editors who use talk pages make more edits to the main namespace than new editors who don't use talk pages.
On 16 March 2020, the 50 millionth edit was made using the visual editor on desktop.
Seven years ago this week, the Editing team made the visual editor available by default to all logged-in editors using the desktop site at the English Wikipedia. Here's what happened since its introduction:
The 50 millionth edit using the visual editor on desktop was made this year. More than 10 million edits have been made here at the English Wikipedia.
More than 2 million new articles have been created in the visual editor. More than 600,000 of these new articles were created during 2019.
Almost 5 million edits on the mobile site have been made with the visual editor. Most of these edits have been made since the Editing team started improving the mobile visual editor in 2018.
The proportion of all edits made using the visual editor has been increasing every year.
Editors have made more than 7 million edits in the 2017 wikitext editor, including starting 600,000 new articles in it. The 2017 wikitext editor is VisualEditor's built-in wikitext mode. You can enable it in your preferences.
In 2019, 35% of the edits by newcomers, and half of their first edits, were made using the visual editor. This percentage has been increasing every year since the tool became available.
More than 300 editors used the Reply tool at these four Wikipedias. They posted more than 7,400 replies during the study period.
Of the people who posted a comment with the Reply tool, about 70% of them used the tool multiple times. About 60% of them used it on multiple days.
Comments from Wikipedia editors are positive. One said, أعتقد أن الأداة تقدم فائدة ملحوظة؛ فهي تختصر الوقت لتقديم رد بدلًا من التنقل بالفأرة إلى وصلة تعديل القسم أو الصفحة، التي تكون بعيدة عن التعليق الأخير في الغالب، ويصل المساهم لصندوق التعديل بسرعة باستخدام الأداة. ("I think the tool has a significant impact; it saves time to reply while the classic way is to move with a mouse to the Edit link to edit the section or the page which is generally far away from the comment. And the user reaches to the edit box so quickly to use the Reply tool.")[29]
The Editing team released the Reply tool as a Beta Feature at eight other Wikipedias in early August. Those Wikipedias are in the Chinese, Czech, Georgian, Serbian, Sorani Kurdish, Swedish, Catalan, and Korean languages. If you would like to use the Reply tool at your wiki, please tell User talk:Whatamidoing (WMF).
The Reply tool is still in active development. Per request from the Dutch Wikipedia and other editors, you will be able to customize the edit summary. (The default edit summary is "Reply".) A "ping" feature is available in the Reply tool's visual editing mode. This feature searches for usernames. Per request from the Arabic Wikipedia, each wiki will be able to set its own preferred symbol for pinging editors. Per request from editors at the Japanese and Hungarian Wikipedias, each wiki can define a preferred signature prefix in the page MediaWiki:Discussiontools-signature-prefix. For example, some languages omit spaces before signatures. Other communities want to add a dash or a non-breaking space.
New requirements for user signatures
The new requirements for custom user signatures began on 6 July 2020. If you try to create a custom signature that does not meet the requirements, you will get an error message.
Existing custom signatures that do not meet the new requirements will be unaffected temporarily. Eventually, all custom signatures will need to meet the new requirements. You can check your signature and see lists of active editors whose custom signatures need to be corrected. Volunteers have been contacting editors who need to change their custom signatures. If you need to change your custom signature, then please read the help page.
Next: New discussion tool
Next, the team will be working on a tool for quickly and easily starting a new discussion section to a talk page. To follow the development of this new tool, please put the New Discussion Tool project page on your watchlist.
Hello! Voting in the 2020 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 7 December 2020. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Completion rates for comments made with the Reply tool and full-page wikitext editing. Details and limitations are in this report.
The Reply tool is available at most other Wikipedias.
The Reply tool has been deployed as an opt-out preference to all editors at the Arabic, Czech, and Hungarian Wikipedias.
It is also available as a Beta Feature at almost all Wikipedias except for the English, Russian, and German-language Wikipedias. If it is not available at your wiki, you can request it by following these simple instructions.
Research notes:
As of January 2021, more than 3,500 editors have used the Reply tool to post about 70,000 comments.
There is preliminary data from the Arabic, Czech, and Hungarian Wikipedia on the Reply tool. Junior Contributors who use the Reply tool are more likely to publish the comments that they start writing than those who use full-page wikitext editing.[30]
The Editing and Parsing teams have significantly reduced the number of edits that affect other parts of the page. About 0.3% of edits did this during the last month.[31] Some of the remaining changes are automatic corrections for Special:LintErrors.
A large A/B test will start soon.[32] This is part of the process to offer the Reply tool to everyone. During this test, half of all editors at 24 Wikipedias (not including the English Wikipedia) will have the Reply tool automatically enabled, and half will not. Editors at those Wikipeedias can still turn it on or off for their own accounts in Special:Preferences.
During Talk pages consultation 2019, editors said that it should be easier to know about new activity in conversations they are interested in. The Notifications project is just beginning. What would help you become aware of new comments? What's working with the current system? Which pages at your wiki should the team look at? Please post your advice at mw:Talk:Talk pages project/Notifications.
An automated process has detected that when you recently edited Centro del Calamar Gigante, you added a link pointing to the disambiguation page Annex.
Thanks for uploading File:Alien (1986) - Alien queen.jpg. The media description page currently specifies that it is non-free and may only be used on Wikipedia under a claim of fair use. However, it is currently orphaned, meaning that it is not used in any articles on Wikipedia. If the media was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that media for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
_Alt.png)
Thank you for contributing to Wikipedia. We always appreciate when users upload new images. However, it appears that one or more of the images you have recently uploaded or added to an article may fail our non-free image policy. Most often, this involves editors uploading or using a copyrighted image of a living person. For other possible reasons, please read up on our Non-free image criteria. If you have any questions please ask them at the Media copyright questions page. Werieth (talk) 11:12, 8 March 2013 (UTC)
Hello, I'm BracketBot. I have automatically detected that your edit to List of carnivorous plant periodicals may have broken the syntax by modifying 1 "()"s. If you have, don't worry, just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.
. Hamham31Heke! 00:59, 10 August 2013 (UTC)
The Wikipedia Library
gmail.com. Thanks and cheers, Jake Ocaasi via MediaWiki message delivery (talk) 23:41, 20 June 2014 (UTC)
Thank you to the translators for participating and the translatewiki.net staff for facilitating this initiative.
The Wikipedia Library
icon) for quicker access. [14] There is also now a "Templates used on this page" feature there. [15]
to start editing.
these pages: the main project page, Updates, Replying, and User testing.
A large A/B test will start soon.[32] This is part of the process to offer the Reply tool to everyone. During this test, half of all editors at 24 Wikipedias (not including the English Wikipedia) will have the Reply tool automatically enabled, and half will not. Editors at those Wikipeedias can still turn it on or off for their own accounts in Special:Preferences.
_-_Alien_queen.jpg){kind=link}
_-_Alien_queen.jpg)){kind=link}
.png){kind=link}
.png){kind=link}
