User talk:Quiddity (WMF)

Welcome to Wikimedia Commons, Quiddity (WMF)!

First steps tutorial Our first steps tour and our frequently asked questions will help you a lot after registration. They explain how to customize the interface (for example the language), how to upload files and our basic licensing policy (Wikimedia Commons only accepts free content). You don't need technical skills in order to contribute here. Be bold when contributing and assume good faith when interacting with others. This is a wiki. Getting help More information is available at the community portal. You may ask questions at the help desk, village pump or on IRC channel #wikimedia-commons (webchat). You can also contact an administrator on their talk page. If you have a specific copyright question, ask at the copyright village pump.

Goodies, tips, and tricks Put Babel boxes on your user page so others know what languages you can speak and indicate your graphic abilities. You can find the files you have uploaded in your Uploads. Please sign your name on Talk pages by typing ~~~~. To link to an image page without embedding the image, type: [[:File:Foo.jpg]], which produces: File:Foo.jpg. You may enable gadgets (custom features) for your account. There are several tools to upload files. Have you edited Wikipedia before? This guide might be useful. Made a mistake? Do you want to have a file renamed or moved? Use the move link and wait for an authorized user to rename it. Do you want to have your recently uploaded picture removed? Tag it as {{speedy|reason here}}. For more information read the deletion guidelines.

-- Wikimedia Commons Welcome (talk) 20:34, 27 September 2013 (UTC)

Rights

Hi, I added autopatroller, patroller, and rollbacker to your rights here. No need to revew your posts, ;o) Yann (talk) 21:56, 11 August 2015 (UTC)

Thanks for that, and the comment at the Village Pump. :) Quiddity (WMF) (talk) 22:07, 11 August 2015 (UTC)

Tech News: 2016-13

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

• MediaWiki now supports the semantic web standards of Microdata and RDFa 1.0. On Wikimedia projects, a configuration change must be requested in order to enable RDFa 1.0. [1] [2]

Problems

• Adding references with Citoid was broken for approximately 6 hours on 24 March. This was fixed. [3]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 29 March. It will be on non-Wikipedia wikis and some Wikipedias from 30 March. It will be on all wikis from 31 March (calendar).
• You will be able to remove the header and footer style from User language (babel) boxes. This will make it easier to use them with other userboxes. [4]

Meetings

• You can join the next meeting with part of the Architecture committee, which will discuss a few topics. The meeting will be on 30 March at 21:00 (UTC). See how to join.
• The Architecture committee has sent a summary of new and ongoing RFC discussions.

Future changes

• Commons will soon have improved access to Wikidata's data. It will then be possible to access data about any concept on any page on Commons. Assistance with testing this on the beta cluster is appreciated. [5]
• Wikibits.js will not be loaded by default anymore starting April 2016. Gadget and script authors should have already updated their code since the previous announcements, but there is another migration path available if needed. See wikitech-l for details.

Corrections

• Last week Tech News said the new MediaWiki version would come to wikis from 21 March to 23 March. The right dates were 22 March to 24 March.

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

19:37, 28 March 2016 (UTC)

Tech News: 2016-23

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

• MathML/SVG is now the default <math> rendering mode on Wikimedia projects. [6][7]

Changes this week

• The history page can tell you if a page on your watchlist was updated since you last visited it. This now works the same way in Vector as in other skins. The change broke local designs on some wikis. This will be fixed this week. [8]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 7 June. It will be on non-Wikipedia wikis and some Wikipedias from 8 June. It will be on all wikis from 9 June (calendar).

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

20:43, 6 June 2016 (UTC)

Tech News: 2016-29

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

• Due to the rollback, new sorting of Notifications on the Fly-Out Menus has been deployed with a delay. [9]
• Due to the rollback, the daily special patch deployment process has been changed. [10]
• In notifications, "Messages" are now called "Notices". [11]

Problems

• On July 12 all wikis were rolled back to MediaWiki 1.28.0-wmf.8 due to a problem in the log-in system. [12][13]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 19 July. It will be on non-Wikipedia wikis and some Wikipedias from 20 July. It will be on all wikis from 21 July (calendar).
• Special:Log now has a help link. [14]
• The RevisionSlider can be tested on the beta cluster. From 22 July, it will be available as a beta feature at: German Wikipedia, Arabic Wikipedia, Hebrew Wikipedia. [15][16][17]

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 19 July at 19:00 (UTC). See how to join.
• You can join the next meeting with the Architecture committee. The topic this week is "Devise plan for a cross-wiki watchlist back-end". The meeting will be on 20 July at 21:00 (UTC). See how to join. [18]

Future changes

• User scripts and bots can no longer use http:// to edit wiki pages. [19][20]
• Gerrit is going to be updated. Developers are invited to test it. [21]

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

20:13, 18 July 2016 (UTC)

Test announcement

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 "Automatically enable most beta features".

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.

James Forrester (Product Manager, Editing department, Wikimedia Foundation) 19:23, 14 December 2016 (UTC)

Tech News: 2016-51

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 9 January 2017.
• The writers of the technical newsletter are asking for your opinion. Did you get the information you wanted this year? Did we miss important technical news in 2016? What kind of information was too late? Please tell us! You can write in your language. Thank you!

Recent changes

• Administrators and translation administrators can now use Special:PageLanguage on wikis with the Translate extension. This means you can say what language a page is in. The Translate extension will use that language as the source language when you translate. Previously this was always the wiki's default language. This was usually English. [22]
• Wikis connected to Wikidata can now use the parser function {{#statements: }} to get formatted data. You can also use {{#property: }} to get raw data. You can see the difference between the two statements. There are also similar new functions in Lua. [23]

Problems

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

Changes this week

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

Meetings

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

Future changes

• The 2016 Community Wishlist Survey is done. It decides what the Community Tech team will work on during 2017. You can see the results.

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

20:22, 19 December 2016 (UTC)

Notification

Hello, This message is being sent to inform you that the following consensus has been archived at COM:VP/P:

• Proposal: Enable beta function of Flow on own talk page
• Outcome: No consensus

This is in relation to an issue with which you may have been involved. Regards, --Steinsplitter (talk) 14:59, 12 April 2017 (UTC)

Deploying the Phonos in-line audio player to your Wiki

Hello!

Apologies as this message is not in your language, ⧼Please help translate⧽ to your language.

As part of fulfilling a wishlist proposal of providing audio links that play on click, this wiki will soon be able to use the inline audio player implemented by Phonos.

With the inline audio player, you can add text-to-speech audio snippets to wiki pages by simply using a tag: <phonos file="audio file" label="Listen"/> The above tag will render the text to a speaker, and clicking on it plays the audio instantly without taking you to another page. A common example where you can use this feature is in adding pronunciation to words as illustrated on the English Wiktionary below.

{{audio|en|En-uk-English.oga|Audio (UK)}}

Could become:

<phonos file="En-uk-English.oga" label="Audio (UK)"/>

The inline audio player will be available in your wiki in the coming weeks; in the meantime, we would like you to read about it and give us feedback or ask questions about it in this talk page.

Thank you!

UOzurumba (WMF) (talk On behalf of the WMF Language team.

Deploying the Phonos in-line audio player to your Wiki

Hello!

Apologies if this message is not in your language, ⧼Please help translate⧽ to your language.

This wiki will soon be able to use the inline audio player implemented by the Phonos extension. This is part of fulfilling a wishlist proposal of providing audio links that play on click.

With the inline audio player, you can add text-to-speech audio snippets to wiki pages by simply using a tag:

<phonos file="audio file" label="Listen"/>

The above tag will show the text next to a speaker icon, and clicking on it will play the audio instantly without taking you to another page. A common example where you can use this feature is in adding pronunciation to words as illustrated on the English Wiktionary below.

{{audio|en|En-uk-English.oga|Audio (UK)}}

Could become:

<phonos file="En-uk-English.oga" label="Audio (UK)"/>

The inline audio player will be available in your wiki in 2 weeks time; in the meantime, we would like you to read about the features and give us feedback or ask questions about it in this talk page.

Thank you!

UOzurumba (WMF), on behalf of the Foundation's Language team

02:12, 27 July 2023 (UTC)

Plans to enable Content and Section Translation tool in your Wikipedia

Hello Friends!

Apologies as this message is not in your native language, Please help translate to your language.

The WMF Language team is pleased to let you know that we would like to enable the Section and Content translation tool in this Wikipedia. For this, our team will love you to read about the tool and test the Section Translation tool so you can:

• Give us your feedback
• Ask us questions
• Tell us know how to improve it

Below is background information about the tools and how you can test the Section translation tool.

Background information

Content Translation has been a successful tool for editors to create content in their language. More than one million articles have been created across all languages since the tool was released in 2015. However, the tool is not out of beta in this Wikipedia, limiting the discoverability of the tool and its use and blocking the enablement of the Section translation in your Wikipedia.

Section Translation extends the capabilities of Content Translation to support mobile devices. On mobile, the tool will:

• Guide you to translate one section at a time in order to expand existing articles or create new ones
• Make it easy to transfer knowledge across languages anytime from your mobile device

We plan to enable the tools in the next 2 weeks if there are no objections from your community. After it is enabled, we’ll monitor the content created with the tools and process all the feedback. In any case, feel free to raise any concerns or questions you may already have as a reply to this message or on the project talk page.

Try the Section translation tool

Before the enablement, you can try the current implementation of the tool in our testing instance. Once it is enabled, you’ll have access to https://wikipedia.org/wiki/Special:ContentTranslation with your mobile device. You can select an article to translate, and machine translation will be provided as a starting point for editors to improve.

Provide feedback

Please provide feedback about Section translation on the project talk page. We want to hear about your impressions on

• The section translation tool
• What do you think about our plans to enable it
• Your ideas for improving the tool

Thanks and we look forward to your feedback and questions.

UOzurumba (WMF) (talk) 01:43, 2 November 2023 (UTC) On behalf of the WMF Language team.