Vikicitaro:Diskutejo - Vikicitaro

(Apologies for writing in English. Please translate if necessary)

We would like to let you know about Beta Features, a new program from the Wikimedia Foundation that lets you try out new features before they are released for everyone.

Think of it as a digital laboratory where community members can preview upcoming software and give feedback to help improve them. This special preference page lets designers and engineers experiment with new features on a broad scale, but in a way that's not disruptive.

Beta Features is now ready for testing on MediaWiki.org. It will also be released on Wikimedia Commons and MetaWiki this Thursday, 7 November. Based on test results, the plan is to release it on all wikis worldwide on 21 November, 2013.

Here are the first features you can test this week:

• Media Viewer — view images in large size or full screen
• VisualEditor Formulæ (for wikis with VisualEditor) — edit algebra or equations on your pages
• Typography Refresh — make text more readable (coming Thursday)

Would you like to try out Beta Features now? After you log in on MediaWiki.org, a small 'Beta' link will appear next to your 'Preferences'. Click on it to see features you can test, check the ones you want, then click 'Save'. Learn more on the Beta Features page.

After you've tested Beta Features, please let the developers know what you think on this discussion page -- or report any bugs here on Bugzilla. You're also welcome to join this IRC office hours chat on Friday, 8 November at 18:30 UTC.

Beta Features was developed by the Wikimedia Foundation's Design, Multimedia and VisualEditor teams. Along with other developers, they will be adding new features to this experimental program every few weeks. They are very grateful to all the community members who helped create this project — and look forward to many more productive collaborations in the future.

Enjoy, and don't forget to let developers know what you think! Keegan (WMF) (talk) 19:48, 5 Nov. 2013 (UTC)

Distributed via Global message delivery (wrong page? Correct it here), 19:48, 5 Nov. 2013 (UTC)

Hi all,

The Wikimedia legal team invites you to participate in the development of the new Wikimedia trademark policy.

The current trademark policy was introduced in 2009 to protect the Wikimedia marks. We are now updating this policy to better balance permissive use of the marks with the legal requirements for preserving them for the community. The new draft trademark policy is ready for your review here, and we encourage you to discuss it here.

We would appreciate if someone would translate this message into your language so more members of your community can contribute to the conversation.

Thanks,
Yana & Geoff

On January 21 2014 the MediaWiki extension Universal Language Selector (ULS) was disabled on this wiki. A new preference was added for logged-in users to turn on ULS. This was done to prevent slow loading of pages due to ULS webfonts, a behaviour that had been observed by the Wikimedia Technical Operations team on some wikis.

We are now ready to enable ULS again. The temporary preference to enable ULS will be removed. A new checkbox has been added to the Language Panel to enable/disable font delivery. This will be unchecked by default for this wiki, but can be selected at any time by the users to enable webfonts. This is an interim solution while we improve the feature of webfonts delivery.

You can read the announcement and the development plan for more information. Apologies for writing this message only in English. Thank you. Runa

Hello all,

Please join a discussion about a proposed amendment to the Wikimedia Terms of Use regarding undisclosed paid editing and we encourage you to voice your thoughts there. Please translate this statement if you can, and we welcome you to translate the proposed amendment and introduction. Please see the discussion on Meta Wiki for more information. Thank you! Slaporte (WMF) 22:00, 21 Feb. 2014 (UTC)

I apologize if this message is not in your language. Please help translate it.

Do you have an idea for a project that could improve your community? Individual Engagement Grants from the Wikimedia Foundation help support individuals and small teams to organize experiments for 6 months. You can get funding to try out your idea for online community organizing, outreach, tool-building, or research to help make Vikicitaro better. In March, we’re looking for new project proposals.

Examples of past Individual Engagement Grant projects:

• Organizing social media for Chinese Wikipedia ($350 for materials)
• Improving gadgets for Visual Editor ($4500 for developers)
• Coordinating access to reliable sources for Wikipedians ($7500 for project management, consultants and materials)
• Building community and strategy for Wikisource (€10000 for organizing and travel)

Proposals are due by 31 March 2014. There are a number of ways to get involved!

Hope to have your participation,

--Siko Bouterse, Head of Individual Engagement Grants, Wikimedia Foundation 19:44, 28 Feb. 2014 (UTC)

Hey everyone :)

I just wanted to let you know that Wikiquote will be the next sister project to be supported by Wikidata. Initially you will be able to maintain the links between the language editions of Wikiquote on Wikidata. This means you will no longer have to maintain them in the wiki text of each article. (However you will still be able to if you want to and local links will overwrite the ones from Wikidata in that case.) We plan to enable this on April 8th for you. At a later point (depending on how this initial roll-out goes) you will also get access to the other data on Wikidata like the date of birth of a scientist for example.

If you have any questions please come to d:Wikidata:Wikiquote where we'll try to answer all of them. If you're already familiar with Wikidata and want to act as an ambassador please add your name to the list there to help people find you.

I'm looking forward to welcoming you all to Wikidata.

Cheers Lydia Pintscher 21:58, 7 Mar. 2014 (UTC)

This week, the typography on Wikimedia sites will be updated for all readers and editors who use the default "Vector" skin. This change will involve new serif fonts for some headings, small tweaks to body content fonts, text size, text color, and spacing between elements. The schedule is:

• April 1st: non-Wikipedia projects will see this change live
• April 3rd: Wikipedias will see this change live

This change is very similar to the "Typography Update" Beta Feature that has been available on Wikimedia projects since November 2013. After several rounds of testing and with feedback from the community, this Beta Feature will be disabled and successful aspects enabled in the default site appearance. Users who are logged in may still choose to use another skin, or alter their personal CSS, if they prefer a different appearance. Local common CSS styles will also apply as normal, for issues with local styles and scripts that impact all users.

For more information:

• Summary of changes and FAQ
• Discussion page for feedback or questions
• Post on blog.wikimedia.org

-- Steven Walling (Product Manager) on behalf of the Wikimedia Foundation's User Experience Design team

Hello! It was noted that on this wiki you have less than 10 local files. Presumably, you therefore don't have interest nor energies to have hundreds templates with the now required HTML, even less a local EDP. However, this means that users here will experience a mostly broken and/or illegal uploading. I propose to

• have local upload restricted to the "Administrantoj" group (for emergency uploads) and
• the sidebar point to commons:Special:UploadWizard,

so that you can avoid local maintenance and all users can have a functioning, easy upload interface in their own language. All registered users can upload on Commons and existing files will not be affected.

I'll get this done in one week from now.

1. If you disagree with the proposal, just remove your wiki from the list.
2. To make the UploadWizard even better, please tell your experience and ideas on commons:Commons:Upload Wizard feedback.

Nemo 20:38, 19 Maj. 2014 (UTC)

Greetings, my apologies for writing in English.

I wanted to let you know that Media Viewer will be released to this wiki in the coming weeks. Media Viewer allows readers of Wikimedia projects to have an enhanced view of files without having to visit the file page, but with more detail than a thumbnail. You can try Media Viewer out now by turning it on in your Beta Features. If you do not enjoy Media Viewer or if it interferes with your work after it is turned on you will be able to disable Media Viewer as well in your preferences. I invite you to share what you think about Media Viewer and how it can be made better in the future.

Thank you for your time. - Keegan (WMF) 21:29, 23 Maj. 2014 (UTC)

--This message was sent using MassMessage. Was there an error? Report it!

Greetings— and sorry for writing in English, please translate if it will help your community,

The Wikimedia Foundation's Multimedia team is happy to announce that Media Viewer was just released on this site today.

Media Viewer displays images in larger size when you click on their thumbnails, to provide a better viewing experience. Users can now view images faster and more clearly, without having to jump to separate pages — and its user interface is more intuitive, offering easy access to full-resolution images and information, with links to the file repository for editing. The tool has been tested extensively across all Wikimedia wikis over the past six months as a Beta Feature and has been released to the largest Wikipedias, all language Wikisources, and the English Wikivoyage already.

If you do not like this feature, you can easily turn it off by clicking on "Disable Media Viewer" at the bottom of the screen, pulling up the information panel (or in your your preferences) whether you have an account or not. Learn more in this Media Viewer Help page.

Please let us know if you have any questions or comments about Media Viewer. You are invited to share your feedback in this discussion on MediaWiki.org in any language, to help improve this feature. You are also welcome to take this quick survey in English, en français, o español.

We hope you enjoy Media Viewer. Many thanks to all the community members who helped make it possible. - Fabrice Florin (WMF) (talk) 21:54, 19 Jun. 2014 (UTC)

--This message was sent using MassMessage. Was there an error? Report it!

’’My apologies for writing in English.’’

Hello,

I am notifying you that a brainstorming session has been started on Meta to help the Wikimedia Foundation increase and better affect community participation in software development across all wiki projects. Basically, how can you be more involved in helping to create features on Wikimedia projects? We are inviting all interested users to voice their ideas on how communities can be more involved and informed in the product development process at the Wikimedia Foundation. It would be very appreciated if you could translate this message to help inform your local communities as well.

I and the rest of my team welcome you to participate. We hope to see you on Meta.

Kind regards, -- Rdicerb (WMF) talk 22:15, 21 Aŭg. 2014 (UTC)

--This message was sent using MassMessage. Was there an error? Report it!

Hello all,

There are currently requests for comment open on meta to create two new global groups. The first is a group for members of the OTRS permissions queue, which would grant them autopatrolled rights on all wikis except those who opt-out. That proposal can be found at m:Requests for comment/Creation of a global OTRS-permissions user group. The second is a group for Wikimedia Commons admins and OTRS agents to view deleted file pages through the 'viewdeletedfile' right on all wikis except those who opt-out. The second proposal can be found at m:Requests for comment/Global file deletion review.

We would like to hear what you think on both proposals. Both are in English; if you wanted to translate them into your native language that would also be appreciated.

It is possible for individual projects to opt-out, so that users in those groups do not have any additional rights on those projects. To do this please start a local discussion, and if there is consensus you can request to opt-out of either or both at m:Stewards' noticeboard.

Thanks and regards, Ajraddatz (talk) 18:04, 26 Okt. 2014 (UTC)

Hello,

AbuseFilter is a MediaWiki extension used to detect likely abusive behavior patterns, like pattern vandalism and spam. In 2013, Global AbuseFilters were enabled on a limited set of wikis including Meta-Wiki, MediaWiki.org, Wikispecies and (in early 2014) all the "small wikis". Recently, global abuse filters were enabled on "medium sized wikis" as well. These filters are currently managed by stewards on Meta-Wiki and have shown to be very effective in preventing mass spam attacks across Wikimedia projects. However, there is currently no policy on how the global AbuseFilters will be managed although there are proposals. There is an ongoing request for comment on policy governing the use of the global AbuseFilters. In the meantime, specific wikis can opt out of using the global AbuseFilter. These wikis can simply add a request to this list on Meta-Wiki. More details can be found on this page at Meta-Wiki. If you have any questions, feel free to ask on m:Talk:Global AbuseFilter.

Thanks,

PiRSquared17, Glaisher

Hello. Please excuse the English. I would be grateful if you translated this message!

VisualEditor, a rich-text editor for MediaWiki, will soon be available on this wiki as a Beta Feature. The estimated date of activation is Wednesday, 26 November.

To access it, you will need to visit the Betaj funkcioj page after the deployment and tick the box next to "⧼Visualeditor-preference-core-label⧽". (If you have enabled the "Aŭtomate ŝalti plejparton de betaj funkciojn" option, VisualEditor will be automatically available for you.) There will also be a "⧼Visualeditor-preference-language-label⧽" that you can enable if you need it.

Then, you just have to click on "Redakti" to start VisualEditor, or on "Redakti fonton" to edit using wikitext markup. You can even begin to edit pages with VisualEditor and then switch to the wikitext editor simply by clicking on its tab at any point, and you can keep your changes when doing so.

A guide was just published at mediawiki.org so that you can learn how to support your community with this transition: please read and translate it if you can! You will find all the information about the next steps there. Please report any suggestions or issues at the main feedback page. You will also receive the next issues of the multilingual monthly newsletter here on this page: if you want it delivered elsewhere, for example at your personal talk page, please add the relevant page here.

Thanks for your attention and happy editing, Elitre (WMF) 18:12, 21 Nov. 2014 (UTC)

Did you know?

Basic table editing is now available in VisualEditor. You can add and remove rows and columns from 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).

Basic support for editing tables is now available. You can add and delete tables, add and remove rows and columns, set or remove a caption for a table, and merge cells together. To change the contents of a cell, double-click inside it. More features will be added in the coming months. In addition, VisualEditor now ignores broken, invalid rowspan and colspan elements, instead of trying to repair them.

You can now use find and replace in VisualEditor, reachable through the tool menu or by pressing ^ Ctrl+F or ⌘ Cmd+F.

You can now create and edit simple <blockquote> paragraphs for quoting and indenting content. This changes a "Alineo" into a "Bloka citado".

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.

The current VisualEditor design will be replaced 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 on other sites in early January. (You can see a developer preview of the old "Apex" theme and the new "MediaWiki" one which will replace it.)

The Editing team plans to add auto-fill features for citations in January.

Planned changes to the media search dialog will make choosing between possible images easier.

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• Translations of the user guide for most languages are outdated. Only Ukrainian, Portuguese, Spanish, French, and Dutch translations 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 "Grasa" and "Kursiva" icons for the character formatting menu in Phabricator.
• The design research team wants to see how real editors work. Please sign up for their research program.
• If you would like to help with translations of this newsletter, please subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Subscribe or unsubscribe at Meta. Thank you!

— Elitre (WMF)

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

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

Due to some breaking changes in MobileFrontend and VisualEditor, VisualEditor was not working correctly on the mobile site for a couple of days in early January. The teams apologize for the problem.

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

• starts a new task, like opening the ⧼visualeditor-toolbar-savedialog⧽ dialog: blue ,
• takes a constructive action, like inserting a citation: green ,
• might remove or lose your work, like removing a link: red , or
• is neutral, like opening a link in a new browser window: gray .

The TemplateData editor has been completely re-written to use a different design based on the same OOjs UI system as VisualEditor. (T67815, T73746.) This change fixed a couple of existing bugs and improved usability. (T73077, T73078.)

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 Wikipedia requested the ability to use VisualEditor in the "Article Incubator" or drafts namespace. (T86688, T87027.) If your community would like VisualEditor enabled on another namespace on your wiki, then you can file a request in Phabricator. Please include a link to a community discussion about the requested change.

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

• 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, and you can also contact James F. to learn more about this initiative.
• 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 Meta. 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. Thank you!

— Elitre (WMF)

Ŝanĝo de x-anstataŭado en Vikicitaro

redakti

Por malŝalto de malnova x-sistemo kaj ŝalto de Universala LingvoElektilo kun x-metoda anstataŭado

redakti

Por malŝalto de malnova x-sistemo kaj ŝalto de Universala LingvoElektilo kun alia anstataŭado ol x-metoda

redakti

Hi, this message is to let you know that, on domains like eo.m.wikipedia.org, unregistered users cannot edit. At the Wikimedia Forum, where global configuration changes are normally discussed, a few dozens users propose to restore normal editing permissions on all mobile sites. Please read and comment!

Thanks and sorry for writing in English, Nemo 22:32, 1 Mar. 2015 (UTC)

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.

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

The Editing team is slowly adding auto-fill features for citations. This is currently available only at the French, Italian, and English Wikipedias. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to improve precision and reduce the need for manual corrections by contributing to the Citoid service's definitions for each website.

Citoid requires good TemplateData for your citation templates. If you would like to request this feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.

The special character inserter has been improved, based upon feedback from active users. After this, VisualEditor was made available to all users of Wikipedias on the Phase 5 list on 30 March. This affected 53 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh.

Work continues to support languages with complex requirements, such as Korean and Japanese. These languages use input method editors ("IMEs”). Recent improvements to cursoring, backspace, and delete behavior will simplify typing in VisualEditor for these users.

The design for the image selection process is now using a "masonry fit" model. Images in the search results are displayed at the same height but at variable widths, similar to bricks of different sizes in a masonry wall, or the "packed" mode in image galleries. This style helps you find the right image by making it easier to see more details in images.

You can now drag and drop categories to re-arrange their order of appearance ​on the page.

The pop-up window that appears when you click on a reference, image, link, or other element, is called the "context menu". It now displays additional useful information, such as the destination of the link or the image's filename. The team has also added an explicit "Edit" button in the context menu, which helps new editors open the tool to change the item.

Invisible templates are marked by a puzzle piece icon so they can be interacted with. Users also will be able to see and edit HTML anchors now in section headings.

Users of the TemplateData GUI editor can now set a string as an optional text for the 'deprecated' property in addition to boolean value, which lets you tell users of the template what they should do instead. (T90734)

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

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

• 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 "Grasa" and "Kursiva" 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!

— Elitre (WMF)

Sorry for English, I hope someone translates this.
Pywikibot (then "Pywikipediabot") was started back in 2002. In 2007 a new branch (formerly known as "rewrite", now called "core") was started from scratch using the MediaWiki API. The developers of Pywikibot have decided to stop supporting the compat version of Pywikibot due to bad performance and architectural errors that make it hard to update, compared to core. If you are using pywikibot compat it is likely your code will break due to upcoming MediaWiki API changes (e.g. T101524). It is highly recommended you migrate to the core framework. There is a migration guide, and please contact us if you have any problem.

There is an upcoming MediaWiki API breaking change that compat will not be updated for. If your bot's name is in this list, your bot will most likely break.

Thank you,
The Pywikibot development team, 19:30, 5 June 2015 (UTC)

Sorry for English, I hope someone translates this.
Pywikibot (then "Pywikipediabot") was started back in 2002. In 2007 a new branch (formerly known as "rewrite", now called "core") was started from scratch using the MediaWiki API. The developers of Pywikibot have decided to stop supporting the compat version of Pywikibot due to bad performance and architectural errors that make it hard to update, compared to core. If you are using pywikibot compat it is likely your code will break due to upcoming MediaWiki API changes (e.g. T101524). It is highly recommended you migrate to the core framework. There is a migration guide, and please contact us if you have any problem.

There is an upcoming MediaWiki API breaking change that compat will not be updated for. If your bot's name is in this list, your bot will most likely break.

Thank you,
The Pywikibot development team, 19:30, 5 June 2015 (UTC)

(Sorry for writing in English)

When using data from Wikidata on Wikipedia and other sister projects, there is currently a limitation in place that hinders some use cases: data can only be accessed from the corresponding item. So, for example, the Wikipedia article about Berlin can only get data from the Wikidata item about Berlin but not from the item about Germany. This had technical reasons. We are now removing this limitation. It is already done for a number of projects. Your project is one of the next ones:

• 11 June 2015: all Wikiquote, all remaining Wikivoyage
• 15 June 2015: Wikipedias: ar, ca, es, hu, ko, ro, uk, vi

We invite you to play around with this new feature if you are one of the people who have been waiting for this for a long time. If you have technical issues/questions with this you can come to d:Wikidata:Contact the development team.

How to use it, once it is enabled:

• Parser function: {{#property:P36|from=Q183}} to get the capital from the item about Germany
• Lua: see mw:Extension:Wikibase Client/Lua

I hope it will be helpful for you and allow you to do useful things with the help of Wikidata.

Cheers Lydia Pintscher 14:05, 7 Jun. 2015 (UTC)

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 and fixed many bugs and changed 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.

Auto-fill features for citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now created inside a single tool. Inside that tool, choose the tab you want (⧼citoid-citeFromIDDialog-mode-auto⧽, ⧼citoid-citeFromIDDialog-mode-manual⧽, or ⧼citoid-citeFromIDDialog-mode-reuse⧽). The cite button is now labeled with the word "⧼visualeditor-toolbar-cite-label⧽" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "⧼Citoid-citeFromIDDialog-lookup-button⧽", for the submit button.

The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and appropriate icons for disambiguation pages, redirect pages and empty pages (where applicable). 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, "Ekzemplo", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter. (T53049)

The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design feature is being used for the cite button on wikis where the Citoid service is enabled.

The team has released a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• The weekly task triage meetings continue to be open to volunteers, usually on Wednesday 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 Q4 blocker, though. Instead, go to Phabricator and "associate" the VisualEditor 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.
• The team is planning the second VisualEditor-related "translathon" for July. Please follow this task on Phabricator for details and updates! Announcements will follow in due course.

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!

— Elitre (WMF)

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 and fixed many bugs and changed 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.

Auto-fill features for citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now created inside a single tool. Inside that tool, choose the tab you want (⧼citoid-citeFromIDDialog-mode-auto⧽, ⧼citoid-citeFromIDDialog-mode-manual⧽, or ⧼citoid-citeFromIDDialog-mode-reuse⧽). The cite button is now labeled with the word "⧼visualeditor-toolbar-cite-label⧽" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "⧼Citoid-citeFromIDDialog-lookup-button⧽", for the submit button.

The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and appropriate icons for disambiguation pages, redirect pages and empty pages (where applicable). 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, "Ekzemplo", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter. (T53049)

The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design feature is being used for the cite button on wikis where the Citoid service is enabled.

The team has released a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• The weekly task triage meetings continue to be open to volunteers, usually on Wednesday 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 Q4 blocker, though. Instead, go to Phabricator and "associate" the VisualEditor 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.
• The team is planning the second VisualEditor-related "translathon" for July. Please follow this task on Phabricator for details and updates! Announcements will follow in due course.

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!

— Elitre (WMF)

Apologies for writing in English.

Hi everyone.

Over the last few years, the Wikimedia Foundation has been working towards enabling HTTPS by default for all users, including unregistered ones, for better privacy and security for both readers and editors. This has taken a long time, as there were different aspects to take into account. Our servers haven't been ready to handle it. The Wikimedia Foundation has had to balance sometimes conflicting goals.

Forced HTTPS has just been implemented on all Wikimedia projects. Some of you might already be aware of this, as a few Wikipedia language versions were converted to HTTPS last week and the then affected communities were notified.

Most of Wikimedia editors shouldn't be affected at all. If you edit as registered user, you've probably already had to log in through HTTPS. We'll keep an eye on this to make sure everything is working as it should. Do get in touch with us if you have any problems after this change or contact me if you have any other questions.

/Johan (WMF)

Apologies for writing in English.

Hi everyone.

Over the last few years, the Wikimedia Foundation has been working towards enabling HTTPS by default for all users, including unregistered ones, for better privacy and security for both readers and editors. This has taken a long time, as there were different aspects to take into account. Our servers haven't been ready to handle it. The Wikimedia Foundation has had to balance sometimes conflicting goals.

Forced HTTPS has just been implemented on all Wikimedia projects. Some of you might already be aware of this, as a few Wikipedia language versions were converted to HTTPS last week and the then affected communities were notified.

Most of Wikimedia editors shouldn't be affected at all. If you edit as registered user, you've probably already had to log in through HTTPS. We'll keep an eye on this to make sure everything is working as it should. Do get in touch with us if you have any problems after this change or contact me if you have any other questions.

/Johan (WMF)

There is a proposal at the Commons Village Pump requesting feedback about the thumbnails of static GIF images: It states that static GIF files should have their thumbnails created in PNG. The advantages of PNG over GIF would be visible especially with GIF images using an alpha channel. (compare the thumbnails on the side)

This change would affect all wikis, so if you support/oppose or want to give general feedback/concerns, please post them to the proposal page. Thank you. --McZusatz (talk) & MediaWiki message delivery (diskuto) 05:07, 24 Jul. 2015 (UTC)

There is a proposal at the Commons Village Pump requesting feedback about the thumbnails of static GIF images: It states that static GIF files should have their thumbnails created in PNG. The advantages of PNG over GIF would be visible especially with GIF images using an alpha channel. (compare the thumbnails on the side)

This change would affect all wikis, so if you support/oppose or want to give general feedback/concerns, please post them to the proposal page. Thank you. --McZusatz (talk) & MediaWiki message delivery (diskuto) 07:41, 24 Jul. 2015 (UTC)

Hi,
The Community Engagement department at the Wikimedia Foundation has launched a new learning campaign. The WMF wants to record community impressions about what makes a healthy online community. Share your views and/or create a drawing and take a chance to win a Wikimania 2016 scholarship! Join the WMF as we begin a conversation about Community Health. Contribute a drawing or answer the questions on the campaign's page.

The world is changing. The way we relate to knowledge is transforming. As the next billion people come online, the Wikimedia movement is working to bring more users on the wiki projects. The way we interact and collaborate online are key to building sustainable projects. How accessible are Wikimedia projects to newcomers today? Are we helping each other learn?
Share your views on this matter that affects us all!
We invite everyone to take part in this learning campaign. Wikimedia Foundation will distribute one Wikimania Scholarship 2016 among those participants who are eligible.

• All participants must have a registered user of at least one month antiquity on any Wikimedia project before the starting date of the campaign.
• All eligible contributions must be done until August 23, 2015 at 23:59 UTC
• Wiki link: Community Health learning campaign
• URL https://meta.wikimedia.org/wiki/Grants:Evaluation/Community_Health_learning_campaign
• Contact: María Cruz / Twitter: [[Uzanto:|]]WikiEval #CommunityHealth / email: eval[[Uzanto:|]]wikimediaŜablono:Dotorg

Hi,
The Community Engagement department at the Wikimedia Foundation has launched a new learning campaign. The WMF wants to record community impressions about what makes a healthy online community. Share your views and/or create a drawing and take a chance to win a Wikimania 2016 scholarship! Join the WMF as we begin a conversation about Community Health. Contribute a drawing or answer the questions on the campaign's page.

The world is changing. The way we relate to knowledge is transforming. As the next billion people come online, the Wikimedia movement is working to bring more users on the wiki projects. The way we interact and collaborate online are key to building sustainable projects. How accessible are Wikimedia projects to newcomers today? Are we helping each other learn?
Share your views on this matter that affects us all!
We invite everyone to take part in this learning campaign. Wikimedia Foundation will distribute one Wikimania Scholarship 2016 among those participants who are eligible.

• All participants must have a registered user of at least one month antiquity on any Wikimedia project before the starting date of the campaign.
• All eligible contributions must be done until August 23, 2015 at 23:59 UTC
• Wiki link: Community Health learning campaign
• URL https://meta.wikimedia.org/wiki/Grants:Evaluation/Community_Health_learning_campaign
• Contact: María Cruz / Twitter: [[Uzanto:|]]WikiEval #CommunityHealth / email: eval[[Uzanto:|]]wikimediaŜablono:Dotorg

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

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.

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. We thank the translators for participating and the translatewiki.net staff for facilitating this initiative.

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

Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top. In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.

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

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

• Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page is now using Flow instead of LiquidThreads.
• 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 mediawiki.org 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 "Grasa" and "Kursiva" 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 us directly, so that we can notify you when the next issue is ready. Thank you!

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

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.

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. We thank the translators for participating and the translatewiki.net staff for facilitating this initiative.

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

Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top. In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.

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

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

• Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page is now using Flow instead of LiquidThreads.
• 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 mediawiki.org 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 "Grasa" and "Kursiva" 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 us directly, so that we can notify you when the next issue is ready. Thank you!

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 "Ŝalti al vida redaktado".

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.

Educational features: The first time ever you use the visual editor, it now draws your attention to the Ligilo and ⧼visualeditor-toolbar-cite-label⧽ tools. When you click on the tools, it explains why you should use them. (T108620) Alongside this, the welcome message for new users has been simplified to make editing more welcoming. (T112354) More in-software educational features are planned.

Links: It is now easier to understand when you are adding text to a link and when you are typing plain text next to it. (T74108, T91285) The editor now fully supports ISBN, PMID or RFC numbers. (T109498, T110347, T63558) These "magic links" use a custom link editing tool.

Uploads: Registered editors can now upload images and other media to Commons while editing. Click the new tab in the "Enmeti Bildoj kaj aŭdvidaĵoj" 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 it on all devices regardless of size if they wish. (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 "Forigi" 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, T113354) When editing formulæ and other blocks, errors are shown as you edit. It is also possible to edit some types of graphs; adding new ones, and support for new types, will be coming.

On the English Wikipedia, the visual editor is now automatically available to anyone who creates an account. The preference switch was moved to the normal location, under Special:Preferences.

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

• Share your ideas and ask questions at 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 What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).
• Local admins can set up the Citoid automatic reference feature for your wiki. If you need help, then please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
• The weekly task triage meetings are open to volunteers. Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

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

Hi everyone! Apologies for posting in English. Translations are very welcome.

The Community Tech team at the Wikimedia Foundation is focused on building improved curation and moderation tools for experienced Wikimedia contributors. We're now starting a Community Wishlist Survey to find the most useful projects that we can work on.

For phase 1 of the survey, we're inviting all active contributors to submit brief proposals, explaining the project that you'd like us to work on, and why it's important. Phase 1 will last for 2 weeks. In phase 2, we'll ask you to vote on the proposals. Afterwards, we'll analyze the top 10 proposals and create a prioritized wishlist.

While most of this process will be conducted in English, we're inviting people from any Wikimedia wiki to submit proposals. We'll also invite volunteer translators to help translate proposals into English.

Your proposal should include: the problem that you want to solve, who would benefit, and a proposed solution, if you have one. You can submit your proposal on the Community Wishlist Survey page, using the entry field and the big blue button. We will be accepting proposals for 2 weeks, ending on November 23.

We're looking forward to hearing your ideas!

Community Tech Team via MediaWiki message delivery (diskuto) 21:58, 9 Nov. 2015 (UTC)

Hello! Wikimania 2016 scholarships will soon be open; by the end of the week we'll form the committee and we need your help, see Scholarship committee for details.

If you want to carefully review nearly a thousand applications in January, you might be a perfect committee member. Otherwise, you can volunteer as "ambassador": you will observe all the committee activities, ensure that people from your language or project manage to apply for a scholarship, translate scholarship applications written in your language to English and so on. Ambassadors are allowed to ask for a scholarship, unlike committee members.

Wikimania 2016 scholarships subteam 10:49, 10 Nov. 2015 (UTC)

Hi everyone! Apologies for posting this in English. Translations are very welcome.

We're beginning the second part of the Community Tech team's Community Wishlist Survey, and we're inviting all active contributors to vote on the proposals that have been submitted.

Thanks to you and other Wikimedia contributors, 111 proposals were submitted to the team. We've split the proposals into categories, and now it's time to vote! You can vote for any proposal listed on the pages, using the {{Support}} tag. Feel free to add comments pro or con, but only support votes will be counted. The voting period will be 2 weeks, ending on December 14.

The proposals with the most support votes will be the team's top priority backlog to investigate and address. Thank you for participating, and we're looking forward to hearing what you think!

Community Tech via

This is a message from the Wikimedia Foundation. Translations are available.

As many of you know, January 15 is Wikipedia’s 15th Birthday!

People around the world are getting involved in the celebration and have started adding their events on Meta Page. While we are celebrating Wikipedia's birthday, we hope that all projects and affiliates will be able to utilize this celebration to raise awareness of our community's efforts.

Haven’t started planning? Don’t worry, there’s lots of ways to get involved. Here are some ideas:

• Join/host an event. We already have more than 80, and hope to have many more.
• Talk to local press. In the past 15 years, Wikipedia has accomplished extraordinary things. We’ve made a handy summary of milestones and encourage you to add your own. More resources, including a press release template and resources on working with the media, are also available.
• Design a Wikipedia 15 logo. In place of a single icon for Wikipedia 15, we’re making dozens. Add your own with something fun and representative of your community. Just use the visual guide so they share a common sensibility.
• Share a message on social media. Tell the world what Wikipedia means to you, and add #wikipedia15 to the post. We might re-tweet or share your message!

Everything is linked on the Wikipedia 15 Meta page. You’ll find a set of ten data visualization works that you can show at your events, and a list of all the Wikipedia 15 logos that community members have already designed.

If you have any questions, please contact Zachary McCune or Joe Sutherland.

Thanks and Happy nearly Wikipedia 15!
-The Wikimedia Foundation Communications team

Posted by the MediaWiki message delivery, 20:58, 18 Dec. 2015 (UTC) • Please help translate to your language • Helpo

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.

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

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

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

The single edit tab project will combine the "Redakti" and "Redakti fonton" tabs into a single "Redakti" tab, like the system already used on the mobile website. (T102398, T58337) Initially, the "Redakti" 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 Redaktado tab of Special:Preferences in the drop-down menu about "Reĝimo de redaktado:".

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

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

• Please try the new system for the single edit 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:
  • Memori lastan redaktilon,
  • Ĉiam uzi la vidan redaktilon laŭeble,
  • Ĉiam uzi la fontan redaktilon, and
  • Montri ambaŭ redaktilajn langetojn. (This is the current state for people already 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 What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).

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

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.

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

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

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

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

The single edit tab project will combine the "Redakti" and "Redakti fonton" tabs into a single "Redakti" tab. This is similar to the system already used on the mobile website. (T102398) Initially, the "Redakti" 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 Redaktado tab of Special:Preferences:

• Memori lastan redaktilon,
• Ĉiam uzi la vidan redaktilon laŭeble,
• Ĉiam uzi la fontan redaktilon, and
• Montri ambaŭ redaktilajn langetojn. (This is the state for people using the visual editor now.)

The visual editor uses the same search engine as Special:Search to find links and files. This search will get better at detecting typos and spelling mistakes soon. These improvements to search will appear in the visual editor as well.

The visual editor will be offered to all editors at most "Phase 6" Wikipedias during the next few months. This will affect the following languages, amongst others: Japanese, Korean, Urdu, Persian, Arabic, Tamil, Marathi, Malayalam, Hindi, Bengali, Assamese, Thai, Aramaic.

• 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? Does typing in these languages feels natural in the visual editor? Language engineer David Chan needs to know. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org.
• Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Join the Tech Talk about "Automated citations in Wikipedia: Citoid and the technology behind it" with Sebastian Karcher on 29 February 2016.

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

Hello, I wanted to give a heads up about an upcoming feature for this wiki, which you may already seen in the latest issue of Tech News. Compact Language Links has been available as a beta-feature on all Wikimedia wikis since 2014. With compact language links enabled, users are shown a much shorter list of languages on the interlanguage link section of an article (see image). This will be enabled as a feature in the coming week for all users, which can be turned on or off using a preference setting. We look forward to your feedback and please do let us know if you have any questions. Details about Compact Language Links can be read in the project documentation.

Due to the large scale enablement of this feature, we have had to use MassMessage for this announcement and as a result it is only written in English. We will really appreciate if this message can be translated for other users of this wiki. Thank you. On behalf of the Wikimedia Language team: Runa Bhattacharjee (WMF) (talk) 14:01, 24 jun. 2016 (UTC)Reply

Compact Language Links has been available as a beta-feature on all Wikimedia wikis since 2014. With compact language links enabled, users are shown a much shorter list of languages on the interlanguage link section of an article (see image). Based on several factors, this shorter list of languages is expected to be more relevant for them and valuable for finding similar content in a language known to them. More information about compact language links can be found in the documentation.

From today onwards, compact language links has been enabled as the default listing of interlanguage links on this wiki. However, using the button at the bottom, you will be able to see a longer list of all the languages the article has been written in. The setting for this compact list can be changed by using the checkbox under User Preferences -> Appearance -> Languages

The compact language links feature has been tested extensively by the Wikimedia Language team, which developed it. However, in case there are any problems or other feedback please let us know on the project talk page. It is to be noted that on some wikis the presence of an existing older gadget that was used for a similar purpose may cause an interference for compact language list. We would like to bring this to the attention of the admins of this wiki. Full details are on this phabricator ticket (in English).

Due to the large scale enablement of this feature, we have had to use MassMessage for this announcement and as a result it is only written in English. We will really appreciate if this message can be translated for other users of this wiki. Thank you. On behalf of the Wikimedia Language team: Runa Bhattacharjee (WMF) (talk)-04:21, 28 jun. 2016 (UTC)Reply

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 "Enmeti" menu and click the "Listo de referencoj" 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 "Enmeti" in the dialog to insert the Listo de referencoj. This list will change as you add more footnotes to the page.

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

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

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

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

The "Konservi paĝon" button will say "Publikigi la paĝon". This will affect both the visual and wikitext editing systems. More information is available on Meta.

The visual editor will be offered to all editors at the remaining "Phase 6" Wikipedias during the next few months. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including: Arabic, Hindi, Thai, Tamil, Marathi, Malayalam, Urdu, Persian, Bengali, Assamese, Aramaic and others.

The team is working with the volunteer developers who power Wikisource to provide the visual editor there, for opt-in testing right now and eventually for all users. (T138966)

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

• Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor? Please sign up for the new VisualEditor Community Taskforce.
• Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Watch the Tech Talk by Sebastian Karcher for more information.

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

The Editing team is planning to change the name of the “Konservi paĝon” button to “Publikigi la paĝon” and “Publikigi la ŝanĝojn”. “Publikigi la paĝon” will be used when you create a new page. “Publikigi la ŝanĝojn” will be used when you change an existing page. The names will be consistent in all editing environments.[1][2]

This change will probably happen during the week of 30 August 2016. The change will be announced in Tech News when it happens.

If you are fluent in a language other than English, please check the status of translations at translatewiki.net for “Publikigi la paĝon” and “Publikigi la ŝanĝojn”.

The main reason for this change is to avoid confusion for new editors. Repeated user research studies with new editors have shown that some new editors believed that “Konservi paĝon” would save a private copy of a new page in their accounts, rather than permanently publishing their changes on the web. It is important for this part of the user interface to be clear, since it is difficult to remove public information after it is published. We believe that the confusion caused by the “Konservi paĝon” button increases the workload for experienced editors, who have to clean up the information that people unintentionally disclose, and report it to the functionaries and stewards to suppress it. Clarifying what the button does will reduce this problem.

Beyond that, the goal is to make all the wikis and languages more consistent, and some wikis made this change many years ago. The Legal team at the Wikimedia Foundation supports this change. Making the edit interface easier to understand will make it easier to handle licensing and privacy questions that may arise.

Any help pages or other basic documentation about how to edit pages will also need to be updated, on-wiki and elsewhere. On wiki pages, you can use the wikitext codes {{int:Publishpage}} and {{int:Publishchanges}} to display the new labels in the user's preferred language. For the language settings in your account preferences, these wikitext codes produce “Publikigi la paĝon” and “Publikigi la ŝanĝojn”.

Please share this news with community members who teach new editors and with others who may be interested.

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

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.

• You can now set text as small or big.[3]
• Invisible templates have been shown as a puzzle icon. Now, the name of the invisible template is displayed next to the puzzle icon.[4] A similar feature will display the first part of hidden HTML comments.[5]
• Categories are displayed at the bottom of each page. If you click on the categories, the dialog for editing categories will open.[6]
• At many wikis, you can now add maps to pages. Go to the Insert menu and choose the "Maps" item. The Discovery department is adding more features to this area, like geoshapes. You can read more at mediawiki.org.[7]
• The "Save" button now says "Save page" when you create a page, and "Save changes" when you change an existing page.[8] In the future, the "Konservi paĝon" button will say "Publikigi la paĝon". This will affect both the visual and wikitext editing systems. More information is available on Meta.
• Image galleries now use a visual mode for editing. You can see thumbnails of the images, add new files, remove unwanted images, rearrange the images by dragging and dropping, and add captions for each image. Use the "Options" tab to set the gallery's display mode, image sizes, and add a title for the gallery.[9]

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

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

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

• If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Dankon!

—Elitre (WMF)

Summary: There's a new opt-in Beta Feature of a wikitext mode for the visual editor. Please go try it out.

We in the Wikimedia Foundation's Editing department are responsible for making editing better for all our editors, new and experienced alike. We've been slowly improving the visual editor based on feedback, user tests, and feature requests. However, that doesn't work for all our user needs: whether you need to edit a wikitext talk page, create a template, or fix some broken reference syntax, sometimes you need to use wikitext, and many experienced editors prefer it.

Consequently, we've planned a "wikitext mode" for the visual editor for a long time. It provides as much of the visual editor's features as possible, for those times that you need or want wikitext. It has the same user interface as the visual editor, including the same toolbar across the top with the same buttons. It provides access to the citoid service for formatting citations, integrated search options for inserting images, and the ability to add new templates in a simple dialog. Like in the visual editor, if you paste in formatted text copied from another page, then formatting (such as bolding) will automatically be converted into wikitext.

All wikis now have access to this mode as a Beta Feature. When enabled, it replaces your existing wikitext editor everywhere. If you don't like it, you can reverse this at any time by turning off the Beta Feature in your preferences. We don't want to surprise anyone, so it's strictly an opt-in-only Beta Feature. It won't switch on automatically for anyone, even if you have previously checked the box to "Aŭtomate ŝalti plejparton de betaj funkciojn".

The new wikitext edit mode is based on the visual editor, so it requires JavaScript (as does the current wikitext editor). It doesn't work with gadgets that have only been designed for the older one (and vice versa), so some users will miss gadgets they find important. We're happy to work with gadget authors to help them update their code to work with both editors. We're not planning to get rid of the current main wikitext editor on desktop in the foreseeable future. We're also not going to remove the existing ability to edit plain wikitext without JavaScript. Finally, though it should go without saying, if you prefer to continue using the current wikitext editor, then you may so do.

This is an early version, and we'd love to know what you think so we can make it better. Please leave feedback about the new mode on the feedback page. You may write comments in any language. Thank you.

Plej lastaj teknologiaj novaĵoj de la Vikimedia teknika komunumo. Bonvolu paroli al aliaj uzantoj pri ĉi tiuj ŝanĝoj. Ne ĉiuj ŝanĝoj efikos al vi. Tradukoj estas haveblaj.

Novaĵoj pri teknologio

• Pro la ferioj, la sekvanta afero de novaĵoj pri teknologio estos elsendita je la 9a januaro 2017.
• La verkistoj de la teknika informilo petas vian opinion. Ĉu vi akiris la informon ke vi deziris dum tiu jaro? Ĉu ni mankis gravan teknikan informaĵon dum 2016? Kio informospeco venis tro malfrue? Bonvolu diri al ni! Vi povas skribi per via lingvo. Dankon!

Lastaj ŝanĝoj

• Administrantoj kaj traduk-administrantoj nun povas uzi Specialaĵo:Paĝlingvo sur vikioj kun la traduka kromaĵo. Tio ĉi signifas ke vi povas indiki kion lingvon uzas la paĝo. La traduka kromaĵo uzos tiun lingvon kiel la fonta lingvo kiam vi tradukas. Antaŭe tio estis ĉiam defaŭlte al lingvo de la vikio. Tio ĉi estis kutime Angla. [18]
• Vikioj konektitaj al Vikidatumoj nun povas uzi la funkcioj de sintaksa analizilo {{#statements: }} por akiri formatitan datumon. Vi ankaŭ povas uzi {{#property: }} por akiri krudan datumon. Vi povas vidi la diferencon inter la du ordonoj. Estas ankaŭ similaj novaj funkcioj en Lua. [19]

Problemoj

• Some abuse filters for uploaded files have not worked as they should. We don't know exactly which filters didn't work yet. This means some files that filters should have prevented from being uploaded were uploaded to the wikis. MediaWiki.org and Testwiki have been affected since 13 October. Commons and Meta have been affected since 17 October. Other wikis have been affected since 17 November. [20]

Ŝanĝoj dum ĉi tiu semajno

• Neokazas novan version de MediaWiki ĉi tiu semajno. Ankaŭ nekokazos novan version de MediaWiki dum la sekvanta semajno.

Kunvenoj

• La sekvanta renkontiĝo kun la VisualEditor teamo estos je la 3a januaro je la 20a horo (UTC). Dum la renkontiĝo, vi povas diri al ellaborantoj kiujn cimojn vi opinias kiel la plej gravaj. Vidu kiel aliĝi.

Estontaj ŝanĝoj

• La 2016a Enketo pri komunuma mendolisto estas farita. Ĝi decidas kion la teamo de komunuma teknologio laboros dum 2017. Vi povas konsulti la rezultojn.

Teknologia novaĵoj preparita far tekaj ambasadoroj kaj poŝtita de roboto • Kontribui • Traduki • Akiri helpon • Provizi retroinformadojn • Aboni aŭ malaboni.

Plej lastaj teknologiaj novaĵoj de la Vikimedia teknika komunumo. Bonvolu paroli al aliaj uzantoj pri ĉi tiuj ŝanĝoj. Ne ĉiuj ŝanĝoj efikos al vi. Tradukoj estas haveblaj.

Lastaj ŝanĝoj

• Eventfluos estas nova vojo montri aktivecon en Vikimediaj vikioj. Nuntempe ĝi funkcias kun la abonfluo de lastatempaj ŝanĝoj. Ĝi traktos pli da aferoj poste. Ĝi anstataŭigos RCStream. Iloj kiuj uzas RCStream devus adapti al Eventfluoj antaŭ la 7a julio. [45]

Problemoj

• La Firefogg povas kaŭzi problemojn kun la alŝuta helpilo. Tio ne estos riparita, ĉar Firefox ne subtenos Firefogg en la estonteco. La alŝuta helpilo ne plu longe funkcios kun Firefogg. [46]
• Datenbazoj de Ilaj laboratorioj kaj Vikimediaj laboratorioj estos funkcitene dum 15a februaro. Tio komencos ĉe 17:00 (UTC) kaj daŭros ĉirkaŭ ses horoj. Kelkaj iloj povus havi problemojn dum aŭ post tiam. [47]

Ŝanĝoj dum ĉi tiu semajno

• The TwoColConflict extension is a new way to solve edit conflicts. It makes it easier to copy and paste the relevant text to the text field. It will come to Meta and German Wikipedia this week. It is already available on MediaWiki.org. It will come to more wikis later. [48]
• La nova versio de MediaVikio estos en testaj vikioj kaj MediaWiki.Org ekde 14 februaro. Ĝi estos en ne-Vikipediaj vikioj kaj kelkaj Vikipediaj ekde 15 februaro. Ĝi estos sur ĉiuj vikioj ekde 16 februaro (kalendaro).

Kunvenoj

• Vi povas aliĝi la sekvantan renkontiĝon kun la teamo de vidredaktilo. Dum la renkontiĝo, vi povas diri al disvolvistoj, kiujn cimojn opinias vi estas la plej gravaj. La renkontiĝo okazos la 14 februaro je la 20:00a horo (UTC). Vidu kiel aliĝi.

Estontaj ŝanĝoj

• Paĝaj antaŭprezentoj estos ebligitaj por ensalutantaj uzantoj en la kataluna, greka, rusa kaj itala Vikipedioj en la mezo de februaro. Paĝaj antaŭprezentoj montras al legantoj mallongan parton de ligita artikolo kiam ili ripozas ilian kursoron sur la ligo. Tio estas por helpi ilin kompreni kion ĝi temas proksimume sen foriri la artikolon ili legas. Paĝaj antaŭprezentoj estis antaŭe nomita Hovercards. Ĝi estos disponigita al pli da vikioj poste dum tiu printempo. [49]
• La mendolisto de disvolvantoj estas listo kie disvolvantoj prioritatigas ilojn ke ili bezonas. La voĉdonado fermas ĉe la 14a de februaro 23:59 (UTC). Tiu procedo estas nur por disvolvantoj.

Review

• You can read the 2016 product summary from the Wikimedia Foundation Product group to see what they did with things they said they would work on in the annual plan.

Teknologia novaĵoj preparita far tekaj ambasadoroj kaj poŝtita de roboto • Kontribui • Traduki • Akiri helpon • Provizi retroinformadojn • Aboni aŭ malaboni.

Note: Apologies for cross-posting and sending in English. Message is available for translation on Meta-Wiki.

The Wikimedia movement is beginning a movement-wide strategy discussion, a process which will run throughout 2017. For 15 years, Wikimedians have worked together to build the largest free knowledge resource in human history. During this time, we've grown from a small group of editors to a diverse network of editors, developers, affiliates, readers, donors, and partners. Today, we are more than a group of websites. We are a movement rooted in values and a powerful vision: all knowledge for all people. As a movement, we have an opportunity to decide where we go from here.

This movement strategy discussion will focus on the future of our movement: where we want to go together, and what we want to achieve. We hope to design an inclusive process that makes space for everyone: editors, community leaders, affiliates, developers, readers, donors, technology platforms, institutional partners, and people we have yet to reach. There will be multiple ways to participate including on-wiki, in private spaces, and in-person meetings. You are warmly invited to join and make your voice heard.

The immediate goal is to have a strategic direction by Wikimania 2017 to help frame a discussion on how we work together toward that strategic direction.

Regular updates are being sent to the Wikimedia-l mailing list, and posted on Meta-Wiki. Beginning with this message, monthly reviews of these updates will be sent to this page as well. Sign up to receive future announcements and monthly highlights of strategy updates on your user talk page.

Here is a review of the updates that have been sent so far:

• Update 1 on Wikimedia movement strategy process (15 December 2016)
  • Introduction to process and information about budget spending resolution to support it
• Update 2 on Wikimedia movement strategy process (23 December 2016)
  • Start of search for Lead Architect for movement strategy process
• Update 3 on Wikimedia movement strategy process (8 January 2017)
  • Plans for strategy sessions at upcoming Wikimedia Conference 2017
• Update 4 on Wikimedia movement strategy process (11 January 2017)
  • Introduction of williamsworks
• Update 5 on Wikimedia movement strategy process (2 February 2017)
  • The core movement strategy team, team tracks being developed, introduction of the Community Process Steering Committee, discussions at WikiIndaba conference 2017 and the Wikimedia movement affiliates executive directors gathering in Switzerland
• Update 6 on Wikimedia movement strategy process (10 February 2017)
  • Tracks A & B process prototypes and providing feedback, updates on development of all four Tracks

More information about the movement strategy is available on the Meta-Wiki 2017 Wikimedia movement strategy portal.

Posted by MediaWiki message delivery on behalf of the Wikimedia Foundation, 20:30, 15 feb. 2017 (UTC) • Please help translate to your language • Get help

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• On 22 February the wikipedia.org portal did not work for an hour. This was because of a problem with a JavaScript file. [54]

Changes this week

• You will be able to use <chem> to write chemical formulas in the visual editor. Previously this only worked in the wikitext editor. [55]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 28 February. It will be on non-Wikipedia wikis and some Wikipedias from 1 March. It will be on all wikis from 2 March (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 28 February at 20:00 (UTC). See how to join.

Future changes

• You can soon upload 3D files to Commons. The file formats are AMF and STL. The plan is for this to work later this week but it could be later. [56]
• The name "Wikipedia" will be more obvious at the top of the page when you read Wikipedia in the mobile view. This is because many readers don't realize they are on Wikipedia. [57][58]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now search on English, French, Hebrew and Greek wikis and find words even if you forget the diacritics. It also works if you use diacritics in your search but the wiki doesn't. [59]
• When you use the mobile view and click on a link to an article in another language you will see that article in the mobile view. Previously it changed to the desktop view. [60]

Problems

• Some watchlist gadgets didn't work for a period of time last week. This has now been fixed. [61]
• Admins who click on "mass delete" on a user's Special:Contributions will be taken directly to a list pages created by that user. It has worked like this before, but not lately. [62]

Changes this week

• The way you switch between wikitext and the visual editors in the desktop view has changed. It is now a drop-down menu. This is the same as in the mobile view. [63]
• The "flag the edit in the abuse log" checkbox will be removed from the abuse filter interface. This is because the edits are always flagged in the abuse log. [64]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 7 March. It will be on non-Wikipedia wikis and some Wikipedias from 8 March. It will be on all wikis from 9 March (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 7 March at 20:00 (UTC). See how to join.

Clarification

• The 2017/09 issue of Tech News mentioned 3D file formats you can soon upload to Commons. The AMF format will be available later.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Note: Apologies for cross-posting and sending in English. This message is available for translation on Meta-Wiki.

As we mentioned last month, the Wikimedia movement is beginning a movement-wide strategy discussion, a process which will run throughout 2017. This movement strategy discussion will focus on the future of our movement: where we want to go together, and what we want to achieve.

Regular updates are being sent to the Wikimedia-l mailing list, and posted on Meta-Wiki. Each month, we are sending overviews of these updates to this page as well. Sign up to receive future announcements and monthly highlights of strategy updates on your user talk page.

Here is a overview of the updates that have been sent since our message last month:

• Update 7 on Wikimedia movement strategy process (16 February 2017)
  • Development of documentation for Tracks A & B
• Update 8 on Wikimedia movement strategy process (24 February 2017)
  • Introduction of Track Leads for all four audience tracks
• Update 9 on Wikimedia movement strategy process (2 March 2017)
  • Seeking feedback on documents being used to help facilitate upcoming community discussions

More information about the movement strategy is available on the Meta-Wiki 2017 Wikimedia movement strategy portal.

Posted by MediaWiki message delivery on behalf of the Wikimedia Foundation, 19:43, 9 mar. 2017 (UTC) • Please help translate to your language • Get help

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes this week

• You will be able to show references from <references /> tags in more than one column on your wiki. This is the list of footnotes for the sources in the article. How many columns you see will depend on how big your screen is. On some wikis, some templates already do this. Templates that use <references /> tags will need to be updated, and then later the change can happen for all reference lists. [65][66]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 14 March. It will be on non-Wikipedia wikis and some Wikipedias from 15 March. It will be on all wikis from 16 March (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 14 March at 19:00 (UTC). See how to join.

Future changes

• Some old web browsers will not be able to use JavaScript on Wikimedia wikis in the future. If you have an old web browser on your computer you can upgrade to a newer version. [67]
• CSS in templates will be stored in a separate page in the future. [68][69]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

This message, "We invite you to join the movement strategy conversation (now through April 15)", was sent through multiple channels by Gregory Varnum on 15 and 16 of March 2017 to village pumps, affiliate talk pages, movement mailing lists, and MassMessage groups. A similar message was sent by Nicole Ebber to organized groups and their mailing lists on 15 of March 2017. This version of the message is available for translation and documentation purposes

Dear Wikimedians/Wikipedians:

Today we are starting a broad discussion to define Wikimedia's future role in the world and develop a collaborative strategy to fulfill that role. You are warmly invited to join the conversation.

There are many ways to participate, by joining an existing conversation or starting your own:

Track A (organized groups): Discussions with your affiliate, committee or other organized group (these are groups that support the Wikimedia movement).

Track B (individual contributors): On Meta or your local language or project wiki.

This is the first of three conversations, and it will run between now and April 15. The purpose of cycle 1 is to discuss the future of the movement and generate major themes around potential directions. What do we want to build or achieve together over the next 15 years?

We welcome you, as we create this conversation together, and look forward to broad and diverse participation from all parts of our movement.

• Find out more about the movement strategy process
• Learn more about volunteering to be a Discussion Coordinator

Sincerely,

Nicole Ebber (Track A Lead), Jaime Anstee (Track B Lead), & the engagement support teams

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The Save page button now says Publish page or Publish changes on the Wikimedia wikis except for Wikipedias and Wikinewses. This change will come to Wikipedias later. The point is to make it more clear that the edit will change the page immediately. Publish page is when you save a new page and Publish changes when you edit an existing page. [70]
• DMOZ no longer works. Templates that use DMOZ can be redirected to archive.org or another mirror. DMOZ has been removed from the RelatedSites extension on Wikivoyage. [71]
• You can see monthly page views when you click on Page information in the sidebar. Developers can also get monthly page views through the API. [72]
• The Linter extension is now on smaller Wikimedia wikis. It helps editors find some wikitext errors so they can be fixed. It will come to other Wikimedia wikis later. The extension will be able to find more errors later. [73]
• The MediaWiki-Vagrant portable development environment has been updated to use Debian Jessie. This means local development and testing will be more like on the majority of Wikimedia production servers. [74]

Problems

• On 15 March some interwiki links to other languages were not correctly sorted. This has been fixed. If you still see pages where the interwiki links are not sorted as they should be, they should be fixed automatically with time or you can edit the page and save it without changing anything. If this doesn't work, please report it. [75]

Changes this week

• When you edit with the visual editor, you will be able to switch the direction you write in from right-to-left to left-to-right as you are editing. This is especially important for editors who edit in languages that write from right to left. You can do this with a tool in the editing menu. You can also use the keyboard shortcut Ctrl+Shift+X on PCs or Cmd+Shift+X on Macs. [76]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 21 March. It will be on non-Wikipedia wikis and some Wikipedias from 22 March. It will be on all wikis from 23 March (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 21 marto at 19:00 (UTC). See how to join.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The Konservi paĝon button now says Publikigi la paĝon or Publikigi la ŝanĝojn on most Wikipedias. The point is to make it more clear that the edit will change the page immediately. Publikigi la paĝon is when you save a new page and Publikigi la ŝanĝojn when you edit an existing page. [80]
• The tracking category Kategorio:Paĝoj kun ŝablonaj iteracioj is now added when a template loop is found. A template loop is for example when a template tries to use a second template that uses the first template. [81]
• English Wikipedia now has cookie blocks. It will come to more wikis in the future. This is an extension to the autoblock system so when a user is blocked, the next time they visit the wiki a cookie will be set. This means that even if the user switches accounts and to a new IP address the cookie will block them again. [82]

Problems

• Wikidata descriptions, aliases and labels that used some characters could not be saved. This has now been fixed. [83]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 4 April. It will be on non-Wikipedia wikis and some Wikipedias from 5 April. It will be on all wikis from 6 April (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 4 April at 19:00 (UTC). See how to join.
• You can join the next office hour with the Wikidata team. The meeting will be on 5 April at 16:00 (UTC). See how to join.

Future changes

• New filters for Recent changes will come to Wikidata and Persian, Dutch, Russian, Turkish, Czech and Hebrew Wikipedia on 11 April. The new filters include filtering, highlighting and user intent prediction. User intent prediction means the filter tries to help editors determine if the edit was made in good faith or not. Other wikis will get it later. [84]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Please accept our apologies for cross-posting this message. This message is available for translation on Meta-Wiki.

On behalf of the Wikimedia Foundation Elections Committee, I am pleased to announce that self-nominations are being accepted for the 2017 Wikimedia Foundation Board of Trustees Elections.

The Board of Trustees (Board) is the decision-making body that is ultimately responsible for the long-term sustainability of the Wikimedia Foundation, so we value wide input into its selection. More information about this role can be found on Meta-Wiki. Please read the letter from the Board of Trustees calling for candidates.

The candidacy submission phase will last from April 7 (00:00 UTC) to April 20 (23:59 UTC).

We will also be accepting questions to ask the candidates from April 7 to April 20. You can submit your questions on Meta-Wiki.

Once the questions submission period has ended on April 20, the Elections Committee will then collate the questions for the candidates to respond to beginning on April 21.

The goal of this process is to fill the three community-selected seats on the Wikimedia Foundation Board of Trustees. The election results will be used by the Board itself to select its new members.

The full schedule for the Board elections is as follows. All dates are inclusive, that is, from the beginning of the first day (UTC) to the end of the last.

• April 7 (00:00 UTC) – April 20 (23:59 UTC) – Board nominations
• April 7 – April 20 – Board candidates questions submission period
• April 21 – April 30 – Board candidates answer questions
• May 1 – May 14 – Board voting period
• May 15–19 – Board vote checking
• May 20 – Board result announcement goal

In addition to the Board elections, we will also soon be holding elections for the following roles:

• Funds Dissemination Committee (FDC)
  • There are five positions being filled. More information about this election will be available on Meta-Wiki.

• Funds Dissemination Committee Ombudsperson (Ombuds)
  • One position is being filled. More information about this election will be available on Meta-Wiki.

Please note that this year the Board of Trustees elections will be held before the FDC and Ombuds elections. Candidates who are not elected to the Board are explicitly permitted and encouraged to submit themselves as candidates to the FDC or Ombuds positions after the results of the Board elections are announced.

More information on this year's elections can be found on Meta-Wiki. Any questions related to the election can be posted on the election talk page on Meta-Wiki, or sent to the election committee's mailing list, board-electionswikimedia.org.

On behalf of the Election Committee,
Katie Chan, Chair, Wikimedia Foundation Elections Committee
Joe Sutherland, Community Advocate, Wikimedia Foundation

Posted by MediaWiki message delivery on behalf of the Wikimedia Foundation Elections Committee, 03:36, 7 apr. 2017 (UTC) • Please help translate to your language • Get help

Read this message in another language • Please help translate to your language

The Wikimedia Foundation will be testing its secondary data center in Dallas. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to conduct a planned test. This test will show whether they can reliably switch from one data center to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.

They will switch all traffic to the secondary data center on Wednesday, 19 April 2017. On Wednesday, 3 May 2017, they will switch back to the primary data center.

Unfortunately, because of some limitations in MediaWiki, all editing must stop during those two switches. We apologize for this disruption, and we are working to minimize it in the future.

You will be able to read, but not edit, all wikis for a short period of time.

• You will not be able to edit for approximately 20 to 30 minutes on Wednesday, 19 April and Wednesday, 3 May. The test will start at 14:00 UTC (15:00 BST, 16:00 CEST, 10:00 EDT, 07:00 PDT, 23:00 JST, and in New Zealand at 02:00 NZST on Thursday 20 April and Thursday 4 May).
• If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.

Other effects:

• Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
• There will be code freezes for the weeks of 17 April 2017 and 1 May 2017. Non-essential code deployments will not happen.

This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule. There will be more notifications about this. Please share this information with your community. /User:Whatamidoing (WMF) (talk)

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can add ?safemode=1 to the end of the URL on Wikimedia wikis to disable your personal CSS and JavaScript. Example: https://en.wikipedia.org/wiki/Literature?safemode=1. This means you can test if a problem is because of your user scripts or gadgets without uninstalling them. [89]
• You can now see a list of all autoblocks on Special:AutoblockList. [90]
• The Wikiversity and Wikinews logos are now shown directly from the configuration and not from [[File:Wiki.png]]. If you want to change logo or have an anniversary logo, see how to request a configuration change. This is how it already works for other projects. They can request logo changes the same way. [91]

Problems

• Because of a data centre test you will be able to read but not edit the wikis for 20 to 30 minutes on 19 April. This will start at 14:00 (UTC). You might lose edits if you try to save during this time. You can read more about this. This will also happen on 3 May.

Changes this week

• There is no new Mediawiki version this week. This is because of the data centre test.

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 18 aprilo at 19:00 (UTC). See how to join.

Future changes

• stats.wikimedia.org will be replaced. You can see the new prototype. You can leave feedback on this change.
• Page Previews will be turned on for logged-out users on a large number of wikis in May. It could be postponed and happen later. Page Previews shows readers a short part of a linked article when they rest their mouse pointer on the link. This is to help them understand what it is about without leaving the article they are reading. Page Previews used to be called Hovercards. Users who have tested the feature can give feedback. [92]
• From next week, user scripts using very old deprecated wikibits functions will show errors. These functions have not worked since 2013. You should fix or disable broken scripts. You can see examples of how to upgrade scripts. [93][94]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The content translation tool works again. It was turned off because of a database problem. [100]
• Scripts using very old deprecated wikibits functions show errors. These functions have not worked since 2013. You should fix or disable broken scripts. You can see examples of how to upgrade scripts. This is the same thing as Tech News wrote about in issue 2017/16. You need to add mw.loader.using( 'mediawiki.util' ) block for your scripts also, or add mediawiki.util dependency in gadget ResourceLoader section in MediaWiki:Gadgets-definition. [101][102]

Problems

• Because of a data centre test you will be able to read but not edit the wikis for 20 to 30 minutes on 3 May. This will start at 14:00 (UTC). You might lose edits if you try to save during this time. You can read more about this.

Changes this week

• There is no new MediaWiki version this week. This is because of the data centre test.

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 2 May at 19:00 (UTC). See how to join.

Future changes

• All Wikimedia wikis will have cookie blocks from May 8. This is an extension to the autoblock system so when a user is blocked, the next time they visit the wiki a cookie will be set. This means that even if the user switches accounts and to a new IP address the cookie will block them again. [103]
• The Publikigi la ŝanĝojn, Antaŭrigardo and Montri la ŝanĝojn buttons will look slightly different. This is to fit with the OOUI look. Users can test scripts, gadgets and so on to see if they work with the new interface by adding &ooui=1 to the URL. [104]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

This is a message from the Wikimedia Foundation Elections Committee. Translations are available.

Voting has begun for eligible voters in the 2017 elections for the Wikimedia Foundation Board of Trustees.

The Wikimedia Foundation Board of Trustees is the ultimate governing authority of the Wikimedia Foundation, a 501(c)(3) non-profit organization registered in the United States. The Wikimedia Foundation manages many diverse projects such as Wikipedia and Commons.

The voting phase lasts from 00:00 UTC May 1 to 23:59 UTC May 14. Click here to vote. More information on the candidates and the elections can be found on the 2017 Board of Trustees election page on Meta-Wiki.

On behalf of the Elections Committee,
Katie Chan, Chair, Wikimedia Foundation Elections Committee
Joe Sutherland, Community Advocate, Wikimedia Foundation

Posted by the MediaWiki message delivery • Translate • Get help

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• Some users have a problem with the watchlist. Some changes in categories make the watchlist a blank page. The developers are working on this. Until this is fixed you can try some things that have helped other editors if you have this problem. You can turn on Kaŝi enkategoriigon de paĝoj in your watchlist preferences. You can turn off Etendi la atentaron por montri ĉiujn ŝanĝojn, ne nur la plej lastajn in your watchlist preferences. You can remove problematic categories from Special:EditWatchlist/raw. [105]
• There was a problem with the visual editor for several days. You could not save edits that triggered a CAPTCHA. This would for example be when a new user added external links in references. This was fixed on 2 May. [106]

Changes this week

• When you edit you can switch between the visual editor and the wikitext editor. This works if the wiki you edit has the visual editor. The menu will now say Visual editing and Source editing instead of Switch to visual editing and Switch to code editing. This is because it was confusing when the menu said you could switch to the editor you were already using. [107]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 9 May. It will be on non-Wikipedia wikis and some Wikipedias from 10 May. It will be on all wikis from 11 May (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 9 May at 19:00 (UTC). See how to join.

Future changes

• You will be able to get a notification when a page you created is connected to a Wikidata item. This will come to Wikivoyage on 9 May. If there are no problems it will come to most Wikipedias on 30 May. It will come to other projects and English, French and German Wikipedia later in the summer. It will be opt-in for existing users and opt-out for new users. [108][109]
• Markup that looks like code for language variants might need to be fixed. If -{ is used in transclusions or web addresses it has to be escaped appropriately. You can use -<nowiki/>{ for transclusions and %2D{ in web addresses. A transclusion could for example be when you use -{ in a template: {{1x| sad :-{ face }}. This is because of some code fixes to the preprocessor and affects all wikis. [110][111]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

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 "Antaŭvidi viajn ŝanĝojn".

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.

• A new wikitext editing mode is available as a Beta Feature on desktop devices. The 2017 wikitext editor has the same toolbar as the visual editor and can use the citoid service and other modern tools. Go to Special:Preferences#mw-prefsection-betafeatures to enable the ⧼Visualeditor-preference-newwikitexteditor-label⧽.
• A new visual diff tool is available in VisualEditor's visual mode. You can toggle between wikitext and visual diffs. More features will be added to this later. In the future, this tool may be integrated into other MediaWiki components. [112]
• The team have added multi-column support for lists of footnotes. The <references /> 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. [113]
• 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. [114]
• 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. [115]
• The Kategorioj item has been moved to the top of the Paĝaj opcioj menu (from clicking on the "hamburger" icon) for quicker access. [116] There is also now a "Templates used on this page" feature there. [117]
• You can now create <chem> tags (sometimes used as <ce>) for chemical formulas inside the visual editor. [118]
• Tables can be set as collapsed or un-collapsed. [119]
• The Speciala signo menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) . The team thanks the volunteer developer, Tpt. [120]
• 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. [121]
• There is a new keyboard shortcut for citations: Control+Shift+K on a PC, or Command+Shift+K on a Mac. It is based on the keyboard shortcut for making links, which is Control+K or Command+K respectively. [122]

• The team is working on a syntax highlighting tool. It will highlight matching pairs of <ref> tags and other types of wikitext syntax. You will be able to turn it on and off. It will first become available in VisualEditor's built-in wikitext mode, maybe late in 2017. [123]
• The kind of button used to Antaŭrigardo, Montri la ŝanĝojn, and finish an edit will change in all WMF-supported wikitext editors. The new buttons will use OOjs UI. The buttons will be larger, brighter, and easier to read. The labels will remain the same. You can test the new button by editing a page and adding &ooui=1 to the end of the URL, like this: https://www.mediawiki.org/wiki/Project:Sandbox?action=edit&ooui=1 The old appearance will no longer be possible, even with local CSS changes. [124]
• 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. [125]
• 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. Dankon!

—Elitre (WMF)

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now use ISBNs to automatically generate citations in the visual editor. This works on wikis that have enabled Citoid. [126]
• The Two Column Edit Conflict View is available as a beta feature on all wikis. It is a new interface for the edit conflict resolution page. [127]

Problems

• The mediawiki.util library does not load automatically any more. Your Special:MyPage/common.js may use it. If you have technical problems that started a couple of weeks ago you can try adding mw.loader.using( 'mediawiki.util' ).done(function(){ as the first line in the file and }); as a last one. Tech News wrote about this in the 2017/18 issue. [128]

Changes this week

• The RevisionSlider extension will be a default feature on all wikis. RevisionSlider is an easier way to move between changes in the page history. It has been a default feature on German, Arabic and Hebrew Wikipedia and a beta feature on all wikis. You will be able to turn it off in your preferences. [129]
• There is no new MediaWiki version this week.

Future changes

• Administrators will soon be able to search through deleted pages. [130][131]
• Markup that looks like code for language variants might need to be fixed. Tech News wrote about this last week. If -{ is used in transclusions or web addresses it has to be escaped appropriately. You can use -<nowiki/>{ for transclusions and %2D{ in web addresses. This is because of some code fixes to the preprocessor and affects all wikis. You can now see the full list of wikis with this problem and help fix them to avoid that things break later this month. You might find false positives. You can read more about what to fix. [132][133]

Older unreported changes

• Your Meta user page is shown on all wikis where you don't have a local user page. You can now add the magic word __NOGLOBAL__ to your Meta user page to stop this. [134][135]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Message is available for translation on Meta-Wiki

The Wikimedia movement strategy core team and working groups have completed reviewing the more than 1800 thematic statements we received from the first discussion. They have identified 5 themes that were consistent across all the conversations - each with their own set of sub-themes. These are not the final themes, just an initial working draft of the core concepts.

You are invited to join the online and offline discussions taking place on these 5 themes. This round of discussions will take place between now and June 12th. You can discuss as many as you like; we ask you to participate in the ones that are most (or least) important to you.

Here are the five themes, each has a page on Meta-Wiki with more information about the theme and how to participate in that theme's discussion:

• Healthy, Inclusive Communities
• The Augmented Age
• A Truly Global Movement
• The Most Respected Source of Knowledge
• Engaging in the Knowledge Ecosystem

On the movement strategy portal on Meta-Wiki, you can find more information about each of these themes, their discussions, and how to participate.

Posted by MediaWiki message delivery on behalf of the Wikimedia Foundation • Please help translate to your language • Get help

Translations of this message are available on Meta-Wiki.

On behalf of the Wikimedia Foundation Elections Committee, we are pleased to announce that self-nominations are being accepted for the 2017 Wikimedia Foundation Funds Dissemination Committee and Funds Dissemination Committee Ombudsperson elections. Please read the letter from the Wikimedia Foundation calling for candidates at on the 2017 Wikimedia Foundation elections portal.

Funds Dissemination Committee
The Funds Dissemination Committee (FDC) makes recommendations about how to allocate Wikimedia movement funds to eligible entities. There are five positions being filled. More information about this role can be found at the FDC elections page.

Funds Dissemination Committee Ombudsperson
The Funds Dissemination Committee Ombudsperson receives complaints and feedback about the FDC process, investigates complaints at the request of the Board of Trustees, and summarizes the investigations and feedback for the Board of Trustees on an annual basis. One position is being filled. More information about this role can be found at the FDC Ombudsperson elections page.

The candidacy submission phase will last until May 28 (23:59 UTC).

We will also be accepting questions to ask the candidates until May 28. You can submit your questions on Meta-Wiki. Once the questions submission period has ended on May 28, the Elections Committee will then collate the questions for the candidates to respond to.

The goal of this process is to fill the five community-selected seats on the Wikimedia Foundation Funds Dissemination Committee and the community-selected ombudsperson. The election results will be used by the Board itself to make the appointments.

The full schedule for the FDC elections is as follows. All dates are inclusive, that is, from the beginning of the first day (UTC) to the end of the last.

• May 15 (00:00 UTC) – May 28 (23:59 UTC) – Nominations
• May 15 – May 28 – Candidates questions submission period
• May 29 – June 2 – Candidates answer questions
• June 3 – June 11 – Voting period
• June 12–14 – Vote checking
• June 15 – Goal date for announcing election results

More information on this year's elections can be found at the 2017 Wikimedia Foundation elections portal.

Please feel free to post a note about the election on your project's village pump. Any questions related to the election can be posted on the talk page on Meta-Wiki, or sent to the election committee's mailing list, board-electionswikimedia.org.

On behalf of the Election Committee,
Katie Chan, Chair, Wikimedia Foundation Elections Committee
Joe Sutherland, Community Advocate, Wikimedia Foundation

Posted by the MediaWiki message delivery • Translate • Get help

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can see new files on Special:NewFiles. You can now pick which dates you want to see files from. [139]
• When you read Wikipedia on a mobile device the first paragraph now comes before the infobox. [140]
• You can now remove navigation elements from your results when you search. This could for example be part of an infobox that is only there to help you find the previous or next article. [141]
• New users on Wikivoyages and Wikipedias (except French, English and German) now get a notification when a page they created is connected to Wikidata. Other wikis will get it 13 June. [142]

Problems

• The MediaWiki version from two weeks ago was rolled back. It was fixed late last week. Changes that were planned to go out last week did not happen. [143]

Changes this week

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 6 June at 19:00 (UTC). See how to join.

Future changes

• The 2006 wikitext editor will be removed the week of 27 June. This is the old toolbar with small square blue buttons. You can see a picture of it. 0.03% of active Wikimedia editors use this old tool. They will not see a toolbar at all. [148][149]
• Wikimedia wikis use OCG to create PDFs. The OCG code has a lot of problems and will stop working. It has to be replaced. An alternative is Electron. You can tell the developers what you need the PDF service to be able to do. Electron already works on German Wikipedia. It will be on English Wikipedia later this week so you can test it there too. [150]
• The Architecture Committee will change and get a new name. You can read and comment on the draft that describes the new committee.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Some wikis have the larger and brighter OOjs UI edit page buttons. When you write an edit summary there you can now see how many bytes you have left before the summary is too long. [151]
• When you search on Wikipedia you can now find pages on other Wikimedia projects that could be relevant. You see them next to the search results. [152]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 13 June. It will be on non-Wikipedia wikis and some Wikipedias from 14 June. It will be on all wikis from 15 June (calendar).

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 13 June at 19:00 (UTC). See how to join.

Future changes

• You will soon be able to get a notification when someone tries to log in to your account. You can test this on the test wiki. This will only work if they fail to log in to your account. [153]
• Wikimedia wikis use OCG to create PDFs. The OCG code has a lot of problems and will stop working. It has to be replaced. An alternative is Electron. You can tell the developers what you need the PDF service to be able to do. Electron now works on all Wikimedia projects. [154]
• Administrators can soon search for deleted page titles and find results that are similar to what they searched for. Today the search only finds pages that are exactly the same as what you search for. This is to make it easier to find pages when you don't know the exact title. Administrators on Arabic, Catalan, English, Persian, German, Italian, Polish, and Russian Wikipedia and on mediawiki.org can test this by adding &fuzzy=1 to the end of the web address when looking at Special:Undelete. [155][156]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The <inputbox> has a new searchfilter parameter. You can add values like searchfilter=insource:foo. It will add that to the user's search query. [160]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 27 June. It will be on non-Wikipedia wikis and some Wikipedias from 28 June. It will be on all wikis from 29 June (calendar).
• Users will be able to choose whether they want to see Wikidata changes in enhanced watchlist/recent changes. Previously, this was disabled for everyone. [161]

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 27 June at 19:00 (UTC). See how to join.
• You can join the next WMF Language team office hour, an open session to talk about Wikimedia Language projects. The meeting will be on 27 June at 13:00 UTC. [162]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• There was a problem with maps on Wikimedia wikis that used <mapframe> when you clicked on the link to another map service. Open Street Map or Google Maps are examples of other map services. If you had marked a place on the map the marker would not be in the same place on the other map service. It was in the middle of the map. This has now been fixed. [163]

Changes this week

• Very old and inactive unpublished translations in the Content Translation database will be removed. This is because of technical maintenance. If you have not worked on a translation after 1 January 2016 you will lose it after 6 July. If you want to keep the unfinished translation you need to open it before 6 July with the Content Translation tool. You can continue working on it later. Translations that were started or have been worked on after 1 January 2016 will not be affected.
• There is no new Mediawiki version this week.
• EventStreams is a new way to show activity on Wikimedia wikis. It works with the recent changes feed. It will do more things later. It will replace RCStream. Tools that use RCStream should move to EventStreams before 7 July. Tech News wrote about this in the 2017/07 issue. [164]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• There are sometimes links to pages about the same thing on other Wikimedia projects. A Wikipedia article about Berlin can link to the Wikivoyage guide or Wiktionary entry about Berlin. You can now see when that page has a badge. A badge could be the star that shows that an article is a featured article. [165]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 11 julio. It will be on non-Wikipedia wikis and some Wikipedias from 12 julio. It will be on all wikis from 13 julio (calendar).

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 11 julio at 19:00 (UTC). See how to join.

Future changes

• Mobile users will be able to edit Wikipedia without JavaScript. This will make it possible to edit the wikis from older mobile phones. This will probably happen on 18 July for most wikis. [166]
• We will not use Tidy on Wikimedia wikis in the future. It will be replaced by June 2018. It could be earlier. Editors will need to fix pages that could break. You can read the simplified instructions for editors.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Please help translate to your language • Read this in another language

Hello,

At the request of Wikipedia editors, a new feature has been added to MediaWiki. Long lists of references (also called citations or footnotes) will automatically be displayed in columns. This will make it easier for most people to read the references, especially on narrow screens. Short lists of references will not be affected.

I plan to enable this new feature at this wiki on Monday, 24 July 2017. After that date, use the normal <references /> tag on any page with many references to see this feature. If you do not want columns used on that page, then use this wikitext code instead: <references responsive="0" />

If you believe that this new feature is not appropriate for this wiki, or if you need help adjusting templates, then please contact me at mw:Contributors/Projects/Columns for references. User:Whatamidoing (WMF) (talk)

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• "Wikimedia Labs" is now called "Cloud VPS". "Wikimedia Tool Labs" is now called "Wikimedia Toolforge". This is to help clarify the purpose of these services. [167]

Problems

• On some pages, the Table of Contents is not being shown. It will normally appear if you edit the page again. Investigation is currently ongoing. [168]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 18 July. It will be on non-Wikipedia wikis and some Wikipedias from 19 July. It will be on all wikis from 20 July (calendar).

Meetings

Future changes

• Page Previews, currently a Beta Feature, will be enabled for logged-out users for all remaining Wikipedias (with the exception of English and German) the week of 24 July. An A/B test will be run on English Wikipedia to collect data before approaching the community for further discussion. [170]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

The MediaWiki developers have been slowly improving the accessibility of the user interface. The next step in this transition will change the appearance of some buttons and may break some outdated (non-updated or unmaintained) user scripts and gadgets.

You can see and use the old and new versions now. Most editors will only notice that some buttons are slightly larger and have different colors.

• Comparison of old and new styles

• 

  Buttons before the change

• 

  Buttons after the change

However, this change also affects some user scripts and gadgets. Unfortunately, some of them may not work well in the new system. If you maintain any user scripts or gadgets that are used for editing, please see mw:Contributors/Projects/Accessible editing buttons for information on how to test and fix your scripts. Outdated scripts can be tested and fixed now.

This change will probably reach this wiki on Tuesday, 1 August 2017. Please leave a note at mw:Talk:Contributors/Projects/Accessible editing buttons if you need help.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• Some pages show the error Lua error in mw.wikibase.entity.lua at line 34: The entity data must be a table obtained via mw.wikibase.getEntityObject. This problem happens on pages with a Lua module that uses Wikidata. The developers are working on fixing the problem. You can fix a page by opening it for editing and then saving without changing anything. [176]
• Wikidata and German Wikipedia could not be edited for an hour on 28 July. You can read why and how we could avoid it in the future in the incident report.

Changes later this week

• Some wikis already have the larger and brighter OOjs UI edit page buttons. All remaining wikis except Commons will have these from 1 August. [177]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 1 August. It will be on non-Wikipedia wikis and some Wikipedias from 2 August. It will be on all wikis from 3 August (calendar).

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 1 August at 19:00 (UTC). See how to join.

Future changes

• The default font in the edit window will soon change for some users. Instead of using the browser default it will be monospace. Users can change this in their preferences. This should only change this for some users on Macs and iOS devices. [178]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now see which Wikipedia language versions are read in a specific country. This tool is called Wikipedia Views Visualized. [179]
• The Architecture Committee is now the Wikimedia Technical Committee. You can read the charter. [180]

Problems

• You can get an email when a page on your watchlist was edited. You can choose not to get emails for minor edits. There is a bug that means that you then don't get an email when someone does a normal edit after a minor edit. The developers are working on fixing this. Until it has been fixed you can activate "Sendi al mi ankaŭ retmesaĝojn pro malgrandaj redaktoj de paĝoj kaj dosieroj" at the bottom of "Profilo de uzanto" in your preferences if you want to. [181]
• The thanks button sometimes didn't work for mobile users. This was because of a new bug and has now been fixed. [182]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 8 August. It will be on non-Wikipedia wikis and some Wikipedias from 9 August. It will be on all wikis from 10 August (calendar).

Future changes

• Editors and readers who still use Internet Explorer 8 on Windows XP will not be able to use Wikipedia. Internet Explorer 8 on Windows XP can't connect securely to the wikis. When we allow them to do so it means that we get less security for everyone else. If you use Internet Explorer 8 on Windows XP you can install Firefox 52 ESR instead. Around 0.1% of the traffic to the Wikimedia wikis comes from Internet Explorer 8 on Windows XP. [183]
• Links to sections on Wikipedia don't work well in languages that don't use the Latin script. The URL in the address bar in your browser shows Latin characters like .D0.A1.D1.81.D1.8B.D0.BB.D0.BA.D0.B8 instead of the section heading in the wiki's language. Links to sections in non-Latin scripts will be in the script of that wiki in the future. This will happen in the next few months. [184][185]
• Wiki pages printed by the web browser "Print" function will have an updated style. This new style will be similar to the when you download a page as PDF. It will be better at showing tables, infoboxes and headings. [186][187]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Bureaucrats can now set users as confirmed. Previously only stewards could do this on most wikis. Nothing will change for wikis that have previously decided to let administrators set users as confirmed. [188]

Problems

• The symbols in the language list that show that an article is good or featured in that language doesn't work. Links to the Commons category in the sidebar doesn't work either. The developers are working on fixing it. [189][190]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 15 August. It will be on non-Wikipedia wikis and some Wikipedias from 16 August. It will be on all wikis from 17 August (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now test the new Timeless skin on the test wiki and mediawiki.org. You can turn it on in your preferences. You can report bugs in Phabricator. It will come to more wikis soon. [191][192]
• Your watchlist can now have the option to unwatch pages. You have to turn this on in your preferences. [193]
• If a table has several columns you can often choose which column you want to use to sort the table. This has not worked for some columns for readers who have used Firefox or Safari. This has now been fixed. [194]
• The RelatedArticles extension has shown related pages on Wikivoyages. You will now see the related pages at the end of the article together with an image. Previously the links were in the sidebar. Wikis that want this extension can request it on Phabricator.

Changes later this week

• Videos will now be played in the WebM format in all browsers. Previously some browsers used Ogg Theora (.ogv). If you use Safari, Internet Explorer or Edge you may see slower playback speed at high resolutions. Instead we will get better quality and smaller file size. You can still upload video as Ogg files. They are automatically converted to WebM. This doesn't affect Ogg audio files. [195]
• The default font in the edit window will change for some users this week. Instead of using the browser default, it will be monospace. Users can change this in their preferences. This should only change this for some users on Macs and iOS devices. [196]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 22 August. It will be on non-Wikipedia wikis and some Wikipedias from 23 August. It will be on all wikis from 24 August (calendar).

Meetings

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Syntax highlighting is now a beta feature on Wikimedia wikis with text written from left to right. It will come to right-to-left wikis later. This beta feature is based on CodeMirror. [197][198]
• You will now get a notification when someone tries to log in to your account and fails. If they try from a device or IP address that have logged in to your account before you will be notified after five failed attempts. You can turn this off or choose to get an email notification in your preferences. You can also turn on to get an email when someone logs in to your account from a new device or IP address. [199]

Problems

• Some pages show the error Lua error in mw.wikibase.entity.lua at line 34: The entity data must be a table obtained via mw.wikibase.getEntityObject. This problem happens on pages with a Lua module that use Wikidata. This has now been fixed and no new pages will get this problem. You still need to fix pages that were broken before and still show the error message. You can see how on this page. [200]

Changes later this week

• You can block users from sending you notifications. [201]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 29 August. It will be on non-Wikipedia wikis and some Wikipedias from 30 August. It will be on all wikis from 31 August (calendar).

Meetings

Future changes

• In the future you will have global preferences. This means you could set something in your preferences to work in the same way on all wikis. You will not be forced to use global preferences. The developers are now asking if editors need exceptions. This is where you want to use global settings on almost all wikis, but have some wikis where you want it to work in a different way. If you want this you need to tell the developers now. You can do so on the talk page. [202]
• New filters for edit review is a beta feature to improve recent changes pages. It will work on watchlists from 5 September. [203]
• The jQuery library will be upgraded to version 3 in September 2017. Wikis can ask on Phabricator to get it early, so they can help find and solve problems now.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Tech News

• We are asking Tech News readers five questions to make the newsletter better. You can answer the questions here. We are grateful for every reply we get.

Recent changes

• The RevisionSlider user interface has changed. You can now select revisions by clicking on the bars. You can move the blue knob past the yellow one and the yellow one will move along, and the other way around. [204][205]

Problems

• Some users have problems loading very large watchlists. It is working better than earlier but the problem has not been solved. The developers are working on fixing it. Until it has been fixed you can turn on "Etendi la atentaron por montri ĉiujn ŝanĝojn, ne nur la plej lastajn" in your preferences and see if it helps. [206]

Changes later this week

• New filters for edit review is a beta feature to improve recent changes pages. It will work on watchlists from 5 September. [207]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 5 September. It will be on non-Wikipedia wikis and some Wikipedias from 6 September. It will be on all wikis from 7 September (calendar).

Meetings

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can get a notification when a page you created is connected to a Wikidata item. You can choose to get these notifications in your preferences. Some wikis already had this option. It is now available on all wikis. [209]
• The Newsletter extension is now on mediawiki.org. The newsletter extension is for newsletters where you can subscribe by getting a notification when a new issue has been published. It will come to more wikis later. [210]
• The Linter extension helps you find technical errors in articles. There is now a new high-priority category: tidy-whitespace-bug. This usually affects templates with horizontal lists. You can read more about using Linter and the Tidy whitespace bug. [211]

Problems

• Tech News 2017/36 reported about new filters for edit review coming to watchlists. This was planned to happen last week. It will happen next week instead. [212]

Changes later this week

Meetings

Future changes

• You can't use OCG to create PDFs after 1 October. This is because of technical problems. You can use Electron instead. Most PDFs are already created with Electron. Electron will get missing features before 1 October. You can create books but they will not have all planned features until November or December. You can read more on mediawiki.org.
• New filters for edit review are available now on recent changes as a beta feature. Some of those filters and other features will be deployed as default features in the coming weeks. Users will be able to opt out in their preferences. [213]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Wikitext syntax highlighting is a beta feature on Wikimedia wikis with text written from left to right. This beta feature is based on CodeMirror. You can now search through the entire article with CTRL+F or cmd+F when you edit. Before it just searched through a part of the article. The developers are also fixing a couple of other bugs. [217][218]
• Administrators on wikis that use Structured Discussions as a beta feature or by default can now create and move Structured Discussions boards. Structured Discussions was previously called Flow. [219]

Changes later this week

• You now get a notification when someone tries to log in to your account and fails. If they try from a device or IP address that have logged in to your account before you will be notified after five failed attempts. For security reasons you will soon get an email by default when someone tries to log in to your account and when someone logs in to your account from a new device or IP address. This can be turned off in your preferences. [220]
• Users with extremely old browsers (for example Netscape 2–4, released from 1995–1997) which do not support Unicode will no longer be able to edit. They should try to install a new browser. [221]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 26 September. It will be on non-Wikipedia wikis and some Wikipedias from 27 September. It will be on all wikis from 28 September. (calendar).

Meetings

• You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 27 September at 15:00 (UTC). See how to join.

Future changes

• The Wikimedia Foundation Readers department has proposed changing the mobile website. You can read more on mediawiki.org. This would be a big change.
• You can't use OCG to create PDFs after 1 October. This is because of technical problems. You can still create PDFs. Tech News 2017/37 said the function to create PDFs from books would still work. It is now clear it will not work for the next few months. The developers are working on fixing this. You can read more on mediawiki.org.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now use preload features in the visual editor. This means you can create links to create new pages and some text will already be in the edit window when someone clicks on it. [222]

Changes later this week

Meetings

Future changes

• A new feature called Reading Lists are coming to the Wikipedia mobile apps. First it will be in the Android version. Reading Lists are a private user preference where you can see lists of articles on multiple devices. You can give feedback on this feature. [226]
• The search function has used fallback languages for language analysis. This means a language could be analysed with the grammar of a completely unrelated language to find related words. This will be removed from most wikis the week starting with 9 October. You can read more and give feedback.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The number of active users listed by {{NUMBEROFACTIVEUSERS}} and on Special:Statistics will now only include Wikidata edits as activity on Wikidata and not on other wikis too. [227]
• Previously you could create wiki links starting with two colons. Now you need to use one colon. [[::File:X.jpg]] now has to be [[:File:X.jpg]]. There is now a new Linter category. You can see a list on Special:Linterrors/multi-colon-escape. The Linter extension helps you find technical errors in articles. You can read more about using Linter. [228]

Problems

• You will not be able to edit or upload files to Commons for around 30 minutes on 11 October. This will start at 06:00 UTC. This is because of work to let Commons show 3D models. [229]

Changes later this week

• The font in the edit window is monospace by default. Today you can change preferences to another font family or use "the browser default" instead of monospace. Switching to the browser default has only changed the font on Macs. The option to use browser default will be removed this week. [230]
• If you want to print a page or make a PDF of a page you can do so in the side menu. The way the pages look when you do this will change. You can read more on mediawiki.org.
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 10 October. It will be on non-Wikipedia wikis and some Wikipedias from 11 October. It will be on all wikis from 12 October (calendar).

Meetings

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• When you edit a template with the visual editor it follows the template's format configuration on how to save it. You can now change the format in more powerful ways if your wiki wants it. [231][232]
• The TwoColConflict extension is a new way to solve edit conflicts. It makes it easier to copy and paste the relevant text to the text field. It has been a beta feature for the last five months. You can now try out the new interface on a page where you will actually get simulated edit conflicts. You can give feedback to the developers.

Problems

• There is a problem with recent changes pages and your watchlist that show a large number of pages. Until it is fixed, Wikidata edits will not be shown on recent changes or in your watchlist on Commons or Russian Wikipedia. If necessary, Wikidata edits will be removed from all wikis. [233]
• Notifications are not working for some actions. For example some users don't get a notification when they are mentioned. The developers are working on fixing this. [234]
• Users on some wikis could not change their preferences. This has now been fixed. [235]

Changes later this week

• Editors and readers who still use Internet Explorer 8 on Windows XP will not be able to use Wikipedia from 17 October. Internet Explorer 8 on Windows XP can't connect securely to the wikis. When we allow them to do so it means that we get less security for everyone else. If you use Internet Explorer 8 on Windows XP you can install Firefox 52 ESR instead. Around 0.1% of the traffic to the Wikimedia wikis comes from Internet Explorer 8 on Windows XP. [236]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 17 October. It will be on non-Wikipedia wikis and some Wikipedias from 18 October. It will be on all wikis from 19 October (calendar).

Meetings

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can use ccnorm_contains_any when you create an abuse filter. This can be used to look for multiple words or phrases within a string. It will find words where some characters have been replaced. You can read more in the documentation. [237]

Changes later this week

• When you search in some languages the search function could use specific other languages if the first language didn't work. This is called a fallback language. This didn't work properly and created bad searches. The search index is being fixed to work better. [238]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 24 October. It will be on non-Wikipedia wikis and some Wikipedias from 25 October. It will be on all wikis from 26 October (calendar).

Meetings

Future changes

• There is a Structured Commons community focus group for Commons and Wikidata contributors who want to give input on structured data on Wikimedia Commons. You can sign up to join it. [239]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• If you use the Chrome web browser on Android you can see a download icon on the mobile website. You can download a formatted PDF. It will work in other mobile browsers in the future. [248]
• The abuse filter now has a function called get_matches. You can use it to store matches from regular expressions – one of each capturing group. You can read more in Phabricator.

Problems

• Last week's MediaWiki version didn't come to all Wikipedias because of a database crash. It will be on all wikis on 20 November. [249][250][251]

Changes later this week

• There is no new MediaWiki version this week.

Meetings

Future changes

• Language converter syntax will no longer work inside external links. Wikitext like http://-{zh-cn:foo.com; zh-hk:bar.com; zh-tw:baz.com}- must be replaced. You will have to write -{zh-cn: http://foo.com ; zh-hk: http://bar.com ; zh-tw:http://baz.com }- instead. This only affects languages with Language Converter enabled. Examples of such languages are Chinese and Serbian. This will happen next week. [252][253]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

New print to pdf feature for mobile web readers

The Readers web team will be deploying a new feature this week to make it easier to download PDF versions of articles on the mobile website.

Providing better offline functionality was one of the highlighted areas from the research done by the New Readers team in Mexico, Nigeria, and India. The teams created a prototype for mobile PDFs which was evaluated by user research and community feedback. The prototype evaluation received positive feedback and results, so development continued.

For the initial deployment, the feature will be available to Google Chrome browsers on Android. Support for other mobile browsers to come in the future. For Chrome, the feature will use the native Android print functionality. Users can choose to download a webpage as a PDF. Mobile print styles will be used for these PDFs to ensure optimal readability for smaller screens.

The feature is available starting Wednesday, Nov 15. For more information, see the project page on MediaWiki.org.

Dankon!

Saluton. Please help translate to your language. Dankon!

In July 2017, the Wikimedia Foundation announced the intention to replace Tidy with RemexHTML across the Wikimedia cluster by July 2018. In order to make this switch, a number of broken wikitext patterns were identified that required fixing on wikis, highlighted via the high priority categories in the Linter extension.

While still planning to finish turning off Tidy in July 2018, doing early switches of wikis from Tidy to Remex will let us identify any lingering issues that are not already caught by the linter categories and our QA testing. We are encouraging big wikis that have worked hard to switch sooner, for example.

Since your wiki has zero high-priority errors, we think that it is ready to switch from Tidy to Remex. To be clear, if we notice problems (or if the wiki requests it), we will revert the change, after identifying the source of the problem. If you notice any incorrect rendering, you can use ?action=parsermigration-edit to identify if the switch from Tidy actually caused it.

We are suggesting 5 December 2017 as the possible date for the switch to happen, so there would still be plenty of time to fix any issues before the holidays start. We look forward to hearing any concerns you would have with this plan, and about how we can help make this transition as smooth as possible: if you have any comments, please remember to ping me personally to make sure I notice and address them, otherwise we will assume this message is acknowledged and the deadline works for your community.

Best, mw:User:Elitre (WMF) 10:35, 28 nov. 2017 (UTC)Reply

PS: Apologies if you are seeing this message on a page that is not the best location for it: I have looked for the appropriate target pages (for example, on Meta), but may have found none. Please, by all means, move the message where you see fit, but most importantly, fix the various distribution lists by adding the correct page there, to avoid that this happens again in the future. I appreciate your understanding, and am available for further information and explanations.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Tech News

• Because of the holidays the next issue of Tech News will be sent out on 8 January 2018.

Problems

• When you import a page from another wiki the usernames of the users who edited the article on the wiki you imported it from are shown in the article history. This should link to the users on the original wiki. A script to fix this caused problems for Wikidata and German Wikipedia. It also created a large number of SUL accounts on wikis where editors had never edited. [269]
• Some bot owners got email about their bots logging in from a new computer. If this is from one or a couple of wikis, you can turn these messages off in your preferences on those wikis until the problem has been solved. If not, you can report more about the problem in Phabricator.

Changes later this week

• There is no new MediaWiki version this week. There will be no new MediaWiki version next week either.

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 19 decembro at 19:30 (UTC). See how to join.

Future changes

• Files on Commons will have structured metadata in the future. The developers are now looking for examples of different kinds of metadata to make sure they are aware of them when they build prototypes for structured data on Commons. You can read more and help by giving examples of interesting media files.
• The Structured Commons team are making sure Commons work with structured data. If you regularly contribute to Commons and Wikidata you can answer a survey that helps the team prioritise the tools that are important for the Commons and Wikidata communities. The survey ends on 22 December. You can read more on Commons. You can also help the team decide on better names for "captions" and "descriptions". This ends on 3 January 2018.
• The 2017 Community Wishlist Survey has now ended. You can see the results. They decide what the Community Tech team will work on next year.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• On Wikidata, the "konservi" button when you edit is now called "publikigi". This means all Wikimedia wikis have now changed from "Konservi paĝon" to "Publikigi la ŝanĝojn". This is to help new editors understand what it does. [270][271]
• Some edits will get an automatic tag on all wikis. This will happen when making a page a redirect, blanking a page, removing almost all content, undoing an edit, or rolling back an edit. You can see the tags for example in the recent changes feed, article history, user contributions or on your watchlist. Some wikis had already marked edits like these in other ways. [272]
• Special:UnusedFiles shows files that have been uploaded but are not used. It will show a file that is not used on the wiki it has been uploaded to, even if the file is used on another wiki. The new Special:GloballyUnusedFiles page on Commons only shows files that are not used on any wiki. [273]
• Structured discussions now uses the 2017 wikitext editor instead of its old custom one. This will work with your preference for wikitext or visual editor. The documentation has been updated. [274][275]

Problems

• Older versions of the Chrome web browser on mobile devices may see the PDF download button, but it does not work. The developers are looking into the problem. [276]
• With the new filters in the recent changes, "Ekskludi la elektitajn" in "Nomspacoj" did not work for "Konservitaj filtriloj" between 13 December and 2 January. When you loaded the saved filter all other namespaces were excluded instead. This has now been fixed. If you made any changes to your saved filters between 13 December and 2 January, you need to save your filters with excluded namespaces again. [277]
• The latest version of Google Chrome broke how section links are shown in the address bar. You now see #R%C3%A9sum%C3%A9 instead of #Résumé even if MediaWiki did not encode it that way. This happened in early December. This problem has been solved. The fix will be in Chrome 64 (23 January) or Chrome 65 (6 March). [278]
• Some POST requests to the API took longer than usual in parts of December. This affected the Wikidata UI and some gadgets the most. It has now been fixed. [279]

Changes later this week

Meetings

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Bureaucrats on Wikimedia wikis where the Translate extension is installed can now add and remove the translation administrator permission by default. Administrators of wikis where this extension is enabled can add and remove this permission to or from themselves. Wikis that used a different configuration before have not changed. [284]
• There is a new Discourse test support channel for Wikimedia developers. You can ask questions or answer others questions about MediaWiki and Wikimedia software development. [285]

Problems

• Last week's MediaWiki update was rolled back. This was because of a bug that changed non-ASCII characters when a page was edited. [286][287]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 16 January. It will be on non-Wikipedia wikis and some Wikipedias from 17 January. It will be on all wikis from 18 January (calendar).

Meetings

Future changes

• A few hundred wikis with less than ten high-priority errors in Linter categories will switch to use the Remex parsing library. This is to replace Tidy. It will happen on 31 January. Other wikis will be recommended to switch soon when they have fixed the errors that must be fixed. Tidy will be removed in the middle of 2018. [288][289]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Filters on Special:RecentChangesLinked will get the new look similar to on the recent changes page. Special:RecentChangesLinked will also get some new features. [290][291]

Problems

• With the new OOUI look menus and popups can open upwards instead of downwards. This was meant to make long dropdown menus easier to use. Sometimes these menus have been overlapped by other things. This is now fixed. [292]

Changes later this week

• There is no new MediaWiki version this week.

Meetings

• You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 24 January at 16:00 (UTC). See how to join.

Future changes

• irc.wikimedia.org will be rebooted on 22 February. Some bots use this to get the recent changes feed. They need to be able to reconnect automatically or they will not work until they have been fixed. Most bots can reconnect automatically. [293]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Bureaucrats can now add and remove the accountcreator permission by default. This means the user can help create a large number of accounts, for example for an editathon. Wikis can change this if they want to. [295]
• The Wikidata vandalism dashboard is a new tool to monitor vandalism on Wikidata labels and descriptions. It is filtered by language. [296]
• Info pages for file pages now show the file's SHA1 hash value in the table of basic information. This is so users can see that the file is the same as the one they uploaded. [297]

Problems

• Special:Export has a higher error rate right now. This means that the export does not always work. You should check to make sure your page exports worked. The developers are working on fixing this. [298]

Changes later this week

• When you review an edit made with the visual editor you can check a visual diff of your changes besides the wikitext diff. If you pick one diff type it will remember and show you that in future. The visual diff will now be the type first shown to new users. [299]
• When you use a gallery to show images you can define the size, like gallery widths="150px". You could use em or % instead of px but it would make no difference. You can now only use 150px or nothing (150). If you write something else, instead of treating it like px, it will not work. [300]
• The wording when you send a thanks message will change. Instead of Jes or Ne it will say Thank and Cancel. It will also be easier to understand that all thanks are public. [301]
• Redirects connected to Wikidata can create double Wikidata items. There will now be a tracking category for this. Wikis that don't want it can disable it. [302]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 6 February. It will be on non-Wikipedia wikis and some Wikipedias from 7 February. It will be on all wikis from 8 February (calendar).

Meetings

Future changes

• The Education Program extension will be removed on 30 June. It is replaced by the Programs and Events Dashboard. [303][304]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• TemplateStyles has been deployed to the Swedish Wikipedia. TemplateStyles is a feature to make it easy to add CSS to templates without administrator privileges. This allows for better adaptability to screen sizes, especially on mobile where are half our total page views. If your community would like to be the next to have the feature, please submit a task on Phabricator. [305][306][307]
• Registration pages now collect keyboard/mouse usage information for research on identifying spambots.

Changes later this week

• You can opt in to a new beta feature that lets you use visual diffs on history pages. [308]
• The visual editor shows and lets you edit templates in one way, and reference lists in another. This meant that templates that only contain a fake reference list, like {{reflist}}, would not get updated as you edited. Now they will update as you edit, but you will no longer be able to visually edit them as templates. [309]
• The abuse filter extension has a new feature contains_all that you may use to check if one or more strings are all contained in another given string. [310]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 13 February. It will be on non-Wikipedia wikis and some Wikipedias from 14 February. It will be on all wikis from 15 February (calendar).

Meetings

Future changes

• The settings page and beta options for the mobile website are being improved. [311]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The explanation of the abbreviations on the recent changes page could overlap with the list of changes. This has been fixed. [312][313]
• You can now see statistics for pageviews per wiki per country. You can see this on maps or in a table. [314]

Problems

• Linter is reporting estimated counts instead of actual counts for some wikis. This is because of performance problems. You might notice a false higher number in linter counts for some categories. This will be fixed as soon as the performance problem has been fixed. [315]
• Last week the way that Visual Editor displays references lists was changed. As a result, the references generated by specific templates like {{sfn}} are not visible in the references list whilst editing. [316][317]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 20 February. It will be on non-Wikipedia wikis and some Wikipedias from 21 February. It will be on all wikis from 22 February (calendar).

Meetings

Future changes

• The way edit summaries and log comments are stored in the database is being changed. In the future this will make longer comments possible. [318]
• Edit conflicts could be solved in a different way in the future. You can test a new prototype.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Checkusers and stewards can now view private data such as the IP address in the abuse log. This data is removed regularly. [319]

Problems

• Last week's MediaWiki version was rolled back because of a bug. [320][321]
• Since the deployment train last week until late evening on 20 February UTC, when you thanked someone for an edit, the thank went to the latest unthanked edit to that page. It didn't matter which edit you tried to give thanks for. This has been fixed. [322]
• Special:Statistics did not take newly created pages into account since 13 February 2018. Because of this the statistics are recreated. [323][324][325]

Changes later this week

Meetings

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

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

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 "⧼visualeditor-preference-visualdiffpage-label⧽", you will have a new option. It will give you a new box at the top of every diff page. This box will let you choose either diff system on any edit.

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

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

This screenshot shows the same edit as the wikitext diff. The visual diff highlights the removal of one word and the addition of a new sentence.

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 mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor, and improving the visual diff tool.

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

• The team will talk about editing tools at 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 <references /> 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. [331]
• 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. Dankon!

—Elitre (WMF)

Plej lastaj teknologiaj novaĵoj de la Vikimedia teknika komunumo. Bonvolu paroli al aliaj uzantoj pri ĉi tiuj ŝanĝoj. Ne ĉiuj ŝanĝoj efikos al vi. Tradukoj estas haveblaj.

Lastaj ŝanĝoj

• 3D modeloj nun povas esti elŝutita al Commons. [337]
• Paĝaj Antaŭrigardoj estis ĝisdatigita por uzi HTML por antaŭrigardoj. Tio ĉi riparis multajn aferojn. A/B testojn estis farita sur Angla kaj Germana Vikipedioj por mezuri kiel ĝi estas uzita. Aliaj ŝanĝoj estis ankaŭ faritaj. [338]
• Kelkaj redaktoj devas esti kontrolita kontraŭ tro da kondiĉoj antaŭ ili povas ekkaŭzi filtrilon de fitrakto. Se tio estas la kialo neniu filtrilo estas ekkaŭzita la redakto estos etikedita por revizio. [339]
• Auto-saving has been added to the visual editor and the 2017 wikitext editor. Right now it is meant to help if your browser crashes or if you accidentally close a tab. [340]

Problems

• The abuse filter did not tag all edits that should have been tagged after last week's MediaWiki version had come to the wikis. It was fixed on 9 March (UTC). [341]

Changes later this week

Meetings

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• On March 12 early morning UTC, the number of 503 error messages increased due to an issue on esams datacenter. It has been fixed. [348]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 20 marto. It will be on non-Wikipedia wikis and some Wikipedias from 21 marto. It will be on all wikis from 22 marto (calendar).

Meetings

Future changes

• From April 4, the autopatrol status of edits will only be accessible in the Recent Changes database table, so only for 30 days. [349][350]
• In-Context Help and Onboarding is a new project, aiming to improve retention of new wiki editors. The goal is to give them short tutorials and other training experiences based on their activity. Collaboration team is expecting feedback and comments on the project talk page, especially from people working with newcomers.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes later this week

• Some of the interface icons and text sizes will change slightly, as part of the updates for improved accessibility and consistency. These icons are used in many features, including Notifications, Recent Changes, Beta Features, Visual Editor, 2017 Wikitext Editor, Code Editor, and others. While editor toolbars, dialogs, and menus will appear slightly bigger; elements on special pages will be slightly smaller. Functionality will not change. [351] [352]
• The deprecated #toc and #toctitle CSS ids have been removed. If your wiki was still using these for fake Tables of Content (ToC) then these might lose their styling. They can be replaced with .toc and .toctitle classes where appropriate. [353]
• TemplateStyles will be deployed to the Wikivoyages on 28 March 2018. [354]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 27 March. It will be on non-Wikipedia wikis and some Wikipedias from 28 March. It will be on all wikis from 29 March (calendar).

Meetings

Future changes

• From 9 April, the sort order of categories will be distorted for a short time. We are upgrading versions of an internationalisation library (ICU) and using a maintenance script to update existing database entries. This will last anywhere from a few hours to a few days, depending on wiki size. Read more details. [355]
• Changes are coming to search for Serbian projects. Cyrillic and Latin variants of a word and different grammatical forms of a word will be able to find each other. Read more on MediaWiki in Serbian or English.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Template Wizard script available for testing. It will show up as a puzzle-piece icon in the 2010 WikiEditor. You can click on the icon to insert a template.
• The Wikimedia Communities and Contributors survey is to be sent to participants around the world this week. If you are volunteer developer, and have contributed code to any pieces of MediaWiki, gadgets, or tools, please take 20 to 40 minutes to complete the survey.

Problems

• MediaWiki deployment train has been rolled back to version 1.31.0-wmf.26 on week 13, due to a multiplication of lost connections during MySQL queries. Some of the recent changes may have not been applied. They will be deployed next week. [356][357][358]
• The Notifications badge icons were overlapping other links. This has been fixed. [359]

Changes later this week

Meetings

Future changes

• If you're using, creating or improving Lua modules, you can give your feedback to help harmonizing the modules across wikis and add more useful functions.
• On April 11th, we plan to turn off Tidy on all wikis with less than 50 entries in all high priority linter categories. About 60 wikis will have Tidy replaced. Currently about 600 wikis have had Tidy replaced and we have another 300 wikis to go. We plan to finish this transition from Tidy to RemexHtml by end of June 2018. Please follow T175706 to monitor progress of Tidy replacement. [369][370]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Some pages have templates that describe problems with that article. There is now more information for mobile readers and what is wrong with the article and how they could help fix it. [371]
• You can now thank users for many more actions than edits to a page. This was one of the top ten requests in the Wishlist Survey last year. [372]
• The sort order of categories will have errors for a short time starting Monday 9 April (UTC). We are upgrading versions of an internationalisation library (ICU) and using a script to update the database. This will take between a few hours and a few days depending on wiki size. You can read more details. [373]
• Tag filter titles will now work better on wikis where the tag filter title is in a language that is written in another direction than the language of that wiki. This could for example be an English title (written from left to right) on a Hebrew or an Arabic wiki (written from right to left). [374]

Problems

• The bookmark icon for saved filters on the recent changes page disappeared because of new icon changes. This has now been fixed. [375]
• For a week in March rollbacks got both the rollback and the undo tag on the recent changes page and other pages where you see tags. This has now been fixed. [376]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 10 April. It will be on non-Wikipedia wikis and some Wikipedias from 11 April. It will be on all wikis from 12 April (calendar).
• Patrolled edits now have three states instead of two. Recent changes filters are updated to show unpatrolled, autopatrolled and manually patrolled edits. [377]

Meetings

Future changes

• The iOS and Android apps will get synced reading lists later in April.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• All Wikipedias now have Page Previews.
• The iOS and Android apps now have synced reading lists. This means you can save articles to a private list that can be seen on your other devices if you use the apps.
• The icons in the 2010 wikitext editor have changed. [383]
• The visual editor and the 2017 wikitext ask you to write an edit summary after you press Publish. This button now also shows an ellipsis. This is to show that pressing Publish is not the last step. [384]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 24 April. It will be on non-Wikipedia wikis and some Wikipedias from 25 April. It will be on all wikis from 26 April (calendar).

Meetings

Future changes

• <mapframe> will come to most Wikipedias in May. This means that you can put interactive maps in the articles. Nine Wikipedias that use a strict version of flagged revisions will not get this feature in May. [385]
• The rollback function could change. This was a German community request. All editors with rollback rights can leave feedback on the proposed solution. The last day to leave feedback is 4 May (UTC).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The parameter for unpatrolled edits in recent changes filters changed name. You might need to update saved filters and links. [386]

Problems

• We are migrating wikis from Tidy to Remex. Because of a bug the 250 wikis which do not yet use Remex were switched on 23 April. This is two months early. This meant that pages with broken wikitext showed wrongly to readers. The bug was undone the next day. You can help fix broken wikitext to avoid this problem when your wiki switches. Tidy will be removed on all wikis before July 2018. You can follow the process on Phabricator. [387]

Changes later this week

Meetings

Future changes

• The Wikimedia Cloud Services team is working on a new project called Toolhub. The goal is to make it easier for Wikimedians to discover software tools they can use. You can leave feedback on the talk page or email jhare[[Uzanto:|]]wikimedia.org to leave private feedback.
• All wikis with fewer than 100 high-priority linter errors in all namespaces will switch to use the Remex parsing library. This is to replace Tidy. It will happen on 2 May. Other wikis will be recommended to switch soon when they have fixed the errors that must be fixed. Wikibooks wikis with fewer than 100 high-priority linter errors in the main namespace will switch on 9 May. Tidy will be removed on all wikis before July 2018. [391][392][393]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The Wikimedia Commons mobile app has a new version. It is now easier to find nearby places that need pictures. It helps you with direct uploads and title and category suggestions. The app only works on Android phones. [394]

Problems

• The abuse filters had a problem with blocks where you had changed how long they last. It used the default length everywhere. This was in late April. Abuse filter users should make sure the right block length is used and change them if needed. This is only for filters where how long blocks last had been changed. [395]

Changes later this week

• The advanced search function beta feature will be on all Wikimedia wikis. It makes it easier to use some of the special search functions that most editors don't know exist. [396]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 8 May. It will be on non-Wikipedia wikis and some Wikipedias from 9 May. It will be on all wikis from 10 May (calendar).

Meetings

Future changes

• All wikis with fewer than 100 high-priority linter errors in the main namespace will switch to use the Remex parsing library. This is to replace Tidy. It will happen on 16 May. Other wikis will switch soon when they have fixed the errors that must be fixed. Tidy will be removed on all wikis before July 2018. [397][398]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now use global preferences on most wikis. This means you can set preferences for all wikis at the same time. Before this you had to change them on each individual wiki. Global preferences will come to the Wikipedias later this week. [401][402]
• It is now easier for blocked mobile users to see why they were blocked. [403]
• Wikidata now supports lexicographical data. This helps describe words.
• There is now a checkbox on Special:ListUsers to let you see only users in temporary user groups. [404]
• Some rare invisible Unicode characters have recently been banned from page titles. This includes soft hyphens (U+00AD) and left-to-right (U+2066) and right-to-left (U+2067) isolate markers. Existing pages with these characters will soon be moved by a script. [405]
• There's a new Wikimedia Foundation team to support the Wikimedia technical communities. It's called the Technical Engagement team. Most of the team members did similar work in other teams before this. [406]

Problems

• Some translatable pages are showing old translations instead of latest ones. The cause of this issue has been fixed. We will update all pages automatically to show the latest translations. [407]

Changes later this week

Meetings

Future changes

• Content Translation drafts which have not been updated in over a year will be removed. This allows other users to translate those articles. [411]
• A survey is collecting information on what users think about how Wikimedia wiki pages are loaded. This information could be used in future development. [412]
• Some wikis will switch to use the Remex parsing library. This is to replace Tidy. It will happen on 30 May and 13 June. Wikis with fewer than 100 linter issues in the main namespace in all high-priority linter categories will switch. This includes Wikidata. Tidy will probably be removed on all wikis in the first week of July. [413][414]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The MonoBook skin has been optimised for mobile devices. It now looks different. [415]
• Planet Wikimedia collects blogs about Wikimedia. It will now use the Rawdog feed aggregator to do this instead of Planet. [416][417]
• Redirect links in Special:WhatLinksHere now link to the original page and not the target page. This was done earlier and changed the used messages on some pages. This was a problem for wikis that customized the message. A new change fixed this by using the old messages with one more parameter for customization. Wikis that already changed their customized messages will have to move the customization back again. [418]

Problems

• You will not be able to edit some wikis between 06:00 and 06:30 UTC on 13 June. You can see if your wiki is one of them.
• MassMessage did not work 24–28 May. This is also why last week's Tech News was late. [419]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 5 June. It will be on non-Wikipedia wikis and some Wikipedias from 6 June. It will be on all wikis from 7 June (calendar).

Meetings

Future changes

• The new filters for edit review tools and interface for watchlists will leave beta. This is planned to happen in June or early July. [420][421]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• In the Wikipedia app for Android or iOS users can create reading lists. The reading lists can be seen on different devices if you are logged in to your account. There is now a browser extension so you can add pages to your reading list from a web browser. At the moment it works with Firefox and Chrome. [422]
• There is a new version of Pywikibot. Pywikibot is a tool to automate tasks on MediaWiki wikis. [423]

Problems

• The MonoBook skin was changed to make it work better for mobile users. This caused some problems. The change was rolled back to fix them. The new version is now back on the wikis. MonoBook users can opt out from the new responsive design. [424]

Changes later this week

• The new filters for edit review tools and interface for watchlists will leave beta. For most wikis this will happen on 18 June. For the rest it will happen on 25 June. [425][426]

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 12 June. It will be on non-Wikipedia wikis and some Wikipedias from 13 June. It will be on all wikis from 14 June (calendar).

Meetings

Future changes

• You will be able to move local wiki files to Commons and keep their original data intact. This is planned to come to the first wikis in June.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Update on page issues on mobile web

Please help translate to your language Hi everyone. The Readers web team has recently begun working on exposing issue templates on the mobile website. Currently, details about issues with page content are generally hidden on the mobile website. This leaves readers unaware of the reliability of the pages they are reading. The goal of this project is to improve awareness of particular issues within an article on the mobile web. We will do this by changing the visual styling of page issues.

So far, we have drafted a proposal on the design and implementation of the project. We were also able to run user testing on the proposed designs. The tests so far have positive results. Here is a quick summary of what we learned:

• The new treatment increases awareness of page issues among participants. This is true particularly when they are in a more evaluative/critical mode.
• Page issues make sense to readers and they understand how they work
• Readers care about page issues and consider them important
• Readers had overwhelmingly positive sentiments towards Wikipedia associated with learning about page issues

Our next step would be to start implementing these changes. We wanted to reach out to you for any concerns, thoughts, and suggestions you might have before beginning development. Please visit the project page where we have more information and mockups of how this may look. Please leave feedback on the talk page.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• PAWS, our JupyterHub system, got an upgrade and a logo. Several bugs should be fixed.

Problems

• When a link text was in italics or had other formatting you could sometimes not edit it in the visual editor. This has now been fixed. [433][434]

Changes later this week

• Content translation users who translate between any two of Arabic, English, French, Japanese and Russian will be asked to be part of a research project. This is to create better tools for translating articles. [435]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 26 June. It will be on non-Wikipedia wikis and some Wikipedias from 27 June. It will be on all wikis from 28 June (calendar).

Meetings

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The database for tags will be changed. This will happen on 2 July on French Wikipedia and 9 July on all other wikis. Please report if recent changes get slower or you can't save edits. This could especially affect editors who use the database on ToolForge. [436]

Problems

• Last week's MediaWiki update was rolled back. This was because of a database problem. [437]

Changes later this week

• There is no new MediaWiki version this week.

Meetings

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• WebM video files have smaller file size but still be of the same quality. Creating WebM files will take longer time. [438]
• The new filters for edit review tools and interface for watchlists will leave beta. This was supposed to already have happened but was delayed. For most wikis this will happen on 9 July. For the rest it will happen on 16 July. [439]
• All wikis now use the Remex parsing library instead of Tidy. This could cause errors. You can help fix the errors. [440]

Problems

• When you rolled back an edit it could get both the Rollback and Undo tags. This has been fixed. [441]
• Rollbacks from autopatrolled users were not marked as patrolled. This has been fixed. [442]

Changes later this week

Meetings

Future changes

• Today all administrators can edit CSS and JavaScript for the entire wiki. There will be a new user group for editing CSS and JavaScript. Administrators will no longer automatically be able to do this. This is because it is a security risk when all administrator accounts can edit JavaScript even if they never plan to or do not know how it works. You can read more. [449]
• Page previews will be on by default for new accounts. [450]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

(Please help translate to your language)

Hi all,

I'm preparing a change in who can edit sitewide CSS/JS pages. (These are pages like MediaWiki:Common.css and MediaWiki:Vector.js which are executed in the browser of all readers and editors.) Currently all administrators are able to edit these pages, which poses a serious and unnecessary security risk. Soon, a dedicated, smaller user group will take over this task. Your community will be able to decide who belongs in this group, so this should mean very little change for you. You can find out more and provide feedback at the consultation page on Meta. If you are involved in maintaining CSS/JS code, or policymaking around adminship requests, please give it a look!

Thanks!
Tgr (talk) 08:45, 12 jul. 2018 (UTC) (via global message delivery)Reply

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now use global preferences on Wikimedia wikis. You can set them on the global preferences page. [451]
• You can now see a new log of pages being created at Special:Log/create. It includes pages which are later deleted. It is now available on all Wikimedia wikis except Commons and Wikidata. [452]
• You can see how many pageviews a wiki had from specific countries. The Wikistats2 maps have now been updated. [453]

Changes later this week

• Your watchlist will show changes from the last seven days instead of three. If you have already set a length preference it will not change. [454]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from July 17. It will be on non-Wikipedia wikis and some Wikipedias from July 18. It will be on all wikis from July 19 (calendar).

Meetings

Future changes

• Some articles have messages to readers about problems with the article. For example that it does not cite sources or might not be neutral. Readers do not see these messages on the mobile version. The developers now want to show them. You can read more and leave feedback.
• You can use <inputbox> to create search boxes for specific pages. For example to search the archives of a community discussion page. Instead of prefix:Page name you will see a text that explains which pages are being searched. You can read more and leave feedback.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Plej lastaj teĥnikaj novaĵoj de la Vikimedia teknika komunumo. Bonvolu diri al aliaj uzantoj pri tiuj ŝanĝoj. Ne ĉiuj ŝanĝoj influos vin. Tradukoj estas haveblaj.

Lastaj ŝanĝoj

• Kiam vi ensalutas al via konto vi povas elekti resti ensalutita. Tiu opciilo nun efikas plibone ol antaŭ ĉe portebla versio por uzantoj sen Ĝavoskripto. [455]
• Vikioj kiuj uzas Citoido, aŭtomate povas produkti citaĵojn por svedaj sciigaj retejoj. Tio nur efikas per la vida redaktilo. Tio nun efikas por radio de sveda publika servo. Pli da eblecoj okazos. Aliuloj povus uzi tion por aldoni sciigajn retejojn en aliaj lingvoj en la estonteco. [456]
• Kontribuuloj povas fari maksimume po 90 redaktojn por minuto. Tio estas nova ekde lasta monato. [457]

Ŝanĝoj poste ĉi tiu semajno

• La nova versio de Mediavikio estos ĉe testaj vikioj kaj mediawiki.org ekde 24 julio. Ĝi estos ĉe ne-Vikipediaj vikioj kaj kelkaj Vikipediaj ekde 25 julio. Ĝi estos ĉe ĉiuj vikioj ekde 26 julio (kalendaro).

Kunvenoj

$Technews preparita fare de verkistoj de Teĥnikaj novaĵoj kaj poŝtita per bot • Kontribuu • Traduku • Akiru helpon • Provizu retrosciigon • Abonu aŭ malabonu.

(Please help translate to your language)

Hi all!

To improve the security of our readers and editors, permission handling for CSS/JS pages has changed. (These are pages like MediaWiki:Common.css and MediaWiki:Vector.js which contain code that is executed in the browsers of users of the site.) A new user group, interface-admin, has been created. Starting four weeks from now, only members of this group will be able edit CSS/JS pages that they do not own (that is, any page ending with .css or .js that is either in the MediaWiki: namespace or is another user's user subpage).

You can learn more about the motivation behind the change here.

Please add users who need to edit CSS/JS to the new group (this can be done the same way new administrators are added, by stewards or local bureaucrats). This is a dangerous permission; a malicious user or a hacker taking over the account of a careless interface-admin can abuse it in far worse ways than admin permissions could be abused. Please only assign it to users who need it, who are trusted by the community, and who follow common basic password and computer security practices (use strong passwords, do not reuse passwords, use two-factor authentication if possible, do not install software of questionable origin on your machine, use antivirus software if that's a standard thing in your environment).

Thanks!
Tgr (talk) 13:08, 30 jul. 2018 (UTC) (via global message delivery)Reply

Hi all,

as announced previously, permission handling for CSS/JS pages has changed: only members of the interface-admin (Interfacaj administrantoj) group, and a few highly privileged global groups such as stewards, can edit CSS/JS pages that they do not own (that is, any page ending with .css or .js that is either in the MediaWiki: namespace or is another user's user subpage). This is done to improve the security of readers and editors of Wikimedia projects. More information is available at Creation of separate user group for editing sitewide CSS/JS. If you encounter any unexpected problems, please contact me or file a bug.

Thanks!
Tgr (talk) 12:39, 27 aŭg. 2018 (UTC) (via global message delivery)Reply

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now see moved paragraphs in diffs in the mobile view. It also works on all languages in the desktop view. [469]
• Bureaucrats on all Wikimedia wikis can now remove the interface admin user right. [470]

Problems

• Some diffs show lines in the wrong order. The developers are working on fixing it. [471]

Changes later this week

Meetings

Future changes

• Because of a data centre test you will be able to read but not edit the wikis for up to an hour on 12 September and 10 October. This will start at 14:00 (UTC). You might lose edits if you try to save during this time. The time when you can't edit might be shorter than an hour. You can read more about this.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• There is a new user right for users who can edit CSS and JavaScript for the entire wiki. Before this all admins could edit CSS and JavaScript. This was a security risk. This group is called interface administrators. Administrators can delete user CSS and JavaScript pages. [476][477]
• There will be an A/B test on the Wikipedia mobile website. It starts this week. It tests how we show templates that show information about an article. The test will last two weeks. [478][479]
• You can now use different CSS rules for different skins when you edit templates. This is because of TemplateStyles. [480]
• wp10 in ORES is now called articlequality. [481]
• When you get a new message on your talk page you get a yellow message in the toolbar. The preference to show or not show this has been removed. [482]

Problems

• UploadWizard had problems with campaigns. Users could not upload files. This has now been fixed. [483]
• You can get a notification when a link is made to a page you created. This has not worked since June. It was fixed last week. [484]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 4 September. It will be on non-Wikipedia wikis and some Wikipedias from 5 September. It will be on all wikis from 6 September (calendar).

Meetings

Future changes

• The Wikimedia Foundation Readers department will work on advanced mobile editing. You can read more about this and other things they plan to work on over the next year. You can also see the presentation.
• The RelatedSites extension will be removed from Wikivoyage.
• Unused projects on the Wikimedia Cloud virtual private server will be removed. This will happen in October. Projects can be marked if they are being used. [485]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Read this message in another language • Please help translate to your language

The Wikimedia Foundation will be testing its secondary data centre. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.

They will switch all traffic to the secondary data center on Wednesday, 12 September 2018. On Wednesday, 10 October 2018, they will switch back to the primary data center.

Unfortunately, because of some limitations in MediaWiki, all editing must stop when we switch. We apologize for this disruption, and we are working to minimize it in the future.

You will be able to read, but not edit, all wikis for a short period of time.

• You will not be able to edit for up to an hour on Wednesday, 12 September and Wednesday, 10 October. The test will start at 14:00 UTC (15:00 BST, 16:00 CEST, 10:00 EDT, 07:00 PDT, 23:00 JST, and in New Zealand at 02:00 NZST on Thursday 13 September and Thursday 11 October).
• If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.

Other effects:

• Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
• There will be code freezes for the weeks of 10 September 2018 and 8 October 2018. Non-essential code deployments will not happen.

This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule. There will be more notifications about this. Please share this information with your community. /User:Johan(WMF) (talk)

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• When you added or edited a template with the visual editor the input boxes were very big. This has been fixed. The input boxes will now be smaller until you click on them. Then they will change size to fit the text. [486]

Problems

• Some diffs showed lines in the wrong order. This was fixed last week. [487]
• Marking a cross-wiki notification as read didn't work every time. The other wiki was not updated. This has now been fixed. [488]
• <maplink> did not work for a few days. This was because of a bug. This has now been fixed. [489]
• {{subst:REVISIONUSER}} is used by some templates. For a period edits saved with {{subst:REVISIONUSER}} would save the previous user's name and not your username. This is now fixed. Edits made before the bug was fixed will still be wrong and need to be corrected. [490]
• When you move a page the title still shows the old page name. The developers are working on fixing this. [491]

Changes later this week

• Because of a data centre test you will be able to read but not edit the wikis for up to an hour on 12 September and 10 October. This will start at 14:00 (UTC). You might lose edits if you try to save during this time. The time when you can't edit might be shorter than an hour. You can read more about this.
• Because of the data centre test there will be no new version of MediaWiki this week. Changes for this week will come next week instead.

Meetings

Future changes

• The developers work on making the wikis work better on mobile phones. There is a list of common problems when making content easier to read in the mobile view. You can add things to the page and ask others to help.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The Wikimedia Commons mobile app has a new version. Images uploaded using Nearby are now automatically added to the associated Wikidata item. You can browse other images on Commons. You can see your achievements and your upload statistics. It has also fixed some bugs. [492]
• MediaWiki web requests now have a time limit of 60 seconds for GET requests and 200 seconds for POST requests. [493]

Problems

• You could not see the menu on the notifications page on the mobile version. This has now been fixed. [494]

Changes later this week

• Special:AncientPages can hide disambiguation pages. [495]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 18 September. It will be on non-Wikipedia wikis and some Wikipedias from 19 September. It will be on all wikis from 20 September (calendar).

Meetings

Future changes

• The developers are testing new mobile web navigation. You can use it and give feedback.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Ordinary pages can no longer be loaded as javascript. You could do this using ?action=raw&ctype=text/javascript in the URL. Only fully protected pages in the MediaWiki: namespace or user javascript subpages can be loaded as javascript now. This is for better security. [497][498]

Problems

• New and updated translations from will not reach the wikis for a while. You can still translate messages on translatewiki.net. The Wikimedia wikis will be updated with the new translations later. This is because of work on the translation system. [499][500]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 2 October. It will be on non-Wikipedia wikis and some Wikipedias from 3 October. It will be on all wikis from 4 October (calendar).

Meetings

Future changes

• Because of a data centre test you will be able to read but not edit the wikis for up to an hour on 10 October. This will start at 14:00 (UTC). You might lose edits if you try to save during this time. The time when you can't edit might be shorter than an hour. You can read more about this.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• Some pages, edits and users disappeared for a short while after the server switch. Missing content and users was fixed within a day. Some preferences and other things might take a few more days to fix. [503]
• Wikis are updated with new and updated translations from translatewiki.net again. This will happen once a week. The developers are working on fixing the problem so we can have translation updates more often again. [504]

Changes later this week

• When you create an abuse filter that prevents edits you can now write a specific error message for it. Before this all abuse filters that prevented edits had the same error message. [505]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 16 October. It will be on non-Wikipedia wikis and some Wikipedias from 17 October. It will be on all wikis from 18 October (calendar).

Meetings

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can post proposals for the Community Wishlist Survey. The survey decides what the Community Tech team will work on. You can post proposals until 11 November. You can vote on proposals from 16 November to 30 November.
• The wikis now have a content security policy report. This means that you might get a warning in your javascript console when you load external resources in your user scripts. For security reasons it is recommended that you don't do this. It might not be possible to load external resources in your scripts in the future. [507]

Problems

• Your watchlist can show which changes you have already seen. This did not work for a few days. It has been fixed. [508]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 30 October. It will be on non-Wikipedia wikis and some Wikipedias from 31 October. It will be on all wikis from 1 November (calendar).
• The 2006 wikitext editor is no longer available. It will be removed from Special:Preferences. It has not been the standard editor for a long time. It was replaced by the 2010 wikitext editor. [509][510]

Meetings

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

La enketo pri komunuma deziraro.

Saluton ĉiu,

La enketo pri komunuma deziraro estas la procedo dum kiam la Vikimedia komunumoj decidas pri kio la teamo de komunuma teĥnologio de Vikimedia Fundaĵo devus labori dum la sekvanta jaro.

La teamo de komunuma teĥnologio zorgas pri iloj por sperta Vikimediaj redaktuloj. Vi povas poŝti teknikajn proponojn de nun ĝis la 11a novembro. La komunumoj voĉdonos al la proponoj inter 16a novembro kaj 30a novembro. Vi povas legi pli pri la paĝo pri dezirara enketo.

/User:Johan (WMF)

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

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.

• 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. [511]

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

—Whatamidoing (WMF) (talk)

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now use TemplateWizard to edit templates. This works only with the 2010 wikitext editor and not in the visual editor or the 2017 wikitext editor. If you click on you can enter the information in a pop-up. You can turn on TemplateWizard in your beta feature preferences. [512]

Changes later this week

• You can choose to see edit conflicts in a two-column view. This is a beta feature. You can find it in your preferences. The interface for the two-column edit conflict will change. You can read more.
• When you edit with the visual editor you can use the "Automatic" citation tab. This helps you generate citations. You will now be able to write plain text citations or the title of a journal article or a book in this tab. This will search the Crossref and WorldCat databases and add the top result. [513]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 6 November. It will be on non-Wikipedia wikis and some Wikipedias from 7 November. It will be on all wikis from 8 November (calendar).

Meetings

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Some old mobile browsers can use the watchlist again. This has not worked for a while. These browsers are called grade C browsers. This helps for example Windows Phone 8.1 with Internet Explorer and Lumia 535 with Windows 10. [514]

Problems

• You can choose to see edit conflicts in a two-column view. This is a beta feature. You can find it in your preferences. Users who use this view saw the edit conflict resolution page when they wanted to see a preview. This has been fixed. [515][516][517]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 13 November. It will be on non-Wikipedia wikis and some Wikipedias from 14 November. It will be on all wikis from 15 November (calendar).

Meetings

Future changes

• You can use the content translation tool to translate articles. The developers are working on a new version. One of the changes will be a maintenance category. Articles where users add a lot of text from machine translation without changing it will be in that category. This is so the community can review it. The users will also have been warned before they publish the article that it has a lot of unchanged text from machine translations. [518]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Change coming to how certain templates will appear on the mobile web

Please help translate to your language

Hello,

In a few weeks the Readers web team will be changing how some templates look on the mobile web site. We will make these templates more noticeable when viewing the article. We ask for your help in updating any templates that don't look correct.

What kind of templates? Specifically templates that notify readers and contributors about issues with the content of an article – the text and information in the article. Examples like Template:Unreferenced or Template:More citations needed. Right now these notifications are hidden behind a link under the title of an article. We will format templates like these (mostly those that use Template:Ambox or message box templates in general) to show a short summary under the page title. You can tap on the "Learn more" link to get more information.

For template editors we have some recommendations on how to make templates that are mobile-friendly and also further documentation on our work so far.

If you have questions about formatting templates for mobile, please leave a note on the project talk page or file a task in Phabricator and we will help you.

Dankon!

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can vote on proposals in the Community Wishlist Survey. The survey decides what the Community Tech team will work on. You can vote until 30 November.
• There is an A/B test for sameAs data. This is to make it easier to find the right information with a search engine. This changes the metadata for a wiki page. It doesn't change how the page looks. [519]

Changes later this week

• There is no new MediaWiki version this week.

Meetings

Future changes

• The Wikimedia wikis use templates to show readers there are problems with the content on some pages. For example if there are no sources or the page needs to be rewritten. The mobile website will soon show more information when you use these templates. Some templates may need to be updated. [520]
• The Education Program extension was removed from all Wikimedia projects. The database tables used by the extension will be archived. This will happen in a month. If you want the information on your wiki you should move it to a normal wiki page. [521]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

The Community Wishlist Survey. Please help translate to your language.

Hey everyone,

The Community Wishlist Survey is the process when the Wikimedia communities decide what the Wikimedia Foundation Community Tech should work on over the next year.

The Community Tech team is focused on tools for experienced Wikimedia editors. The communities have now posted a long list of technical proposals. You can vote on the proposals from now until 30 November. You can read more on the wishlist survey page.

/User:Johan (WMF)

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• On wikis with translatable pages you could create a mess when you moved a page that had translatable subpages. A subpage is when you use / to create a new page: /wiki/Page/Subpage. The subpages would be moved but not the translations. The subpages are no longer automatically be moved. This is to make it safer to move pages. [522]

Changes later this week

• The advanced search interface will be available by default on all Wikimedia wikis. It makes it easier to use some of the special search functions that most editors don't know exist. It's already active on German, Farsi, Arabic and Hungarian Wikipedia. [523]
• Special:UnusedCategories show empty categories with no files or other categories. You can soon choose to not show soft redirect categories or some maintenance categories there. You can do this with the magic word __EXPECTUNUSEDCATEGORY__. [524]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 27 November. It will be on non-Wikipedia wikis and some Wikipedias from 28 November. It will be on all wikis from 29 November (calendar).

Meetings

Future changes

• The mw.util.jsMessage() function was deprecated in 2012. It will be removed next week. Look for the warning Use of "mw.util.jsMessage" is deprecated in the JavaScript console to know if you use an affected script or gadget. If you are a gadget maintainer you should check if your JavaScript code contains mw.util.jsMessage. There is a migration guide. It explains how to use mw.notify instead. [525]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Admins will not be able to unblock themselves if they are blocked by someone other than themselves. This is because it can cause damage if someone else takes over an admin account and other admins can't block them. If this is a problem for your community you can report it on Phabricator. You can also ask questions on Meta. There is a discussion on Phabricator about how to solve this if two admins fight with each other on a small wiki. [526]
• Small SVG images are now bigger when you see them in MediaViewer. [527]
• You can go to a section from the edit summary by clicking on the section name. Before this you had to click on the arrow. [528]
• When you jumped to a footnote that was referenced several times in an article it could be difficult to see where you were in the text. Now there are jump marks and highlights to help you find your way back. [529][530]

Changes later this week

• There is no new MediaWiki version this week.

Meetings

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Please help translate to your language

The Wikimedia Foundation security team is implementing a new password policy and requirements. You can learn more about the project on MediaWiki.org.

These new requirements will apply to new accounts and privileged accounts. New accounts will be required to create a password with a minimum length of 8 characters. Privileged accounts will be prompted to update their password to one that is at least 10 characters in length.

These changes are planned to be in effect on December 13th. If you think your work or tools will be affected by this change, please let us know on the talk page.

Dankon!

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 11 December. It will be on non-Wikipedia wikis and some Wikipedias from 12 December. It will be on all wikis from 13 December (calendar).

Meetings

Future changes

• New accounts will need passwords that are at least 8 characters long. Admins, interface admins, bureaucrats, oversighters, CentralNotice admins, global renamers, check users, stewards and some other user groups will need passwords that are at least 10 characters long. This is because an attacker could cause damage to the wikis if they took over these accounts. [531][532]
• When you hover over a footnote it will show you the reference as a pop-up. This is so you don't have to jump down to the bottom of the page to see a reference. This will happen in 2019. Some wikis already have gadgets that do this. You will be able to turn it off. [533]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Tech News

• Because of the holidays the next issue of Tech News will be sent out on 7 January 2019.

Recent changes

• Some templates that show notices about the content of the page will now be shown on the mobile website. In many cases they were hidden before. [534][535]
• Admins can no longer unblock themselves, except for self-blocks. A blocked admin can block the user who blocked them but no one else. This is so no one can block all admins on a wiki without being stopped. [536]
• The ParserMigration extension has been removed. It compared the result of two versions of the MediaWiki wikitext parsing pipeline. It was used when we moved to the Remex parsing library instead of Tidy.

Problems

• <ref> tags can use parameters such as "name" or "group". For example <ref name="adams" group="books">. If a <ref> tag has more than two parameters all parameters are ignored. You don't get a warning that they don't work. This will soon be fixed. [537]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 18 December. It will be on non-Wikipedia wikis and some Wikipedias from 19 December. It will be on all wikis from 20 December (calendar).

Meetings

Future changes

• The Wikimedia Foundation Android app team are working on making it easier to edit on mobile phones. You can read more about these plans. If you have an Android phone and speak at least two languages you can help testing in English. Tell Dchen (WMF) you want to be part of the testing by writing on her talk page or email her.
• tiles.wmflabs.org and wma.wmflabs.org will stop working. They have no maintainers and run an old operating system. Tools which use it could stop working. This includes the mapnik gadget, hill shading, and hike and bike layers. New maintainers could help out and keep it going. [538]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

Please help translate to your language

Love is an important subject for humanity and it is expressed in different cultures and regions in different ways across the world through different gestures, ceremonies, festivals and to document expression of this rich and beautiful emotion, we need your help so we can share and spread the depth of cultures that each region has, the best of how people of that region, celebrate love.

Wiki Loves Love (WLL) is an international photography competition of Wikimedia Commons with the subject love testimonials happening in the month of February.

The primary goal of the competition is to document love testimonials through human cultural diversity such as monuments, ceremonies, snapshot of tender gesture, and miscellaneous objects used as symbol of love; to illustrate articles in the worldwide free encyclopedia Wikipedia, and other Wikimedia Foundation (WMF) projects.

The theme of 2019 iteration is Celebrations, Festivals, Ceremonies and rituals of love.

Sign up your affiliate or individually at Participants page.

To know more about the contest, check out our Commons Page and FAQs

There are several prizes to grab. Hope to see you spreading love this February with Wiki Loves Love!

Kind regards,

Wiki Loves Love Team

Imagine... the sum of all love!

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Tech News writers, editors and translators wish you a pleasant 2019 year.

Recent changes

Problems

• In AbuseFilter, the "Trafik-limigilo" action takes three parameters: count, period and groups. They must now strictly respect the requirements listed on mediawiki.org. A list of broken filters is on Phabricator. If you're familiar with AbuseFilter, please take a look and fix them. [542]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from January 8. It will be on non-Wikipedia wikis and some Wikipedias from January 9. It will be on all wikis from January 10 (calendar).

Meetings

• Search Platform Office Hours is rescheduled to January 9. Check the details for time and date.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

A new beta feature will soon be released on all wikis: The FileExporter. It allows exports of files from a local wiki to Wikimedia Commons, including their file history and page history. Which files can be exported is defined by each wiki's community: Please check your wiki's configuration file if you want to use this feature.

The FileExporter has already been a beta feature on mediawiki.org, meta.wikimedia, deWP, faWP, arWP, koWP and on wikisource.org. After some functionality was added, it's now becoming a beta feature on all wikis. Deployment is planned for January 16. More information can be found on the project page.

As always, feedback is highly appreciated. If you want to test the FileExporter, please activate it in your user preferences. The best place for feedback is the central talk page. Thank you from Wikimedia Deutschland's Technical Wishes project.