User talk:MatthewBurton/Archive2

Your submission at Articles for creation
Pharmavite, which you submitted to Articles for creation, has been created. Thank you for helping Wikipedia!  Chzz  ► 17:30, 4 August 2010 (UTC)
 * Please continue making quality contributions to Wikipedia. Note that because you are a logged-in user, you can create articles yourself, and don't have to post a request.
 * If you would like to help us improve this process, please consider

Your submission at Articles for creation
Styron (company), which you submitted to Articles for creation, has been created. Thank you for helping Wikipedia! Commander Keane (talk) 05:55, 30 August 2010 (UTC)
 * Please continue making quality contributions to Wikipedia. Note that because you are a logged-in user, you can create articles yourself, and don't have to post a request.
 * If you would like to help us improve this process, please consider

Articles you might like to edit, from SuggestBot
SuggestBot predicts that you will enjoy editing some of these articles. Have fun!

SuggestBot picks articles in a number of ways based on other articles you've edited, including straight text similarity, following wikilinks, and matching your editing patterns against those of other Wikipedians. It tries to recommend only articles that other Wikipedians have marked as needing work. Your contributions make Wikipedia better — thanks for helping.

If you have feedback on how to make SuggestBot better, please tell me on SuggestBot's talk page. Thanks from, SuggestBot's caretaker. -- SuggestBot (talk) 20:45, 24 April 2014 (UTC)

VisualEditor global newsletter—June 2014
Did you know? The character formatting menu, or "" menu lets you set bold, italic, and other text styles. "Clear formatting" removes all text styles and removes links to other pages.

Do you think that clear formatting should remove links? Are there changes you would like to see for this menu? Share your opinion at MediaWiki.org.

The user guide has information about how to use VisualEditor. The VisualEditor team is mostly working to fix bugs, improve performance, reduce technical debt, and other infrastructure needs. You can find on Mediawiki.org weekly updates detailing recent work.


 * They have moved the "" link out of the "" menu, into the "" 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  "  for dates and times in the ISO 8601 format, and  "  for values which are true or false. Also, templates that redirect to other templates (like   →  ) 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   and   in the "" menu, rounding out the full set of page options currently planned.
 * The tool to insert special characters is now wider and simpler.

Looking ahead
The VisualEditor team has posted a draft of their goals for the next fiscal year. You can read them and suggest changes on MediaWiki.org.

The team posts details about planned work on VisualEditor's roadmap. You will soon be able to drag-and-drop text as well as images. If you drag an image to a new place, it won't let you place it in the middle of a paragraph. All dialog boxes and windows will be simplified based on user testing and feedback. The VisualEditor team plans to add autofill features for citations. Your ideas about making referencing quick and easy are still wanted. Support for upright image sizes is being developed. The designers are also working on support for viewing and editing hidden HTML comments and adding rows and columns to tables.

Supporting your wiki
Please read VisualEditor/Citation tool for information on configuring the new citation template menu, labeled "". 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 Meta or the English Wikipedia. Thank you! Whatamidoing (WMF) (talk) 04:59, 25 June 2014 (UTC)

VisualEditor newsletter—July and August 2014
''The VisualEditor team is currently working mostly to fix bugs, improve performance, reduce technical debt, and other infrastructure needs. You can find on Mediawiki.org weekly updates detailing recent work.'' VisualEditor - Link editing inline box.png.

The user guide is also being updated.
 * alt=Screenshot of VisualEditor's link tool|240px]]

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 (  tags) are now made through the "" menu, including the "" (manual formatting) footnotes and the ability to re-use an existing citation, both of which were previously accessible only through the "" menu. The "" is still added via the "" menu.
 * When you add an image or other media file, you are now prompted to add an image caption immediately. You can also replace an image whilst keeping the original caption and other settings.
 * All tablet users visiting the mobile web version of Wikipedias will be able to opt-in to a version of VisualEditor from 14 August. You can test the new tool by choosing the beta version of the mobile view in the Settings menu.
 * The link tool has a new "Open" button that will open a linked page in another tab so you can make sure a link is the right one.
 * The "Cancel" button in the toolbar has been removed based on user testing. To cancel any edit, you can leave the page by clicking the Read tab, the back button in your browser, or closing the browser window without saving your changes.

Looking ahead
The team posts details about planned work on the VisualEditor roadmap. The VisualEditor team plans to add auto-fill features for citations soon. Your ideas about making referencing quick and easy are still wanted. Support for upright image sizes is being developed. The designers are also working on support for adding rows and columns to tables. Work to support Internet Explorer is ongoing.

Feedback opportunities
The Editing team will be making two presentations this weekend at Wikimania in London. The first is with product manager James Forrester and developer Trevor Parscal on Saturday at 16:30. The second is with developers Roan Kattouw and Trevor Parscal on Sunday at 12:30.

Please share your questions, suggestions, or problems by posting a note at the VisualEditor feedback page or by joining the office hours discussion on Thursday, 14 August 2014 at 09:00 UTC (daytime for Europe, Middle East and Asia) or on Thursday, 18 September 2014 at 16:00 UTC (daytime for the Americas; evening for Europe).

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)

VisualEditor newsletter—September and October 2014
Did you know? TemplateData is a separate program that organizes information about the parameters that can be used in a template. VisualEditor reads that data, and uses it to populate its simplified template dialogs.

With the new TemplateData editor, it is easier to add information about parameters, because the ones you need to use are pre-loaded.

See the help page for TemplateData for more information about adding TemplateData. The user guide has information about how to use VisualEditor. Since the last newsletter, the Editing team has reduced technical debt, simplified some workflows for template and citation editing, made major progress on Internet Explorer support, and fixed over 125 bugs and requests. Several performance improvements were made, especially to the system around re-using references and reference lists. Weekly updates are posted on Mediawiki.org.

There were three issues that required urgent fixes: a deployment error that meant that many buttons didn't work correctly (bugs 69856 and 69864), a problem with edit conflicts that left the editor with nowhere to go (bug 69150), and a problem in Internet Explorer 11 that caused replaced some categories with a link to the system message, MediaWiki:Badtitletext (bug 70894) when you saved. The developers apologize for the disruption, and thank the people who reported these problems quickly.

Increased support for devices and browsers
Internet Explorer 10 and 11 users now have access to VisualEditor. This means that about 5% of Wikimedia's users will now get an "Edit" tab alongside the existing "Edit source" tab. Support for Internet Explorer 9 is planned for the future.

Tablet users browsing the site's mobile mode now have the option of using a mobile-specific form of VisualEditor. More editing tools, and availability of VisualEditor on smartphones, is planned for the future. The mobile version of VisualEditor was tweaked to show the context menu for citations instead of basic references (bug 68897). A bug that broke the editor in iOS was corrected and released early (bug 68949). For mobile tablet users, three bugs related to scrolling were fixed (bug 66697, bug 68828, bug 69630). You can use VisualEditor on the mobile version of Wikipedia from your tablet by clicking on the cog in the top-right when editing a page and choosing which editor to use.

TemplateData editor
A tool for editing TemplateData will be deployed to more Wikipedias soon.  Other Wikipedias and some other projects may receive access next month. This tool makes it easier to add TemplateData to the template's documentation. When the tool is enabled, it will add a button above every editing window for a template (including documentation subpages). To use it, edit the template or a subpage, and then click the "" button at the top. Read the help page for TemplateData. You can test the TemplateData editor in a sandbox at Mediawiki.org. Remember that TemplateData should be placed either on a documentation subpage or on the template page itself. Only one block of TemplateData will be used per template.

Other changes
Several interface messages and labels were changed to be simpler, clearer, or shorter, based on feedback from translators and editors. The formatting of dialogs was changed, and more changes to the appearance will be coming soon, when VisualEditor implements the new MediaWiki theme from Design. (A preview of the theme is available on Labs for developers.) The team also made some improvements for users of the Monobook skin that improved the size of text in toolbars and fixed selections that overlapped menus.

VisualEditor-MediaWiki now supplies the  or   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  attribute but no   set (bug 69955).

Looking ahead
The team posts details about planned work on the VisualEditor roadmap. The VisualEditor team plans to add auto-fill features for citations soon, perhaps in late October.

The team is also working on support for adding rows and columns to tables, and early work for this may appear within the month. Please comment on the design at Mediawiki.org.

In the future, real-time collaborative editing may be possible in VisualEditor. Some early preparatory work for this was recently done.

Supporting your wiki
At Wikimania, several developers gave presentations about VisualEditor. A translation sprint focused on improving access to VisualEditor was supported by many people. Deryck Chan was the top translator. Special honors also go to संजीव कुमार (Sanjeev Kumar), Robby, Takot, Bachounda, Bjankuloski06 and Ата. A summary of the work achieved by the translation community has been posted here. Thank you all for your work.

VisualEditor can be made available to most non-Wikipedia projects. If your community would like to test VisualEditor, please contact product manager James Forrester or file an enhancement request in Bugzilla.

Please join the office hours on Saturday, 18 October 2014 at 18:00 UTC (daytime for the Americas; evening for Africa and Europe) and on Wednesday, 19 November at 16:00 UTC on IRC.

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

VisualEditor newsletter—November 2014
Did you know? VisualEditor is also available on the mobile version of Wikipedia. Login and click the pencil icon to open the page you want to edit. Click on the gear-shaped settings in the upper-right corner, to pick which editor to use. Choose "Edit" to use VisualEditor, or "Edit source" to use the wikitext editor.

It will remember whether you used wikitext or VisualEditor, and use the same editor the next time you edit an article.

The user guide has information about how to use VisualEditor. Not all features are available in Mobile Web. Since the last newsletter, the Editing Team has fixed many bugs and requests, and worked on support for editing tables and for using non-Latin languages. Their weekly updates are posted on Mediawiki.org. Informal notes from the recent quarterly review were posted on Meta.

Recent improvements
The French Wikipedia should see better search results for links, templates, and media because the new search engine was turned on for everyone there. This change is expected at the Chinese and German Wikipedias next week, and eventually at the English Wikipedia.

The "pawn" system has been mostly replaced. Bugs in this system sometimes added a chess pawn character to wikitext. The replacement provides better support for non-Latin languages, with full support hopefully coming soon.

VisualEditor is now provided to editors who use Internet Explorer 10 or 11 on desktop and mobile devices. Internet Explorer 9 is not supported yet.

The keyboard shortcuts for items in the toolbar's menus are now shown in the menus. VisualEditor will replace the existing design with a new theme from the User Experience / Design group. The appearance of dialogs has already changed in one Mobile version. The appearance on desktops will change soon. (You can see a developer preview of the old "Apex" design and the new "MediaWiki" theme which will replace it.)

Several bugs were fixed for internal and external links. Improvements to MediaWiki's search solved an annoying problem: If you searched for the full name of the page or file that you wanted to link, sometimes the search program could not find the page. A link inside a template, to a local page that does not exist, will now show red, exactly as it does when reading the page. Due to a error, for about two weeks this also affected all external links inside templates. Opening an auto-numbered link node like with the keyboard used to open the wrong link tool. These problems have all been fixed.

TemplateData
''' The tool for quickly editing TemplateData will be deployed to all Wikimedia Foundation wikis on Thursday, 6 November. '''   This tool is already available on the biggest 40 Wikipedias, and now all wikis will have access to it. This tool makes it easier to add TemplateData to the template's documentation. When the tool is enabled, it will add a button above every editing window for a template (including documentation subpages). To use it, edit the template or a subpage, and then click the "" button at the top. Read the help page for TemplateData. You can test the TemplateData editor in a sandbox at Mediawiki.org. Remember that TemplateData should be placed either on a documentation subpage or on the template page itself. Only one block of TemplateData will be used per template.

You can use the new autovalue setting to pre-load a value into a template. This can be used to substitute dates, as in this example, or to add the most common response for that parameter. The autovalue can be easily overridden by the editor, by typing something else in the field.

In TemplateData, you may define a parameter as "required". The template dialog in VisualEditor will warn editors if they leave a "required" parameter empty, and they will not be able to delete that parameter. If the template can function without this parameter, then please mark it as "suggested" or "optional" in TemplateData instead.

Looking ahead
Basic support for inserting tables and changing the number of rows and columns in tables will appear next Wednesday. Advanced features, like dragging columns to different places, will be possible later. The VisualEditor team plans to add auto-fill features for citations soon. To help editors find the most important items more quickly, some items in the toolbar menus will be hidden behind a "More" item, such as "underlining" in the styling menu. The appearance of the media search dialog will improve, to make picking between possible images easier and more visual. The team posts details about planned work on the VisualEditor roadmap.

The user guide will be updated soon to add information about editing tables. The translations for most languages except Spanish, French, and Dutch are significantly out of date. Please help complete the current translations for users who speak your language. Talk to us if you need help exporting the translated guide to your wiki.  You can influence VisualEditor's design . Tell the VisualEditor team what you want changed during the office hours via IRC. The next sessions are on Wednesday, 19 November at 16:00 UTC and on Wednesday 7 January 2015 at 22:00 UTC. You can also share your ideas at mw:VisualEditor/Feedback. Also, user experience researcher Abbey Ripstra is looking for editors to show her how they edit Wikipedia. Please sign up for the research program if you would like to hear about opportunities.

If you would like to help with translations of this newsletter, please subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Subscribe or unsubscribe at VisualEditor/Newsletter. Thank you!

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

VisualEditor newsletter—December 2014


Did you know?

Basic table editing is now available in VisualEditor. You can add and remove rows and columns from existing tables at the click of a button.

The user guide has more information about how to use VisualEditor. Since the last newsletter, the Editing Team has fixed many bugs and worked on table editing and performance. Their weekly status reports are posted on Mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.

VisualEditor was deployed to several hundred remaining wikis as an opt-in beta feature at the end of November, except for most Wiktionaries (which depend heavily upon templates) and all Wikisources (which await integration with ProofreadPage).

Recent improvements
Basic support for editing tables is available. You can insert new tables, add and remove rows and columns, set or remove a caption for a table, and merge cells together. To change the contents of a cell, double-click inside it. More features will be added in the coming months. In addition, VisualEditor now ignores broken, invalid  and   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  paragraphs for quoting and indenting content. This changes a "" into a "".

Some new keyboard sequences can be used to format content. At the start of the line, typing " *  " will make the line a bullet list; " 1.  " or " # " will make it a numbered list; " == " will make it a section heading; " : " will make it a blockquote. If you didn't mean to use these tools, you can press undo to undo the formatting change. There are also two other keyboard sequences: " [[ " for opening the link tool, and " {{ " for opening the template tool, to help experienced editors. The existing standard keyboard shortcuts, like ⌃ Ctrl + K to open the link editor, still work.

If you add a category that has been redirected, then VisualEditor now adds its target. Categories without description pages show up as red.

You can again create and edit galleries as wikitext code.

Looking ahead
VisualEditor will replace the existing design with a new theme designed by the User Experience group. The new theme will be visible for desktop systems at MediaWiki.org in late December and at other sites early January. (You can see a developer preview of the old "Apex" theme and the new "MediaWiki" one which will replace it.)

The Editing team plans to add auto-fill features for citations in January. Planned changes to the media search dialog will make choosing between possible images easier.

Help
If you would like to help with translations of this newsletter, please subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Subscribe or unsubscribe at Meta.
 * 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 "" and "" 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.

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

VisualEditor News 2015—#1


Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's appearance, the coming Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.

The Wikimedia Foundation has named its top priorities for this quarter (January to March). The first priority is making VisualEditor ready for deployment by default to all new users and logged-out users at the remaining large Wikipedias. You can help identify these requirements. There will be weekly triage meetings which will be open to volunteers beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC). Tell Vice President of Engineering Damon Sicore, Product Manager James Forrester and other team members which bugs and features are most important to you. The decisions made at these meetings will determine what work is necessary for this quarter's goal of making VisualEditor ready for deployment to new users. The presence of volunteers who enjoy contributing MediaWiki code is particularly appreciated. Information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins. Due to some breaking changes in MobileFrontend and VisualEditor, VisualEditor was not working correctly on the mobile site for a couple of days in early January. The teams apologize for the problem.

Recent improvements
The new design for VisualEditor aligns with MediaWiki's Front-End Standards as led by the Design team. Several new versions of the OOjs UI library have also been released, and these also affect the appearance of VisualEditor and other MediaWiki software extensions. Most changes were minor, like changing the text size and the amount of white space in some windows. Buttons are consistently color-coded to indicate whether the action: 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.
 * starts a new task, like opening the 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.

Search and replace in long documents is now faster. It does not highlight every occurrence if there are more than 100 on-screen at once (T78234).

Editors at the Hebrew and Russian Wikipedias requested the ability to use VisualEditor in the "Article Incubator" or drafts namespace (T86688, T87027). If your community would like VisualEditor enabled on another namespace on your wiki, then you can file a request in Phabricator. Please include a link to a community discussion about the requested change.

Looking ahead
The Editing team will soon add auto-fill features for citations. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to contribute to the Citoid service's definitions for each website, to improve precision and reduce the need for manual corrections.

We will need editors to help test the new design of the special character inserter, especially if you speak Welsh, Breton, or another language that uses diacritics or special characters extensively. The new version should be available for testing next week. Please contact User:Whatamidoing (WMF) if you would like to be notified when the new version is available. After the special character tool is completed, VisualEditor will be deployed to all users at Phase 5 Wikipedias. This will affect about 50 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh. The date for this change has not been determined.

Let's work together

 * 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 VisualEditor/Newsletter. Translations are available through Meta. Thank you! Whatamidoing (WMF) 20:23, 2 February 2015 (UTC)

VisualEditor News #2—2015
Did you know?

With Citoid in VisualEditor, you click the 'book with bookmark' icon and paste in the URL for a reliable source:



Citoid looks up the source for you and returns the citation results. Click the green "Insert" button to accept its results and add them to the article:



After inserting the citation, you can change it. Select the reference, and click the "Edit" button in the context menu to make changes.

The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's performance, the Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.

The weekly task triage meetings continue to be open to volunteers, each Wednesday at 11:00 (noon) PDT (18:00 UTC). You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug. Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal.

Recent improvements
VisualEditor is now substantially faster. In many cases, opening the page in VisualEditor is now faster than opening it in the wikitext editor. The new system has improved the code speed by 37% and network speed by almost 40%.

The Editing team is slowly adding auto-fill 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).

Looking ahead
The special character inserter in VisualEditor will soon use the same special character list as the wikitext editor. Admins at each wiki will also have the option of creating a custom section for frequently used characters at the top of the list. Instructions for customizing the list will be posted at mediawiki.org.

The team is discussing a test of VisualEditor with new users, to see whether they have met their goals of making VisualEditor suitable for those editors. The timing is unknown, but might be relatively soon.

Let's work together

 * 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 "" and "" icons for the character formatting menu in Phabricator.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

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

VisualEditor News #3—2015
Did you know?

When you click on a link to an article, you now see more information: The link tool has been re-designed: There are separate tabs for linking to internal and external pages.

The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has created new interfaces for the link and citation tools, as well as fixing many bugs and changing some elements of the design. Some of these bugs affected users of VisualEditor on mobile devices. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.

A test of VisualEditor's effect on new editors at the English Wikipedia has just completed the first phase. During this test, half of newly registered editors had VisualEditor automatically enabled, and half did not. The main goal of the study is to learn which group was more likely to save an edit and to make productive, unreverted edits. Initial results will be posted at Meta later this month.

Recent improvements
Auto-fill 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 (,, or ). The cite button is now labeled with the word "" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "", 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 "" each time they want to add another parameter (T95696). The team added a new property for TemplateData, "", 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.

Let's work together

 * 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 list or contact us directly, so that we can notify you when the next issue is ready. Thank you! Whatamidoing (WMF) (talk) 17:31, 6 June 2015 (UTC)

VisualEditor News #4—2015
Read this in another language •  Local subscription list  •  Subscribe to the multilingual edition

Did you know?

You can add quotations marks before and after a title or phrase with a single click.

Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar). Click the button. VisualEditor will add the quotation marks on either side of the text you selected. You can read and help translate the user guide, which has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.

Wikimania
The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations and the future of editing.

Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince,  जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.

For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).

For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).

We published some graphs showing the effect of the event on the Translathon page. Thank you to the translators for participating and the translatewiki.net staff for facilitating this initiative.

Recent improvements
Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.

Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top.

In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.

Future changes
The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.

On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.

Let's work together

 * Share your ideas and ask questions at 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 VisualEditor/IME Testing 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 "" and "" 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 list or contact 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)

VisualEditor update

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

VisualEditor News #5—2015
Read this in another language •  Subscription list for this multilingual newsletter

Did you know?

You can use the visual editor on smartphones and tablets. Click the pencil icon to open the editor for a page. Inside that, use the gear menu in the upper right corner to "".

The editing button will remember which editing environment you used last time, and give you the same one next time. The desktop site will be switching to a system similar to this one in the coming months. You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has fixed many bugs, added new features, and made some small design changes. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving support for languages like Japanese and Arabic, making it easier to edit on mobile devices, and providing rich-media tools for formulæ, charts, galleries and uploading.

Recent improvements
Educational features: The first time you use the visual editor, it now draws your attention to the and  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 " " 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 "" 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.

Future changes
You will soon be able to switch from the wikitext to the visual editor after you start editing. (T49779) Previously, you could only switch from the visual editor to the wikitext editor. Bi-directional switching will make possible a single edit tab. (T102398) This project will combine the "" and "" tabs into a single "" tab, similar to the system already used on the mobile website. The "" tab will open whichever editing environment you used last time.

Let's work together

 * 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 VisualEditor/IME Testing if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - [//jp.wikipedia.org/wiki/Wikipedia:ビジュアルエディター/フィードバック/IME 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 list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

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

ArbCom elections are now open!
MediaWiki message delivery (talk) 16:32, 23 November 2015 (UTC)

VisualEditor News #6—2015
Read this in another language •  Subscription list

Did you know?

A new, simpler system for editing will offer a single Edit button. Once the page has opened, you can switch back and forth between visual and wikitext editing.

If you prefer having separate edit buttons, then you can set that option in your preferences, either in a pop-up dialog the next time you open the visual editor, or by going to Special:Preferences and choosing the setting that you want: The current plan is for the default setting to have the Edit button open the editing environment you used most recently. You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has fixed many bugs and expanded the mathematics formula tool. Their workboard is available in Phabricator. Their current priorities are improving support for languages such as Japanese and Arabic, and providing rich-media tools for formulæ, charts, galleries and uploading.

Recent improvements
You can switch from the wikitext editor to the visual editor after you start editing.

The LaTeX mathematics formula editor has been significantly expanded. (T118616) You can see the formula as you change the LaTeX code. You can click buttons to insert the correct LaTeX code for many symbols.

Future changes
The single edit tab project will combine the "" and "" tabs into a single "" tab, like the system already used on the mobile website. (T102398) Initially, the "" 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 tab of Special:Preferences in the drop-down menu about "".

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)

Testing opportunities
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready.
 * Please try the new system for the single edit tab on test2.wikipedia.org. You can edit while logged out to see how it works for logged-out editors, or you can create a separate account to be able to set your account's preferences.  Please share your thoughts about the single edit tab system at the feedback topic on mediawiki.org or sign up for formal user research (type "single edit tab" in the question about other areas you're interested in).  The new system has not been finalized, and your feedback can affect the outcome.  The team particularly wants your thoughts about the options in Special:Preferences. The current choices in Special:Preferences are:
 * , and
 * .  (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 VisualEditor/IME Testing if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - [//jp.wikipedia.org/wiki/Wikipedia:ビジュアルエディター/フィードバック/IME Japanese]).
 * .  (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 VisualEditor/IME Testing if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - [//jp.wikipedia.org/wiki/Wikipedia:ビジュアルエディター/フィードバック/IME Japanese]).

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

VisualEditor News #1—2016
Read this in another language • Subscription list for this multilingual newsletter

Did you know?

Among experienced editors, the visual editor's table editing is one of the most popular features. If you select the top of a column or the end of a row, you can quickly insert and remove columns and rows.

Now, you can also rearrange columns and rows. Click "Move before" or "Move after" to swap the column or row with its neighbor.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Japanese, Korean, Arabic, Indic, and Han scripts, and improving the single edit tab interface.

Recent changes
You can switch from the wikitext editor to the visual editor after you start editing. This function is available to nearly all editors at most wikis except the Wiktionaries and Wikisources.

Many local feedback pages for the visual editor have been redirected to mw:VisualEditor/Feedback.

You can now re-arrange columns and rows in tables, as well as copying a row, column or any other selection of cells and pasting it in a new location.

The formula editor has two options: you can choose "Quick edit" to see and change only the LaTeX code, or "Edit" to use the full tool. The full tool offers immediate preview and an extensive list of symbols.

Future changes
The single edit tab project will combine the "" and "" tabs into a single "" tab. This is similar to the system already used on the mobile website. (T102398) Initially, the "" 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 tab of Special:Preferences: 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.
 * , and
 * .  (This is the state for people using the visual editor now.)
 * , and
 * .  (This is the state for people using the visual editor now.)

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.

Let's work together
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thanks!
 * Please try out the newest version of the single edit tab on test2.wikipedia.org. You may need to restore the default preferences (at the bottom of test2wiki:Special:Preferences) to see the initial prompt for options. Were you able to find a preference setting that will work for your own editing? Did you see the large preferences dialog box when you started editing an article there?
 * Can you read and type in Korean, Arabic, Japanese, Indic, or Han scripts? Language engineer David Chan needs help from people who often type in these languages. Please see the instructions at mw:VisualEditor/IME Testing 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.

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

Do you want one Edit tab, or two? It's your choice
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 VisualEditor/Feedback.

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

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

Did you know?

It's quick and easy to insert a references list.

Place the cursor where you want to display the references list (usually at the bottom of the page). Open the "" menu and click the "" icon (three books).

If you are using several groups of references, which is relatively rare, you will have the opportunity to specify the group. If you do that, then only the references that belong to the specified group will be displayed in this list of references.

Finally, click "" in the dialog to insert the. This list will change as you add more footnotes to the page.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Arabic and Indic scripts, and adapting the visual editor to the needs of the Wikivoyages and Wikisources.

Recent changes
The visual editor is now available to all users at most Wikivoyages. It was also enabled for all contributors at the French Wikinews.

The single edit tab feature combines the "" and "" tabs into a single "" 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 "" tab of Special:Preferences. The team is now reviewing the feedback and considering ways to improve the design before rolling it out to more people.

Future changes
The "" button will say "". 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.

Let's work together
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready.
 * 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.

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

Editing News #3—2016
Read this in another language • Subscription list for this multilingual newsletter • Subscribe or unsubscribe on the English Wikipedia

Did you know?

Did you know that you can easily re-arrange columns and rows in the visual editor?



Select a cell in the column or row that you want to move. Click the arrow at the start of that row or column to open the dropdown menu (shown). Choose either "Move before" or "Move after" to move the column, or "Move above" or "Move below" to move the row.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has mainly worked on a new wikitext editor. They have also released some small features and the new map editing tool. Their workboard is available in Phabricator. You can find links to the list of work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, releasing the 2017 wikitext editor as a beta feature, and improving language support.

Recent changes

 * You can now set text as small or big.
 * Invisible templates have been shown as a puzzle icon. Now, the name of the invisible template is displayed next to the puzzle icon.  A similar feature will display the first part of hidden HTML comments.
 * Categories are displayed at the bottom of each page. If you click on the categories, the dialog for editing categories will open.
 * 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.
 * The "Save" button now says "Save page" when you create a page, and "Save changes" when you change an existing page. In the future, the "" button will say "".  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.

Future changes
The visual editor will be offered to all editors at the remaining 10 "Phase 6" Wikipedias during the next month. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including Thai, Burmese and Aramaic.

The team is working on a modern wikitext editor. The 2017 wikitext editor will look like the visual editor and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices in October 2016. You can read about this project in a general status update on the Wikimedia mailing list.

Let's work together
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 list or contact 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)

Editing News #1—2017
Read this in another language • Subscription list for this multilingual newsletter

 Did you know?

Did you know that you can review your changes visually?

When you are finished editing the page, type your edit summary and then choose "". In visual mode, you will see additions, removals, new links, and formatting highlighted. Other changes, such as changing the size of an image, are described in notes on the side.



Click the toggle button to switch between visual and wikitext diffs.



The wikitext diff is the same diff tool that is used in the wikitext editors and in the page history.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has spent most of their time supporting the 2017 wikitext editor mode which is available inside the visual editor as a Beta Feature, and adding the new visual diff tool. Their workboard is available in Phabricator. You can find links to the work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor as a beta feature, and improving the visual diff tool.

Recent changes
A new wikitext editing mode is available as a Beta Feature on desktop devices. The 2017 wikitext editor has the same toolbar as the visual editor and can use the citoid service and other modern tools. Go to Special:Preferences to enable the.

A new visual diff tool is available in VisualEditor's visual mode. You can toggle between wikitext and visual diffs. More features will be added to this later. In the future, this tool may be integrated into other MediaWiki components. 

The team have added multi-column support for lists of footnotes. The  block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. You can request multi-column support for your wiki. 

Other changes:
 * You can now use your web browser's function to switch typing direction in the new wikitext mode. This is particularly helpful for RTL language users like Urdu or Hebrew who have to write JavaScript or CSS. You can use Command+Shift+X or Control+Shift+X to trigger this.
 * The way to switch between the visual editing mode and the wikitext editing mode is now consistent. There is a drop-down menu that shows the two options. This is now the same in desktop and mobile web editing, and inside things that embed editing, such as Flow.
 * The item has been moved to the top of the  menu (from clicking on the  VisualEditor - Icon - Menu.svg icon) for quicker access.  There is also now a "Templates used on this page" feature there.
 * You can now create   tags (sometimes used as  ) for chemical formulas inside the visual editor.
 * Tables can be set as collapsed or un-collapsed.
 * The menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) .  The team thanks the volunteer developer, Tpt.
 * A bug caused some section edit conflicts to blank the rest of the page. This has been fixed.  The team are sorry for the disruption.
 * There is a new keyboard shortcut for citations:  + +  on a PC, or  + +  on a Mac.  It is based on the keyboard shortcut for making links, which is  +  on a PC or  +  on a Mac.

Future changes

 * The VisualEditor team is working with the Community Tech team on a syntax highlighting tool. It will highlight matching pairs of   tags and other types of wikitext syntax.  You will be able to turn it on and off.  It will first become available in VisualEditor's built-in wikitext mode, maybe late in 2017.
 * The kind of button used to, , and finish an edit will change in all WMF-supported wikitext editors. The new buttons will use OOjs UI.  The buttons will be larger, brighter, and easier to read.  The labels will remain the same.  You can test the new button by editing a page and adding   to the end of the URL, like this:  https://www.mediawiki.org/wiki/Project:Sandbox?action=edit&ooui=1  The old appearance will no longer be possible, even with local CSS changes.
 * The outdated 2006 wikitext editor will be removed later this year. It is used by approximately 0.03% of active editors.  See a list of editing tools on mediawiki.org if you are uncertain which one you use.

If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. User:Whatamidoing (WMF) (talk) 19:19, 9 May 2017 (UTC)

Orphaned non-free image File:Nuance PDF Reader.png
Thanks for uploading File:Nuance PDF Reader.png. 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 section F5 of the criteria for speedy deletion. Thank you. --B-bot (talk) 17:23, 2 November 2017 (UTC)

Orphaned non-free image File:Nuance PDF Reader screenshot.png
Thanks for uploading File:Nuance PDF Reader screenshot.png. 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 section F5 of the criteria for speedy deletion. Thank you. --B-bot (talk) 17:24, 2 November 2017 (UTC)

Editing News #1—2018
Read this in another language • Subscription list for the English Wikipedia • Subscription list for the multilingual edition Did you know? Did you know that you can now use the visual diff tool on any page?



Sometimes, it is hard to see important changes in a wikitext diff. This screenshot of a wikitext diff (click to enlarge) shows that the paragraphs have been rearranged, but it does not highlight the removal of a word or the addition of a new sentence.

If you enable the Beta Feature for "", you will have a new option. It will give you a new box at the top of every diff page. This box will let you choose either diff system on any edit.

Click the toggle button to switch between visual and wikitext diffs.

In the visual diff, additions, removals, new links, and formatting changes will be highlighted. Other changes, such as changing the size of an image, are described in notes on the side.



This screenshot shows the same edit as the wikitext diff. The visual diff highlights the removal of one word and the addition of a new sentence. An arrow indicates that the paragraph changed location.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the Editing Team has spent most of their time supporting the 2017 wikitext editor mode, which is available inside the visual editor as a Beta Feature, and improving the visual diff tool. Their work board is available in Phabricator. You can find links to the work finished each week at VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor, and improving the visual diff tool.

Recent changes

 * The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools.  The team have been comparing the performance of different editing environments.  They have studied how long it takes to open the page and start typing.  The study uses data for more than one million edits during December and January.  Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor.  Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits.  More information will be posted at Contributors/Projects/Editing performance.
 * The visual diff tool was developed for the visual editor. It is now available to all users of the visual editor and the 2017 wikitext editor.  When you review your changes, you can toggle between wikitext and visual diffs.  You can also enable the new Beta Feature for "Visual diffs".  The Beta Feature lets you use the visual diff tool to view other people's edits on page histories and Special:RecentChanges.
 * Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor.
 * The citoid service automatically translates URLs, DOIs, ISBNs, and PubMed id numbers into wikitext citation templates. This tool has been used at the English Wikipedia for a long time.  It is very popular and useful to editors, although it can be tricky for admins to set up.  Other wikis can have this service, too.  Please read the instructions. You can ask the team to help you enable citoid at your wiki.

Let's work together

 * The team is planning a presentation about editing tools for an upcoming Wikimedia Foundation metrics and activities meeting.
 * Wikibooks, Wikiversity, and other communities may have the visual editor made available by default to contributors. If your community wants this, then please contact Dan Garry.
 * The  block can automatically display long lists of references in columns on wide screens.  This makes footnotes easier to read.  This has already been enabled at the English Wikipedia.  If you want columns for a long list of footnotes on this wiki, you can use either   or the plain (no parameters)   template.  If you edit a different wiki, you can request multi-column support for your wiki.
 * If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Thank you!

—User:Whatamidoing (WMF) (talk) 23:15, 28 February 2018 (UTC)

Editing News #2—2018
Read this in another language •  Subscription list for this multilingual newsletter  •  Subscription list on the English Wikipedia

Did you know?

Did you know that you can use the visual editor on a mobile device?

Tap on the pencil icon to start editing. The page will probably open in the wikitext editor.

You will see another pencil icon in the toolbar. Tap on that pencil icon to the switch between visual editing and wikitext editing.



Remember to publish your changes when you're done.

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 Editing Team has wrapped up most of their work on the 2017 wikitext editor and the visual diff tool. The team has begun investigating the needs of editors who use mobile devices. Their work board is available in Phabricator. Their current priorities are fixing bugs and improving mobile editing.

Recent changes

 * The Editing team has published an initial report about mobile editing.
 * The Editing team has begun a design study of visual editing on the mobile website. New editors have trouble doing basic tasks on a smartphone, such as adding links to Wikipedia articles.  You can read the report.
 * The Reading team is working on a separate mobile-based contributions project.
 * The 2006 wikitext editor is no longer supported. If you used that toolbar, then you will no longer see any toolbar.  You may choose another editing tool in your editing preferences, local gadgets, or beta features.
 * The Editing team described the history and status of VisualEditor in this recorded public presentation (starting at 29 minutes, 30 seconds).
 * The Language team released a new version of Content Translation (CX2) last month, on International Translation Day. It integrates the visual editor to support templates, tables, and images.  It also produces better wikitext when the translated article is published.

Let's work together

 * The Editing team wants to improve visual editing on the mobile website.  Please read their ideas and tell the team what you think would help editors who use the mobile site.
 * The Community Wishlist Survey begins next week.
 * If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly.  We will notify you when the next issue is ready for translation.

— Whatamidoing (WMF) (talk) 17:12, 1 November 2018 (UTC)