Википедия:Техник форум: юрамалар арасында аерма
| Юл номеры - 744: | Юл номеры - 744: | ||
== Tatarca Vikipedide silinecek sayfalar == |
== Tatarca Vikipedide silinecek sayfalar == |
||
Selam değerli editorlar. [[Төркем:Тиз_бетерүгә_кандидатлар|Silinecek sayfalar kategorisi]]nde ç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. Sayğılarımla--[[Кулланучы:Turkmen|Turkmen]] ([[Кулланучы бәхәсе:Turkmen|бәхәс]]) 10 ноя 2019, 08:31 (UTC) |
Selam değerli editorlar. [[:Төркем:Тиз_бетерүгә_кандидатлар|Silinecek sayfalar kategorisi]]nde ç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. Sayğılarımla--[[Кулланучы:Turkmen|Turkmen]] ([[Кулланучы бәхәсе:Turkmen|бәхәс]]) 10 ноя 2019, 08:31 (UTC) |
||
10 ноя 2019, 08:32 юрамасы
 Кайсы бүлегендә сорыйм дип белМӘгәндә, «Сораулар» бүлегенә языгыз. |
Техник форум - Википедиягә бәйле техник мәсьәләләр турында мәгълүматлар тупланылышы.
Фикер алышу, ярдәм сорау, яңалыклар һәм үзгәртүләр турында бәхәсләшү урыны өчен бәхәс бүлеген кара.
Викимедиа фонды техник төркеме атна-саен әзерли торган соңгы үзгәрешләр турындагы инглиз телендәге бюллетеньнәр җыелмасы белән шулай ук русча һәм кайбер башка телләргә тәрҗемәләре аркылы танышырга була. Шул бюллетеньнәр чыгуга, сезнең бәхәс битегезгә килүләре өчен аларга язылырга да була.
Шул ук төркемнең айлык җыелышларында катнашу, үткән җыелышлары протоколлары, отчетлары һәм презентацияләре белән танышу өчен монда кара (инглизчә).
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
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
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. Рәхмәт!
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 that you can review your changes visually?
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+Kon a PC, orCommand+Shift+Kon a Mac. It is based on the keyboard shortcut for making links, which isControl+KorCommand+Krespectively. [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=1to 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. Рәхмәт!
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.
- Read over the help page, it is brief and has screenshots
- Login or register an account on Beta English Wikipedia
- Visit Global Preferences and try enabling and disabling some settings
- Visit some other language and project test wikis such as English Wikivoyage, the Hebrew Wikipedia and test the settings
- 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 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. Рәхмәт!
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.
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. Рәхмәт!
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:
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:
- 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.
- 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.
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
- 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
- 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. Sayğılarımla--Turkmen (бәхәс) 10 ноя 2019, 08:31 (UTC)