Lalit82in

Thanks for uploading Image:Shri P L Mistry.jpg. The image has been identified as not specifying the copyright status of the image, which is required by Wikipedia's policy on images. Even if you created the image yourself, you still need to release it so Wikipedia can use it. If you don't indicate the copyright status of the image on the image's description page, using an appropriate copyright tag, it may be deleted some time in the next seven days. If you made this image yourself, you can use copyright tags like {{PD-self}} (to release all rights), {{self|CC-by-sa-3.0|GFDL}} (to require that you be credited), or any tag here - just go to the image, click edit, and add one of those. If you have uploaded other images, please verify that you have provided copyright information for them as well.

For more information on using images, see the following pages:

• Wikipedia:Image use policy
• Wikipedia:Image copyright tags

This is an automated notice by MifterBot. For assistance on the image use policy, see Wikipedia:Media copyright questions. NOTE: once you correct this, please remove the tag from the image's page. --MifterBot ^{(Talk • Contribs • Owner)} 10:18, 1 October 2008 (UTC)Reply

Thank you for uploading Image:Ecb logo.GIF. However, it currently is missing information on its copyright status. Wikipedia takes copyright very seriously. It may be deleted soon, unless we can determine the license and the source of the image. If you know this information, then you can add a copyright tag to the image description page.

If you have uploaded other files, consider checking that you have specified their license and tagged them, too. You can find a list of files you have uploaded by following this link.

If you have any questions, please feel free to ask them at the media copyright questions page. Thanks again for your cooperation.  Asenine  17:44, 1 October 2008 (UTC)Reply

Thank you for uploading Image:Image1.gif. However, it currently is missing information on its copyright status. Wikipedia takes copyright very seriously. It may be deleted soon, unless we can determine the license and the source of the image. If you know this information, then you can add a copyright tag to the image description page.

If you have uploaded other files, consider checking that you have specified their license and tagged them, too. You can find a list of files you have uploaded by following this link.

If you have any questions, please feel free to ask them at the media copyright questions page. Thanks again for your cooperation.  Asenine  17:50, 1 October 2008 (UTC)Reply

This is an automated message from CorenSearchBot. I have performed a web search with the contents of Sonana Khetlaji, and it appears to include a substantial copy of http://www.rajasthantours.net/rajasthan-festival-fair/khetlaji-fair.htm. For legal reasons, we cannot accept copyrighted text or images borrowed from other web sites or printed material; such additions will be deleted. You may use external websites as a source of information, but not as a source of sentences.

This message was placed automatically, and it is possible that the bot is confused and found similarity where none actually exists. If that is the case, you can remove the tag from the article and it would be appreciated if you could drop a note on the maintainer's talk page. CorenSearchBot (talk) 10:05, 10 October 2008 (UTC)Reply

Hi Lalit82in!
We thank you for uploading Image:Khetlaji.jpg, but there is a problem. Your image is currently missing information on its copyright status. Wikipedia takes copyright very seriously. Unless you can help by adding a copyright tag, it may be deleted by an Administrator. If you know this information, then we urge you to add a copyright tag to the image description page. We apologize for this, but all images must confirm to policy on Wikipedia.

If you have any questions, please feel free to ask them at the media copyright questions page. Thanks so much for your cooperation.
This message is from a robot.

--John Bot III (talk) 13:43, 10 October 2008 (UTC)Reply

Thanks for uploading Image:Jawai1.gif. You don't seem to have said where the image came from, who created it, or what the copyright status is. We require this information to verify that the image is legally usable on Wikipedia, and because most image licenses require giving credit to the image's creator.

To add this information, click on this link, then click "Edit this page" and add the information to the image's description. If you need help, post your question on Wikipedia:Media copyright questions.

For more information on using images, see the following pages:

• Wikipedia:Image use policy
• Wikipedia:Image copyright tags

Thank you for your cooperation. --ImageTaggingBot (talk) 00:57, 5 December 2008 (UTC)Reply

Hello, this is a message from an automated bot. A tag has been placed on O P Jangir, by another Wikipedia user, requesting that it be speedily deleted from Wikipedia. The tag claims that it should be speedily deleted because O P Jangir seems to be about a person, group of people, band, club, company, or web content, but it does not indicate how or why the subject is notable: that is, why an article about that subject should be included in an encyclopedia. Under the criteria for speedy deletion, articles that do not assert the subject's importance or significance may be deleted at any time. Please see the guidelines for what is generally accepted as notable.

To contest the tagging and request that administrators wait before possibly deleting O P Jangir, please affix the template {{hangon}} to the page, and put a note on its talk page. If the article has already been deleted, see the advice and instructions at WP:WMD. Feel free to contact the bot operator if you have any questions about this or any problems with this bot, bearing in mind that this bot is only informing you of the nomination for speedy deletion; it does not perform any nominations or deletions itself. To see the user who deleted the page, click here CSDWarnBot (talk) 20:10, 13 December 2008 (UTC)Reply

Thanks for uploading File:OPJangir.jpg. The image has been identified as not specifying the source and creator of the image, which is required by Wikipedia's policy on images. If you don't indicate the source and creator of the image on the image's description page, it may be deleted some time in the next seven days. If you have uploaded other images, please verify that you have provided source information for them as well.

For more information on using images, see the following pages:

• Wikipedia:Image use policy
• Wikipedia:Image copyright tags

This is an automated notice by OrphanBot. For assistance on the image use policy, see Wikipedia:Media copyright questions. 07:14, 23 December 2008 (UTC)Reply

Thanks for uploading File:A tomb of Laila and Majnu, in Bijnore village near the Pakistan border in Sriganganagar district - 16pix3.jpg. You don't seem to have said where the image came from, who created it, or what the copyright status is. We require this information to verify that the image is legally usable on Wikipedia, and because most image licenses require giving credit to the image's creator.

To add this information, click on this link, then click "Edit this page" and add the information to the image's description. If you need help, post your question on Wikipedia:Media copyright questions.

For more information on using images, see the following pages:

• Wikipedia:Image use policy
• Wikipedia:Image copyright tags

Thank you for your cooperation. --ImageTaggingBot (talk) 11:06, 4 May 2009 (UTC)Reply

Thanks for uploading File:BNKRAJS logo.gif. You don't seem to have said where the image came from, who created it, or what the copyright status is. We require this information to verify that the image is legally usable on Wikipedia, and because most image licenses require giving credit to the image's creator.

To add this information, click on this link, then click "Edit this page" and add the information to the image's description. If you need help, post your question on Wikipedia:Media copyright questions.

For more information on using images, see the following pages:

• Wikipedia:Image use policy
• Wikipedia:Image copyright tags

Thank you for your cooperation. --ImageTaggingBot (talk) 08:06, 11 May 2009 (UTC)Reply

Thanks for uploading File:GSGurjar.jpg. You don't seem to have indicated the license status of the image. Wikipedia uses a set of image copyright tags to indicate this information; to add a tag to the image, select the appropriate tag from this list, click on this link, then click "Edit this page" and add the tag to the image's description. If there doesn't seem to be a suitable tag, the image is probably not appropriate for use on Wikipedia.

For help in choosing the correct tag, or for any other questions, leave a message on Wikipedia:Media copyright questions. Thank you for your cooperation. --ImageTaggingBot (talk) 11:05, 15 May 2009 (UTC)Reply

Thanks for uploading File:VasundharaRaje.jpg. You don't seem to have indicated the license status of the image. Wikipedia uses a set of image copyright tags to indicate this information; to add a tag to the image, select the appropriate tag from this list, click on this link, then click "Edit this page" and add the tag to the image's description. If there doesn't seem to be a suitable tag, the image is probably not appropriate for use on Wikipedia.

For help in choosing the correct tag, or for any other questions, leave a message on Wikipedia:Media copyright questions. Thank you for your cooperation. --ImageTaggingBot (talk) 12:07, 15 May 2009 (UTC)Reply

Thanks for uploading File:Map rajasthan dist num 8.PNG. You don't seem to have indicated the license status of the image. Wikipedia uses a set of image copyright tags to indicate this information; to add a tag to the image, select the appropriate tag from this list, click on this link, then click "Edit this page" and add the tag to the image's description. If there doesn't seem to be a suitable tag, the image is probably not appropriate for use on Wikipedia.

For help in choosing the correct tag, or for any other questions, leave a message on Wikipedia:Media copyright questions. Thank you for your cooperation. --ImageTaggingBot (talk) 13:06, 29 May 2009 (UTC)Reply

A tag has been placed on Government Medical College, Kota requesting that it be speedily deleted from Wikipedia. This has been done under section A7 of the criteria for speedy deletion, because the article appears to be about about a person, organization (band, club, company, etc.) or web content, but it does not indicate how or why the subject is important or significant: that is, why an article about that subject should be included in an encyclopedia. Under the criteria for speedy deletion, such articles may be deleted at any time. Please see the guidelines for what is generally accepted as notable

If you think that this notice was placed here in error, you may contest the deletion by adding {{hangon}}tothe top of the page that has been nominated for deletion (just below the existing speedy deletion or "db" tag), coupled with adding a note on the talk page explaining your position, but be aware that once tagged for speedy deletion, if the page meets the criterion it may be deleted without delay. Please do not remove the speedy deletion tag yourself, but don't hesitate to add information to the page that would render it more in conformance with Wikipedia's policies and guidelines. Lastly, please note that if the page does get deleted, you can contact one of these admins to request that they userfy the page or have a copy emailed to you. peterl (talk) 10:12, 11 June 2009 (UTC)Reply

I don't think you have enough nmber of edits to have your name on the list at WP:IND EDITS. Please DO NOT add your name again to the list as I will report you next time. Even I have far more edits than you do... --Rsrikanth05 (talk) 12:06, 13 June 2009 (UTC)Reply

This is an automated message from CorenSearchBot. I have performed a web search with the contents of Baba Ramdevji (movie), and it appears to be very similar to another Wikipedia page: Baba Ramdevji. It is possible that you have accidentally duplicated contents, or made an error while creating the page— you might want to look at the pages and see if that is the case. If you are intentionally moving or duplicating content, please be sure you have followed the procedure at Wikipedia:Splitting by acknowledging the duplication of material in edit summary to preserve attribution history.

This message was placed automatically, and it is possible that the bot is confused and found similarity where none actually exists. If that is the case, you can remove the tag from the article and it would be appreciated if you could drop a note on the maintainer's talk page. CorenSearchBot (talk) 06:39, 5 July 2009 (UTC)Reply

Aproposed deletion template has been added to the article Baba Ramdev (movie), suggesting that it be deleted according to the proposed deletion process because of the following concern:

No sources to show notability. See WP:NOTFILM.

All contributions are appreciated, but this article may not satisfy Wikipedia's criteria for inclusion, and the deletion notice should explain why (see also "What Wikipedia is not" and Wikipedia's deletion policy). You may prevent the proposed deletion by removing the {{dated prod}} notice, but please explain why you disagree with the proposed deletion in your edit summary or on its talk page.

Please consider improving the article to address the issues raised because, even though removing the deletion notice will prevent deletion through the proposed deletion process, the article may still be deleted if it matches any of the speedy deletion criteria or it can be sent to Articles for Deletion, where it may be deleted if consensus to delete is reached. APK coffee talk 07:08, 5 July 2009 (UTC)Reply

I have nominated Baba Ramdev (movie), an article that you created, for deletion. I do not think that this article satisfies Wikipedia's criteria for inclusion, and have explained why at Wikipedia:Articles for deletion/Baba Ramdev (movie). Your opinions on the matter are welcome at that same discussion page; also, you are welcome to edit the article to address these concerns. Thank you for your time.

Please contact me if you're unsure why you received this message. APK coffee talk 07:33, 5 July 2009 (UTC)Reply

I have nominated Bai Chali Sasariye, an article that you created, for deletion. I do not think that this article satisfies Wikipedia's criteria for inclusion, and have explained why at Wikipedia:Articles for deletion/Bai Chali Sasariye. Your opinions on the matter are welcome at that same discussion page; also, you are welcome to edit the article to address these concerns. Thank you for your time.

Please contact me if you're unsure why you received this message. APK coffee talk 06:41, 7 July 2009 (UTC)Reply

  Hello. In case you didn't know, when you add content to talk pages and Wikipedia pages that have open discussion, you should sign your posts by typing four tildes ( ~~~~ ) at the end of your comment. You may also click on the signature button   located above the edit window. This will automatically insert a signature with your username or IP address and the time you posted the comment. This information is useful because other editors will be able to tell who said what, and when. Thank you. --SineBot (talk) 09:51, 8 July 2009 (UTC)Reply

To stop receiving this newsletter, or to receive it in a different format, please list yourself in the appropriate section here. Delivered automatically by -- Tinu Cherian BOT - 15:11, 18 July 2009 (UTC)Reply

You recently made an addition to the {{herbs and spices}} template of a herb used solely for medicinal use. This template is strictly for culinary herbs and spices, a better template would be the {{medicinal herbs & fungi}} template which is designed for this use. --Jeremy (blah blah • I did it!) 18:09, 4 August 2009 (UTC)Reply

Thanks for correcting the data of Bamnera website. This website was created by me. Kindly give your feedback on this. —Preceding unsigned comment added by Rasikdave (talk • contribs) 13:50, 1 September 2009 (UTC)Reply

Thanks for correcting the data of Bamnera website, but unfortunately, you have updated incorrect information regarding National Highway no. 14 wrote as " Beawar Radhanpur" highway. You might be correct of updating only "bamnera" related updates from my side, but just to inform you I RANK much much better in Wikimapia with any of your wikipedian, Hence ones again I am correcting the information by keeping you informed.RasikdaveRasikdave (talk) 10:25, 9 September 2009 (UTC)Reply

This is an automated message from CorenSearchBot. I have performed a web search with the contents of Bani Thani, and it appears to include a substantial copy of http://marspower.in/products.asp. For legal reasons, we cannot accept copyrighted text or images borrowed from other web sites or printed material; such additions will be deleted. You may use external websites as a source of information, but not as a source of sentences. See our copyright policy for further details.

This message was placed automatically, and it is possible that the bot is confused and found similarity where none actually exists. If that is the case, you can remove the tag from the article and it would be appreciated if you could drop a note on the maintainer's talk page. CorenSearchBot (talk) 09:17, 9 October 2009 (UTC)Reply

Hello, and welcome to Wikipedia! We welcome and appreciate your contributions, such as Uttam Prakash Agarwal, but we regretfully cannot accept copyrighted text or images borrowed from either web sites or printed material. This article appears to be a copy from http://www.icai.org/post.html?post_id=4010, and therefore a copyright violation. The copyrighted text has been or will soon be deleted. While we appreciate contributions, we must require all contributors to understand and comply with our copyright policy. Wikipedia takes copyright violations very seriously, and persistent violators are liable to be blocked from editing.

If you believe that the article is not a copyright violation, or if you have permission from the copyright holder to release the content freely under allowance license, then you should do one of the following:

• If you have permission from the author to release the text under the Creative Commons Attribution-ShareAlike License (CC-BY-SA), leave a message explaining the details at Talk:Uttam Prakash Agarwal and send an email with confirmation of permission to "permissions-en (at) wikimedia (dot) org". Make sure you quote the exact page name, Uttam Prakash Agarwal, in your email. See Wikipedia:Requesting copyright permission for instructions.
• If a note on the original website states that re-use is permitted "under the Creative Commons Attribution-ShareAlike License (CC-BY-SA), version 3.0, or that the material is released into the public domain leave a note at Talk:Uttam Prakash Agarwal with a link to where we can find that note.
• If you own the copyright to the material: send an e-mail from an address associated with the original publication to permissions-en(at)wikimedia(dot)org or a postal message to the Wikimedia Foundation permitting re-use under the Creative Commons Attribution-ShareAlike License and GNU Free Documentation License, and note that you have done so on Talk:Uttam Prakash Agarwal. See Wikipedia:Donating copyrighted materials for instructions.

It may also be necessary for the text be modified to have an encyclopedic tone and to follow Wikipedia article layout. For more information on Wikipedia's policies, see Wikipedia's policies and guidelines.

If you would like to begin working on a new version of the article you may do so at this temporary page. Leave a note at Talk:Uttam Prakash Agarwal saying you have done so and an administrator will move the new article into place once the issue is resolved. Thank you, and please feel welcome to continue contributing to Wikipedia. Happy editing! Moonriddengirl ^(talk) 12:33, 27 March 2010 (UTC)Reply

Hello. Your account has been granted the "reviewer" userright, allowing you to review other users' edits on certain flagged pages. Pending changes, also known as flagged protection, will be commencing a two-month trial at approximately 23:00, 2010 June 15 (UTC).

Reviewers can review edits made by users who are not autoconfirmed to articles placed under flagged protection. Flagged protection is applied to only a small number of articles, similarly to how semi-protection is applied but in a more controlled way for the trial.

When reviewing, edits should be accepted if they are not obvious vandalismorBLP violations, and not clearly problematic in light of the reason given for protection (see Wikipedia:Reviewing process). More detailed documentation and guidelines can be found here.

If you do not want this userright, you may ask any administrator to remove it for you at any time. Courcelles (talk) 03:57, 16 June 2010 (UTC)Reply

This newsletter is automatically delivered by -- Tinu Cherian BOT - 18:19, 30 June 2010 (UTC)Reply

--naveenpf (talk) 03:52, 13 November 2010 (UTC)Reply

This newsletter is automatically delivered by User:Od Mishehu AWB, operated by עוד מישהו Od Mishehu 09:41, 24 November 2010 (UTC)Reply

Hi,

Please see the message at WikiProject Indian roads subject "Madhya Pradesh State Highway Shields" and please mark your comments --naveenpf (talk) 03:31, 27 November 2010 (UTC)Reply

Thank you for uploading File:Busstand.JPG. However, it currently is missing information on its copyright status. Wikipedia takes copyright very seriously. It may be deleted soon, unless we can determine the license and the source of the file. If you know this information, then you can add a copyright tag to the image description page.

If you have uploaded other files, consider checking that you have specified their license and tagged them, too. You can find a list of files you have created in your upload log.

If you have any questions, please feel free to ask them at the media copyright questions page. Thanks again for your cooperation. Sfan00 IMG (talk) 23:53, 10 January 2011 (UTC)Reply

Thank you for uploading File:Manganiyars Performing.jpg. However, it currently is missing information on its copyright status. Wikipedia takes copyright very seriously. It may be deleted soon, unless we can determine the license and the source of the file. If you know this information, then you can add a copyright tag to the image description page.

If you have uploaded other files, consider checking that you have specified their license and tagged them, too. You can find a list of files you have created in your upload log.

If you have any questions, please feel free to ask them at the media copyright questions page. Thanks again for your cooperation. Sfan00 IMG (talk) 00:21, 11 January 2011 (UTC)Reply

A tag has been placed on Template:Villages in Pali district requesting that it be speedily deleted from Wikipedia. This has been done under section T3 of the criteria for speedy deletion, because it is a deprecated or orphaned template. After seven days, if it is still unused and the speedy deletion tag has not been removed, the template will be deleted.

If the template is intended to be substituted, please feel free to remove the speedy deletion tag and please consider putting a note on the template's page indicating that it is substituted so as to avoid any future mistakes (<noinclude>{{transclusionless}}</noinclude>).

Thanks. — This, that, and the other (talk) 06:59, 23 January 2011 (UTC)Reply

The article O P Jangir has been proposed for deletion because of the following concern:

Very limited citability in GScholar, does not appear to pass WP:PROF

While all contributions to Wikipedia are appreciated, content or articles may be deleted for any of several reasons.

You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.

Please consider improving the article to address the issues raised. Removing {{proposed deletion/dated}} will stop the proposed deletion process, but other deletion processes exist. The speedy deletion process can result in deletion without discussion, and articles for deletion allows discussion to reach consensus for deletion. Nsk92 (talk) 12:35, 17 July 2011 (UTC)Reply

Good day! Could you help me and provide translations for the following 100 basic word in Rajasthani. Not in the standard Hindi but in your native local variety (dialect) if you (used to) speak any (and then indicate please precise location like state – district – town/village). If there are synonyms or known dialectal variants provide them with comments if possible. Also please indicate if you know that certain words are borrowing. You can fill in right here using either IPA transcription or any other spelling you like (just describe your conventions). Thank you in advance! --Koryakov Yuri (talk) 12:16, 17 August 2011 (UTC)Reply

• I, me –
• thou (you, singular) –
• we –
• this –
• that –
• who? –
• what? –
• not –
• all –
• many –
• one –
• two –
• big –
• long –
• small –
• woman –
• man (adult male) –
• man (human being) –
• fish –
• bird –
• dog –
• louse –
• tree –
• seed –
• leaf –
• root –
• bark (of a tree) –
• skin –
• meat (flesh) –
• blood –
• bone –
• fat –
• egg –
• horn –
• tail –
• feather (of a bird) –
• hair –
• head –
• ear –
• eye –
• nose –
• mouth –
• tooth –
• tongue –
• claw (nail) –
• foot –
• knee –
• hand –
• belly –
• neck –
• breast(s) (of a woman) –
• heart –
• liver –
• drink (verb) –
• eat (verb) –
• bite (verb) –
• see (verb) –
• hear (verb) –
• know (verb) –
• sleep (verb) –
• die (verb) –
• kill (verb) –
• swim (verb) –
• fly (verb) –
• walk/go (verb) –
• come (verb) –
• lie (down) (verb) –
• sit (verb) –
• stand (verb) –
• give (verb) –
• say (verb) –
• sun –
• moon –
• star –
• water –
• rain –
• stone –
• sand –
• earth –
• cloud –
• smoke –
• fire –
• ash –
• burn (trans. verb) –
• road (path) –
• mountain –
• red –
• green –
• yellow –
• white –
• black –
• night –
• warm (hot) –
• cold –
• full –
• new –
• good –
• round –
• dry –
• name –

Thanks for uploading File:Raj Patrika 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 orphaned, meaning that it is 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).

PLEASE NOTE:

• I am a bot, and will therefore not be able to answer your questions. If you have a question, place a {{helpme}} template, along with your question, beneath this message.
• I will remove the request for deletion if the file is used in an article once again.
• If you receive this notice after the image is deleted, and you want to restore the image, click here to file an un-delete request.
• To opt out of these bot messages, add {{bots|deny=DASHBot}} to your talk page.
• If you believe the bot has made an error, please turn it off here and leave a message on my owner's talk page.

Thank you. DASHBot (talk) 18:21, 31 August 2011 (UTC)Reply

Hello,

My name is Victor Grigas, and I'm a storyteller at the Wikimedia foundation. We're telling stories of Wikipedia users, editors, donors, programmers and staff to paint a picture of who uses Wikipedia - for the 2011 fundraiser.

I am in the process of planning a trip to India to gather stories from Indian Wikipedians in face-to-face interviews (possibly on video).

My primary goal is to conduct 15-20 interviews, and hopefully enough of my interviews will make compelling stories that will effectively solicit donations from the public. These stories may also be used for other communication purposes by the foundation.

I found your userpage on a list of prolific Wikipedians and thought I’d reach out to you. Prolific editing is always a good story to tell!

If you are interested in participating, please contact me via my email:

vgrigas@wikimedia.org

Thank you for your time!

Victor

About me: I have been a Wikipedia editor since 2005. My userpage can be found here: http://en.wikipedia.org/wiki/User:Victorgrigas

I see that you created a few more articles. You should create them with "State Highway <number> (Rajasthan)" as the title because "RJ SH <number>" isn't a very meaningful title to our global audience, although it makes a great redirect. Also, you don't need to add List of State Highways in Rajasthan as a "See also" because it's now in the infobox. One last tip, but don't use the |states= parameter to list the districts when we have |districts= for that purpose. Then if you pipe the links to the name, you'll get a meaningful addition to the infobox. Imzadi 1979 → 00:12, 21 November 2011 (UTC)Reply

Thanks for uploading File:Raj Patrika 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).

Note that any non-free images not used in any articles will be deleted after seven days, as described in the criteria for speedy deletion. Thank you. Skier Dude (talk) 04:47, 1 March 2012 (UTC)Reply

Hello friends, we are a number of editors from WikiProject India have got together to assess the many thousands of articles under the stewardship of the project, and we'd love to have you, a fellow member, join us. These articles require assessment, that is, the addition of a WikiProject template to the talk page of an article, assessing it for quality and importance and adding a few extra parameters to it.

As of March 11, 2012, 07:00 UTC, WikiProject India has 95,998 articles under its stewardship. Of these 13,980 articles are completely unassessed (both for class and importance) and another 42,415 articles are unassessed for importance only. Accordingly, a Tag & Assess 2012 drive-cum-contest has begun from March 01, 2012 to last till May 31, 2012.

If you are new to assessment, you can learn the minimum about how to evaluate from Part One of the Assessment Guide. Part Two of the Guide will help you learn to employ the full functionality of the talk page template, should you choose to do so.

You can sign up on the Tag & Assess page. There are a number of awards to be given in recognition of your efforts. Come & join us to take part in this exciting new venture. You'll learn more about India in this way.

ssriram_mt (talk) & AshLin (talk) (Drive coordinators)

Delivered per requestonWikipedia:Bot requests. 01:20, 12 March 2012 (UTC) The Helpful Bot 01:20, 12 March 2012 (UTC)Reply

Hi. When you recently edited Rani, Rajasthan, you added a link pointing to the disambiguation page Luni (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.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 14:26, 4 April 2012 (UTC)Reply

 Template:Notable Gujarati writers has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Lfdder (talk) 23:11, 28 July 2013 (UTC)Reply

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 "Edit^beta"
• 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)
• Categories with ':'s in their names (like Category:Wikipedia:Privacy) now work correctly (T53902)
• 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.

As always, if you have questions or suggestions, or if you encounter problems, please let everyone know by posting problem reports at Wikipedia:VisualEditor/Feedback and ideas at Wikipedia talk:VisualEditor. Thank you! Whatamidoing (WMF) 23:21, 6 August 2013 (UTC)Reply

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.

For other questions or suggestions, or if you encounter problems, please let everyone know by posting problem reports at Wikipedia:VisualEditor/Feedback and other ideas at Wikipedia talk:VisualEditor. Thank you! Whatamidoing (WMF) 17:37, 21 August 2013 (UTC)Reply

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.

For more details, read VisualEditor's user guide.

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.

For other questions or suggestions, or if you encounter problems, please let everyone know by posting problem reports at Wikipedia:VisualEditor/Feedback and other ideas at Wikipedia talk:VisualEditor. Thank you! Whatamidoing (WMF) (talk) 21:41, 5 September 2013 (UTC)Reply

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.

For more details, read VisualEditor's user guide.

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.

For other questions or suggestions, or if you encounter problems, please let everyone know by posting problem reports at Wikipedia:VisualEditor/Feedback and other ideas at Wikipedia talk:VisualEditor. Thank you! Whatamidoing (WMF) (talk) 21:43, 19 September 2013 (UTC)Reply

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.

For more information, read Wikipedia:VisualEditor/User guide.

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.

For other questions or suggestions, or if you encounter problems, please let everyone know by posting problem reports at Wikipedia:VisualEditor/Feedback and other ideas at Wikipedia talk:VisualEditor. Thank you! Whatamidoing (WMF) (talk) 18:43, 16 October 2013 (UTC)Reply

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.

For more information about how to use VisualEditor, read Wikipedia:VisualEditor/User guide.

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 Deleteor← 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 IRC to 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.

If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at Wikipedia:VisualEditor/Feedback. Thank you! Whatamidoing (WMF) 22:08, 20 November 2013 (UTC)Reply

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+Vor⌘ 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:Randomtohttps://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.

If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at Wikipedia:VisualEditor/Feedback. Thank you! Whatamidoing (WMF) (talk) 20:39, 19 December 2013 (UTC)Reply

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 hoursonIRC 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.
• Wikipedia:VisualEditor/User guide was updated recently to show some new and upcoming features.

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.

Subscriptions to this newsletter are managed at Wikipedia:VisualEditor/Newsletter. Please add or remove your name to change your subscription settings. If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at Wikipedia:VisualEditor/Feedback. Thank you! Whatamidoing (WMF) 20:04, 17 January 2014 (UTC)Reply

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.

• The main priority is redesigning the reference dialog, with the goal of providing autofill features for ISBNs and URLs and streamlining the process. Current concept drawings are available at mw:VisualEditor/Design/Reference Dialog. Please share your ideas about making referencing quick and easy with the designers.
• 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.
• The character inserter tool in the "Insert" menu is being redesigned. Your feedback on the special character inserter is still wanted, especially if you depend on Wikipedia's character inserters for your normal editing rather than using the ones built into your computer.
• You can now see a help page about keyboard shortcuts in the page menu (three bars next to the Cancel button) (T54844).
• If you edit categories, your changes will now display correctly after saving the page (T50560).
• Saving the page should be faster now (T61660).
• 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").

If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at Wikipedia:VisualEditor/Feedback. Thank you! Whatamidoing (WMF) 04:21, 20 February 2014 (UTC)Reply

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 character inserter tool in the "Insert" menu has been slightly redesigned, to introduce larger buttons. Your suggestions for more significant changes to the special character inserter are still wanted.
• 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+S shortcuts 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.

If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at Wikipedia:VisualEditor/Feedback or by joining the office hours on 19 April 2014 at 2000 UTC. Thank you! MediaWiki message delivery (talk) 22:44, 20 March 2014 (UTC)Reply

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.

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.

If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at Wikipedia:VisualEditor/Feedback or by joining the office hours on Monday, 19 May 2014 at 18:00 UTC. If you'd like to get this on your own page, subscribe at Wikipedia:VisualEditor#Newsletter for English Wikipedia only or at meta:VisualEditor/Newsletter for any project. Thank you! Whatamidoing (WMF) (talk) 20:23, 23 April 2014 (UTC)Reply

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.

Read the user guide for more information.

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.

Eventually, the VisualEditor team plans to add autofill features for these citations. When this long-awaited feature is created, you could add an ISBN, URL, DOI or other identifier to the citation tool, and VisualEditor would automatically fill in as much information for that source as possible. The concept drawings can be seen at mw:VisualEditor/Design/Reference Dialog, and your ideas about making referencing quick and easy are still wanted.

• 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.

If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at mw:VisualEditor/Feedback or by joining the office hours on Thursday, 19 June 2014 at 10:00 UTC. If you'd like to get this newsletter on your own page (about once a month), please subscribe at w:en:Wikipedia:VisualEditor/Newsletter for English Wikipedia only or at meta:VisualEditor/Newsletter for any project. Thank you! Whatamidoing (WMF) 22:16, 21 May 2014 (UTC)Reply

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.

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.

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).

To change your subscription to this newsletter, please see the subscription pages on Metaorthe English Wikipedia. Thank you! Whatamidoing (WMF) (talk) 04:59, 25 June 2014 (UTC)Reply

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.

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.

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).

If you'd like to get this newsletter on your own page (about once a month), please subscribe at w:en:Wikipedia:VisualEditor/Newsletter for English Wikipedia only or at Meta for any project. Thank you! Whatamidoing (WMF) (talk) 18:14, 8 August 2014 (UTC)Reply

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.

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.

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.

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 UTConIRC.

Give feedback on VisualEditor at mw:VisualEditor/Feedback. Subscribe or unsubscribe at Meta. To help with translations, please subscribe to the Translators mailing list or contact Elitre at Meta. Thank you!

— Whatamidoing (WMF) (talk) 00:10, 8 October 2014 (UTC)Reply

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.

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.

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.

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.

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!

— Whatamidoing (WMF) 20:41, 6 November 2014 (UTC)Reply

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).

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.

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 features for citations in January. Planned changes to the media search dialog will make choosing between possible images easier.

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• 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.
• The design research team wants to see how real editors work. Please sign up for their research program.

If you would like to help with translations of this newsletter, please subscribe to the Translators mailing listorcontact us directly, so that we can notify you when the next issue is ready. Subscribe or unsubscribe at Meta.

Thank you! WhatamIdoing (WMF) (talk) 23:37, 20 December 2014 (UTC)Reply

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.

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.

The Editing team will soon add auto-fill features for citations. The Citoid service takes a URLorDOI 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.

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• Please help complete translations of the user guide for users who speak your language.
• 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.

Subscribe or unsubscribe at Wikipedia:VisualEditor/Newsletter. Translations are available through Meta. Thank you! Whatamidoing (WMF) 20:23, 2 February 2015 (UTC)Reply

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.

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 features for 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).

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.

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• 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!
• The design research team wants to see how real editors work. Please sign up for their research program.
• 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 listorcontact us directly, so that we can notify you when the next issue is ready. Thank you!

-Whatamidoing (WMF) (talk), 17:50, 3 April 2015 (UTC)Reply

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.

Atest 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.

Auto-fill features for 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.

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• 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 listorcontact 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)Reply

Read this in another language • Local subscription list • Subscribe to the multilingual edition

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.

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.

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.  

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.

• Share your ideas and ask questions at Wikipedia:VisualEditor/Feedback.
• 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 design research team wants to see how real editors work. Please sign up for their research program.
• 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.

If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing listorcontact Elitre directly, so that she can notify you when the next issue is ready. Thank you! Whatamidoing (WMF) (talk) 00:01, 8 August 2015 (UTC)Reply

This note is only delivered to English Wikipedia subscribers of the visual editor's newsletter.

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)Reply

Read this in another language • Subscription list for this multilingual newsletter

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.

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 sheet music 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.

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.

• Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page uses Flow for discussions.
• 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).
• Local admins can set up the Citoid automatic reference feature for your wiki. If you need help, then 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 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.

If you can't read this in your favorite language, then please help us with translations! Subscribe to the Translators mailing listorcontact us directly, so that we can notify you when the next issue is ready. Thank you!

— Whatamidoing (WMF) 04:16, 30 October 2015 (UTC)Reply

Hi,
You appear to be eligible to vote in the current Arbitration Committee election. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to enact binding solutions for disputes between editors, primarily related to serious behavioural issues that the community has been unable to resolve. This includes the ability 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. If you wish to participate, you are welcome to review the candidates' statements and submit your choices on the voting page. For the Election committee, MediaWiki message delivery (talk) 13:48, 24 November 2015 (UTC)Reply

Read this in another language • Subscription list

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.

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.

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:".

The visual editor will be offered to all editors at the following Wikipedias in early 2016: Amharic, Buginese, Min Dong, Cree, Manx, Hakka, Armenian, Georgian, Pontic, Serbo-Croatian, Tigrinya, Mingrelian, Zhuang, and Min Nan. (T116523) Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. The developers would like to know how well it works. Please tell them what kind of computer, web browser, and keyboard you are using.

In 2016, the feedback pages for the visual editor on many Wikipedias will be redirected to mediawiki.org. (T92661)

• Please try the new system for the single edit tabontest2.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.orgorsign 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 listorcontact us directly, so that we can notify you when the next issue is ready. Thank you!

Whatamidoing (WMF), 00:54, 24 December 2015 (UTC)Reply

Read this in another language • Subscription list for this multilingual newsletter

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.

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.

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.

The visual editor will be offered to all editors at most "Phase 6" Wikipedias during the next few months. The developers would like to know how well the visual editor works in your language. They particularly 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 the following languages: Japanese, Korean, Urdu, Persian, Arabic, Tamil, Marathi, Malayalam, Hindi, Bengali, Assamese, Thai, Aramaic and others.

• Please try out the newest version of the single edit tabontest2.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).
• Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Join the Tech Talk about "Automated citations in Wikipedia: Citoid and the technology behind it" with Sebastian Karcher on 29 February 2016.

If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing listorcontact us directly, so that we can notify you when the next issue is ready. Thanks!

– Whatamidoing (WMF) 17:47, 25 February 2016 (UTC)Reply

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.

You can choose one or two edit tabs. If you chose one edit tab, then you can switch between the two editing environments by clicking the buttons in the toolbar (shown in the screenshots). See Help:VisualEditor/User guide#Switching between the visual and wikitext editors for more information and screenshots.

There is more information about this interface change at mw:VisualEditor/Single edit tab. If you have questions, suggestions, or problems to report, then please leave a note at Wikipedia:VisualEditor/Feedback.

Whatamidoing (WMF) 19:22, 11 April 2016 (UTC)Reply

Editing News #2—2016 Read this in another language • Subscription list for this multilingual newsletter

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.

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.

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 visual editor will be offered to all editors at the remaining "Phase 6" Wikipedias during the next few months. 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: Arabic, Hindi, Thai, Tamil, Marathi, Malayalam, Urdu, Persian, Bengali, Assamese, Aramaic and others.

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.

• Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor? Please sign up for the new VisualEditor Community Taskforce.
• 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 listorcontact us directly, so that we can notify you when the next issue is ready. Thank you!

Whatamidoing (WMF) (talk), 21:09, 30 June 2016 (UTC)Reply

Read this in another language • Subscription list for this multilingual newsletter • Subscribe or unsubscribe on the English Wikipedia

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.

• You can now set text as small or big.[3]
• 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]

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.

Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor? Please sign up for the new VisualEditor Community Taskforce.

If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing listorcontact us directly, so that we can notify you when the next issue is ready. Thank you! Whatamidoing (WMF) (talk) 18:19, 14 October 2016 (UTC)Reply

Hi. The Wikipedia:WikiProject Asia/The 10,000 Challenge has recently started, based on the UK/Ireland Wikipedia:The 10,000 Challenge and Wikipedia:WikiProject Africa/The 10,000 Challenge. The idea is not to record every minor edit, but to create a momentum to motivate editors to produce good content improvements and creations and inspire people to work on more countries than they might otherwise work on. There's also the possibility of establishing smaller country or regional challenges for places like South East Asia, Japan/China or India etc, much like Wikipedia:The 1000 Challenge (Nordic). For this to really work we need diversity and exciting content and editors from a broad range of countries regularly contributing. At some stage we hope to run some contests to benefit Asian content, a destubathon perhaps, aimed at reducing the stub count would be a good place to start, based on the current Wikipedia:WikiProject Africa/The Africa Destubathon which has produced near 200 articles in just three days. If you would like to see this happening for Asia, and see potential in this attracting more interest and editors for the country/countries you work on please sign up and being contributing to the challenge! This is a way we can target every country of Asia, and steadily vastly improve the encyclopedia. We need numbers to make this work so consider signing up as a participant! Thank you. --Ser Amantio di Nicolao^{Che dicono a Signa?}_{Lo dicono a Signa.} 05:03, 20 October 2016 (UTC)Reply

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.

If you wish to participate in the 2016 election, please review the candidates' statements and submit your choices on the voting page. MediaWiki message delivery (talk) 22:08, 21 November 2016 (UTC)Reply