Wikipedia:Kedai Kopi (teknikal)/Archive4

Global preferences available for testing

Apologies for writing in English. Please help translate to your language.

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) 00:24, 27 Februari 2018 (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. [1]
• Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor. [2]
• 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. [3]
• 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. Terima kasih!

—Elitre (WMF)

20:56, 2 Mac 2018 (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) 21:09, 12 Mac 2018 (UTC)

We need your feedback to improve Lua functions

Hello,

(I’m sorry for writing in English. Please help translate to your language)

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.

Terima kasih! Lea Lacroix (WMDE) 08:55, 27 Mac 2018 (UTC)

Singaporean wikipedians

Hi (sorry to write in english), could you add your category of singaporean inhabitant contributors to the wikidata item ?

Thank you --CreativeC (bincang) 20:11, 12 April 2018 (UTC)

@CreativeC: Sorry for late reply, as for now Kategori:Ahli Wikipedia di Singapura (in English Category:Wikipedians in Singapore) is an empty category without anyone using it. If you are to be happen a Singaporean, then please add this category Kategori:Ahli Wikipedia di Singapura into your profile in this Malay Wikipedia. SNN95 Talk to me, beybeh! 23:52, 24 April 2018 (UTC)

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

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

Please help translate to your language

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

18:55, 4 Mei 2018 (UTC)

Pemadaman laman dan kecurian sejarah suntingan

Saya lihat ada beberapa pengguna bukan penyelia yang memadamkan laman dan memindahkan laman lain bagi menindan laman tersebut. Saya hairan adakah pengguna bukan penyelia boleh memadamkan laman. Juga saya bimbang berlakukan pencurian kredit, memadam sejarah penyunting asal dan menggantikan dengan suntingan yang dicurinya. Bagaimana kita boleh mengatasi masalah ini. Yosri (bincang) 10:37, 27 Mei 2018 (UTC)

Improvements coming soon on Watchlists

Hello

Sorry to use English. Please help translate to your language! Thank you.

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) 13:14, 7 Jun 2018 (UTC)

Update on page issues on mobile web

Update on page issues on mobile web

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

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

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

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

CKoerner (WMF) (talk) 20:58, 12 Jun 2018 (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) 14:38, 2 Julai 2018 (UTC)

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

(Please help translate to your language)

Hi all,

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

Thanks!
Tgr (talk) 10:50, 9 Julai 2018 (UTC) (via global message delivery)

Technical Advice IRC Meeting

We'd like to invite you to the weekly Technical Advice IRC meeting. The Technical Advice IRC Meeting (TAIM) is a weekly support event for volunteer developers. Every Wednesday, two full-time developers are available to help you with all your questions about Mediawiki, gadgets, tools and more! This can be anything from "how to get started" and "who would be the best contact for X" to specific questions on your project.

The Technical Advice IRC meeting is every Wednesday 3-4 pm UTC as well as on every first Wednesday of the month 11-12 pm UTC.

If you already know what you would like to discuss or ask, please add your topic to the next meeting: Technical Advice IRC meeting

Cheers, -- Michael Schönitzer (WMDE) (talk) 14:27, 30 July 2018 (UTC)

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) 21:28, 6 Ogos 2018 (UTC)

Cara untuk mendapatkan kebenaran hakcipta logo untuk dimuatnaik ke laman Commons

Salam. Bagaimana cara untuk mendapatkan kebenaran daripada pihak yang memegang hakcipta logo untuk dimuatnaik ke laman Commons?

Adakah pihak yang memegang hakcipta tersebut perlu menulis surat rasmi kepada Wikipedia untuk membenarkan logo mereka dipaparkan di Wikipedia?

Terima kasih.

Hasrolhashim (bincang) 04:47, 11 Ogos 2018 (UTC)

Saya tak rasa anda akan dapat, kerana ia terlalu liberal. Bagaimanapun rujuk Meminta kebenaran hakcipta. Yosri (bincang) 15:42, 11 Ogos 2018 (UTC)

Mengenai templat kotak info petempatan

Saya telah memindah balik kandungan Templat:Kotak info petempatan ke Templat:Infobox settlement, dan laman kotak info petempatan telah menjadi laman transklusi dengan parameter-parameter yang sudah diterjemah ke dalam bahasa Melayu. Biasanya saya menterjemah terus parameter-parameter Inggeris dalam laman templat itu sendiri tetapi templat-templat yang besar seperti {{Kotak info petempatan}} adalah terlalu rumit dan mempunyai sintaks parameter yang berulang-ulang, jadinya ia membuatkan penterjemahan parameter terlalu meleret-leret dan menjadikan kandungan laman tersebut lewah. Walau bagaimanapun, adalah tidak menjadi masalah jika {{infobox settlement}} masih digunakan kerana kedua-dua templat mempunyai asas kandungan yang sama, cuma {{kotak info petempatan}} adalah lebih disyorkan supaya sintaks rencana yang mengandungi templat ini nampak lebih 'Melayu'. Saya mempunyai rancangan untuk membuat perkara yang serupa kepada templat-templat kotak info yang lain, dan saya harap ianya dapat menggalakkan penyunting berbahasa Melayu untuk lebih biasa menyunting dalam Wikipedia ini, dan seterusnya memberigakan bahasa Melayu serta mengurangkan kebergantungan kepada bahasa Inggeris dalam aspek teknikal. Zulfadli51 (bincang) 10:35, 30 Oktober 2018 (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. [4]

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. Terima kasih!

—Whatamidoing (WMF) (talk)

14:17, 2 November 2018 (UTC)

mw.util.jsMessage

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

09:39, 26 November 2018 (UTC)