Википедия:Техник форум

Ярдәм үзәге · Җәмгыять үзәге · Форум · Порталлар · Сайланган эчтәлек · Проектлар · Мөрәҗәгатьләр · Бәяләү эшчәнлеге Авторлык хокуклары · Бот хуҗалары · Идарәчеләр форумы · Кагыйдәләр турында · Сораулар бирү · Техник форум · Хаталар буенча · Яңалыклар уртаклашу · Башкаларга сыймаганы

Татар Википедиясе форумына рәхим итегез! Кайсы бүлегендә сорыйм дип белМӘгәндә, «Сораулар» бүлегенә языгыз. Хәбәр калдырганда үз электрон почта адресыгызны һәм башка контактларны күрсәтмәгез — СПАМдан имин булыр, җавап исә барыбер сорау урнаштырылган биттә булачак!

Яңа тема башлар өчен, монда басыгыз Press here to start a new topic Нажмите сюда, чтобы начать новую тему

Техник форум - Википедиягә бәйле техник мәсьәләләр турында мәгълүматлар тупланылышы.
Фикер алышу, ярдәм сорау, яңалыклар һәм үзгәртүләр турында бәхәсләшү урыны өчен бәхәс бүлеген кара.

Викимедиа фонды техник төркеме атна-саен әзерли торган соңгы үзгәрешләр турындагы инглиз телендәге бюллетеньнәр җыелмасы белән шулай ук русча һәм кайбер башка телләргә тәрҗемәләре аркылы танышырга була. Шул бюллетеньнәр чыгуга, сезнең бәхәс битегезгә килүләре өчен аларга язылырга да була.

Шул ук төркемнең айлык җыелышларында катнашу, үткән җыелышлары протоколлары, отчетлары һәм презентацияләре белән танышу өчен монда кара (инглизчә).

VisualEditor News #6—2015

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.

Recent improvements

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

Future changes

The single edit tab project will combine the "Үзгәртү" and "Вики-текстны үзгәртү" tabs into a single "Үзгәртү" tab, like the system already used on the mobile website. (T102398, T58337) Initially, the "Үзгәртү" tab will open whichever editing environment you used last time. Your last editing choice will be stored as a cookie for logged-out users and as an account preference for logged-in editors. Logged-in editors will be able to set a default editor in the Үзгәртү tab of Special:Preferences in the drop-down menu about "Үзгәртү режимы:".

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

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

Testing opportunities

• Please try the new system for the single edit tab on test2.wikipedia.org. You can edit while logged out to see how it works for logged-out editors, or you can create a separate account to be able to set your account's preferences. Please share your thoughts about the single edit tab system at the feedback topic on mediawiki.org or sign up for formal user research (type "single edit tab" in the question about other areas you're interested in). The new system has not been finalized, and your feedback can affect the outcome. The team particularly wants your thoughts about the options in Special:Preferences. The current choices in Special:Preferences are:
  • Соңгы мөхәрриремне хәтерләү,
  • Всегда открывать визуальный редактор, если это возможно,
  • Всегда открывать редактор исходного текста, and
  • Показывать мне оба варианта редактора. (This is the current state for people 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. Рәхмәт!

Elitre (WMF), 25 дек 2015, 00:06 (UTC)

VisualEditor News #1—2016

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

Did you know?

Among experienced editors, the visual editor's table editing is one of the most popular features.

If you select the top of a column or the end of a row, you can quickly insert and remove columns and rows.

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

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

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

Recent changes

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

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

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

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

Future changes

The single edit tab project will combine the "Үзгәртү" and "Вики-текстны үзгәртү" tabs into a single "Үзгәртү" tab. This is similar to the system already used on the mobile website. (T102398) Initially, the "Үзгәртү" tab will open whichever editing environment you used last time. Your last editing choice will be stored as an account preference for logged-in editors, and as a cookie for logged-out users. Logged-in editors will have these options in the Үзгәртү tab of Special:Preferences:

• Соңгы мөхәрриремне хәтерләү,
• Всегда открывать визуальный редактор, если это возможно,
• Всегда открывать редактор исходного текста, and
• Показывать мне оба варианта редактора. (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.

Let's work together

• 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. Рәхмәт!

Elitre (WMF), 26 фев 2016, 19:21 (UTC)

Editing News #2—2016

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

Did you know?

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

Place the cursor where you want to display the references list (usually at the bottom of the page). Open the "Кертеп кую" menu and click the "Искәрмәләр исемлеге" icon (three books).

If you are using several groups of references, which is relatively rare, you will have the opportunity to specify the group. If you do that, then only the references that belong to the specified group will be displayed in this list of references. Finally, click "Кертеп кую" in the dialog to insert the Искәрмәләр исемлеге. This list will change as you add more footnotes to the page.

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

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

Recent changes

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

The single edit tab feature combines the "Үзгәртү" and "Вики-текстны үзгәртү" tabs into a single "Үзгәртү" tab. It has been deployed to several Wikipedias, including Hungarian, Polish, English and Japanese Wikipedias, as well as to all Wikivoyages. At these wikis, you can change your settings for this feature in the "Үзгәртү" tab of Special:Preferences. The team is now reviewing the feedback and considering ways to improve the design before rolling it out to more people.

Future changes

The "Битне саклау" button will say "Битне бастыру". This will affect both the visual and wikitext editing systems. More information is available on Meta.

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

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

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

Let's work together

• 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. Рәхмәт!

m:User:Elitre (WMF), 3 июл 2016, 17:20 (UTC)

The Wikimedia Developer Summit wants you

The Wikimedia Developer Summit is the annual meeting to push the evolution of MediaWiki and other technologies supporting the Wikimedia movement. The next edition will be held in San Francisco on January 9–11, 2017.

We welcome all Wikimedia technical contributors, third party developers, and users of MediaWiki and the Wikimedia APIs. We specifically want to increase the participation of volunteer developers and other contributors dealing with extensions, apps, tools, bots, gadgets, and templates.

Important deadlines:

• Monday, October 24: last day to request travel sponsorship. Applying takes less than five minutes.
• Monday, October 31: last day to propose an activity. Bring the topics you care about!

More information: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit

Subscribe to weekly updates: https://www.mediawiki.org/wiki/Topic:Td5wfd70vptn8eu4

MKramer (WMF) (talk) 14 окт 2016, 19:07 (UTC)

Editing News #3—2016

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.

Recent changes

• You can now set text as small or big.[1]
• Invisible templates have been shown as a puzzle icon. Now, the name of the invisible template is displayed next to the puzzle icon.[2] A similar feature will display the first part of hidden HTML comments.[3]
• Categories are displayed at the bottom of each page. If you click on the categories, the dialog for editing categories will open.[4]
• 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.[5]
• The "Save" button now says "Save page" when you create a page, and "Save changes" when you change an existing page.[6] In the future, the "Битне саклау" button will say "Битне бастыру". This will affect both the visual and wikitext editing systems. More information is available on Meta.
• Image galleries now use a visual mode for editing. You can see thumbnails of the images, add new files, remove unwanted images, rearrange the images by dragging and dropping, and add captions for each image. Use the "Options" tab to set the gallery's display mode, image sizes, and add a title for the gallery.[7]

Future changes

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

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

Let's work together

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

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

—Elitre (WMF)

15 окт 2016, 17:49 (UTC)

Developer Wishlist Survey: propose your ideas

At the Wikimedia Developer Summit, we decided to organize a Developer Wishlist Survey, and here we go:

https://www.mediawiki.org/wiki/Developer_Wishlist

The Wikimedia technical community seeks input from developers for developers, to create a high-profile list of desired improvements. The scope of the survey includes the MediaWiki platform (core software, APIs, developer environment, enablers for extensions, gadgets, templates, bots, dumps), the Wikimedia server infrastructure, the contribution process, and documentation.

The best part: we want to have the results published by Wednesday, February 15. Yes, in a month, to have a higher chance to influence the Wikimedia Foundation annual plan FY 2017-18.

There's no time to lose. Propose your ideas before the end of January, either by pushing existing tasks in Phabricator or by creating new ones. You can find instructions on the wiki page. Questions and feedback are welcome especially on the related Talk page.

The voting phase is expected to start on February 6 (tentative). Watch this space (or even better, the wiki page) - SSethi_(WMF) January 21st, 2017 3:07 AM (UTC)

Developer Wishlist Survey: Vote for Proposals

Almost two weeks ago, the Technical Collaboration team invited proposals for the first edition of the Developer Wishlist survey!

We collected around 77 proposals that were marked as suitable for the developer wishlist and met the defined scope and criteria. These proposals fall into the following nine categories: Frontend, Backend, Code Contribution (Process, Guidelines), Extensions, Technical Debt, Developer Environment, Documentation, Tools (Phabricator, Gerrit) and Community Engagement.

Voting phase starts now and will run until February 14th, 23:59 UTC. Click here on a category and show support for the proposals you care for most. Use the 'Vote' and 'Endorse' buttons next to a proposal to do so.

What happens next?
Proposals that will gather most votes will be included in the final results which will be published on Wednesday, February 15th. These proposals will also be considered in the Wikimedia Foundation’s annual plan FY 2017-18 - SSethi_(WMF) (talk) 04:41, 6 February 2017 (UTC)

Editing News #1—2017

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

Did you know?

Did you know that you can review your changes visually?

When you are finished editing the page, type your edit summary and then choose "Кертелгән үзгәрешләрегезне тикшерү".

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

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

The wikitext diff is the same diff tool that is used in the wikitext editors and in the page history. You can read and help translate the user guide, which has more information about how to use the visual editor.

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

Recent changes

• A new wikitext editing mode is available as a Beta Feature on desktop devices. The 2017 wikitext editor has the same toolbar as the visual editor and can use the citoid service and other modern tools. Go to Special:Preferences#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. [8]
• 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. [9]
• 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. [10]
• 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. [11]
• The Төркемнәр item has been moved to the top of the Биттәге гамәлләр menu (from clicking on the "hamburger" icon) for quicker access. [12] There is also now a "Templates used on this page" feature there. [13]
• You can now create <chem> tags (sometimes used as <ce>) for chemical formulas inside the visual editor. [14]
• Tables can be set as collapsed or un-collapsed. [15]
• The Махсус тамгалар menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) . The team thanks the volunteer developer, Tpt. [16]
• 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. [17]
• 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. [18]

Future changes

• 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. [19]
• The kind of button used to Алдан карау, Үзгәрешләрне күрсәтү, and finish an edit will change in all WMF-supported wikitext editors. The new buttons will use OOjs UI. The buttons will be larger, brighter, and easier to read. The labels will remain the same. You can test the new button by editing a page and adding &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. [20]
• 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. [21]
• 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. Рәхмәт!

—Elitre (WMF)

12 май 2017, 18:05 (UTC)

Improvements coming soon to Recent Changes

Hello

Sorry to use English. Пожалуйста, помогите перевести на ваш язык! Спасибо.

In short: starting on 26 September, New Filters for Edit Review (now in Beta) will become standard on Recent Changes. 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 improves Special:RecentChanges and Special:RecentChangesLinked (and soon, Special:Watchlist – see below).

Based on a new design, it adds new features that 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.

Concerning RecentChanges

Starting on 26 September, New Filters for Edit Review will become standard on Recent Changes. We have decided to do this release because of a long and successful Beta test phase, positive feedback from various users and positive user testing.

Some features will remain as Beta features and will be added later. Learn more about those different features.

If your community has specific concerns about this deployment or internal discussion, it can request to have the deployment to their wikis delayed to October 1, if they have sensible, consistent with the project, actionable, realistic feedback to oppose (at the development team's appreciation).

You will also be able to opt-out this change in your preferences.

Concerning Watchlists

Starting on September 19, the Beta feature will have a new option. Watchlists will have all filters available now on the Beta Recent Changes improvements.

If you have already activated the Beta feature "⧼eri-rcfilters-beta-label⧽", you have no action to take. If you haven't activated the Beta feature "⧼eri-rcfilters-beta-label⧽" and you want to try the filters on Watchlists, please go to your Beta preferences on September 19.

How to be ready

Please share this announcement!

Do you use Gadgets that change things on your RecentChanges or Watchlist pages, or have you customized them with scripts or CSS? 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 ping me if you have questions.

On behalf of the Global Collaboration team, Trizek (WMF) 14 сен 2017, 15:27 (UTC)

Бета (?) мөмкинлекне "кабызу"

Инглиз википедиясендә, тычканны искәрмә номеры өстенә китергәч, ул искәрмәнең тексты күренә. Ягъни искәрмә текстын укыр өчен, битнең азагына кадәр төшеп һәм кире менеп торасы юк, бик уңайлы. Безнең википедиядә дә бу мөмкин булсын өчен нишләргә кирәк икән? IlnarSelimcan (бәхәс) 13 дек 2017, 17:11 (UTC)

Тәҗрибәле кулланучылар белән аралашканда сорармын. Үзем белмим.--frhdkazan (бәхәс) 13 дек 2017, 18:03 (UTC)

Global preferences available for testing

Apologies for writing in English. Пожалуйста, помогите перевести на ваш язык.

Greetings,

Global preferences, a highly request feature in the 2016 Community Wishlist, is available for testing.

1. Read over the help page, it is brief and has screenshots
2. Login or register an account on Beta English Wikipedia
3. Visit Global Preferences and try enabling and disabling some settings
4. Visit some other language and project test wikis such as English Wikivoyage, the Hebrew Wikipedia and test the settings
5. Report your findings, experience, bugs, and other observations

Once the team has feedback on design issues, bugs, and other things that might need worked out, the problems will be addressed and global preferences will be sent to the wikis.

Please let me know if you have any questions. Thanks! --Keegan (WMF) (talk) 27 фев 2018, 00:24 (UTC)

Editing News #1—2018

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.

Recent changes

• The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools. The team have been comparing the performance of different editing environments. They have studied how long it takes to open the page and start typing. The study uses data for more than one million edits during December and January. Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor. Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits. More information will be posted at 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. [22]
• Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor. [23]
• 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.

Let's work together

• 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. [24]
• 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. Рәхмәт!

—Elitre (WMF)

2 мар 2018, 20:56 (UTC)

Notification from edit summary

Greetings,

The ability to notify other users in edit summaries will be available later this week, on 15 March 2018. Other users can be notified if a link to their user page is provided in an edit summary. Some user-made gadgets and scripts that automatically put user names in edit summaries may need to be changed to put a colon in the link, such as [[:User:Example]]. You can change how you receive these mention notifications in your preferences. This feature was highly requested in the 2017 Community Wishlist survey, and feedback is welcome.

Thanks, happy editing to you. -Keegan (WMF) (talk) 12 мар 2018, 21:09 (UTC)

We need your feedback to improve Lua functions

Hello,

(I’m sorry for writing in English. Пожалуйста, помогите перевести на ваш язык)

If you’re regularly using Lua modules, creating and improving some of them, we need your feedback!

The Wikidata development team would like to provide more Lua functions, in order to improve the experience of people who write Lua scripts to reuse Wikidata's data on the Wikimedia projects. Our goals are to help harmonizing the existing modules across the Wikimedia projects, to make coding in Lua easier for the communities, and to improve the performance of the modules.

We would like to know more about your habits, your needs, and what could help you. We have a few questions for you on this page. Note that if you don’t feel comfortable with writing in English, you can answer in your preferred language.

Рәхмәт! Lea Lacroix (WMDE) 27 мар 2018, 08:55 (UTC)

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) 24 апр 2018, 21:38 (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)

4 май 2018, 18:55 (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) 7 июн 2018, 13:15 (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) 12 июн 2018, 20:58 (UTC)

Tidy to RemexHtml

The Parsing team will be replacing Tidy with RemexHtml at this wiki on 5 July 2018.

Some pages at this wiki use outdated HTML. This change may change the appearance of those pages. Special:LintErrors has a complete list of affected pages.

Read this e-mail message for more information. Read the instructions at mw:Help:Extension:Linter. You can ask questions at mw:Talk:Parsing/Replacing Tidy. Thank you for helping fix these problems.

m:User:Elitre (WMF) 2 июл 2018, 14:38 (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) 9 июл 2018, 10:50 (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) 6 авг 2018, 21:28 (UTC)

Editing News #2—2018

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.

Recent changes

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

Let's work together

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

—Whatamidoing (WMF) (talk)

2 ноя 2018, 14:17 (UTC)

Editing News #1—July 2019

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?

Every article has a pencil icon at the top. Tap on the pencil icon to start editing.

Edit Cards

This is what the new Edit Cards for editing links in the mobile visual editor look like. You can try the prototype here: 📲 Try Edit Cards.

Welcome back to the Editing newsletter.

Since the last newsletter, the team has released two new features for the mobile visual editor and has started developing three more. All of this work is part of the team's goal to make editing on mobile web simpler.

Before talking about the team's recent releases, we have a question for you:

Are you willing to try a new way to add and change links?

If you are interested, we would value your input! You can try this new link tool in the mobile visual editor on a separate wiki.

Follow these instructions and share your experience:

📲 Try Edit Cards.

Recent releases

The mobile visual editor is a simpler editing tool, for smartphones and tablets using the mobile site. The Editing team recently launched two new features to improve the mobile visual editor:

1. Section editing
   • The purpose is to help contributors focus on their edits.
   • The team studied this with an A/B test. This test showed that contributors who could use section editing were 1% more likely to publish the edits they started than people with only full-page editing.
2. Loading overlay
   • The purpose is to smooth the transition between reading and editing.

Section editing and the new loading overlay are now available to everyone using the mobile visual editor.

New and active projects

This is a list of our most active projects. Watch these pages to learn about project updates and to share your input on new designs, prototypes and research findings.

• Edit cards: This is a clearer way to add and edit links, citations, images, templates, etc. in articles. You can try this feature now. Go here to see how: 📲 Try Edit Cards.
• Mobile toolbar refresh: This project will learn if contributors are more successful when the editing tools are easier to recognize.
• Mobile visual editor availability: This A/B test asks: Are newer contributors more successful if they use the mobile visual editor? We are collaborating with 20 Wikipedias to answer this question.
• Usability improvements: This project will make the mobile visual editor easier to use. The goal is to let contributors stay focused on editing and to feel more confident in the editing tools.

Looking ahead

• Wikimania: Several members of the Editing Team will be attending Wikimania in August 2019. They will lead a session about mobile editing in the Community Growth space. Talk to the team about how editing can be improved.
• Talk Pages: In the coming months, the Editing Team will begin improving talk pages and communication on the wikis.

Learning more

The VisualEditor on mobile is a good place to learn more about the projects we are working on. The team wants to talk with you about anything related to editing. If you have something to say or ask, please leave a message at Talk:VisualEditor on mobile.

PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk)

23 июл 2019, 18:32 (UTC)

Editing News #2 – Mobile editing and talk pages

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

Inside this newsletter, the Editing team talks about their work on the mobile visual editor, on the new talk pages project, and at Wikimania 2019.

Help

What talk page interactions do you remember? Is it a story about how someone helped you to learn something new? Is it a story about how someone helped you get involved in a group? Something else? Whatever your story is, we want to hear it!

Please tell us a story about how you used a talk page. Please share a link to a memorable discussion, or describe it on the talk page for this project. The team wants your examples. These examples will help everyone develop a shared understanding of what this project should support and encourage.

Talk pages project

The Talk Pages Consultation was a global consultation to define better tools for wiki communication. From February through June 2019, more than 500 volunteers on 20 wikis, across 15 languages and multiple projects, came together with members of the Foundation to create a product direction for a set of discussion tools. The Phase 2 Report of the Talk Page Consultation was published in August. It summarizes the product direction the team has started to work on, which you can read more about here: Talk Page Project project page.

The team needs and wants your help at this early stage. They are starting to develop the first idea. Please add your name to the "Getting involved" section of the project page, if you would like to hear about opportunities to participate.

Mobile visual editor

The Editing team is trying to make it simpler to edit on mobile devices. The team is changing the visual editor on mobile. If you have something to say about editing on a mobile device, please leave a message at Talk:VisualEditor on mobile.

Edit Cards

What happens when you click on a link. The new Edit Card is bigger and has more options for editing links.

• On 3 September, the Editing team released version 3 of Edit Cards. Anyone could use the new version in the mobile visual editor.
• There is an updated design on the Edit Card for adding and modifying links. There is also a new, combined workflow for editing a link's display text and target.
• Feedback: You can try the new Edit Cards by opening the mobile visual editor on a smartphone. Please post your feedback on the Edit cards talk page.

Toolbar

The editing toolbar is changing in the mobile visual editor. The old system had two different toolbars. Now, all the buttons are together. Tell the team what you think about the new toolbar.

• In September, the Editing team updated the mobile visual editor's editing toolbar. Anyone could see these changes in the mobile visual editor.
  • One toolbar: All of the editing tools are located in one toolbar. Previously, the toolbar changed when you clicked on different things.
  • New navigation: The buttons for moving forward and backward in the edit flow have changed.
  • Seamless switching: an improved workflow for switching between the visual and wikitext modes.
• Feedback: You can try the refreshed toolbar by opening the mobile VisualEditor on a smartphone. Please post your feedback on the Toolbar feedback talk page.

Wikimania

The Editing Team attended Wikimania 2019 in Sweden. They led a session on the mobile visual editor and a session on the new talk pages project. They tested two new features in the mobile visual editor with contributors. You can read more about what the team did and learned in the team's report on Wikimania 2019.

Looking ahead

• Talk Pages Project: The team is thinking about the first set of proposed changes. The team will be working with a few communities to pilot those changes. The best way to stay informed is by adding your username to the list on the project page: Getting involved.
• Testing the mobile visual editor as the default: The Editing team plans to post results before the end of the calendar year. The best way to stay informed is by adding the project page to your watchlist: VisualEditor as mobile default project page.
• Measuring the impact of Edit Cards: This study asks whether the project helped editors add links and citations. The Editing team hopes to share results in November. The best way to stay informed is by adding the project page to your watchlist: Edit Cards project page.

– PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk)

29 окт 2019, 11:12 (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 5 ноя 2019, 07:28 (UTC)

Tatarca Vikipedide silinecek sayfalar

Selam değerli editorlar. Silinecek sayfalar kategorisinde çok sayda sayfa bulunmakta. Ben bu sayfaların temizlenmesinde sizlere yardımda buluna bilirim. Sadece sizin izniniz gerekir. Türkce yazdığım için üzgünüm. Tatarca anlıyorum, lakin konuşamıyorum. Bir çok Türk dillerinde vikilerde çalışıyorum, yardımcı oluyorum. Sizlere de yardım etmek isterim. Sayğılarımla--Turkmen (бәхәс) 10 ноя 2019, 08:31 (UTC)

• Riza. --Derslek (бәхәс) 10 ноя 2019, 08:43 (UTC)

Editing news 2020 #1 – Discussion tools

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

This early version of the Reply tool automatically signs and indents comments.

The Editing team has been working on the talk pages project. The goal of the talk pages project is to help contributors communicate on wiki more easily. This project is the result of the Talk pages consultation 2019.

In a future update, the team plans to test a tool for easily linking to another user's name, a rich-text editing option, and other tools.

The team is building a new tool for replying to comments now. This early version can sign and indent comments automatically. Please test the new Reply tool.

• On 31 March 2020, the new җавап бирү tool was offered as a Beta Feature editors at four Wikipedias: Arabic, Dutch, French, and Hungarian. If your community also wants early access to the new tool, contact User:Whatamidoing (WMF).
• The team is planning some upcoming changes. Please review the proposed design and share your thoughts on the talk page. The team will test features such as:
  • an easy way to mention another editor ("pinging"),
  • a rich-text visual editing option, and
  • other features identified through user testing or recommended by editors.

To hear more about Editing Team updates, please add your name to the "Get involved" section of the project page. You can also watch these pages: the main project page, Updates, Replying, and User testing.

– PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk)

8 апр 2020, 19:27 (UTC)

Content Translation tool announcement: Machine translation support through Google Translate enabled for Tatar

English:

Hello!

Recently Google announced the availability of 5 more languages on Google Translate. This allows us to add machine translation support for Tatar on the Content Translation tool. As part of ongoing maintenance, this has now been enabled, and you can use it while translating Wikipedia articles into Tatar.

Please note, machine translation is an optional feature in Content Translation, and translators choose the best options for the content that they are translating. We strongly recommend that you read through the Help documents to get familiar with the process of using machine translation with Content Translation and the measures that exist to preserve the quality of machine-translated text through reviews and restrictions. If you have any feedback or questions, please do not hesitate to contact us through the Content Translation Project talk page, or on Phabricator ticket number 246319.

This message is written in English. Please help us translate it for the benefit of other users of this Wikipedia.

Thank you!

По-русски:

Здравствуйте!

Недавно компания Гугл объявила о доступности еще пяти языков в Google Translate. Это позволяет нам добавить поддержку машинного перевода для татарского языка в Инструменте перевода содержания. В рамках текущего обслуживания эта функция теперь включена, и вы можете использовать её при переводе статей Википедии на татарский язык.

Обратите внимание, что машинный перевод является дополнительной функцией в Переводе содержания, и именно переводчики выбирают лучшие варианты для содержания, которое они переводят. Мы настоятельно рекомендуем вам ознакомиться с документами справки, чтобы ознакомиться с процессом с использованием машинного перевода с Переводом содержания и меры, существующие для улучшения качества машинно-переведённого текста посредством проверок и ограничений. Если у вас есть какие-либо отзывы или вопросы, пожалуйста, не стесняйтесь обращаться к нам через Страницу обсуждения проекта Перевода содержания или в Фабрикаторе.

Спасибо! Амир Э. Аһарони (WMF) (бәхәс) 15 июн 2020, 19:17 (UTC)

Editing news 2020 #2

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

The new features include a toolbar. What do you think should be in the toolbar?

This issue of the Editing newsletter includes information the Talk pages project, an effort to help contributors communicate on wiki more easily.

• Reply tool: This is available as a Beta Feature at the four partner wikis (Arabic, Dutch, French, and Hungarian Wikipedias). The Beta Feature is called "Фикер алышу кораллары". The Beta Feature will get new features soon. The new features include writing comments in a new visual editing mode and pinging other users by typing @. You can test the new features on the Beta Cluster now. Some other wikis will have a chance to try the Beta Feature in the coming months.
• New requirements for user signatures: Soon, users will not be able to save invalid custom signatures in Special:Preferences. This will reduce signature spoofing, prevent page corruption, and make new talk page tools more reliable. Most editors will not be affected.
• New discussion tool: The Editing team is beginning work on a simpler process for starting new discussions. You can see the initial design on the project page.
• Research on the use of talk pages: The Editing team worked with the Wikimedia research team to study how talk pages help editors improve articles. We learned that new editors who use talk pages make more edits to the main namespace than new editors who don't use talk pages.

– Whatamidoing (WMF) (talk)

17 июн 2020, 20:33 (UTC)

Editing news 2020 #3

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

More than 50 million edits have been made using the visual editor on desktop.

Seven years ago this month, the Editing team offered the visual editor to most Wikipedia editors. Since then, editors have achieved many milestones:

• More than 50 million edits have been made using the visual editor on desktop.
• More than 2 million new articles have been created in the visual editor. More than 600,000 of these new articles were created during 2019.
• The visual editor is increasingly popular. The proportion of all edits made using the visual editor has increased every year since its introduction.
• In 2019, 35% of the edits by newcomers (logged-in editors with ≤99 edits) used the visual editor. This percentage has increased every year.
• Almost 5 million edits on the mobile site have been made with the visual editor. Most of these edits have been made since the Editing team started improving the mobile visual editor in 2018.
• On 17 November 2019, the first edit from outer space was made in the mobile visual editor. 🚀 👩‍🚀
• Editors have made more than 7 million edits in the 2017 wikitext editor, including starting 600,000 new articles in it. The 2017 wikitext editor is VisualEditor's built-in wikitext mode. You can enable it in your preferences.

Whatamidoing (WMF) (talk)

9 июл 2020, 12:55 (UTC)

Татар википедиясе конверторы

Бүгеннән, ягъни 27.09.2020 алып Татар википедиясе конверторы хакында тавыш бирү уза. Әлеге тавыш бирү ризалык тавышлары өстенлеге белән тәмамланса, татар википедиясендә латин имлясында язылган мәкаләләрне - кирилл һәм кирилл имлясындагы мәкаләләрне латин әлифбасында уку мөмкинлеге ачылачак. Шуны искәртеп үтү зарур:

• Әлеге конвертер латин имлясындагы мәкаләләрнең һәм игезәк мәкаләләрнең язмышын хәл итми. Моның өчен Илнур әфәнде башка тавыш бирүне ачып җибәрде.
• Бу конвертер бер мәкаләне бер үк вакытында латин һәм кирилл имлясында язу яки мөхәррирләүне инкяр итми (хәрефләр һәм иҗекләр буенча төрле имляда язу түгел, ә сүз, җөмлә, абзац күләмендә генә язу). Әмма бу яңа зур мөмкинлек башка тавыш бирүдән соң гына ачылуы мотлак, ягъни әлегә техник мөмкинлек кенә тудыра.

--Фәрһад (бәхәс) 27 сен 2020, 13:51 (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) 16 фев 2021, 17:45 (UTC)

Wikimania 2021: Individual Program Submissions

Dear all,

Wikimania 2021 will be hosted virtually for the first time in the event's 15-year history. Since there is no in-person host, the event is being organized by a diverse group of Wikimedia volunteers that form the Core Organizing Team (COT) for Wikimania 2021.

Event Program - Individuals or a group of individuals can submit their session proposals to be a part of the program. There will be translation support for sessions provided in a number of languages. See more information here.

Below are some links to guide you through;

• Program Submissions
• Session Submission Guidelines
• FAQ

Please note that the deadline for submission is 18th June 2021.

Announcements- To keep up to date with the developments around Wikimania, the COT sends out weekly updates. You can view them in the Announcement section here.

Office Hour - If you are left with questions, the COT will be hosting some office hours (in multiple languages), in multiple time-zones, to answer any programming questions that you might have. Details can be found here.

Best regards,

MediaWiki message delivery (бәхәс) 16 июн 2021, 04:18 (UTC)

On behalf of Wikimania 2021 Core Organizing Team

Editing news 2021 #2

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

When newcomers had the Reply tool and tried to post on a talk page, they were more successful at posting a comment. (Source)

Earlier this year, the Editing team ran a large study of the Reply Tool. The main goal was to find out whether the Reply Tool helped newer editors communicate on wiki. The second goal was to see whether the comments that newer editors made using the tool needed to be reverted more frequently than comments newer editors made with the existing wikitext page editor.

The key results were:

• Newer editors who had automatic ("default on") access to the Reply tool were more likely to post a comment on a talk page.
• The comments that newer editors made with the Reply Tool were also less likely to be reverted than the comments that newer editors made with page editing.

These results give the Editing team confidence that the tool is helpful.

Looking ahead

The team is planning to make the Reply tool available to everyone as an opt-out preference in the coming months. This has already happened at the Arabic, Czech, and Hungarian Wikipedias.

The next step is to resolve a technical challenge. Then, they will deploy the Reply tool first to the Wikipedias that participated in the study. After that, they will deploy it, in stages, to the other Wikipedias and all WMF-hosted wikis.

You can turn on "Фикер алышу кораллары" in Beta Features now. After you get the Reply tool, you can change your preferences at any time in Special:Preferences#mw-prefsection-editing-discussion.

–Whatamidoing (WMF) (talk)

24 июн 2021, 14:14 (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 19 окт 2021, 05:57 (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) 29 дек 2021, 03:15 (UTC)

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

<languages />

Hello all,

The ceremony of the 2021 Wikimedia Coolest Tool Award will take place virtually on Friday 14 January 2022, 17:00 UTC.

This award is highlighting software tools that have been nominated by contributors to the Wikimedia projects. The ceremony will be a nice moment to show appreciation to our tool developers and maybe discover new tools!

Read more about the livestream and the discussion channels.

Thanks for joining! 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) 22 гый 2022, 14:45 (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 17 фев 2022, 17:59 (UTC)

Editing news 2022 #1

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

New editors were more successful with this new tool.

The New topic tool helps editors create new ==Sections== on discussion pages. New editors are more successful with this new tool. You can read the report. Soon, the Editing team will offer this to all editors at the 20 Wikipedias that participated in the test. You will be able to turn it off at Special:Preferences#mw-prefsection-editing-discussion.

Whatamidoing (WMF) 2 май 2022, 18:55 (UTC)

Coolest Tool Award 2022: Call for nominations

The fourth edition of the Coolest Tool Award welcomes your nominations! What is your favorite Wikimedia related software tool? Please submit your favorite tools by October 12, 2022! The awarded projects will be announced and showcased in a virtual ceremony in December.

MediaWiki message delivery 3 окт 2022, 18:30 (UTC)

Join the Coolest Tool Award 2022: Friday, Dec 16th, 17:00 UTC

The fourth edition of the Wikimedia Coolest Tool Award will happen online on Friday 16 December 2022 at 17:00 UTC!

This award is highlighting software tools that have been nominated by contributors to the Wikimedia projects. The ceremony will be a nice moment to show appreciation to our tool developers and maybe discover new tools!

Read more about the livestream and the discussion channels.

Thanks for joining! -Komla

MediaWiki message delivery 5 дек 2022, 18:53 (UTC)

Enabling Section Translation: a new mobile translation experience

Привет Tatar Wikipedians!

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

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

• Give us your feedback

• Ask us questions

• Tell us how to improve it.

Below is background information about Section translation, why we have chosen your community, and how to test it.

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. The Wikimedia Foundation Language team has improved the translation experience further with the Section Translation. The WMF Language team enabled the early version of the tool in February 2021 in Bengali Wikipedia. Through their feedback, the tool was improved and ready for your community to test and provide feedback to make it better.

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.

Tatar Wikipedia seems an ideal candidate to enjoy this new tool since it has Content Translation tool enabled by default.

We plan to enable the tool in the coming weeks if there are no objections from your community. After it is enabled, we’ll monitor the content created with the tool and process all the feedback. In any case, feel free to raise any concerns or questions you may already have in any of the following formats:

• As a reply to this message

• On the project talk page.

Try the tool

Before the enablement, you can try the current implementation of the tool in our testing instance. Once it is enabled on Tatar Wikipedia, you’ll have access to https://tt.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 in any of the formats you are most comfortable with. We want to hear about your impressions on:

• The tool

• What you think about our plans to enable it

• Your ideas for improving the tool.

Thanks, and we look forward to your feedback.

UOzurumba (WMF) (бәхәс) 6 дек 2022, 02:38 (UTC)

Section Translation tool enabled in Tatar Wikipedia

Hello Friends!

The WMF Language team is pleased to let you know that the Section Translation tool is now enabled in Tatar Wikipedia. It means you can translate content one section at a time using your mobile devices with ease.

Now you can also start translating an article on your mobile device right when you notice it is missing in Tatar. 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.

Image of the entry point

Content created with the tool will be marked with the “sectiontranslation” tag for the community to review. We’ll monitor the content created, but we are very interested in hearing about your experience using the tool and reviewing the content created with it.

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

Thank you!

UOzurumba (WMF) (бәхәс) 4 гый 2023, 04:52 (UTC)

Editing news 2023 #1

Прочитайте это на другом языке • Подписной лист на этот многоязычный информационный бюллетень

Этот бюллетень включает два ключевых обновления о работе команды Редактирование:

1. Команда редактирования завершит добавление новых возможностей в проект Страницы беседы и развернет его.
2. Они начинают новый проект, Проверка редактирования.

Проект разговорных страниц

Некоторые из предстоящих изменений

Команда редакторов почти закончила первый этап проекта Страницы беседы. Почти все новые функции уже доступны в Бета-версия функции для Фикер алышу кораллары.

Он показывает информацию об активности обсуждения, например, дату последнего комментария. Вскоре появится новая кнопка "Яңа тема өстәү". Вы сможете отключить их в Special:Preferences#mw-prefsection-editing-discussion. Пожалуйста, скажите им, что вы думаете.

Ежедневная скорость завершения редактирования по тестовым группам: DiscussionTools (тестовая группа) и наложение MobileFrontend (контрольная группа)

Завершился A/B-тест для Фикер алышу кораллары на мобильном сайте. Редакторы были более успешны с Фикер алышу кораллары. Команда редакторов включает эти функции для всех редакторов на мобильном сайте.

Новый проект: Проверка редактирования

Команда редакторов начинает проект помощи новым редакторам Википедии. Он поможет людям выявить некоторые проблемы до того, как они нажмут "Үзгәрешләрне саклау". Первый инструмент будет поощрять людей добавлять ссылки, когда они добавляют новый контент. Пожалуйста, смотрите на этой странице для получения дополнительной информации. Вы можете присоединяйтесь к конференц-звонку по 3 March 2023, чтобы узнать больше.

–Whatamidoing (WMF) (бәхәс) 22 фев 2023, 23:24 (UTC)

Отключено расширение Graph

Вчера «Фонд Викимедиа» оповестил о том, что в интересах безопасности наших пользователей было отключено расширение Graph. Это означает, что страницы, использовавшие графики, сейчас отображают небольшой пустой блок. Чтобы проинформировать читателей о причине этого, сообщества могут указать короткое сообщение, которое будет отображено читателям вместо графика до разрешения этой проблемы. Сообщение можно определить в каждой вики на странице MediaWiki:Graph-disabled. Сотрудники «Фонда Викимедиа» рассматривают возможные варианты и предполагаемую дату. Подпишитесь на публичную задачу на «Фабрикаторе», чтобы следить за обновлениями: T334940

--MediaWiki message delivery (бәхәс) 19 апр 2023, 17:36 (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, IndicTrans2 and Softcatalà. 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 its quality, and if you prefer the MinT machine translation as default in your Wikipedia.

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

Thank you!

UOzurumba (WMF) (бәхәс) 4 июл 2023, 22:02 (UTC) On behalf of the WMF Language team.

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

27 июл 2023, 02:26 (UTC)

Временные учетные записи для незарегистрированных редакторов

Прочтите это на вашем языке • Пожалуйста, помогите перевести на ваш язык • Пожалуйста, сообщите другим пользователям об этих изменениях

В следующем году незарегистрированные редакторы начнут использовать временные учетные записи.

В 2024 году редакторы, которые еще не зарегистрировали учетную запись, автоматически начнут использовать временные учетные записи. Эти редакторы иногда называются "IP-редакторами", потому что IP-адрес отображается в истории страниц.

Команда по продуктам доверия и безопасности выступила на Викимании с презентацией об этом изменении. Вы можете посмотреть это на YouTube.

Более подробная информация доступна по адресу м:Редактирование IP: Повышение конфиденциальности и предотвращение злоупотреблений.

SGrabarczuk (WMF) (бәхәс) 30 сен 2023, 02:05 (UTC)

Скоро: новая функция подссылки - попробуйте!

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.

Пожалуйста, помогите нам распространить сообщение. --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 (бәхәс) 27 сен 2024, 18:57 (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) 22 окт 2024, 11:29 (UTC)

Proposal to enable the "Contribute" entry point in Tatar Wikipedia

Привет Tatar Wikipedians,

Apologies as this message is not in your language. Пожалуйста, помогите перевести на ваш язык.

The WMF Language and Product Localization team proposes enabling an entry point called "Contribute" to your Wikipedia.

The Contribute entry point is based on collaborative work with other product teams in the Wikimedia Foundation on Edit discovery, which validated the entry point as a persistent and constant path that contributors took to discover ways to contribute content in Wikipedia.

Therefore, enabling this entry point in your Wikipedia will help contributors quickly discover available tools and immediately click to start using them. This entry point is designed to be a central point for discovering contribution tools in Tatar Wikipedia.

Who can access it

Once it is enabled in your Wikipedia, newcomers can access the entry point automatically by just logging into their account, click on the User drop-down menu and choose the "Contribute" icon, which takes you to another menu where you will find a self-guided description of what you can do to contribute content, as shown in the image below. An option to "view contributions" is also available to access the list of your contributions.

For experienced contributors, the Contribute icon is not automatically shown in their User drop-down menu. They will still see the "Contributions" option unless they change it to the "Contribute" manually.

This feature is available in four Wikipedia (Albanian, Malayalam, Mongolian, and Tagalog). We have gotten valuable feedback that helped us improve its discoverability. Now, it is ready to be enabled in other Wikis. One major improvement was to make the entry point optional for experienced contributors who still want to have the "Contributions" entry point as default.          

We plan to enable it on mobile for Wikis, where the Section translation tool is enabled. In this way, we will provide a main entry point to the mobile translation dashboard, and the exposure can still be limited by targeting only the mobile platform for now. If there are no objections to having the entry point for mobile users from your community, we will enable it by 10th December 2024.

We welcome your feedback and questions in this thread on our proposal to enable it here. Suppose there are no objections, we will deploy the "Contribute" entry point in your Wikipedia.

We look forward to your response soon.

Thank you!

On behalf of the WMF Language and Product Localization team. UOzurumba (WMF) (бәхәс) 28 ноя 2024, 04:31 (UTC)