This is an archive of past discussions with User:Jc86035. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
There are a number of user boxes you can add to your user page to indicate interests and which wiki projects you belong to.
Development
On Tuesday, we are deploying usage tracking (no arbitrary access yet) to Dutch Wikipedia and French Wikisource, and subscription tracking on Wikidata. There should be no noticeable changes for users. These are necessary steps towards enabling arbitrary access in clients.
Worked on making language fallback work in the suggester (when adding a new statement or searching for an item)
More work on RDF output and the query service
Added Special:RedirectEntity for redirecting items
Investigated and working to fix JS bug on items with “invalid” values (phabricator:92975)
Did work towards having entity ids in revision histories and in diffs linked with their label (like on watchlists or in the recentchanges)
We rolled out usage tracking on the first two wikis (French Wikisource and Dutch Wikipedia). Users should not notice anything. More wikis will follow in the next weeks. This is the remaining step for enabling arbitrary access on wikis other than Commons.
The students team is working hard to get a first release of the improved constraint reports and checks against 3rd party databases out.
Ricordisamoa fixed the issue with long descriptions being cut off.
We fixed the focus flow in the property selector.
We improved the messages on Special:EntityData to make it more understandable.
Hello, Jc86035, and welcome to STiki! Thank you for your recent contributions using our tool. We at STiki hope you like using the tool and decide to continue using it in the future. Here are some pages that you might find helpful:
Userboxes - Do not hesitate to wear the STiki label with pride by choosing from a selection of userboxes!
We hope you enjoy maintaining Wikipedia with STiki! If you have any questions, problems, or suggestions don't hesitate to drop a note over at the STiki talk page and we'll be more than happy to help. Again, welcome, and thanks! West.andrew.g (developer) and Widr (talk) 05:07, 6 May 2015 (UTC)
Disambiguation link notification for May 6
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Vinod, you added a link pointing to the disambiguation page Gujarati. 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.
A study has been published about how Wikidata can help significantly improve the quality of medical content on Wikipedia. This is why we do Wikidata! \o/
The Wikidata Menu Challenge has started and goes on to May 27. Add labels, images and pronunciation audio to a list of around 290 items to help show off the power of Wikidata at a food festival.
Hovercards also show the target's label and ID now. (Try them by turning them on in the beta features section of your preferences.)
Continued working on RDF export
More work on making it possible to add a reference right away when adding a statement (and allowing the full statement incl references to be edited at the same time)
Did more work to make usage tracking possible on multilingual wikis (namely Commons)
@Secondarywaltz: I know the templates are used in groups; I just didn't occur to me to nominate the rest of the templates in the groups as well. Thanks for reminding me though. Jc86035 (talk • contribs) Use {{re|Jc86035}} to reply to me 06:41, 13 May 2015 (UTC)
Past: Andy Mabbett (User:Pigsonthewing) spoke about authority control in Wikidata (and sister projects) at the World Digital Library's Arab Peninsula Regional Group Symposium, organised in conjunction with the Qatar National Library, in Doha on 13 May. His slides, with an Arabic translation, will be online soon.
Past: Wikidata editing workshop at the Wikimedia Conference in Berlin
Past: Wikidata workshop for archivists of Catalan City of Justice
Upcoming: MediaWiki hackathon in Lyon
Other Noteworthy Stuff
Elections for the board of the Wikimedia Foundation are ongoing. Wikidata should be well represented among the voters. Go and vote!
Dutch Wikipedia and French Wikisource now have the arbitrary access feature. Persian Wikipedia, English Wikivoyage and Hebrew Wikipedia are following today. Italian Wikipedia and all remaining Wikisource projects are following on June 1st.
English Wikipedia is running a bot to add authority control templates to many articles that are filled completely from Wikidata. Italian Wikipedia is doing so as well.
It appears they used to be used internally as part of a standard phraseology or somesuch, but were phased out at some point in the past - see zh:國音電報. I'm not sure if any part of the TRA section needs to be kept. Alakzi (talk) 20:51, 21 May 2015 (UTC)
@Alakzi: Given that it seems to be no longer in use, it should probably be removed, especially given that there is also a numbered station code. Jc86035 (talk • contribs) Use {{re|Jc86035}} to reply to me 08:56, 22 May 2015 (UTC)
Quite so. Perhaps we could place the TRA "level" in |category=, and with "mileage" in |distance=, we've got everything covered. Alakzi (talk) 10:37, 22 May 2015 (UTC)
I was about three-quarters in when I noticed I'd had a space before the line list's first item, but other than that, the replacement of it went smoothly. Alakzi (talk) 21:49, 22 May 2015 (UTC)
Wikidata weekly summary #159
Here's your quick overview of what has been happening around Wikidata over the last week.
Wikidata descriptions can be soon be edited in the Wikipedia iOS app.
A early preview of the official SPARQL endpoint for Wikidata has been created to query Wikidata. Remember that it is not stable and still beta. A short introduction to SPARQL can be found in Lucie's slides.
If you are not familiar with SPARQL yet, a tool has been created by Tpt and Bene* to generate SPARQL queries from natural language questions.
To do SPARQL queries from the command line, a command line tool was crafted by Marius.
The special page to query for badges is within reach.
A feedback session on the architecture of Wikibase was held.
We got a cool presentation by Maxime about inventaire.io.
We figured out the next steps to make Wikidata more mobile friendly.
Hi Jc86035. Any idea what a "bus rotary" is? Check the values of |bus=. If you could also review my wrapper in the sandbox, I'd appreciate it. Thanks. Alakzi (talk) 17:55, 18 May 2015 (UTC)
@Alakzi: I'm not really sure what "bus rotary" means, although the version of the bus services switch at {{Infobox Japan station}} suggests it means a route terminates at the bus stop. The wrapper is quite good, although I'm not sure if "Station"/「站」 should be kept in the title while it isn't kept in the title in most other places. I've also added the |operator2= header to {{Infobox station/sandbox2}} (it needs a little bit of fixing-up), but it's neither in the main {{Infobox station}} template nor in {{Infobox China station/sandbox}}. Jc86035 (talk | contribs) Use {{re|Jc86035}} to reply to me 09:41, 19 May 2015 (UTC)
Thank you. |operator2= could be accommodated in |type= or |symbol= - or am I missing something? Also, I'm not quite sure what the |station_code= is - atonal Pinyin? Alakzi (talk) 10:04, 19 May 2015 (UTC)
@Alakzi: No, not yet. I haven't added all of the logos to {{Rail-interchange}} yet (since I'm adding them along with the {{China line}} links) but I can add all the logo symbols first if necessary. (Side note – the sandbox currently uses |symbol3=, which doesn't currently exist in the live version of {{Infobox station}}, but the sandbox of {{Infobox station}} has it since I converted it to use a module for the symbols. Could you help merge the sandbox code to the main template? Thanks.) Jc86035 (talk • contribs) Use {{re|Jc86035}} to reply to me 14:01, 31 May 2015 (UTC)
These icons have been causing quite a stir, so I think it would be better if you were to open an edit request and I let someone else do it. Alakzi (talk) 14:11, 31 May 2015 (UTC)
Template deletion nomination
Hello, Jc86035. You have new messages at Kxx's talk page. You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.
You say "legend3" is redundant to "Color box". I use this template to show football team colors. Color box is too large to use for this purpose. Delete Color box instead. First you have put "See TfD" notice before all legends, then someone has broken the collapsible feature of the collapsible box. My pages look terrible. Red_devil_41 (talk) 18:16, 29 May 2015 (UTC)
@Red devil 41: I've put the TfD notice in <noinclude> tags so that it doesn't display in transclusions. The collapsible tables not working seems to have been a server error; I experienced this as well and there's a thread at the village pump about it, but it looks like it's gone now. I'm not sure how {{Colorbox}} would be too large for your purposes, since the only visible differences of {{Legend3}} are that it's slightly thinner and that the text is too small. Can you give me an example of a page where replacement of {{Legend3}} with {{Colorbox}} or {{Color box}} would make it look worse? Jc86035 (talk • contribs) Use {{re|Jc86035}} to reply to me 04:28, 30 May 2015 (UTC)
For example; if legend3 is used:
Team One v Team Two
00 Xxxxx 0000 Round 1
Team One
0 – 0
Team Two
Xxxxxx Stadium, X City
Sunday, 00:00
Xxxxx Xxxxxx 00' Xxxxxxx Xxxxxx 00'
Report
00' Xxxxx Xxxxxx 00' Xxxxx Xxxxxxx
Referee: Xxxxx Xxxxxx
Or, if color box is used:
Team One v Team Two
00 Xxxxx 0000 Round 1
Team One
0 – 0
Team Two
Xxxxxx Stadium, X City
Sunday, 00:00
Xxxxx Xxxxxx 00' Xxxxxxx Xxxxxx 00'
Report
00' Xxxxx Xxxxxx 00' Xxxxx Xxxxxxx
Referee: Xxxxx Xxxxxx
In football boxes; national flags are used to indicate national football teams. For club teams however, team coat of arms are not allowed to use. Instead, I thought, team colors are relevant. Team colors are considered as inseparable parts of football teams. When "color box" is used, the result is something larger than flags. Although it was not in exact dimensions, "legend3" fits better.
Hi Jc. I'm wondering if you could explain the slightly odd interface of Module:Rail-interchange multi (slashes and pluses) - I assume this is to facilitate specifying multiple symbols for location X without having to repeat location X? I wonder if there's a way to make it less opaque. Alakzi (talk) 10:29, 1 June 2015 (UTC)
@Alakzi: The reason it works like that is a legacy of Sameboat's sandbox module, which he suggested to me back in February would be useful for displaying multiple symbols in {{Infobox station}}. That module (which creates a table, like this one) uses newlines for the separator between each row, but since the implementation in {{Infobox station}} uses the #if parser function (which, as you probably know, would make the separator not work) I changed it to use plus signs. Since I don't really know how to write Lua code, improving it would best be left to someone who knows how to write Lua better than I can. (The current approach, however, has the advantages of (in doublerow) easily allowing the first symbol instead of the last to be in the middle if there is an odd number of symbols, and allowing more than one parameter to be passed through to {{rint}} through |symbol= of {{Infobox station}}.) Jc86035 (talk • contribs) Use {{re|Jc86035}} to reply to me 10:39, 1 June 2015 (UTC)
OK. This is only going to be used internally in {{Infobox station}}, correct? If so, we can revisit the interface if it ever becomes an issue. Honestly, I don't think that faux-tables are at all necessary here; the symbols could simply be divided by a linebreak. Alakzi (talk) 15:03, 1 June 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 featuresfor citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now created inside a single tool. Inside that tool, choose the tab you want (⧼citoid-citeFromIDDialog-mode-auto⧽, ⧼citoid-citeFromIDDialog-mode-manual⧽, or ⧼citoid-citeFromIDDialog-mode-reuse⧽). The cite button is now labeled with the word "⧼visualeditor-toolbar-cite-label⧽" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "⧼Citoid-citeFromIDDialog-lookup-button⧽", for the submit button.
The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and/or appropriate icons for disambiguation pages, redirect pages and empty pages. Search results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appeared over the first match in the link inspector (T98085).
The special character inserter in VisualEditor now uses the same special character list as the wikitext editor. Admins at each wiki can also create a custom section for frequently used characters at the top of the list. Please read the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing each character in the special character inserter (T70425).
Several improvements have been made to templates. When you search for a template to insert, the list of results now contains descriptions of the templates. The parameter list inside the template dialog now remains open after inserting a parameter from the list, so that users don’t need to click on "⧼visualeditor-dialog-transclusion-add-param⧽" each time they want to add another parameter (T95696). The team added a new property for TemplateData, "Example", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter (T53049).
The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design feature is being used for the cite button on wikis where the Citoid service is enabled.
The team has released a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.
The weekly task triage meetings continue to be open to volunteers, each Wednesday at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal. You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug.
If your Wikivoyage, Wikibooks, Wikiversity, or other community wants to have VisualEditor made available by default to contributors, then please contact James Forrester.
If you would like to request the Citoid automatic reference feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you! Whatamidoing (WMF) (talk) 17:31, 6 June 2015 (UTC)
Wikidata weekly summary #161
Here's your quick overview of what has been happening around Wikidata over the last week.
Wikidata has passed German Wikipedia in number of items with images (743850 dewp articles vs. 804885 items) - now only second to English-language Wikipedia.
Catalan Wikipedia is moving Taxon IDs to Wikidata.
Zolo did a comparison of English/French/German/Chinese and Cebuano Wikipedias in terms of main types of articles. Biographies were compared by period, nationality and occupation.
Italian Wikipedia and all remaining Wikisource projects now have arbitrary access. The rollout will continue. The schedule for the next projects is at d:Wikidata:Arbitrary access.
The Content Translation tool now automatically connects translated articles to Wikidata. (Thanks Content Translation developers!) Previously translated but unconnected articles have been connected by a bot. (Thanks Amir!)
Code review of the extensions written by a team of students to improve the constraint reports and make it possible to automatically check our data against other databases. A first version will go live soon pending further codereview and fixes.
@Secondarywaltz: I didn't add them originally; I just moved them from |type=, which is where Northwest put them, to the built-in symbol parameters. The logo appears to be displayed on station entrance signage. Jc86035 (talk • contribs) Use {{re|Jc86035}} to reply to me 13:08, 10 June 2015 (UTC)
Thank you. I could not find it in widespread use. If a logo had been in station articles before then it could have been updated, but in this application I agree that it is probably just decorative and redundant. Secondarywaltz (talk) 13:21, 10 June 2015 (UTC)
A challenge was raised to calculate the degrees of separation to Kevin Bacon. Already one routine has been produced, the next step is to use live data so that we can work on reducing the number of intermediary steps.
Deployed arbitrary access on all Wikivoyage and Wikiquote projects and announced the next ones. See d:Wikidata:Arbitrary access for more.
More fine tuning on entity usage tracking (relevant for arbitrary access)
Fixed bug that sometimes allowed multiple properties to have the same label in a given language (phabricator:T102148)
More work on automatically creating redirects when merging items
More code review of the Wikidata Quality extensions (improved constraint reports and checks against 3rd party databases). Starting to look good for a first deployment.
The sitelinks heading hierarchy changed and includes a “Site links” heading now that is only shown on mobile. This is a DOM change needed to make Wikidata work better on mobile.
Started working on having PHPCS coverage for the major Wikibase.git code base to find small code issues more easily
Prepared Wikibase.git for the DataModel 3.0 switch
Released Wikibase DataModel Serialization 1.4
Released Wikibase Internal Serialization 1.4
New releases of several DataValue components, including DataValues Number 0.5, DataValues JavaScript 0.7 and ValueView 0.14.5
Since train distruptions in Singapore is common, is it okay to create a page for that. Just today, train service were already distrupted after a train fault. MarcusCheeKJ (talk) 05:29, 15 June 2015 (UTC)
Here's your quick overview of what has been happening around Wikidata over the last week.
Discussions
German language Wikipedia closed its RfC on usage of Wikidata data. As a result Wikidata data can be used on the project as long as it happens through a template and it has a non-Wikimedia reference.
Events/Blogs/Press
Past: Office hour on IRC. We talked about cool things that happened around Wikidata over the past 3 months got an update on upcoming developments and Freebase and more. You can read the log.
Fixed an issue where you'd sometimes select the wrong value when entering a statement unintentionally (phabricator:T98471)
Switched the whole code base to make use of DataModel 3.0
The concept of “claims” no longer exists in Wikibase, as all places in the software work with statements. We are making this more and more explicit in the code.
More work on getting the Wikibase Quality extensions ready for deployment. They'll improve constraint checking and provide checks against 3rd party databases.
Special:UnconnectedPages had to be reworked (thanks Amir!) because of huge performance issues. Because of this it loses some functionality (being able to specify where the list starts and limiting the list to pages that have local interwiki links). We're working on bringing functionality back without the performance penalty.
Enabled arbitrary access on arwiki, cawiki, eswiki, huwiki, kowiki, rowiki, ukwiki, viwiki, and usage tracking on dewiki, ruwiki, cswiki and all s3 wikis. (ruwiki and cswiki get arbitrary access on June 23)
Finishing work on improved handling “invalid” values and statements with deleted properties.
Small breaking DOM change: Wikibase no longer adds its own h1 tag but uses MediaWiki's default .firstHeading element. (phabricator:T93534)
Upcoming: Wikimania. There will be several talks and workshops related to Wikidata. Say hi at the "Ask Us Anything" session for Wikidata if you're there.
Machine readable versions (in various formats) of Wikibase entities will be advertised in their page heads as alternate link. (phabricator:T96298)
Fixed property label on item pages not scrolling anymore (phabricator:T94588)
More work on getting the Wikibase Quality extensions ready for release. The part doing constraint violation checks should go to test.wikidata.org next week. The part doing checks against 3rd party databases will still take a bit longer but is also shaping up nicely.
Made it possible to create items even when another user is mass-creating items (phabricator:T103796)
Bene* worked more on making Wikidata work nicely on mobile
Fixed weird issue with cursor jumping around in sitelink input field (phabricator:T103489)
Fixed an issue where it was not possible to edit a statement after you removed its only reference (phabricator:T103603)
Lydia will be traveling for much of July. Expect her to be a bit less responsive during that time.
Upcoming: Wikimania. There will be several talks and workshops related to Wikidata. Say hi at the "Ask Us Anything" session for Wikidata if you're there.
Other Noteworthy Stuff
A new database report lists people categorized as dead in Wikipedia, but lacking Property:P570 (date of death). It's updated several times during the day. There are about 20 to 30 new entries each day. There is currently some backlog from the Arabic, Marathi, and Thai Wikipedias. Items updated first in Wikidata wont appear in the report. They are listed directly in Wikidata's recent deaths report.
You're competent to be a template editor. Would you like to apply for the right? Is there anything that worries you? Alakzi (talk) 14:49, 10 July 2015 (UTC)
@Alakzi: I'd be fine with applying for the right, but I don't meet criteria 5 yet and I'd need to avoid screw-ups like this. Also, I'm not really sure what I would be using it for, except maybe adding Module:Unsubst to protected templates and fixing infoboxes affected by the MediaWiki:Common.css edit which left-aligned all the row headers. Jc86035 (talk • contribs) Use {{re|Jc86035}} to reply to me 05:14, 11 July 2015 (UTC)
Wikidata weekly summary #166
Here's your quick overview of what has been happening around Wikidata over the last week.
Attending Wikimania 2015 in Mexico City right now, meeting awesome people that already use or want to know everything about Wikidata.
After the next deployment, redirects will be automatically created when merging items.
Special:UnconnectedPages can now be queried via the query API, thanks to Ladsgroup.
Migrating away from an older serializer to the DataModel Serialization component.
Worked on a new time parser that can parse formats like M/D/Y, Y M D and so on.
Fixed a bug where a value could not be edited when save failed.
Made the snak type, badge and rank selectors position themselves after resizing the browser window and introduced a possibility to collapse the sitelinks sections.
Worked on a change in editing to be able to edit a statement and it’s references in one step.
You can add quotations marks before and after a title or phrase with a single click.
Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar).
Click the button. VisualEditor will add the quotation marks on either side of the text you selected.
You can read and help translate the user guide, which has more information about how to use VisualEditor.
Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.
Wikimania
The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.
Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.
For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).
For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).
We published some graphs showing the effect of the event on the Translathon page. Thank you to the translators for participating and the translatewiki.net staff for facilitating this initiative.
Recent improvements
Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.
Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top.
In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.
Future changes
The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.
On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.
Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help.
If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
Please file requests for language-appropriate "Bold" and "Italic" icons for the styling menu in Phabricator.
The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.
