विकिपीडिया:तन्त्रांशसभा

TNएषः समुदायः/सदस्यः टेक-वार्ताः इतः परं प्राप्स्यति ।

Time to bring embedded maps (‘mapframe’) to most Wikipedias

Time to bring embedded maps (‘mapframe’) to most Wikipedias

कृपया अपनी भाषा में अनुवादित करने में सहायता करें

Mapframe is a feature that enables users to easily display interactive maps right on wiki pages. Currently, most Wikipedias don’t have mapframe. But fifteen Wikipedias, along with all the other Wikimedia projects, are using mapframe today to display maps on thousands of pages.

A little background: over the last few months, the Foundation’s Collaboration team has been working to improve the stability and user experience of the maps service. In addition, a question about long-term support for the maps service was recently settled, and a small team has been assigned for routine maintenance. Given these developments, bringing the benefits of mapframe to Wikipedias that lack the feature seems both safe and supportable. Nine Wikipedias that use a stricter version of Flagged Revisions will not get mapframe in this release.

Maps are a valuable form of visual data that can improve readers’ understanding across a wide range of topics. If you know of any reasons why mapframe shouldn’t be implemented on your Wikipedia, let us know on the project talk page. Unless we hear from you, we plan to release mapframe to most Wikipedias in May, 2018. So, if you foresee an issue, please let us hear from you. Otherwise, happy mapping!

CKoerner (WMF) (talk) २१:३८, २४ अप्रैल २०१८ (UTC)

Wikitext highlighting out of beta

Wikitext syntax highlighting, also known as CodeMirror, has been moved out of Beta Features and is available in the 2017 Wikitext Editor on all wikis. Syntax highlighting helps you see problems in your wikitext before previewing or publishing text. Please try out the tool if you did not do so while it was being developed, and feedback is welcome. - Keegan (WMF) (talk)

१८:५५, ४ मई २०१८ (UTC)

Improvements coming soon on Watchlists

Hello

Sorry to use English. कृपया अपनी भाषा में अनुवादित करने में सहायता करें! धन्यवाद।

In short: starting on June 18, New Filters for Edit Review (now in Beta) will become standard on Watchlists. They provide an array of new tools and an improved interface. If you prefer the current page you will be able to opt out. Learn more about the New Filters.

What is this feature again?

This feature is used by default on Special:RecentChanges, Special:RecentChangesLinked and as a Beta feature on Special:Watchlist.

Based on a new design, that feature adds new functions to those pages, to ease vandalism tracking and support of newcomers:

• Filtering - filter recent changes with easy-to-use and powerful filters combinations, including filtering by namespace or tagged edits.
• Highlighting - add a colored background to the different changes you are monitoring. It helps quick identification of changes that matter to you.
• Bookmarking to keep your favorite configurations of filters ready to be used.
• Quality and Intent Filters - those filters use ORES predictions. They identify real vandalism or good faith intent contributions that need help. They are not available on all wikis.

You can know more about this project by visiting the quick tour help page.

About the release on Watchlists

Over 70,000 people have activated the New Filters beta, which has been in testing on Watchlist for more than eight months. We feel confident that the features are stable and effective, but if you have thoughts about these tools or the beta graduation, please let us know on the project talk page. In particular, tell us if you know of a special incompatibility or other issue that makes the New Filters problematic on your wiki. We’ll examine the blocker and may delay release on your wiki until the issue can be addressed.

The deployment will start on June 18 or on June 25, depending on the wiki (check the list). After the deployment, you will also be able to opt-out this change directly from the Watchlist page and also in your preferences.

How to be ready?

Please share this announcement!

If you use local Gadgets that change things on your Watchlist pages, or have a customized scripts or CSS, be ready. You may have to make some changes to your configuration. Despite the fact that we have tried to take most cases into consideration, some configurations may break. The Beta phase is a great opportunity to have a look at local scripts and gadgets: some of them may be replaced by native features from the Beta feature.

Please share your questions and comments on the feedback page.

On behalf of the Collaboration team, Trizek (WMF) १३:१४, ७ जून २०१८ (UTC)

Update on page issues on mobile web

Update on page issues on mobile web

कृपया अपनी भाषा में अनुवादित करने में सहायता करें 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.

CKoerner (WMF) (talk) २०:५८, १२ जून २०१८ (UTC)

Consultation on the creation of a separate user group for editing sitewide CSS/JS

(कृपया अपनी भाषा में अनुवादित करने में सहायता करें)

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) १०:५०, ९ जुलाई २०१८ (UTC) (via global message delivery)

Enabling a helpful feature for Template editors

Hello.

The team working on TemplateStyles at the Wikimedia Foundation would like to enable TemplateStyles on this wiki.

TemplateStyles is a feature to allow non-administrators to write and manage CSS styles for templates. It allows contributors who edit templates to separate content and presentation. A good web practice that makes it easier to manage the layout of templates. If you don't edit templates, this will not have any impact on your contributions.

TemplateStyles is useful for a few reasons.

• It makes it possible for templates to work better on mobile.
• It cuts out confusion on where to apply CSS rules.
• Editing CSS is currently limited to administrators, which is a major barrier to participation.
• All stylesheets must be loaded on all pages (whether they actually use the page or not), which wastes bandwidth and makes debugging style rules more difficult.

You can learn more about TemplateStyles on MediaWiki.org. Technical documentation is also available.

This is an optional feature and no one must use it, but template contributors are encouraged to do so! Please discuss and let us know if there are any concerns. If there are no concerns we will proceed to deploy the feature on the 9th of August.

Thank you.

CKoerner (WMF) (talk) २१:२८, ६ अगस्त २०१८ (UTC)

mw.util.jsMessage

Hi, the mw.util.jsMessage() function was deprecated in 2012, and will soon not be working. According to phab:P7840 there's at least one gadget using this function on your wiki, but it is likely it won't cause much of a problem anyway. We don't see this function being used much and this message is mainly to be on the safe side. There's a migration guide that explains how to use mw.notify instead. See phab:T193901 for more information. /Johan (WMF)

०९:३९, २६ नवम्बर २०१८ (UTC)

Wikidata Bridge: edit Wikidata’s data from Wikipedia infoboxes

Sorry for writing this message in English - feel free to help us translating it :)

Hello all,

Many language versions of Wikipedia use the content of Wikidata, the centralized knowledge base, to fill out the content of infoboxes. The data is stored in Wikidata and displayed, partially or completely, in the Wikipedia’s language, on the articles. This feature is used by many template editors, but brought several issues that were raised by communities in various places: not being able to edit the data directly from Wikipedia was one of them.

This is the reason why the Wikidata Bridge project started, with the goal of offering a way to Wikipedia editors to edit Wikidata’s data more easily. This will be achieved by an interface, connected to the infobox, that users can access directly from their local wiki.

The project is now at an early stage of development. A lot of user research has been done, and will continue to be done through the different phases of the project. The next steps of development will be achieved by the development team working at Wikimedia Deutschland, starting now until the end of 2019.

In order to make sure that we’re building a tool that is answering editors’ needs, we’re using agile methods in our development process. We don’t start with a fixed idea of the tool we want to deliver: we will build it together with the editors, based on feedback loops that we will regularly organize. The first version will not necessarily have all of the features you want, but it will keep evolving.

Here’s the planned timeline:

• From June to August, we will build the setup and technical groundwork.
• From September to November 2019, we will develop the first version of the feature and publish a test system so you can try it and give feedback.
• Later on, we will test the feature on a few projects, in collaboration with the communities.
  • We will first focus on early adopters communities who already implemented a shortcut from their infoboxes to edit Wikidata (for example Russian, Catalan, Basque Wikipedias)
  • but we also welcome also communities who volunteer to be part of the first test round.
  • Then we will reach some of the big Wikipedias (French, German, English) in order to see if the project scales and to address their potentially different needs.
  • Even later, we can consider enabling the feature on all the other projects.

In any case, no deployment or big change will be enforced on the projects without talking to the communities first, and helping the template builders to prepare for the changes they will have to do on the infoboxes’ code.

If you want to get involved, there are several ways to help:

• Read and help translating the documentation pages
• Follow the updates and participate in the first feedback loop
• Talk about it with your local community

More ideas will be added on this page along the way

If you have any questions for the development team, feel free to ask them on the main talk page. You can also ask under this message, but if you expect an answer from me, please make sure to ping me.

Thanks for your attention, Lea Lacroix (WMDE) १३:०३, २४ जून २०१९ (UTC)

Google Code-In will soon take place again! Mentor tasks to help new contributors!

Hi everybody! Google Code-in (GCI) will soon take place again - a seven week long contest for 13-17 year old students to contribute to free software projects. Tasks should take an experienced contributor about two or three hours and can be of the categories Code, Documentation/Training, Outreach/Research, Quality Assurance, and User Interface/Design. Do you have any Lua, template, gadget/script or similar task that would benefit your wiki? Or maybe some of your tools need better documentation? If so, and you can imagine enjoying mentoring such a task to help a new contributor, please check out mw:Google Code-in/2019 and become a mentor. If you have any questions, feel free to ask at our talk page. Many thanks in advance! --Martin Urbanec ०७:२८, ५ नवम्बर २०१९ (UTC)

Technical maintenance planed‬

A maintenance operation will be performed tomorrow morning UTC time (Wednesday 17th at 07:00 AM UTC).

It will impact all wikis and is supposed to last up to one minute.

During this time, new translations may fail, and Notifications may not be delivered. For more details about the operation and on all impacted services, please check on Phabricator.

A banner will be displayed 30 minutes before the operation.

Thank you, SGrabarczuk (WMF) १७:४५, १६ फेब्रवरी २०२१ (UTC)

Coolest Tool Award 2021: Call for nominations

The third edition of the m:Coolest Tool Award is looking for nominations!

Tools play an essential role for the Wikimedia projects, and so do the many volunteer developers who experiment with new ideas and develop and maintain local and global solutions to support the Wikimedia communities. The Coolest Tool Award aims to recognize and celebrate the coolest tools in a variety of categories.

The awarded projects will be announced and showcased in a virtual ceremony in December. Deadline to submit nominations is October 27. More information: m:Coolest Tool Award. Thanks for your recommendations! -- SSethi (WMF) for the 2021 Coolest Tool Academy team ०५:५६, १९ अक्टोबर् २०२१ (UTC)

Community Wishlist Survey 2022 is coming. Help us!

The Community Wishlist Survey 2022 starts in less than two weeks (Monday 10 January 2022, 18:00 UTC). We, the team organizing the Survey, need your help.

Translate important messages

Promote the Survey Among anyone and everyone you know who has an account on wiki. Promote the Survey on social media, via instant messaging apps, in other groups and chats, in your WikiProject, Wikimedia affiliate - wherever contributors with registered accounts may be.

Only you can make the difference

How many people will hear and read about the Survey in their language? How many will decide to participate? Will there be enough of you to vote for a change you would like to see? It all depends on you, volunteers.

Why are we asking?

• We have improved the documentation. It's friendlier and easier to use. This will mean little if it's only in English.
• Thousands of volunteers haven't participated in the Survey yet. We'd like to improve that, too. Three years ago, 1387 people participated. Last year, there were 1773 of them. We hope that in the upcoming edition, there will be even more. You are better than us in contacting Wikimedians outside of wikis. We have prepared some images to share. More to come.

What is the Community Wishlist Survey?

It's an annual survey that allows contributors to the Wikimedia projects to propose and vote for tools and platform improvements. Long years of experience in editing or technical skills are not required.

Thanks, and be safe and successful in 2022! SGrabarczuk (WMF) (talk) ०३:१५, २९ डिसेम्बर् २०२१ (UTC)

Save the Date: Coolest Tool Award 2021: this Friday, 17:00 UTC

<languages />

सभी को नमस्कार,

2021 Wikimedia Coolest Tool Award का समारोह वस्तुतः शुक्रवार 14 जनवरी 2022, 17:00 UTC पर होगा।

यह पुरस्कार विकिमीडिया परियोजनाओं में योगदानकर्ताओं द्वारा नामित सॉफ्टवेयर टूल को हाइलाइट कर रहा है। समारोह हमारे टूल डेवलपर्स की सराहना करने और नए टूल खोजने के लिए एक अच्छा क्षण होगा!

लाइवस्ट्रीम और चर्चा चैनलों के बारे में और पढ़ें।

जुड़ने के लिए धन्यवाद! andre (talk) -08:02, 6 January 2022 (UTC)

Last two days for submitting proposals

Tomorrow is the last day for submitting proposals for the Community Wishlist Survey 2022.

Also, everyone is welcome to translate, promote, and discuss proposals. SGrabarczuk (WMF) (talk) १४:४५, २२ जनवरी २०२२ (UTC)

Rollout of the new audio and video player

कृपया अपनी भाषा में अनुवादित करने में सहायता करें

Hello,

Over the next months we will gradually change the audio and video player of Wikis from Kultura to Video.js and with that, the old player won’t be accessible anymore. The new player has been active as a beta feature since May 2017.

The new player has many advantages, including better design, consistent look with the rest of our interface, better compatibility with browsers, ability to work on mobile which means our multimedia will be properly accessible on iPhone, better accessibility and many more.

The old player has been unmaintained for eight years now and is home-brewn (unlike the new player which is a widely used open source project) and uses deprecated and abandoned frameworks such as jQuery UI. Removing the old player’s code also improves performance of the Wikis for anyone visiting any page (by significantly reducing complexity of the dependency graph of our ResourceLoader modules. See this blog post.). The old player has many open bugs that we will be able to close as resolved after this migration.

The new player will solve a lot of old and outstanding issues but also it will have its own bugs. All important ones have been fixed but there will be some small ones to tackle in the future and after the rollout.

What we are asking now is to turn on the beta feature for the new player and let us know about any issues.

You can track the work in T100106

Thank you, Amir १७:५९, १७ फेब्रवरी २०२२ (UTC)

Enabling Content and Section translation tool in Sanskrit Wikipedia

नमस्ते Friends!

Apologies as this message is not in your native language, कृपया अपनी भाषा में अनुवादित करने में सहायता करें.

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

• Give us your feedback
• Ask us questions
• Tell us 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 Sanskrit 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 on Sanskrit Wikipedia in the coming week 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 on Sanskrit Wikipedia, you’ll have access to https://sa.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) (alderique) 12:06 29 xun 2022 (UTC) On behalf of the WMF Language team.

@[[:योजकः ::bh:User:UOzurumba (WMF|User:UOzurumba (WMF]]: Can't see Sanskrit. Please help. ॐNehalDaveND•✉•✎ १५:३०, ३० आगस्ट् २०२२ (UTC)

Hello ॐNehalDaveND,

The Content translation is still a beta feature in Sanskrit Wikipedia. So, you have to enable it by checking the "Content Translation" box. You can find the Content translation box by clicking the "Beta features" button located in the "Preferences" icon (top right side of your Wikipedia page). For the Section Translation, you can only access the tool now from the test instance.

Once these tools are enabled permanently in your Wiki, your community won't have to go through this process to access the tool.

I hope my reply answer's your question; please let me know if you need any further help or explanation. We look forward to enabling these tools in your Wikipedia soon.

Thank you!

UOzurumba (WMF) (चर्चा) २३:५८, ७ सेप्टेम्बर् २०२२ (UTC)

Content and Section Translation tool enabled in Sanskrit Wikipedia

नमस्ते Friends!

The WMF Language team is pleased to let you know that we have enabled the Section translation and Content translation tools in Sanskrit Wikipedia.

The Content translation tool can be discovered by users through several entry points. However, users not interested in translation can disable it from their preferences. Also, with the Section translation tool, you can start translating an article on your mobile device right when you notice it is missing in Sanskrit. From a Wikipedia article in any language, switch languages and search for संस्कृतम्. If the article does not exist, an option to translate it will appear, as shown in the image below.

We know that these tools will help translators in your community to add content using any device with ease. Content created with the Content and Section Translation tool will be marked with the "contenttranslation" and “sectiontranslaiton” tag, respectively, for the community to review. We’ll monitor the content created, but we are very interested in hearing about your experience using the tools and reviewing the content created with it.

So, enjoy the tools and provide feedback on improving it.

Thank you! UOzurumba (WMF) (चर्चा) २०:५५, २१ सेप्टेम्बर् २०२२ (UTC)

कूलेस्ट टूल अवार्ड 2022: नामांकन के लिए कॉल

कूलेस्ट टूल अवार्ड का चौथा संस्करण आपके नामांकन का स्वागत करता है! आपका पसंदीदा विकिमीडिया संबंधित सॉफ्टवेयर टूल क्या है? कृपया अपने पसंदीदा उपकरण प्रस्तुत करें 12 अक्टूबर, 2022 तक! पुरस्कृत परियोजनाओं की घोषणा दिसंबर में एक वर्चुअल समारोह में की जाएगी और उन्हें प्रदर्शित भी किया जाएगा।

MediaWiki message delivery १८:३०, ३ अक्टोबर् २०२२ (UTC)

कूलेस्ट टूल अवार्ड 2022 में शामिल हों: शुक्रवार, दिसंबर 16, 17:00 यूटीसी

2021 Wikimedia Coolest Tool Award का समारोह वस्तुतः शुक्रवार 14 जनवरी 2022, 17:00 UTC पर होगा।

यह पुरस्कार विकिमीडिया परियोजनाओं में योगदानकर्ताओं द्वारा नामित सॉफ्टवेयर टूल को हाइलाइट कर रहा है। समारोह हमारे टूल डेवलपर्स की सराहना करने और नए टूल खोजने के लिए एक अच्छा क्षण होगा!

लाइवस्ट्रीम और चर्चा चैनलों के बारे में और पढ़ें।

जुड़ने के लिए धन्यवाद! -Komla

MediaWiki message delivery १८:५३, ५ डिसेम्बर् २०२२ (UTC)

Graph extension disabled

Yesterday the Wikimedia Foundation noted that in the interests of the security of our users, the Graph extension was disabled. This means that pages that were formerly displaying graphs will now display a small blank area. To help readers understand this situation, communities can now define a brief message that can be displayed to readers in place of each graph until this is resolved. That message can be defined on each wiki at MediaWiki:Graph-disabled. Wikimedia Foundation staff are looking at options available and expected timelines. For updates, follow the public Phabricator task for this issue: T334940

--MediaWiki message delivery (चर्चा) १७:३६, १९ एप्रिल् २०२३ (UTC)

Automatic citations based on ISBN are broken

Apologies if this message does not reach you in your favorite language. You can help translate it centrally at Meta. Thanks for your help.

We have recently become unable to access the WorldCat API which provided the ability to generate citations using ISBN numbers. The Wikimedia Foundation's Editing team is investigating several options to restore the functionality, but will need to disable ISBN citation generation for now.

This affects citations made with the VisualEditor Automatic tab, and the use of the citoid API in gadgets and user scripts, such as the autofill button on refToolbar. Please note that all the other automatic ways of generating citations, including via URL or DOI, are still available.

You can keep updated on the situation via Phabricator, or by reading the next issues of m:Tech News. If you know of any users or groups who rely heavily on this feature (for instance, someone who has an upcoming editathon), I'd appreciate it if you shared this update with them.

Elitre (WMF), on behalf of the Editing team.

MediaWiki message delivery (चर्चा) १९:४५, ११ मे २०२३ (UTC)

MinT Machine Translation added to your Wikipedia

नमस्ते!

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

The WMF Language team has added another machine translation (MT) system for Content Translation in your Wikipedia called MinT; you can use MinT machine translation when translating Wikipedia articles using the Content and Section Translation tool.

The WMF Language team provides the MinT service. It is hosted in the Wikimedia Foundation Infrastructure with neural machine translation models that other organizations have released with an open-source license. MinT integrates translation based on NLLB-200, OpusMT and IndicTrans2 which is the model MinT is using in your Wikipedia. This MT is set as optional in your Wikipedia. Still, you can choose not to use it by selecting "Start with empty paragraph" from the "Initial Translation" dropdown menu.

Since MinT is hosted in the WMF Infrastructure and the models are open source, it adheres to Wikipedia's policies about attribution of rights, your privacy as a user and brand representation. You can find more information about the MinT Machine translation and the models on this page.

Please note that the use of the MinT MT is not compulsory. However, we would want your community to:

• use it to improve the quality of the Machine Translation service
• provide feedback about the service and its quality, and the service you prefer as default for your Wikipedia.

We trust that introducing this MT is a good support to the Content Translation tool.

Thank you!

UOzurumba (WMF) (सम्भाषणम्) ०८:०५, ३ जुलै २०२३ (UTC)

Deploying the Phonos in-line audio player to your Wiki

नमस्ते!

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

०२:२६, २७ जुलै २०२३ (UTC)

Temporary accounts for unregistered editors

Read this in your language • कृपया अपनी भाषा में अनुवादित करने में सहायता करें • Please tell other users about these changes

Next year, unregistered editors will start using temporary accounts.

In 2024, editors who have not registered an account will automatically begin using temporary accounts. These editors are sometimes called "IP editors" because the IP address is displayed in the page history.

The Trust and Safety Product team gave a presentation at Wikimania about this change. You can watch it on YouTube.

There is more information at m:IP Editing: Privacy Enhancement and Abuse Mitigation.

SGrabarczuk (WMF) (सम्भाषणम्) ०२:०५, ३० सेप्टेम्बर् २०२३ (UTC)

Making MinT a default Machine Translation for your Wikipedia

नमस्ते Sanskrit Wikipedians!

Apologies as this message is not in your native language, कृपया अपनी भाषा में अनुवादित करने में सहायता करें.

The WMF Language team wants to make MinT the default machine translation support in Sanskrit Wikipedia Content Translation. MinT uses the IndicTrans2 machine translation model, which recently has a new version.

Our proposal to set MinT as the default machine translation service in this Wikipedia will expose contributors to open source service by default and allow them to switch to other services if they prefer those services. Contributors can decide to switch to another translation service that is not default if they prefer the service, which will be helpful in analysing user preferences in the future.

The WMF Language team is requesting feedback from members of this community in this thread if making the MinT the default translation service is okay in Sanskrit Wikipedia. If there are no objections to the above proposal. In that case, MinT will become the default machine translation in this Wikipedia by the 6th of February 2024.

Thank you for your feedback.

UOzurumba (WMF) (चर्चा) ०४:५५, १७ जनवरी २०२४ (UTC) On behalf of the WMF Language team.

Coming soon: A new sub-referencing feature – try it!

Hello. For many years, community members have requested an easy way to re-use references with different details. Now, a MediaWiki solution is coming: The new sub-referencing feature will work for wikitext and Visual Editor and will enhance the existing reference system. You can continue to use different ways of referencing, but you will probably encounter sub-references in articles written by other users. More information on the project page.

We want your feedback to make sure this feature works well for you:

• Please try the current state of development on beta wiki and let us know what you think.
• Sign up here to get updates and/or invites to participate in user research activities.

Wikimedia Deutschland’s Technical Wishes team is planning to bring this feature to Wikimedia wikis later this year. We will reach out to creators/maintainers of tools and templates related to references beforehand.

Please help us spread the message. --Johannes Richter (WMDE) (talk) 10:36, 19 August 2024 (UTC)

'Wikidata item' link is moving. Find out where...

Apologies for cross-posting in English. Please consider translating this message.फलकम्:Tracked

Hello everyone, a small change will soon be coming to the user-interface of your Wikimedia project. The Wikidata item sitelink currently found under the General section of the Tools sidebar menu will move into the In Other Projects section.

We would like the Wiki communities feedback so please let us know or ask questions on the Discussion page before we enable the change which can take place October 4 2024, circa 15:00 UTC+2. More information can be found on the project page.

We welcome your feedback and questions.
MediaWiki message delivery (चर्चा) १८:५६, २७ सेप्टेम्बर् २०२४ (UTC)

'Wikidata item' link is moving, finally.

Hello everyone, I previously wrote on the 27th September to advise that the Wikidata item sitelink will change places in the sidebar menu, moving from the General section into the In Other Projects section. The scheduled rollout date of 04.10.2024 was delayed due to a necessary request for Mobile/MinervaNeue skin. I am happy to inform that the global rollout can now proceed and will occur later today, 22.10.2024 at 15:00 UTC-2. Please let us know if you notice any problems or bugs after this change. There should be no need for null-edits or purging cache for the changes to occur. Kind regards, -Danny Benjafield (WMDE) ११:२८, २२ अक्टोबर् २०२४ (UTC)