Wikipidia:Warung Kupi

Salamat datang di Warung Kupi! Arsip Ngini adalah tutungkaran nang dipakai gasan mamandirakan masalah téknis, kabijakan, wan uprasi matan Wikipidia basa Banjar. Di sini, Pian kawa bapandir sagala kumintar wan saran tumatan hati nang paling dalam sahubungan lawan Wikipidia. Gasan masalah nang labih ngalih, Pian kawa mahubungi bubuhan pambakal Wikipidia sacara langsung. Jangan kada ingat mambariakan tanda tangan wan tanggal di uncit/akhir pasan Pian (nang caranya mangatikakan ~~~~ atawa mamicik tumbul "tanda tangan" di toolbar pambabakan). Hi! Welcome to Banjar Wikipedia's Village Pump. You don't speak Banjar? You can visit our Embassy page and leave a note in it's talk page or still leave a note here and we will respond as best as we can. Thanks!

Panulisan ngaran daerah

Ulun handak mausul, dimapa amunnya panulisan ngaran daerah mamakai hurup nang sebujurannya haja? misalnya kabupaten "Tabalong" jangan ditulis "Tabalung". Fani 00:10, 7 Agustus 2011 (ICT)

setuju Riemogerz 21:50, 28 Agustus 2011 (ICT)

Sabujurnya aslinya Tabaluung. Ezagren ^bapandir 12:43, 29 Agustus 2011 (ICT)

Pembicaraan mengenai Banjarpedia

Ulun rasa masalah Banjarpedia nang Ezagren usulakan tumatan Facebook, parlu jua kita pandirakan di Warung Kupi jua. Kayapa manurut hampian ? Riemogerz ۞ 12:15, 3 Uktubir 2011 (ICT)

Hudah dilaksanakan, bus! Ezagren ^bapandir 27 Disimbir 2011 20.23 (ICT)

Language support group for Banjar

The Wikimedia Foundation has brought together a new team of developers who are dedicated to language support. This team is to support all the languages and consequently it is not realistic to expect that the team members can provide proper support for your language. It is for this reason that we are looking for volunteers who will make up a language support team.

This language support team will be asked to provide us with information about their language. Such information may need to be provided either to us or on a website that we will indicate to you. Another activity will be to test software that will likely have an effect on the running of the MediaWiki software. We are looking for people who clearly identify their ability. Formal knowledge is definitely appreciated.

As much of the activity will be concentrated on translatewiki.net, it will be a plus when team members know how to localise at translatewiki.net. Thanks, Gmeijssen 16 Uktubir 2011 11.32 (ICT)

Usulan parubahan tampilan

Tampat Pamungutan Suara (TPS) sudah ditutup.

Tampat Pamungutan Suara (TPS) ditutup sabab sudah maliwati batas waktu pambarian suara. (Itihi hasil akhir pamungutan suara di bawah)

---

Usulan parubahan tampilan Tungkaran Tatambaian Wikipidia Bahasa Banjar, nang ulun rasa mulai bahari kadada barubah. Kaya apa amun ulun usulakan tampilan Tungkaran Tatambaian kaya ini itihi ja.

Salam. Riemogerz ۞ 30 Disimbir 2011 00.34 (ICT)

Tulung umpat mambari suara barupa sapakat (tulis {{sapakat}}), kada tahu (tulis {{kada tahu}}), atawa manulak (tulis {{manulak}}).

Bahasa Indonesia

Usulan perubahan tampilan Halaman Utama Wikipedia Bahasa Banjar, yang saya rasa dari dulu tidak ada perubahan. Bagaimana bila saya usulkan tampilan Halaman Utama seperti ini lihat disini.

Tolong ikut memberi suara berupa sepakat (tulis {{sapakat}}), tidak tau (tulis {{kada tahu}}), atau menolak (tulis {{manulak}}).

Katantuan

• Amun dalapan puluh parsin urang nang mambari suara disini sapakat, maka Tungkaran Tatambaian cagar diganti.
• Pamungutan suara ditutup tanggal 31 Disimbir 2011 (sakira tahun hanyar kita baisi tungkaran hanyar jua)

Bahasa Indonesia

• Kalau delapan puluh persen orang yang memberi suara disini sepakat, maka Halaman Utama akan diganti.
• Pemungutan suara ditutup tanggal 31 Desember 2011 (agar tahun baru kita punya halaman baru juga)

Nang sapakat

• Sapakat Riemogerz ۞ 30 Disimbir 2011 10.14 (ICT)
• Sapakat Naval Scene 30 Disimbir 2011 11.04 (ICT)
• Sapakat Cukup bagus, akan lebih fungsional jika File:Wikibar.png dijadikan pranala untuk menyunting bagian itu. Kenrick95 30 Disimbir 2011 15.02 (ICT)
•  Hakun haja ulun, langsung rilis malam tahun puga. Ezagren ^bapandir 31 Disimbir 2011 11.07 (ICT)
•  Hakun parubahan ka baik ulun hadangi --J Subhi ^{”pamandiran”} 31 Disimbir 2011 14.01 (ICT)
• Sapakat tampilannya jadi bagus dan menyediakan gambaran bagus tentang basa banjar, ada Pegonnya juga ... ^^, (120.166.47.87 31 Disimbir 2011 14.25 (ICT))^{Nang kada tadaptar kada baisi hak suara. RieMogerztalk 31 Disimbir 2011 15.14 (ICT)}
• Sapakat bagus..Stephensuleeman 31 Disimbir 2011 20.41 (ICT)

Kumintar

• Mas Kenrick95, bisa membantu untuk hal itu ? Saya sedikit kesulitan menyesuaikan rancangan tampilan Halaman Utama (Tungkaran Tatambaian) dengan konsep yang saya buat, karena ini kali pertamanya saya memberanikan diri untuk membuat sebuah lompatan besar :D Riemogerz ۞ 30 Disimbir 2011 21.33 (ICT)

  Sudah saya sunting halaman pengguna tempat Anda menampilkan rancangan Halaman Utama. Mohon disesuaikan dengan kebutuhan Wikipedia bahasa Banjar. Salam. Kenrick95 30 Disimbir 2011 21.47 (ICT)

  Terimakasih atas bantuannya, salam. RieMogerz^talk 31 Disimbir 2011 10.53 (ICT)

• Sepertinya proyek pergantian halaman utama untuk WBB ini adalah proyek dadakan, hahaha... Terlalu banyak kekurangan, padahal sudah ada yang sepakat ya... RieMogerz^talk 31 Disimbir 2011 16.10 (ICT)
• Masih ada benang merah dengan tampilan terdahulu, cuman saya lihat baberapa fitur kok jadi hilang ? Seperti fitur search ? Menurut pendapat saya, alangkah baiknya jika fitur tetap dipertahankan yang dirubah tampilannya saja. Saya mungkin vote setuju ^^ Thedonz 31 Disimbir 2011 19.43 (ICT)

  Menurut saya fitur pencarian sudah ada di sebelah kanan atas, disamping tab pindahkan maka dari itu, tidak perlu dikenakan lagi pada kotak selamat datang :) RieMogerz^talk 31 Disimbir 2011 21.14 (ICT)

Hasil

• Pemungutan suara resmi ditutup.
• Enam dari tujuh suara yang memberikan suaranya dinyatakan sah.
• Seratus persen yang memberikan suaranya menyatakan sepakat untuk melakukan pergantian halaman utama.
• Tampilan diterima untuk diganti menjadi seperti yang diajukan. Terimakasih.

RieMogerz^talk 31 Disimbir 2011 23.05 (ICT)

Saran gasan kumunitas

Kaya apa amun di Wikipidia Bahasa Banjar naiya kita ulah kamus, kada kaya di wiktionary pang. Tapi sakadar sagan kita mangatahui pangartiannya haja. Kayapa amun ma'ulahnya disini (Wikipidia:Kamus Banjar) ? RieMogerz^talk 31 Disimbir 2011 12.07 (ICT)

Usulan diatas dibatalakan haja gin lah, sudah tatamu Kamus nang bujurnya, jadi kada usah haja, kaina di wiktionary banjar haja,, haha,, RieMogerz^talk 31 Disimbir 2011 21.08 (ICT)

Imbah ulun itihi di id:wikipedia sakalinya ada kamus di wikipidia ? pranalanya naya, id:Wikipedia:Kamus. --- RieMogerZ 12 Januari 2012 00.48 (ICT)

Bagus amun kaitu. Ezagren ^bapandir 13 Januari 2012 10.39 (ICT)

Usulan gasan maulah katantuan di WBB

Ulun ma'usulakan amun kita baisi jua kariteria gasan artikal di WBB, jangan kaya artikal Bahasa Palémbang‎, nang manurut ulun kurang sasuai di andak di Wikipidia,, nang pasnya nintu amun manurut ulun diandak di Wikikamus atawa Wiktionary pang... kayapa amun manurut sampian barataan ?? - RieMogerz^talk 3 Januari 2012 19.39 (ICT)

Usulan bahasa

Kayapa amun pamakaian istilah ((Bahasa Indonesia)) versi diubah manjadi mudil.

- RieMogerz^pandiri 6 Januari 2012 17.43 (ICT)

Harus digagai 'hulu apa arti matan versi dan alasan paubahan manjadi mudil. Ezagren ^bapandir 13 Januari 2012 10.44 (ICT)

Parsamaan nang ulun tamui :

Manurut KBBI :

ver·si /vérsi/ n 1 bentuk terjemahan cerita, buku, dsb dl bahasa lain: Shakespeare -- Prancis; 2 model; menurut cara: film “Romeo and Juliet” -- India; 3 anggapan (pelukisan, penggambaran, dsb) tt sesuatu dr seseorang atau suatu sudut pandang: tt perkara pemerkosaan itu, -- polisi tidak sama dng -- saksi

Manurut Kamus Banjar Indonesia, penulis Abdul Djebar Hapip :

mudil (H) aneh, lucu --> model (K)

Parsamaannya ada di kata model, marga urang banjar kada tapi kawa basasambat hurup o lawan i, makanya manurut ulun sambatannya jadi mudil. --- RieMogerZ 13 Januari 2012 14.54 (ICT)

Usulan gasan pambabakan / paulahan tungkaran panting

Bahasa Banjar

Umpat saran gasan panulisan atawa panarjamahan bahasa matan bahasa Indunisia/Inggris ka bahasa Banjar tarutama tungkaran Wikipidia:(isi) atawa Patulungan:(isi) diharapakan dipandirakan lawan kumunitas, kayapa amun satiap panarjamahan nintu harus mandapatakan parsatujuan. Paling kada diadaakan pamungutan suara ?

Bahasa Indonesia

Sekedar saran untuk penulisan atau penerjemahan bahasa dari bahasa Indonesia/Inggris ke bahasa Banjar terutama halaman Wikipedia:(isi) atau Bantuan:(isi) diharapkan dibicarakan dengan komunitas, bagaimana kalau setiap penerjemahan itu harus mendapatkan persetujuan. Paling tidak diadakan pemungutan suara ?

Cuntuh : id:Wikipedia:Permohonan pendapat

- RieMogerz^pandiri 7 Januari 2012 00.56 (ICT)

Ayuha, mun kaitu, akun haja ulun. Ezagren ^bapandir 7 Januari 2012 08.58 (ICT)

Artinya kada kawa lagi babarang mausulakan atawa ma'artiakan tungkaran nang dimaksud ka bahasa banjar langsung, tanpa parsatujuan bubuhan pamakai WBB. Kaya itu kah pambakal ?? --- RieMogerZ 7 Januari 2012 16.09 (ICT)

Amun artikal, pambakal bibasakan manarjamahakan sasuai kamampuan. Mun samunyaan dipakai pamungutan suara, lapah lah pamilu di sia. Ezagren ^bapandir 8 Januari 2012 01.18 (ICT)

Amun artikal, ulun kada masalah siapa haja kawa mambabak sasuai kamampuan. Tapi amun tungkaran nang riskan cuntuhnya kaya artikal Patulung:Isi, Wikipidia:Pambakal, atawa nang lainnya tu nah, harus malalui pamilu kayapa ? Ayuja nang bahari tuh, biar ae sudah, tapi amun nang dudi kada bulih lagi ? --- RieMogerZ 9 Januari 2012 23.00 (ICT)

Tinjau

Saya minta tolong kepada pengurus untuk memeriksa terjemahan saya pada halaman berikut

• Patulung:Isi/Mambabak Wikipidia
• Patulung:Isi/Manjalajahi Wikipidia
• Patulung:HotCat
• Citakan:Pangatas tungkaran patulung

Ilham Cahyo Nugroho ^{Bapandir I'am} 8 Januari 2012 15.02 (ICT)

Untuk Pengurus:Pembukaan Keanggotaan Baru Wikimedia Indonesia

Halo Pengurus,

Pada tanggal 31 Januari hingga 15 Februari 2012, Wikimedia Indonesia akan membuka kembali pendaftaran keanggotaan baru. Untuk itu, saya ingin meminta izin dan memohon bantuan dari para pengurus untuk memasang site notice selama tanggal tersebut dengan pranala menuju Halaman Keanggotaan dan menyertakan kontak info@wikimedia.or.id untuk mendaftar dan mendapatkan informasi lebih lanjut.

Terima kasih. 06Ivonne 23 Januari 2012 23.40 (ICT)

Silakan mengirim pesannya yang seperti apa agar segera dipasang di "sitenotice". Ezagren ^bapandir 24 Januari 2012 19.11 (ICT)

Request for adminship

Bagaimana syarat dan kriteria menjadi Pengurus dan Birokrat di Wikipedia bahasa Banjar ini? Soalnya Wikipedia ini belum punya birokrat. --Dede2008 (pandir) 24 Juli 2012 17.35 (ICT)

Kalau syarat dan kriteria menjadi pengurus di sini, tentunya selain bisa berbahasa Banjar dengan baik, juga aktif berkontribusi sehingga memenuhi PP (Paubahan Pahanyarnya). Untuk syarat birokrat, adalah menjadi pengurus dahulu. Setiap pengguna boleh mengajukan calon birokrat yang masih berstatus pengurus. Ezagren ^bapandir 25 Juli 2012 02.14 (ICT)

Kalau saya boleh berkomentar, saya pikir birokrat di WBB masih belum diperlukan, mengingat pengurus WBB juga tidak terlalu banyak, bahkan bisa dibilang tidak banyak. Namun tidak menutup kemungkinan nanti akan ada birokrat :) Tapi kalau saya pikir belum akan terlalu berguna menjadi birokrat di WBB, jadi ya tunggu nanti aja, entah gimana komentar yang lain :) RieMogerZ 30 Agustus 2012 14.23 (ICT)

Wikimania 2014 di Bukittinggi

Salam!

Kami dari Wikipedia Bahasa Indonesia sedang mengajukan proposal untuk Wikimania 2014 di Bukittinggi, Sumatera Barat, Indonesia. Untuk itu, kami membutuhkan dukungan para Wikipedian Banjar.

Jika berhasil, Wikimania ini untuk pertama kali akan diselenggarakan di Asia Tenggara. Perlu juga kami beritahukan bahwa dua kota lain yang dipertaruhkan adalah London dan Sydney, yang tentu saja jauh dari Indonesia.

Sejauh ini, tawaran ini masih tidak resmi. Kerjasama para Wikipedian Banjar sangat diperlukan, untuk menyunting halaman proposal kami, menyarankan beberapa perubahan, atau menandatangani petisi dukungan. Kami tunggu!

Kunjungi halaman proposal Wikimania 2014 di Bukittinggi di sini dan tandatangani dukungan Anda!

Salam Wikipedia, ~ ~ ~ ~

Bantuan terjemahan

Mohon bantuan terjemah http://ms.wikipedia.org/wiki/1_SGM kepada bahasa Banjar secara lengkap untuk diguna sebagai template bagi rencana lainnya. Yosri (pandir) 12 Pibuari 2013 01.26 (ICT)

Catalan Culture Challenge

I apologize if this message is not in your language. Please help translate it.

The Catalan-speaking world... Want to find out more? From March 16 to April 15 we will organise the Catalan Culture Challenge, a Wikipedia editing contest in which victory will go to those who start and improve the greatest number of articles about 50 key figures of Catalan culture. You can take part by creating or expanding articles on these people in your native language (or any other one you speak). It would be lovely to have you on board. :-)

We look forward to seeing you! Salam Wikipedia

Amical Wikimedia--Kippelboy (pandir) 15 Marit 2014 15.25 (ICT)

No one needs free knowledge in Esperanto

There is a current discussion on German Wikipedia on a decision of Asaf Bartov, Head of WMF Grants and Global South Partnerships, Wikimedia Foundation, who rejected a request for funding a proposal from wikipedians from eowiki one year ago with the explanation the existence, cultivation, and growth of the Esperanto Wikipedia does not advance our educational mission. No one needs free knowledge in Esperanto. On meta there has also started a discussion about that decision. --Holder (pandir) 5 Mai 2014 16.37 (ICT)

VisualEditor global newsletter—June 2014

This is a one-time mailing to projects that may need this information. Future newsletters will be available as opt-in only. To receive future newsletters (about one per month), please add your page to the subscribers' list at m:VisualEditor/Newsletter. You're welcome to translate to your language.

Did you know?

The character formatting menu, or "Gaya teks" menu lets you set bold, italic, and other text styles. "Clear formatting" removes all text styles and removes links to other pages.

Do you think that clear formatting should remove links? Are there changes you would like to see for this menu? Share your opinion at MediaWiki.org.

The user guide has information about how to use VisualEditor.

The VisualEditor team is mostly working to fix bugs, improve performance, reduce technical debt, and other infrastructure needs. You can find on Mediawiki.org weekly updates detailing recent work.

• They have moved the "Pintasan papan tombol" link out of the "Opsi halaman" menu, into the "Bantuan" menu. Within dialog boxes, buttons are now more accessible (via the Tab key) from the keyboard.
• You can now see the target of the link when you click on it, without having to open the inspector.
• The team also expanded TemplateData: You can now add a parameter type  "date" for dates and times in the ISO 8601 format, and  "boolean" for values which are true or false. Also, templates that redirect to other templates (like {{citeweb}} → {{cite web}}) now get the TemplateData of their target (bug 50964). You can test TemplateData by editing mw:Template:Sandbox/doc.
• Category: and File: pages now display their contents correctly after saving an edit (bug 65349, bug 64239)
• They have also improved reference editing: You should no longer be able to add empty citations with VisualEditor (bug 64715), as with references. When you edit a reference, you can now empty it and click the "use an existing reference" button to replace it with another reference instead. 
• It is now possible to edit inline images with VisualEditor. Remember that inline images cannot display captions, so existing captions get removed. Many other bugs related to images were also fixed.
• You can now add and edit {{DISPLAYTITLE}} and __DISAMBIG__ in the "Opsi halaman" menu, rounding out the full set of page options currently planned.
• The tool to insert special characters is now wider and simpler.

Looking ahead

The VisualEditor team has posted a draft of their goals for the next fiscal year. You can read them and suggest changes on MediaWiki.org.

The team posts details about planned work on VisualEditor's roadmap. You will soon be able to drag-and-drop text as well as images. If you drag an image to a new place, it won't let you place it in the middle of a paragraph. All dialog boxes and windows will be simplified based on user testing and feedback. The VisualEditor team plans to add autofill features for citations. Your ideas about making referencing quick and easy are still wanted. Support for upright image sizes is being developed. The designers are also working on support for viewing and editing hidden HTML comments and adding rows and columns to tables.

Supporting your wiki

Please read VisualEditor/Citation tool for information on configuring the new citation template menu, labeled "⧼visualeditor-toolbar-cite-label⧽". This menu will not appear unless it has been configured on your wiki.

If you speak a language other than English, we need your help with translating the user guide. The guide is out of date or incomplete for many languages, and what's on your wiki may not be the most recent translation. Please contact us if you need help getting started with translation work on MediaWiki.org.

VisualEditor can be made available to most non-Wikipedia projects. If your community would like to test VisualEditor, please contact product manager James Forrester or file an enhancement request in Bugzilla.

Please share your questions, suggestions, or problems by posting a note at mw:VisualEditor/Feedback or by joining the office hours on Saturday, 19 July 2014 at 21:00 UTC (daytime for the Americas and Pacific Islands) or on Thursday, 14 August 2014 at 9:00 UTC (daytime for Europe, Middle East, Asia).

If you'd like to get this newsletter on your own page (about once a month), please subscribe at Meta (or at w:en:Wikipedia:VisualEditor/Newsletter for English Wikipedia only). Thank you! --Elitre (WMF), 26 Juni 2014 05.33 (ICT)

Updates related to VisualEditor

Please help translate this message in your language. Thanks :)

Hi, everybody. This is a reminder that we invite you to discuss VisualEditor's recent development and plans ahead during the next office hours with James Forrester (Product Manager):

• Thursday, August 14, 9:00 UTC;
• Thursday, September 18, 16:00 UTC.

If you are not able to attend but have a question for James, you can leave your question at mediawiki.org or on my talk page by the day before, and I will try to get a response. We plan to continue these monthly sessions as long as there is community interest, and to announce them through the VisualEditor global newsletter as well (please subscribe your talk page there to get the latest news about the software).

Most of the VisualEditor team will be at Wikimania in London in August! You'll be able to meet the developers during the Hackaton or at the following sessions:

• VisualEditor — helping users edit more easily, Saturday, August 9;
• VisualEditor — engineering against the odds, Sunday, August 10.

WMF community liaisons will share a booth with community advocates at the Community Village and look forward to talking to you there. Thanks for your attention! --User:Elitre (WMF) 31 Juli 2014 23.02 (ICT)

VisualEditor global newsletter—July and August 2014

The VisualEditor team is currently working mostly to fix bugs, improve performance, reduce technical debt, and other infrastructure needs. You can find on Mediawiki.org weekly updates detailing recent work.

Dialog boxes in VisualEditor have been re-designed to use action words instead of icons. This has increased the number of items that need to be translated. The user guide is also being updated.

The biggest visible change since the last newsletter was to the dialog boxes. The design for each dialog box and window was simplified. The most commonly needed buttons are now at the top. Based on user feedback, the buttons are now labeled with simple words (like "Cancel" or "Done") instead of potentially confusing icons (like "<" or "X"). Many of the buttons to edit links, images, and other items now also show the linked page, image name, or other useful information when you click on them.

• Hidden HTML comments (notes visible to editors, but not to readers) can now be read, edited, inserted, and removed. A small icon (a white exclamation mark on a dot) marks the location of each comments. You can click on the icon to see the comment.
• You can now drag and drop text and templates as well as images. A new placement line makes it much easier to see where you are dropping the item. Images can no longer be dropped into the middle of paragraphs.
• All references and footnotes (<ref> tags) are now made through the "⧼visualeditor-toolbar-cite-label⧽" menu, including the "⧼visualeditor-dialogbutton-reference-tooltip⧽" (manual formatting) footnotes and the ability to re-use an existing citation, both of which were previously accessible only through the "Sisipkan" menu. The "⧼visualeditor-dialogbutton-referencelist-tooltip⧽" is still added via the "Sisipkan" menu.
• When you add an image or other media file, you are now prompted to add an image caption immediately. You can also replace an image whilst keeping the original caption and other settings.
• All tablet users visiting the mobile web version of Wikipedias will be able to opt-in to a version of VisualEditor from 14 August. You can test the new tool by choosing the beta version of the mobile view in the Settings menu.
• The link tool has a new "Open" button that will open a linked page in another tab so you can make sure a link is the right one.
• The "Cancel" button in the toolbar has been removed based on user testing. To cancel any edit, you can leave the page by clicking the Read tab, the back button in your browser, or closing the browser window without saving your changes.

Looking ahead

The team posts details about planned work on the VisualEditor roadmap. The VisualEditor team plans to add auto-fill features for citations soon. Your ideas about making referencing quick and easy are still wanted. Support for upright image sizes is being developed. The designers are also working on support for adding rows and columns to tables. Work to support Internet Explorer is ongoing.

Feedback opportunities

The Editing team will be making two presentations this weekend at Wikimania in London. The first is with product manager James Forrester and developer Trevor Parscal on Saturday at 16:30. The second is with developers Roan Kattouw and Trevor Parscal on Sunday at 12:30. There is a VisualEditor Translation Sprint going on during Wikimania; whether you're in London or not, any contributions are welcome!

Please share your questions, suggestions, or problems by posting a note at the VisualEditor feedback page or by joining the office hours discussion on Thursday, 14 August 2014 at 09:00 UTC (daytime for Europe, Middle East and Asia) or on Thursday, 18 September 2014 at 16:00 UTC (daytime for the Americas; evening for Europe).

If you'd like to get this newsletter on your own page (about once a month), please subscribe at w:en:Wikipedia:VisualEditor/Newsletter for English Wikipedia only or at Meta for any project. Thank you! --Elitre (WMF), 9 Agustus 2014 21.40 (ICT)

Help for translate

Hello and sorry for writing in English. Can anyone help me translate a small article (2 paragraphs) from English to your language? Please, fell free to answer in my talk page in your wiki. Thanks! Xaris333 (pandir) 12 Agustus 2014 07.41 (ICT)

VisualEditor News #8—2014

Did you know?

TemplateData is a separate program that organizes information about the parameters that can be used in a template. VisualEditor reads that data, and uses it to populate its simplified template dialogs.

With the new TemplateData editor, it is easier to add information about parameters, because the ones you need to use are pre-loaded.

See the help page for TemplateData for more information about adding TemplateData. The user guide has information about how to use VisualEditor.

Since the last newsletter, the Editing team has reduced technical debt, simplified some workflows for template and citation editing, made major progress on Internet Explorer support, and fixed over 125 bugs and requests. Several performance improvements were made, especially to the system around re-using references and reference lists. Weekly updates are posted on Mediawiki.org.

There were three issues that required urgent fixes: a deployment error that meant that many buttons didn't work correctly (bugs 69856 and 69864), a problem with edit conflicts that left the editor with nowhere to go (bug 69150), and a problem in Internet Explorer 11 that replaced some categories with a link to the system message MediaWiki:Badtitletext (bug 70894) when you saved. The developers apologize for the disruption, and thank the people who reported these problems quickly.

Increased support for devices and browsers

Internet Explorer 10 and 11 users now have access to VisualEditor. This means that about 5% of Wikimedia's users will now get an "Edit" tab alongside the existing "Edit source" tab. Support for Internet Explorer 9 is planned for the future.

Tablet users browsing the site's mobile mode now have the option of using a mobile-specific form of VisualEditor. More editing tools, and availability of VisualEditor on smartphones, is planned for the future. The mobile version of VisualEditor was tweaked to show the context menu for citations instead of basic references (bug 68897). A bug that broke the editor in iOS was corrected and released early (bug 68949). For mobile tablet users, three bugs related to scrolling were fixed (bug 66697, bug 68828, bug 69630). You can use VisualEditor on the mobile version of Wikipedia from your tablet by clicking on the cog in the top-right when editing a page and choosing which editor to use.

TemplateData editor

The tool for editing TemplateData has been deployed to 30 more Wikipedias this week. Other Wikipedias and some other projects may receive access next month. This tool makes it easier to add TemplateData to the template's documentation. When the tool is enabled, it will add a button above every editing window for a template (including documentation subpages). To use it, edit the template page or a subpage, and then click the "Kelola DataTemplat" button at the top. Read the help page for TemplateData. You can test the TemplateData editor in a sandbox at Mediawiki.org. Remember that TemplateData should be placed either on a documentation subpage or on the template page itself. Only one block of TemplateData will be used per template.

Other changes

Several interface messages and labels were changed to be simpler, clearer, or shorter, based on feedback from translators and editors. The formatting of dialogs was changed, and more changes to the appearance will be coming soon, when VisualEditor implements the new MediaWiki theme from Design. (A preview of the theme is available on Labs for developers.) The team also made some improvements for users of the Monobook skin that improved the size of text in toolbars and fixed selections that overlapped menus.

VisualEditor-MediaWiki now supplies the mw-redirect and mw-disambig class on links to redirects and disambiguation pages, so that user gadgets that colour in these types of links can be created.

Templates' fields can be marked as 'required' in TemplateData. If a parameter is marked as required, then you cannot delete that field when you add a new template or edit an existing one (bug 60358).

Language support improved by making annotations use bi-directional isolation (so they display correctly with cursoring behaviour as expected) and by fixing a bug that crashed VisualEditor when trying to edit a page with a dir attribute but no lang set (bug 69955).

Looking ahead

The team posts details about planned work on the VisualEditor roadmap. The VisualEditor team plans to add auto-fill features for citations soon, perhaps in late October.

The team is also working on support for adding rows and columns to tables, and early work for this may appear within the month. Please comment on the design at Mediawiki.org.

In the future, real-time collaborative editing may be possible in VisualEditor. Some early preparatory work for this was recently done.

Supporting your wiki

At Wikimania, several developers gave presentations about VisualEditor. A translation sprint focused on improving access to VisualEditor was supported by many people. Deryck Chan was the top translator. Special honors also go to संजीव कुमार (Sanjeev Kumar), Robby, Takot, Bachounda, Bjankuloski06 and Ата. A summary of the work achieved by the translation community is available. Thank you all for your work.

This was the first translatable VisualEditor newsletter, so thanks to everybody who made this possible! If it hasn't been delivered in your language, and you'd like to help with translations in the future, please subscribe to the Translators mailing list or contact Elitre (WMF), so that you will be notified when the next issue is due.

VisualEditor can be made available to most non-Wikipedia projects. If your community would like to test VisualEditor, please contact product manager James Forrester or file an enhancement request in Bugzilla.

Please join the office hours on Saturday, 18 October 2014 at 18:00 UTC (daytime for the Americas; evening for Africa and Europe) and on Wednesday, 19 November at 16:00 UTC on IRC.

Give feedback on VisualEditor at mw:VisualEditor/Feedback. Subscribe or unsubscribe at Meta. Thank you! —Elitre (WMF)

13 Uktubir 2014 16.49 (ICT)

Languages in censuses

Hello, Dear wikipedians. I invite you to edit and improve this article and to add information about your and other country.--Kaiyr (pandir) 31 Uktubir 2014 18.19 (ICT)

Global AbuseFilter

Hello,

AbuseFilter is a MediaWiki extension used to detect likely abusive behavior patterns, like pattern vandalism and spam. In 2013, Global AbuseFilters were enabled on a limited set of wikis including Meta-Wiki, MediaWiki.org, Wikispecies and (in early 2014) all the "small wikis". Recently, global abuse filters were enabled on "medium sized wikis" as well. These filters are currently managed by stewards on Meta-Wiki and have shown to be very effective in preventing mass spam attacks across Wikimedia projects. However, there is currently no policy on how the global AbuseFilters will be managed although there are proposals. There is an ongoing request for comment on policy governing the use of the global AbuseFilters. In the meantime, specific wikis can opt out of using the global AbuseFilter. These wikis can simply add a request to this list on Meta-Wiki. More details can be found on this page at Meta-Wiki. If you have any questions, feel free to ask on m:Talk:Global AbuseFilter.

Thanks,

PiRSquared17, Glaisher

— 15 Nupimbir 2014 00.36 (ICT)

VisualEditor News #9—2014

Did you know?

VisualEditor is also available on the mobile version of Wikipedia. Log in and click the pencil icon to open the page you want to edit. Click on the gear-shaped settings button in the upper-right corner to pick which editor to use. Choose "⧼Mobile-frontend-editor-visual-editor⧽" to use VisualEditor, or "⧼Mobile-frontend-editor-source-editor⧽" to use the wikitext editor.

It will remember whether you used wikitext or VisualEditor, and use the same editor the next time you edit an article.

The user guide has information about how to use VisualEditor. Not all features are available on the mobile website.

Since the last newsletter, the Editing Team has fixed many bugs and requests, and worked on support for editing tables and for using non-Latin languages. Their weekly updates are posted on Mediawiki.org. Informal notes from the recent quarterly review were posted on Meta.

Recent improvements

Basic support for inserting tables and changing the number of rows and columns in them was just introduced to Wikipedias. Advanced features, like dragging columns to different places, will be added later.

To help editors find the most important items more quickly, some items in the toolbar menus are now hidden behind a "Lainnya" item, such as "Garis bawah" in the styling menu.

The French Wikipedia should see better search results for links, templates, and media because the new search engine was turned on for everyone there. This change is expected at the Chinese and German Wikipedias this week, and the following week at the English Wikipedia.

The "pawn" system has been mostly replaced. Bugs in this system sometimes added a chess pawn character to wikitext. The replacement provides better support for non-Latin languages, with full support hopefully coming soon.

VisualEditor is now provided to editors who use Internet Explorer 10 or 11 on desktop and mobile devices. Internet Explorer 9 is not supported yet.

The keyboard shortcuts for items in the toolbar menus are now shown in the menus.

VisualEditor will replace the existing design with a new theme from the User Experience/Design group. The appearance of dialog boxes has already changed in the mobile version. The appearance on desktops will change soon. You are welcome to compare the old "Apex" design and the new "MediaWiki" theme which will replace it.

Several bugs were fixed for internal and external links. Improvements to MediaWiki's search solved an annoying problem: If you searched for the full name of the page or file that you wanted to link, sometimes the search engine could not find the page. A link inside a template to a local page that does not exist will now show red, exactly as it does when reading the page. Due to an error, for about two weeks this also affected all external links inside templates. Opening an auto-numbered link node like [1] with the keyboard used to open the wrong link tool. These problems have all been fixed.

TemplateData

The tool for quickly editing TemplateData has been deployed to all Wikimedia Foundation wikis on Thursday, 6 November. This tool was already available on the biggest 40 Wikipedias, and now all wikis will have access to it. This tool makes it easier to add TemplateData to the template's documentation. When the tool is enabled, it will add a button above every editing window for a template (including documentation subpages). To use it, edit the template or a subpage, and then click the "Kelola DataTemplat" button at the top. Read the help page for TemplateData to learn more about it. You can test the TemplateData editor in a sandbox at Mediawiki.org. Remember that TemplateData should be placed either on a documentation subpage or on the template page itself. Only one block of TemplateData will be used per template.

You can use the new autovalue setting to pre-load a value into a template. This can be used to substitute dates, as in this example, or to add the most common value for that parameter. The autovalue can be overridden by the editor, by typing something else in the field.

In TemplateData, you may define a parameter as "required". The template dialog box in VisualEditor will warn editors if they leave a "required" parameter empty, and they will not be able to delete that parameter. If the template can function without this parameter, then please mark it as "disarankan" or "opsional" in TemplateData instead.

Looking ahead

The VisualEditor team plans to add auto-fill features for citations soon. The appearance of the media search dialog will improve, to make picking between possible images easier and more visual. The team posts details about planned work on the VisualEditor roadmap.

The user guide is being updated to add information about editing tables. The translations of the user guide for most languages except Spanish, French, and Dutch are significantly out of date. Please help complete the current translations for users who speak your language. Talk to us if you need help exporting the translated guide to your wiki.

You can influence VisualEditor's design! Tell the VisualEditor team what you want changed during the office hours via IRC. The next sessions are on Wednesday, 19 November at 16:00 UTC and on Wednesday 7 January 2015 at 22:00 UTC. You can also share your ideas at mw:VisualEditor/Feedback.

Also, user experience researcher Abbey Ripstra is looking for editors to show her how they edit Wikipedia. Please sign up for the research program if you would like to hear about opportunities.

If you would like to help with translations of this newsletter, please subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Subscribe or unsubscribe at Meta. Thank you! —Elitre (WMF)

15 Nupimbir 2014 06.29 (ICT)

VisualEditor News #10—2014

Did you know?

Basic table editing is now available in VisualEditor. You can add and remove rows and columns from tables at the click of a button.

The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has fixed many bugs and worked on table editing and performance. Their weekly status reports are posted on mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.

VisualEditor was deployed to several hundred remaining wikis as an opt-in beta feature at the end of November, except for most Wiktionaries (which depend heavily upon templates) and all Wikisources (which await integration with ProofreadPage).

Recent improvements

Basic support for editing tables is now available. You can add and delete tables, add and remove rows and columns, set or remove a caption for a table, and merge cells together. To change the contents of a cell, double-click inside it. More features will be added in the coming months. In addition, VisualEditor now ignores broken, invalid rowspan and colspan elements, instead of trying to repair them.

You can now use find and replace in VisualEditor, reachable through the tool menu or by pressing ^ Ctrl+F or ⌘ Cmd+F.

You can now create and edit simple <blockquote> paragraphs for quoting and indenting content. This changes a "Paragraf" into a "Blok kutipan".

Some new keyboard sequences can be used to format content. At the start of the line, typing "* " will make the line a bullet list; "1." or "#" will make it a numbered list; "==" will make it a section heading; ": " will make it a blockquote. If you didn't mean to use these tools, you can press undo to undo the formatting change.

There are also two other keyboard sequences: "[[" for opening the link tool, and "{{" for opening the template tool, to help experienced editors. The existing standard keyboard shortcuts, like ^ Ctrl+K to open the link editor, still work.

If you add a category that has been redirected, then VisualEditor now adds its target. Categories without description pages show up as red.

You can again create and edit galleries as wikitext code.

Looking ahead

The current VisualEditor design will be replaced with a new theme designed by the User Experience group. The new theme will be visible for desktop systems at mediawiki.org in late December and on other sites in early January. (You can see a developer preview of the old "Apex" theme and the new "MediaWiki" one which will replace it.)

The Editing team plans to add auto-fill features for citations in January.

Planned changes to the media search dialog will make choosing between possible images easier.

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• Translations of the user guide for most languages are outdated. Only Ukrainian, Portuguese, Spanish, French, and Dutch translations are nearly current. Please help complete the current translations for users who speak your language.
• Talk to the Editing team during the office hours via IRC. The next session is on Wednesday, 7 January 2015 at 22:00 UTC.
• File requests for language-appropriate "Tebal" and "Cetak miring" icons for the character formatting menu in Phabricator.
• The design research team wants to see how real editors work. Please sign up for their research program.
• If you would like to help with translations of this newsletter, please subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Subscribe or unsubscribe at Meta. Thank you!

— Elitre (WMF)

27 Disimbir 2014 01.59 (ICT)

VisualEditor News #1—2015

Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's appearance, the coming Citoid reference service, and support for languages with complex input requirements. Status reports are posted on mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.

The Wikimedia Foundation has named its top priorities for this quarter (January to March). The first priority is making VisualEditor ready for deployment by default to all new users and logged-out users at the remaining large Wikipedias. You can help identify these requirements. There will be weekly triage meetings which will be open to volunteers beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC). Tell Vice President of Engineering Damon Sicore, Product Manager James Forrester and other team members which bugs and features are most important to you. The decisions made at these meetings will determine what work is necessary for this quarter's goal of making VisualEditor ready for deployment to new users. The presence of volunteers who enjoy contributing MediaWiki code is particularly appreciated. Information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins.

Due to some breaking changes in MobileFrontend and VisualEditor, VisualEditor was not working correctly on the mobile site for a couple of days in early January. The teams apologize for the problem.

Recent improvements

The new design for VisualEditor aligns with MediaWiki's Front-End Standards as led by the Design team. Several new versions of the OOjs UI library have also been released, and these also affect the appearance of VisualEditor and other MediaWiki software extensions. Most changes were minor, like changing the text size and the amount of white space in some windows. Buttons are consistently color-coded to indicate whether the action:

• starts a new task, like opening the Simpan halaman dialog: blue ,
• takes a constructive action, like inserting a citation: green ,
• might remove or lose your work, like removing a link: red , or
• is neutral, like opening a link in a new browser window: gray .

The TemplateData editor has been completely re-written to use a different design based on the same OOjs UI system as VisualEditor. (T67815, T73746.) This change fixed a couple of existing bugs and improved usability. (T73077, T73078.)

Search and replace in long documents is now faster. It does not highlight every occurrence if there are more than 100 on-screen at once.(T78234.)

Editors at the Hebrew and Russian Wikipedia requested the ability to use VisualEditor in the "Article Incubator" or drafts namespace. (T86688, T87027.) If your community would like VisualEditor enabled on another namespace on your wiki, then you can file a request in Phabricator. Please include a link to a community discussion about the requested change.

Looking ahead

The Editing team will soon add auto-fill features for citations. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to contribute to the Citoid service's definitions for each website, to improve precision and reduce the need for manual corrections.

We will need editors to help test the new design of the special character inserter, especially if you speak Welsh, Breton, or another language that uses diacritics or special characters extensively. The new version should be available for testing next week. Please contact User:Whatamidoing (WMF) if you would like to be notified when the new version is available. After the special character tool is completed, VisualEditor will be deployed to all users at Phase 5 Wikipedias. This will affect about 50 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh. The date for this change has not been determined.

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• Please help complete translations of the user guide for users who speak your language.
• Join the weekly bug triage meetings beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC); information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins, and you can also contact James F. to learn more about this initiative.
• Talk to the Editing team during the office hours via IRC. The next session is on Thursday, 19 February 2015 at 19:00 UTC.
• Subscribe or unsubscribe at Meta. If you would like to help with translations of this newsletter, please subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

— Elitre (WMF)

6 Pibuari 2015 01.30 (ICT)

VisualEditor News #2—2015

Did you know?

With Citoid in VisualEditor, you click the 'book with bookmark' icon and paste in the URL for a reliable source:

Citoid looks up the source for you and returns the citation results. Click the green "Insert" button to accept its results and add them to the article:

After inserting the citation, you can change it. Select the reference, and click the "Edit" button in the context menu to make changes.

The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's performance, the Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.

The weekly task triage meetings continue to be open to volunteers, each Wednesday at 11:00 (noon) PDT (18:00 UTC). You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug. Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal.

Recent improvements

VisualEditor is now substantially faster. In many cases, opening the page in VisualEditor is now faster than opening it in the wikitext editor. The new system has improved the code speed by 37% and network speed by almost 40%.

The Editing team is slowly adding auto-fill features for citations. This is currently available only at the French, Italian, and English Wikipedias. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to improve precision and reduce the need for manual corrections by contributing to the Citoid service's definitions for each website.

Citoid requires good TemplateData for your citation templates. If you would like to request this feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.

The special character inserter has been improved, based upon feedback from active users. After this, VisualEditor was made available to all users of Wikipedias on the Phase 5 list on 30 March. This affected 53 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh.

Work continues to support languages with complex requirements, such as Korean and Japanese. These languages use input method editors ("IMEs”). Recent improvements to cursoring, backspace, and delete behavior will simplify typing in VisualEditor for these users.

The design for the image selection process is now using a "masonry fit" model. Images in the search results are displayed at the same height but at variable widths, similar to bricks of different sizes in a masonry wall, or the "packed" mode in image galleries. This style helps you find the right image by making it easier to see more details in images.

You can now drag and drop categories to re-arrange their order of appearance ​on the page.

The pop-up window that appears when you click on a reference, image, link, or other element, is called the "context menu". It now displays additional useful information, such as the destination of the link or the image's filename. The team has also added an explicit "Edit" button in the context menu, which helps new editors open the tool to change the item.

Invisible templates are marked by a puzzle piece icon so they can be interacted with. Users also will be able to see and edit HTML anchors now in section headings.

Users of the TemplateData GUI editor can now set a string as an optional text for the 'deprecated' property in addition to boolean value, which lets you tell users of the template what they should do instead. (T90734)

Looking ahead

The special character inserter in VisualEditor will soon use the same special character list as the wikitext editor. Admins at each wiki will also have the option of creating a custom section for frequently used characters at the top of the list. Instructions for customizing the list will be posted at mediawiki.org.

The team is discussing a test of VisualEditor with new users at the English Wikipedia, to see whether they have met their goals of making VisualEditor suitable for those editors. The timing is unknown, but might be relatively soon. (T90666)

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• Can you translate from English into any other language? Please check this list to see whether more interface translations are needed for your language. Contact us to get an account if you want to help!
• The design research team wants to see how real editors work. Please sign up for their research program.
• File requests for language-appropriate "Tebal" and "Cetak miring" icons for the character formatting menu in Phabricator.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. 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. Thank you!

— Elitre (WMF)

11 April 2015 02.48 (ICT)

Galicia 20 - 20 Challenge

Wikipedia:Galicia 20 - 20 Challenge is a public writing competition which will improve and translate this list of 20 really important articles into as many languages as possible. Everybody can help in any language to collaborate on writing and/or translating articles related to Galicia. To participate you just need to sign up here. Thank you very much.--Breogan2008 (pandir) 9 Juni 2015 17.04 (ICT)

VisualEditor News #3—2015

Did you know?

When you click on a link to an article, you now see more information:

The link tool has been re-designed:

There are separate tabs for linking to internal and external pages. The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has created new interfaces for the link and citation tools and fixed many bugs and changed some elements of the design. Some of these bugs affected users of VisualEditor on mobile devices. Status reports are posted on mediawiki.org. The worklist for April through June is available in Phabricator.

A test of VisualEditor's effect on new editors at the English Wikipedia has just completed the first phase. During this test, half of newly registered editors had VisualEditor automatically enabled, and half did not. The main goal of the study is to learn which group was more likely to save an edit and to make productive, unreverted edits. Initial results will be posted at Meta later this month.

Recent improvements

Auto-fill features for citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now created inside a single tool. Inside that tool, choose the tab you want (⧼citoid-citeFromIDDialog-mode-auto⧽, ⧼citoid-citeFromIDDialog-mode-manual⧽, or ⧼citoid-citeFromIDDialog-mode-reuse⧽). The cite button is now labeled with the word "⧼visualeditor-toolbar-cite-label⧽" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "⧼Citoid-citeFromIDDialog-lookup-button⧽", for the submit button.

The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and appropriate icons for disambiguation pages, redirect pages and empty pages (where applicable). Search results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appeared over the first match in the link inspector. (T98085)

The special character inserter in VisualEditor now uses the same special character list as the wikitext editor. Admins at each wiki can also create a custom section for frequently used characters at the top of the list. Please read the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing each character in the special character inserter. (T70425)

Several improvements have been made to templates. When you search for a template to insert, the list of results now contains descriptions of the templates. The parameter list inside the template dialog now remains open after inserting a parameter from the list, so that users don’t need to click on "Tambah informasi lainnya" each time they want to add another parameter. (T95696) The team added a new property for TemplateData, "Example", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter. (T53049)

The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design feature is being used for the cite button on wikis where the Citoid service is enabled.

The team has released a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• The weekly task triage meetings continue to be open to volunteers, usually on Wednesday at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker, though. Instead, go to Phabricator and "associate" the VisualEditor Q4 blocker project with the bug.
• If your Wikivoyage, Wikibooks, Wikiversity, or other community wants to have VisualEditor made available by default to contributors, then please contact James Forrester.
• If you would like to request the Citoid automatic reference feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
• The team is planning the second VisualEditor-related "translathon" for July. Please follow this task on Phabricator for details and updates! Announcements will follow in due course.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. 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. Thank you!

— Elitre (WMF)

13 Juni 2015 17.44 (ICT)

VisualEditor News #3—2015

Did you know?

When you click on a link to an article, you now see more information:

The link tool has been re-designed:

There are separate tabs for linking to internal and external pages. The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has created new interfaces for the link and citation tools and fixed many bugs and changed some elements of the design. Some of these bugs affected users of VisualEditor on mobile devices. Status reports are posted on mediawiki.org. The worklist for April through June is available in Phabricator.

A test of VisualEditor's effect on new editors at the English Wikipedia has just completed the first phase. During this test, half of newly registered editors had VisualEditor automatically enabled, and half did not. The main goal of the study is to learn which group was more likely to save an edit and to make productive, unreverted edits. Initial results will be posted at Meta later this month.

Recent improvements

Auto-fill features for citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now created inside a single tool. Inside that tool, choose the tab you want (⧼citoid-citeFromIDDialog-mode-auto⧽, ⧼citoid-citeFromIDDialog-mode-manual⧽, or ⧼citoid-citeFromIDDialog-mode-reuse⧽). The cite button is now labeled with the word "⧼visualeditor-toolbar-cite-label⧽" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "⧼Citoid-citeFromIDDialog-lookup-button⧽", for the submit button.

The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and appropriate icons for disambiguation pages, redirect pages and empty pages (where applicable). Search results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appeared over the first match in the link inspector. (T98085)

The special character inserter in VisualEditor now uses the same special character list as the wikitext editor. Admins at each wiki can also create a custom section for frequently used characters at the top of the list. Please read the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing each character in the special character inserter. (T70425)

Several improvements have been made to templates. When you search for a template to insert, the list of results now contains descriptions of the templates. The parameter list inside the template dialog now remains open after inserting a parameter from the list, so that users don’t need to click on "Tambah informasi lainnya" each time they want to add another parameter. (T95696) The team added a new property for TemplateData, "Example", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter. (T53049)

The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design feature is being used for the cite button on wikis where the Citoid service is enabled.

The team has released a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• The weekly task triage meetings continue to be open to volunteers, usually on Wednesday at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker, though. Instead, go to Phabricator and "associate" the VisualEditor Q4 blocker project with the bug.
• If your Wikivoyage, Wikibooks, Wikiversity, or other community wants to have VisualEditor made available by default to contributors, then please contact James Forrester.
• If you would like to request the Citoid automatic reference feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
• The team is planning the second VisualEditor-related "translathon" for July. Please follow this task on Phabricator for details and updates! Announcements will follow in due course.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. 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. Thank you!

— Elitre (WMF)

13 Juni 2015 21.02 (ICT)

Content Translation beta-feature is now available

Putar media

How to use Content Translation - a short video (English)

Hello, Content Translation has now been enabled as an opt-in beta feature on the Banjar Wikipedia. To start translating:

1. Please enable the Beta feature in your preferences by checking the box for Content Translation.
2. Visit the page Special:ContentTranslation or to your contributions page to open the tool.
3. Click on the blue button to create a new translation.
4. A dialog will be displayed. In the From section select the language of the original article and the article name, and the language you would like to translate to. Also add the title of the new article (or the original title will be inserted) and click on Translate to begin. Your language preferences will be remembered for the next time.
5. You will see a screen consisting of three columns. The left column contains the text of the source language and the middle column is for the translated text. Using the right column you can perform several actions such as insert source text, remove the inserted text source text, add or remove links etc.
6. After you translate the article, you can publish it directly as a new page on the Banjar Wikipedia by using the publish button that appears. In case the article gets created by another user while you were translating, you will see an option to save the newly published translation under your user namespace.
7. The number of published pages can be seen on the Content Translation stats page.

Since this is the first time we have installed the tool on this Wikipedia, there are chances that there may be some problems or service disruptions which we are not yet aware of. We will be monitoring the usage to check for any failures or issues, but please do let us know on the Content Translation talk page or through Phabricator if you spot any problems that prevent you from using the tool. For more information, please read the information available in the User Guide. Our announcement is written only in English, and we would really appreciate if this message can be translated to reach more users of this Wikipedia. Thank you. --KartikMistry (pandir) 16 Juni 2015 22.37 (ICT)

VisualEditor News #4—2015

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

Did you know?

You can add quotations marks before and after a title or phrase with a single click.

Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar).

Click the button. VisualEditor will add the quotation marks on either side of the text you selected.

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

Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.

Wikimania

The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.

Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.

For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).

For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).

We published some graphs showing the effect of the event on the Translathon page. We thank the translators for participating and the translatewiki.net staff for facilitating this initiative.

Recent improvements

Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.

Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top. In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.

Future changes

The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.

On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page is now using Flow instead of LiquidThreads.
• 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 mediawiki.org if you can help.
• If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
• Please file requests for language-appropriate "Tebal" and "Cetak miring" icons for the styling menu in Phabricator.
• The design research team wants to see how real editors work. Please sign up for their research program.
• The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

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. Thank you!

—Elitre (WMF), 15 Agustus 2015 05.28 (ICT)

VisualEditor News #4—2015

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

Did you know?

You can add quotations marks before and after a title or phrase with a single click.

Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar).

Click the button. VisualEditor will add the quotation marks on either side of the text you selected.

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

Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.

Wikimania

The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.

Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.

For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).

For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).

We published some graphs showing the effect of the event on the Translathon page. We thank the translators for participating and the translatewiki.net staff for facilitating this initiative.

Recent improvements

Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.

Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top. In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.

Future changes

The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.

On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page is now using Flow instead of LiquidThreads.
• 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 mediawiki.org if you can help.
• If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
• Please file requests for language-appropriate "Tebal" and "Cetak miring" icons for the styling menu in Phabricator.
• The design research team wants to see how real editors work. Please sign up for their research program.
• The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

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. Thank you!

—Elitre (WMF), 15 Agustus 2015 07.05 (ICT)

VisualEditor News #5—2015

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

Did you know?

You can use the visual editor on smartphones and tablets.

Click the pencil icon to open the editor for a page. Inside that, use the gear menu in the upper right corner to "Switch to visual editing".

The editing button will remember which editing environment you used last time, and give you the same one next time. The desktop site will be switching to a system similar to this one in the coming months.

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, added new features, and made some small design changes. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving support for languages like Japanese and Arabic, making it easier to edit on mobile devices, and providing rich-media tools for formulæ, charts, galleries and uploading.

Recent improvements

Educational features: The first time ever you use the visual editor, it now draws your attention to the Pranala and ⧼visualeditor-toolbar-cite-label⧽ tools. When you click on the tools, it explains why you should use them. (T108620) Alongside this, the welcome message for new users has been simplified to make editing more welcoming. (T112354) More in-software educational features are planned.

Links: It is now easier to understand when you are adding text to a link and when you are typing plain text next to it. (T74108, T91285) The editor now fully supports ISBN, PMID or RFC numbers. (T109498, T110347, T63558) These "magic links" use a custom link editing tool.

Uploads: Registered editors can now upload images and other media to Commons while editing. Click the new tab in the "Sisipkan Media" tool. You will be guided through the process without having to leave your edit. At the end, the image will be inserted. This tool is limited to one file at a time, owned by the user, and licensed under Commons's standard license. For more complex situations, the tool links to more advanced upload tools. You can also drag the image into the editor. This will be available in the wikitext editor later.

Mobile: Previously, the visual editor was available on the mobile Wikipedia site only on tablets. Now, editors can use it on all devices regardless of size if they wish. (T85630) Edit conflicts were previously broken on the mobile website. Edit conflicts can now be resolved in both wikitext and visual editors. (T111894) Sometimes templates and similar items could not be deleted on the mobile website. Selecting them caused the on-screen keyboard to hide with some browsers. Now there is a new "Hapus" button, so that these things can be removed if the keyboard hides. (T62110) You can also edit table cells in mobile now.

Rich editing tools: You can now add and edit sheet music in the visual editor. (T112925) There are separate tabs for advanced options, such as MIDI and Ogg audio files. (T114227, T113354) When editing formulæ and other blocks, errors are shown as you edit. It is also possible to edit some types of graphs; adding new ones, and support for new types, will be coming.

On the English Wikipedia, the visual editor is now automatically available to anyone who creates an account. The preference switch was moved to the normal location, under Special:Preferences.

Future changes

You will soon be able to switch from the wikitext to the visual editor after you start editing. (T49779) Previously, you could only switch from the visual editor to the wikitext editor. Bi-directional switching will make possible a single edit tab. (T102398) This project will combine the "Babak" and "Sunting sumber" tabs into a single "Babak" tab, similar to the system already used on the mobile website. The "Babak" tab will open whichever editing environment you used last time.

Let's work together

• Share your ideas and ask questions at VisualEditor/Feedback. This feedback page uses Flow for discussions.
• 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).
• Local admins can set up the Citoid automatic reference feature for your wiki. If you need help, then please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
• The weekly task triage meetings are open to volunteers. Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

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. Thank you!

—Elitre (WMF), 31 Uktubir 2015 01.18 (ICT)

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 "Babak" and "Sunting sumber" tabs into a single "Babak" tab, like the system already used on the mobile website. (T102398, T58337) Initially, the "Babak" 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 Pambabakan tab of Special:Preferences in the drop-down menu about "Editing mode:".

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:
  • Remember my last editor,
  • Always give me the visual editor if possible,
  • Always give me the source editor, and
  • Show me both editor tabs. (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. Terima kasih!

Elitre (WMF), 25 Disimbir 2015 07.06 (ICT)

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 "Babak" and "Sunting sumber" tabs into a single "Babak" tab. This is similar to the system already used on the mobile website. (T102398) Initially, the "Babak" 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 Pambabakan tab of Special:Preferences:

• Remember my last editor,
• Always give me the visual editor if possible,
• Always give me the source editor, and
• Show me both editor tabs. (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. Terima kasih!

Elitre (WMF), 27 Pibuari 2016 03.21 (ICT)

Compact Links coming soon to this wiki

Please help translate to your language

Screenshot of Compact Language Links interlanguage list

Hello, I wanted to give a heads up about an upcoming feature for this wiki, which you may already seen in the latest issue of Tech News. Compact Language Links has been available as a beta-feature on all Wikimedia wikis since 2014. With compact language links enabled, users are shown a much shorter list of languages on the interlanguage link section of an article (see image). This will be enabled as a feature in the coming week for all users, which can be turned on or off using a preference setting. We look forward to your feedback and please do let us know if you have any questions. Details about Compact Language Links can be read in the project documentation.

Due to the large scale enablement of this feature, we have had to use MassMessage for this announcement and as a result it is only written in English. We will really appreciate if this message can be translated for other users of this wiki. Thank you. On behalf of the Wikimedia Language team: Runa Bhattacharjee (WMF) (talk) 24 Juni 2016 21.01 (ICT)

Compact Language Links enabled in this wiki today

Please help translate to your language

Screenshot of Compact Language Links interlanguage list

Compact Language Links has been available as a beta-feature on all Wikimedia wikis since 2014. With compact language links enabled, users are shown a much shorter list of languages on the interlanguage link section of an article (see image). Based on several factors, this shorter list of languages is expected to be more relevant for them and valuable for finding similar content in a language known to them. More information about compact language links can be found in the documentation.

From today onwards, compact language links has been enabled as the default listing of interlanguage links on this wiki. However, using the button at the bottom, you will be able to see a longer list of all the languages the article has been written in. The setting for this compact list can be changed by using the checkbox under User Preferences -> Appearance -> Languages

The compact language links feature has been tested extensively by the Wikimedia Language team, which developed it. However, in case there are any problems or other feedback please let us know on the project talk page. It is to be noted that on some wikis the presence of an existing older gadget that was used for a similar purpose may cause an interference for compact language list. We would like to bring this to the attention of the admins of this wiki. Full details are on this phabricator ticket (in English).

Due to the large scale enablement of this feature, we have had to use MassMessage for this announcement and as a result it is only written in English. We will really appreciate if this message can be translated for other users of this wiki. Thank you. On behalf of the Wikimedia Language team: Runa Bhattacharjee (WMF) (talk)-28 Juni 2016 11.21 (ICT)

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 "Sisipkan" menu and click the "Daftar referensi" 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 "Sisipkan" in the dialog to insert the Daftar referensi. 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 "Babak" and "Sunting sumber" tabs into a single "Babak" 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 "Pambabakan" 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 "Simpan tungkaran" button will say "Terbitkan halaman". 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. Terima kasih!

m:User:Elitre (WMF), 4 Juli 2016 00.20 (ICT)

Wikipedia to the Moon working phase

Dear Banjar Wikipedia language community,

First of all, I am sorry to write this in English.

You may already have heard about Wikipedia to the Moon: A team of scientists called the “PT Scientists” are going to send a space craft to the moon in 2017 and they want to take Wikipedia along with them. Because Wikipedia is so big, we cannot send all of it to the moon. That is why the international Wikipedia-community has voted to send all “Featured Articles and Featured Lists“ from all languages in Wikipedia.

“Featured Articles“ is a category in many language versions of Wikipedia that collects the very best articles in that language. Your community does not currently have a „Featured Articles“ category. Ideally, we want to take every language on Wikipedia to the moon and we also want to take the best articles in your language. That is why we would like you to tell us what the very best articles in your language are.

There are two ways you could do this:

1) You could introduce the categories “Featured Article” and “Featured List” in your language version of Wikipedia and vote for the best articles and put them in the category. We will take every article that is tagged as a “Featured Article” or a “Featured List” to the moon

2) You could vote for the best articles in your language version of Wikipedia and put them all on one a new Wikipedia page. If you let us know where we can find that list here, we will also take the articles to the moon.

The deadline for Wikipedia to the Moon is 31 October 2016. After that date, we will put all the Featured Articles and Lists onto a special disc and give it to the “PT Scientists.” They will take the Wikipedia articles into space next year.

--Denis Schroeder (WMDE) (pandir) 17 Agustus 2016 20.20 (ICT)