Wikipidia:Warung Kupi (Teknis)

bjn: Parmintaan gasan bandira bot harus diulah di tungkaran ini. Wiki ini mangguna'akan kabijakan standar bot, wan mamungkinakan bot global dan pa'ijinan utumatis bot janis tartantu. Bot lain harus ditarapakan di bawah ini, dan limbah itu maminta aksés matan pramugara jaka kadada kabaratan.
en: Requests for the bot flag should be made on this page. This wiki uses the standard bot policy, and allows global bots and automatic approval of certain types of bots. Other bots should apply below, and then request access from a steward if there is no objection.

Upload berkas[babak asal mulanya]

Gimana cara upload berkas? Aris riyanto 13:59, 27 Nupimbir 2010 (ICT)

Aplikasi "Hunggahakan barakas" akan aktif dengan sendirinya beberapa hari kemudian. --Ezagren ^bapandir 14:04, 27 Nupimbir 2010 (ICT)

Ok terima kasih :) Aris riyanto 14:21, 27 Nupimbir 2010 (ICT)

Requests for a bot flag[babak asal mulanya]

Xqbot[babak asal mulanya]

Xqbot doesn't know how to do (well) its so-called "cosmetic changes" (actually a kind of vandalism), but it is a "global bot". I don't want to see here these so-called "cosmetic changes". --Budelberger 22:35, 31 Uktubir 2010 (ICT) (). (ArthurBot, TXiKiBoT, VolkovBot... are good bots.)

The discussion is not about Xqbot, but about the local bot policy. Carsrac 16:58, 1 Nupimbir 2010 (ICT)

But local bot policy will give rights to the worst bot I've ever seen, Xqbot. --Budelberger 17:12, 1 Nupimbir 2010 (ICT) (

). (ArthurBot, TXiKiBoT, VolkovBot and a few other are good bots.)

Budelberger, please stop stalking me. Xqt 20:48, 1 Nupimbir 2010 (ICT)

Are you, you : Xqt, Xqbot ? No. I'm talking about the worst bot I've ever seen, your bot ; why have you deactivated "your" so-called "cosmetic changes" on simple.Wp if in your poor own opinion -- removing categorizing templates, etc. -- they are correct ?... --Budelberger 21:27, 1 Nupimbir 2010 (ICT) (

). (Because DJSasso has the power to block it on simple. Alas ! ty, cdo, hak and poor other Wikipedias don't have a clever DJSasso to stop vandalisms.) (Ask TXiKi or Volkov to teach you how good first quality bots work well.)

If you have any remarks according the bot please use our bug tracker. Since I am member of the development group and mw coder I am interested fixing errors if there are some. But unqualified statements are not very helpful in this matter. (eod) Xqt 22:10, 1 Nupimbir 2010 (ICT)

Xqt, We must be patient to face this user. Ezagren ^bapandir 22:22, 1 Nupimbir 2010 (ICT)

The end of your message was deleted... : "...until I have sysop access to block Him !"... --Budelberger 04:59, 2 Nupimbir 2010 (ICT) (

).

« Actually it's not our responsibility, it's that of the bot runner to make sure there are no bugs. »… Stop your so-called « cosmetic changes » everywhere, not only in this Happy Wikipedia, Simple ! --Budelberger 22:24, 1 Nupimbir 2010 (ICT) (

). (DJSasso has told you all I have to say about defaultsort, categorizing template, etc.)

Actually cosmetic changes bot is well accepted at Indonesian Wikipedia. (I am also a cosmetic changes bot owner; nowadays that script is buggy so I stop it for a while) Kenrick95 22:42, 1 Nupimbir 2010 (ICT)

The standard policy does only allow interwiki and redirect bots. Cosmetic change bots are not automaticly allowed by the policy. Carsrac 01:35, 2 Nupimbir 2010 (ICT)

Well, well, well... So, Welcome here to Xqtbot ! --Budelberger 04:59, 2 Nupimbir 2010 (ICT) (

).

Ignore Budelberger, he is a cross-wiki troll. Xqt is a valuable member of any community. -Djsasso 03:12, 28 Januari 2011 (ICT)

A local bot flag is no longer needed. This is a global bot, and this wiki recently enabled global bots. —Pathoschild 23:20:56, 21 Pibuari 2011 (UTC)

TjBot[babak asal mulanya]

I request a bot flag for TjBot

Bot operator: id:user:Tjmoel
List of botflags on other projects: ar, be-x-old, cs, de, es, et, fr, hr, id, it, lb, lt, lv, ms, no, pl, ru, sr, sw, tr, uk, zh-yue, zh

.. Contributions in all Wikimedia projects see here. Flags and edit counter in other projects see here.

Purpose: interwiki
Technical details: use pywikipedia

— Tjmoel^bicara 18:05, 27 Nupimbir 2010 (UTC)

A local bot flag is no longer needed. This is a global bot, and this wiki recently enabled global bots. —Pathoschild 23:21:47, 21 Pibuari 2011 (UTC)

Mjbmrbot[babak asal mulanya]

Operator : Mjbmr
Automatic or Manually Assisted : Automatic
Programming Language(s) : Python (pywikipedia)
Function Summary : Interwiki
Already has a bot flag (Y/N) : Yes, see here
Function Details : Just interwikis, thanks

Mjbmr 23:20, 28 Nupimbir 2010 (ICT)

Done --Mav 05:15, 19 Disimbir 2010 (ICT)

HiW-Bot[babak asal mulanya]

Operator : Hedwig in Washington
Automatic or Manually Assisted : automatic
Programming Language(s) : Python (pywikipedia), daily update
Function Summary : Interwiki, Internationalization by removing chaos in Babel-Category so it can be used properly and easy. Double redirects will be added shortly
Already has a bot flag (Y/N) : Yes: DE, EN, FR, SL, AR, NL, TH, UDM, TT, NN, KA, DA, BE-X-OLD, BAT-SMG, ARZ and LB, others pending. see here
Function Details : just using the standard interwiki.py; parameters: -auto -all - log -catr

I humbly request bot status on this wiki in order to update Interwiki, and improve Internationalization by removing chaos in Babel so it can be used properly and easy by everyone.

Thank you for consideration! --Hedwig in Washington 10:17, 6 Siptimbir 2011 (ICT)

Botrie[babak asal mulanya]

I request a bot flag for Botrie

Bot operator: user:Riemogerz
List of botflags on other projects:
Purpose: Interwiki, mambaiki kasalahan panulisan kata, mambari pasan salamat datang
Technical details: use pywikipedia

10 Januari 2012 00.42 (ICT)

Bot flag for WikitanvirBot[babak asal mulanya]

Operator : Wikitanvir
Automatic or Manually Assisted : Automatic
Programming Language(s) : Python (pywikipedia)
Function Summary : Interwiki
Edit period(s) : Daily
Edit rate requested : 3/4 edits per minute at most
Already has a bot flag : Yes, flagged on 100+ Wikipedias. See here.
Function Details : Bot will patrol recent changes and new pages, and add, remove, or modify interwiki links in autonomous mode.

Already have done with 50+ test edits. Thanks in advance. — Tanvir • 01:55, 21 Nupimbir 2010 (ICT)

What is your python version? Xqt 14:42, 22 Nupimbir 2010 (ICT)

My Python version is 2.5.5. Sorry for answering in late. — Tanvir • 00:17, 30 Nupimbir 2010 (ICT)

Bot flag granted per request here and on Meta. --Erwin 03:58, 10 Disimbir 2010 (ICT)

Bot policy[babak asal mulanya]

Hello. To facilitate steward granting of bot access, I suggest implementing the standard bot policy on this wiki. In particular, this policy allows stewards to automatically flag known interlanguage linking bots (if this page says that is acceptable), which form the vast majority of such requests. The policy also enables global bots on this wiki (if this page says that is acceptable), which are trusted bots that will be given bot access on every wiki that allows global bots.

This policy makes bot access requesting much easier for local users, operators, and stewards. To implement it we only need to create a redirect to this page from Wikipidia:Bot policy, and add a line at the top noting that it is used here. Please read the text at m:Bot policy before commenting. If you object, please say so; I hope to implement in two weeks if there is no objection, since it is particularly written to streamline bot requests on wikis with little or no community interested in bot access requests. Xqt 22:21, 20 Uktubir 2010 (ICT)

HakunKenrick95 18:19, 27 Uktubir 2010 (ICT)
HakunCarsrac 00:34, 28 Uktubir 2010 (ICT)
Hakun — Tanvir • 16:04, 2 Disimbir 2010 (ICT)

Done. —Pathoschild 21:54:27, 21 Pibuari 2011 (UTC)

Request for sysop access[babak asal mulanya]

Ezagren[babak asal mulanya]

I would like to request for sysop access in this Banjar Wikipedia. I would like to improve on:

MediaWiki for Banjar Wikipedia
designing and protecting front page
increasing the edit keys
protecting vandalized articles

Thank you. --Ezagren ^bapandir 23:42, 26 Uktubir 2010 (ICT)

You "would like to improve"... I don't think so ; bjn.Wikipedia was not ready to leave Incubator (keywords were translated not in Banjar, but in Indonesian, see here) but it did : is it time "to improve on MediaWiki for Banjar Wikipedia" ?... Wp/bjn was approved by experts... I think that you want, as many others, own your Wikipedia, your Private Wikipedia, where you may revert and delete others' edits, protect your articles (all bjn articles are yours), and block other users, except a few friends (Amdf, who has a Gaul in Wp/mrj ?... That's what you want ? to be the Banjar Amdf ?). Your first edit as Administrateur ? "protect" (that is : "block") "Main Page" and its templates... --Budelberger 23:06, 31 Uktubir 2010 (ICT) (

). (A good Wikipedia working well is a Wikipedia without any Administrateur.)

Handak ikam itu apa gerang? Ulun kada mangarti. Wikipidia ini ampun samunyaan urang. Ezagren ^bapandir 13:43, 1 Nupimbir 2010 (ICT)

Before requesting to own a Wikipedia (Oooops ! "sysop access"...), you have to learn some magic words, you and your clever friend Erik Anggara. --Budelberger 16:51, 1 Nupimbir 2010 (ICT) (

).

Oooops, sorry! I miss it. I know it. Ezagren ^bapandir 17:42, 1 Nupimbir 2010 (ICT)

I'm very proud to have taught you how to use some magic words : I think in a few years, you'll be able to ask for owning your own Private Wikipedia, your so-called "sysop access". --Budelberger 19:06, 1 Nupimbir 2010 (ICT) (

). (Do you ask others before adding your "bjn" in Main Pages ?... No, of course ; but you don't like to have small languages in your own Private Property. For others to, Banjar language is a small language, but your racialist rules have not spread everywhere.) (You are right : removing "includeonly" pair in a template is not a "stupid edit" ; I give to you and your friend Anggara a Star.)

Ezagren doesn't like other languages, see here, but other languages must love its Banjar language, see here, etc. --Budelberger 19:02, 15 Nupimbir 2010 (ICT) (

).

Instead I do not know, but "include" it only just missed from editing. Sometime I'll make Wikipidia:BintangWiki. Me and my friends have tried to make this Banjar Wikipedia, so it is okay if I volunteered to be sysop for Banjar Wikipedia become better and organized. I volunteered as a sysop is also on the advice of fellow users in Wikipedia. --Ezagren ^bapandir 20:19, 1 Nupimbir 2010 (ICT)

Banjar.Wp had to be well organized and written in Banjar -- not in Indonesian -- in Incubator, not here. What was not done in Incubator will be done here, with and by the same Dream Team ?... --Budelberger 21:38, 1 Nupimbir 2010 (ICT) (

). (You revert first, and don't think after reverting, missing some magic words meanwhile ; that's why you want "sysop access".)

Saya tidak mengerti jalan pikiran Anda. Sorry! --Ezagren ^bapandir 22:03, 1 Nupimbir 2010 (ICT)

Hakun[babak asal mulanya]

Hakun --J Subhi ^{”pamandiran”} 05:13, 27 Uktubir 2010 (ICT)
Hakun --Alamnirvana^pamandiran 17:15, 27 Uktubir 2010 (ICT)
Hakun --Mimihitam 18:11, 27 Uktubir 2010 (ICT)
Hakun --Kenrick95 18:19, 27 Uktubir 2010 (ICT)
Hakun --BlackKnight 23:30, 27 Uktubir 2010 (ICT)
Hakun --39Agung 23:33, 27 Uktubir 2010 (ICT)
Hakun --Carsrac 00:35, 28 Uktubir 2010 (ICT)
Hakun --Alagos 02:44, 28 Uktubir 2010 (ICT)
Hakun --M. Adiputra 19:27, 28 Uktubir 2010 (ICT)
Hakun Xqt 23:20, 1 Nupimbir 2010 (ICT)

Kada Hakun[babak asal mulanya]

Riemogerz[babak asal mulanya]

I would like to request for access to this Banjar sysop Wikipedia. I would like to Improve on:

protect some important pages
protecting vandalized articles
perform other sysop access

Thanks. :) Rie Mog erZ 28 Januari 2012 19.48 (ICT)

Hakun[babak asal mulanya]

Hakun Bennylin 29 Januari 2012 15.29 (ICT)
Hakun, ai! Ezagren ^bapandir 29 Januari 2012 18.28 (ICT)
Hakun, jua ai!--J Subhi ^{”pamandiran”} 31 Januari 2012 21.11 (ICT)

Selamat, Anda sudah diangkat menjadi admin Wikipedia bahasa Banjar. Untuk sementara silakan baca (atau kalau bisa diterjemahkan) id:Wikipedia:Pedoman pengurus dan id:Wikipedia:Nasihat bagi pengurus baru. Dan kalau butuh mentoring tambahan untuk pengurus, kita bisa lakukan (hubungi saya di id.wiki, atau Ezagren). Bennylin (pandir) 27 April 2012 21.31 (ICT)

Kada tahu[babak asal mulanya]

Manulak[babak asal mulanya]

Something strange[babak asal mulanya]

See here, here, here, here and here.

Budelberger 17:03, 1 Nupimbir 2010 (ICT) ().

I think no matter. --Ezagren ^bapandir 20:12, 1 Nupimbir 2010 (ICT)

Where are Bennylin's and Gombang's creation/log ? --Budelberger 22:27, 1 Nupimbir 2010 (ICT) (

).

In another language wikipedia. Later they also will visit here. So, given a welcome. Ezagren ^bapandir 22:41, 1 Nupimbir 2010 (ICT)

That is what is called a sockpuppet ! You're requesting for "sysop access" and you have already 2 sockpuppets !... --Budelberger 23:04, 1 Nupimbir 2010 (ICT) (

). (First, second.)

Hi, I'm not sure what you're asking here. Could you please explain? Bennylin 29 Januari 2012 15.31 (ICT)

translations request[babak asal mulanya]

I need your help translation bot comments to bjn. I list the tokens for en and id here:

   'en': (u'robot ', u'Adding', u'Removing', u'Modifying'),
   'id': (u'bot ', u'Menambah', u'Membuang', u'Mengubah'),
   'bjn': (u'bot ', u'Manambah', u'Mambuang', u'Ma'ubah'),

   'en': u'Robot: Fixing double redirect to %s',
   'id': u,
   'bjn': u'Robot: Pamasangan paugahan ganda ka %s',

This depend on all interwiki and redirect bots. Thanks in advance. Xqt 22:46, 1 Nupimbir 2010 (ICT)

First part done in pyrev:8693. Thanks Xqt 23:18, 1 Nupimbir 2010 (ICT)

Done in pyrev:8718 thanks. Xqt 03:24, 12 Nupimbir 2010 (ICT)

Usulan parubahan tampilan[babak asal mulanya]

Pamungutan suara di tungkaran naya sudah tuntung wan sudah ada kasapakatan.

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[babak asal mulanya]

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[babak asal mulanya]

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. RieMogerz^talk 31 Disimbir 2011 15.14 (ICT)}
Sapakat bagus..Stephensuleeman 31 Disimbir 2011 20.41 (ICT)

Nang kada tahu[babak asal mulanya]

Nang manulak[babak asal mulanya]

Kumintar[babak asal mulanya]

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[babak asal mulanya]

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)

No one needs free knowledge in Esperanto[babak asal mulanya]

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[babak asal mulanya]

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 "Antasan papan picikan" link out of the "Opsi halaman" menu, into the "Patulung" 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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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):

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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)

Language support group for Banjar[babak asal mulanya]

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 gasan pambabakan / paulahan tungkaran panting[babak asal mulanya]

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 ?? --- Rie Mog erZ 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 ? --- Rie Mog erZ 9 Januari 2012 23.00 (ICT)

Request for adminship[babak asal mulanya]

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 :) Rie Mog erZ 30 Agustus 2012 14.23 (ICT)

No one needs free knowledge in Esperanto[babak asal mulanya]

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[babak asal mulanya]

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 "Antasan papan picikan" link out of the "Opsi halaman" menu, into the "Patulung" 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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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):

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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 "Paragrap" 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[babak asal mulanya]

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[babak asal mulanya]

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 "Kandal" and "Citak hiring" 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[babak asal mulanya]

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[babak asal mulanya]

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 ⧼visualeditor-toolbar-savedialog⧽ 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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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 "Kandal" and "Citak hiring" 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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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, "Contoh", 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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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, "Contoh", 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[babak asal mulanya]

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[babak asal mulanya]

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:

Please enable the Beta feature in your preferences by checking the box for Content Translation.
Visit the page Special:ContentTranslation or to your contributions page to open the tool.
Click on the blue button to create a new translation.
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.
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.
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.
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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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 "Kandal" and "Citak hiring" 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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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 "Kandal" and "Citak hiring" 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[babak asal mulanya]

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 "Beralih ke penyuntingan visual".

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[babak asal mulanya]

Educational features: The first time ever you use the visual editor, it now draws your attention to the Tautan 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 Gambar dan 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[babak asal mulanya]

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 "Babak asal mulanya" 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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

The single edit tab project will combine the "Babak" and "Babak asal mulanya" 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 "Mode penyuntingan:".

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[babak asal mulanya]

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:
- Ingat penyunting terakhir saya,
- Selalu tampilkan penyunting visual bila dimungkinkan.,
- Selalu tampilkan penyunting sumber, and
- Tampilkan kedua tab penyunting. (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)

Banjar is missing[babak asal mulanya]

Banjar is missing from this page:
https://meta.wikimedia.org/wiki/There_is_also_a_Wikipedia_in_your_language
More than 100 languages are now listed.
Thank you, Varlaam (pandir) 1 Pibuari 2016 11.56 (ICT)

VisualEditor News #1—2016[babak asal mulanya]

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[babak asal mulanya]

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[babak asal mulanya]

The single edit tab project will combine the "Babak" and "Babak asal mulanya" 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:

Ingat penyunting terakhir saya,
Selalu tampilkan penyunting visual bila dimungkinkan.,
Selalu tampilkan penyunting sumber, and
Tampilkan kedua tab penyunting. (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[babak asal mulanya]

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[babak asal mulanya]

Tolong bantu terjemahkan ke bahasa Anda

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[babak asal mulanya]

Tolong bantu terjemahkan ke bahasa Anda

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[babak asal mulanya]

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 "Daptar rujukan" 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 "Sisipakan" in the dialog to insert the Daptar rujukan. 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[babak asal mulanya]

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 "Babak asal mulanya" 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[babak asal mulanya]

The "Simpan tungkaran" button will say "Tarbitakan tungkaran". 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[babak asal mulanya]

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)

Editing News #3—2016[babak asal mulanya]

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

Did you know?

Did you know that you can easily re-arrange columns and rows in the visual editor?

Select a cell in the column or row that you want to move. Click the arrow at the start of that row or column to open the dropdown menu (shown). Choose either "Move before" or "Move after" to move the column, or "Move above" or "Move below" to move the row.

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

Since the last newsletter, the VisualEditor Team has mainly worked on a new wikitext editor. They have also released some small features and the new map editing tool. Their workboard is available in Phabricator. You can find links to the list of work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, releasing the 2017 wikitext editor as a beta feature, and improving language support.

Recent changes[babak asal mulanya]

You can now set text as small or big.[2]
Invisible templates have been shown as a puzzle icon. Now, the name of the invisible template is displayed next to the puzzle icon.[3] A similar feature will display the first part of hidden HTML comments.[4]
Categories are displayed at the bottom of each page. If you click on the categories, the dialog for editing categories will open.[5]
At many wikis, you can now add maps to pages. Go to the Insert menu and choose the "Maps" item. The Discovery department is adding more features to this area, like geoshapes. You can read more at mediawiki.org.[6]
The "Save" button now says "Save page" when you create a page, and "Save changes" when you change an existing page.[7] In the future, the "Simpan tungkaran" button will say "Tarbitakan tungkaran". This will affect both the visual and wikitext editing systems. More information is available on Meta.
Image galleries now use a visual mode for editing. You can see thumbnails of the images, add new files, remove unwanted images, rearrange the images by dragging and dropping, and add captions for each image. Use the "Options" tab to set the gallery's display mode, image sizes, and add a title for the gallery.[8]

Future changes[babak asal mulanya]

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

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

Let's work together[babak asal mulanya]

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

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

—Elitre (WMF)

16 Uktubir 2016 00.50 (ICT)

JavaScript error[babak asal mulanya]

Hi, everyone. As you may or may not know, there are JavaScript errors on this project. The errors are TypeError: Cannot read property 'getParamValue' of undefined and TypeError: $.cookie is not a function. To fix this,

mw.util.addCSS(...);

needs to be replaced with

mw.loader.using( 'mediawiki.util', function() {
	mw.util.addCSS(...);
} );

in MediaWiki:Common.js. Please note that it appears more than once.

Pinging some admins: Ezagren, Riemogerz.

Feel free to ping me if you need help or have any questions. Nirmos (pandir) 15 Mai 2017 07.19 (ICT)

@Nirmos: It has been replaced. Please check.

Here, in Banjar Wikipedia, there is a problem when you want to edit, i.e. this (below editing page) can't be clicked. Can you solve the problem? Ezagren ^{(kirim pasan)} 18 Mai 2017 22.17 (ICT)

Ezagren: Now the error is JavaScript parse error: Parse error: Syntax error in file 'MediaWiki:Common.js' on line 113 because you removed a { and forgot to add } ); in Special:Diff/56608. Nirmos (pandir) 19 Mai 2017 01.33 (+07)[balas]

Ezagren: Do you need in help with fixing this? Could you start with rolling back to Special:PermanentLink/54315 and then we can make the necessary changes together to make sure it is correct? Nirmos (pandir) 23 Mai 2017 13.22 (+07)[balas]

New notification when a page is connected to Wikidata[babak asal mulanya]

Hello all,

(Tolong bantu terjemahkan ke bahasa Anda)

The Wikidata development team is about to deploy a new feature on all Wikipedias. It is a new type of notification (via Echo, the notification system you see at the top right of your wiki when you are logged in), that will inform the creator of a page, when this page is connected to a Wikidata item.

You may know that Wikidata provides a centralized system for all the interwikilinks. When a new page is created, it should be connected to the corresponding Wikidata item, by modifying this Wikidata item. With this new notification, editors creating pages will be informed when another editor connects this page to Wikidata.

This feature will be deployed on May 30th on all the Wikipedias, excepting English, French and German. This feature will be disable by default for existing editors, and enabled by default for new editors.

This is the first step of the deployments, the Wikipedias and other Wikimedia projects will follow in the next months.

If you have any question, suggestion, please let me know by pinging me. You can also follow and leave a comment on the Phabricator ticket.

Thanks go to Matěj Suchánek who developed this feature!

Terima kasih! Lea Lacroix (WMDE) (talk)

m:Requests for comment/Global centralnotice for the blockade of the Turkish government[babak asal mulanya]

Hi, you are invited to participate in the discussion on the proposal to make a banner through m: centralnotice to inform more people around the world about what the Turkish government has done about Wikipedia, ie all the language versions of Wikipedia are You are obscured, so in Turkey it is impossible to view the * .wikipedia.org site. To hope that the Turkish government will remove the block, it is necessary to raise awareness of this fact around the world because it is important to succeed in this mission because Wikipedia can not be seen in Turkey. With this message also for those interested, I invite him to sign the Wikimedian appeal.

If you have any questions or questions do not hesitate to contact me. Thanks best regards. --Samuele2002 (Talk!) 19 Mai 2017 00.55 (ICT)

Update on page issues on mobile web[babak asal mulanya]

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

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

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

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

CKoerner (WMF) (talk) 13 Juni 2018 03.58 (ICT)

Enabling a helpful feature for Template editors[babak asal mulanya]

Hello.

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

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

TemplateStyles is useful for a few reasons.

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

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

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

Thank you.

CKoerner (WMF) (talk) 7 Agustus 2018 04.28 (ICT)

Wikidata changes now also appear in enhanced recent changes[babak asal mulanya]

Hello, and sorry to write this message in English. You can help translating it.

Starting from today, you will be able to display Wikidata changes in both modes of the recent changes and the watchlist.

Read and translate the full message

Terima kasih! Lea Lacroix (WMDE) 29 Juni 2017 15.33 (ICT)

(wrong target page? you can fix it here)

Improved search in deleted pages archive[babak asal mulanya]

Tolong bantu terjemahkan ke bahasa Anda

During Wikimedia Hackathon 2016, the Discovery team worked on one of the items on the 2015 community wishlist, namely enabling searching the archive of deleted pages. This feature is now ready for production deployment, and will be enabled on all wikis, except Wikidata.

Right now, the feature is behind a feature flag - to use it on your wiki, please go to the Special:Undelete page, and add &fuzzy=1 to the URL, like this: https://test.wikipedia.org/w/index.php?title=Special%3AUndelete&fuzzy=1. Then search for the pages you're interested in. There should be more results than before, due to using ElasticSearch indexing (via the CirrusSearch extension).

We plan to enable this improved search by default on all wikis soon (around August 1, 2017). If you have any objections to this - please raise them with the Discovery team via email or on this announcement's discussion page. Like most Mediawiki configuration parameters, the functionality can be configured per wiki. Once the improved search becomes the default, you can still access the old mode using &fuzzy=0 in the URL, like this: https://test.wikipedia.org/w/index.php?title=Special%3AUndelete&fuzzy=0

Please note that since Special:Undelete is an admin-only feature, this search capability is also only accessible to wiki admins.

Terima kasih! CKoerner (WMF) (talk) 26 Juli 2017 01.39 (ICT)

IMPORTANT: Admin activity review[babak asal mulanya]

Sorry for posting in English, but we have no translation in Banjar; you can translate this notice for future notifications.

Hello. A policy regarding the removal of "advanced rights" (administrator, bureaucrat, etc. ) was adopted by global community consensus in 2013. According to this policy, the stewards are reviewing administrators' activity on all Wikimedia Foundation wikis with no inactivity policy. To the best of our knowledge, your wiki does not have a formal process for removing "advanced rights" from inactive accounts. This means that the stewards will take care of this according to the admin activity review.

We have determined that the following users meet the inactivity criteria (no edits and no log actions for more than 2 years):

User:Riemogerz

These users will receive a notification soon, asking them to start a community discussion if they want to retain some or all of their rights. If the users do not respond, then their advanced rights will be removed by the stewards.

However, if you as a community would like to create your own activity review process superseding the global one, want to make another decision about these inactive rights holders, or already have a policy that we missed, then please notify the stewards on Meta-Wiki so that we know not to proceed with the rights review on your wiki. Thanks, --MarcoAurelio (pandir) 10 Januari 2018 04.04 (ICT)

Editing News #1—2018[babak asal mulanya]

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

Did you know?

Did you know that you can now use the visual diff tool on any page?

Sometimes, it is hard to see important changes in a wikitext diff. This screenshot of a wikitext diff (click to enlarge) shows that the paragraphs have been rearranged, but it does not highlight the removal of a word or the addition of a new sentence.

If you enable the Beta Feature for "Perbedaan visual", you will have a new option. It will give you a new box at the top of every diff page. This box will let you choose either diff system on any edit.

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

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

This screenshot shows the same edit as the wikitext diff. The visual diff highlights the removal of one word and the addition of a new sentence.

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

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

Recent changes[babak asal mulanya]

The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools. The team have been comparing the performance of different editing environments. They have studied how long it takes to open the page and start typing. The study uses data for more than one million edits during December and January. Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor. Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits. More information will be posted at mw:Contributors/Projects/Editing performance.
The visual diff tool was developed for the visual editor. It is now available to all users of the visual editor and the 2017 wikitext editor. When you review your changes, you can toggle between wikitext and visual diffs. You can also enable the new Beta Feature for "Visual diffs". The Beta Feature lets you use the visual diff tool to view other people's edits on page histories and Special:RecentChanges. [9]
Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor. [10]
The citoid service automatically translates URLs, DOIs, ISBNs, and PubMed id numbers into wikitext citation templates. It is very popular and useful to editors, although it can be a bit tricky to set up. Your wiki can have this service. Please read the instructions. You can ask the team to help you enable citoid at your wiki.

Let's work together[babak asal mulanya]

The team will talk about editing tools at an upcoming Wikimedia Foundation metrics and activities meeting.
Wikibooks, Wikiversity, and other communities may have the visual editor made available by default to contributors. If your community wants this, then please contact Dan Garry.
The <references /> block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. You can request multi-column support for your wiki. [11]
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Terima kasih!

—Elitre (WMF)

3 Marit 2018 03.56 (ICT)

Editing News #2—2018[babak asal mulanya]

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

Did you know?

Did you know that you can use the visual editor on a mobile device?

Tap on the pencil icon to start editing. The page will probably open in the wikitext editor.

You will see another pencil icon in the toolbar. Tap on that pencil icon to the switch between visual editing and wikitext editing.

Remember to publish your changes when you're done.

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

Since the last newsletter, the Editing Team has wrapped up most of their work on the 2017 wikitext editor and the visual diff tool. The team has begun investigating the needs of editors who use mobile devices. Their work board is available in Phabricator. Their current priorities are fixing bugs and improving mobile editing.

Recent changes[babak asal mulanya]

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

Let's work together[babak asal mulanya]

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

—Whatamidoing (WMF) (talk)

2 Nupimbir 2018 21.16 (ICT)

Multilingual Shared Templates and Modules[babak asal mulanya]

Hello bjnwiki community! (Tolong bantu terjemahkan ke bahasa Anda)

I recently organized a project to share templates and modules between wikis. It allows modules and templates to be “language-neutral”, and store all text translations on Commons. This means that it is enough to copy/paste a template without any changes, and update the translations separately. If someone fixes a bug or adds a new feature in the original module, you can copy/paste it again without any translation work. My bot DiBabelYurikBot can help with copying. This way users can spend more time on content, and less time on updating and copying templates. Please see project page for details and ask questions on talk page.

P.S. I am currently running for the Wikimedia board, focusing on content and support of multi-language communities. If you liked my projects like maps, graphs, or this one, I will be happy to receive your support. (any registered user group can vote). Thank you! --Yurik (talk) 11 Mai 2019 12.51 (ICT)

Ruang nama (namespace) Lawang[babak asal mulanya]

Saya melihat ruang nama portal mulai dilokalkan menjadi lawang, namun ada 1 hal yang perlu diketahui bersama. Di dalam Wikipedia Banjar belum ada ruang nama portal/lawang. Selama ini portal/lawang menggunakan ruang nama utama yang biasanya dipakai untuk artikel. Untuk itu saya usulkan agar di dibuatkan ruang nama portal/lawang bagi Wikipedia Banjar ini dengan mengusulkannya ke Phabricator. Mungkin Mas @Ezagren: dan Pak @Mnam23: ada masukan? Nanti kesimpulan dari diskusi ini jika memungkinkan akan saya sampaikan ke Phabricator jua. Salam Wirjadisastra (pandir) 17 Mai 2019 19.54 (ICT)

Saya rasa hal tersebut sangat bagus. Saya sendiri cukup lelah menggunakan ruang nama utama. Namun, saya tidak tahu cara mengusulkannya, mengingat saya juga pengguna biasa. Mnam23 (pandir) 18 Mai 2019 20.52 (ICT)

mas @Wirjadisastra: bisa membantu untuk mengusulkannya? Saya sepakat agar dibuatkan segera. Ezagren ^{(kirim pasan)} 20 Mai 2019 08.56 (ICT)

Marakis sabagai pambakal antarmuha[babak asal mulanya]

Maraga kagiatan di WBB nang samagin maningkat, ulun handak maajuakan diri saurang sabagai pangurus atawa pambakal antarmuha di bjn gasan mambaiki'i hal-hal téknis cagar mamudahakan gawi mambabak wan lain-lain. Ezagren ^{(kirim pasan)} 20 Mai 2019 13.22 (ICT)

Manjatu suara[babak asal mulanya]

Hakun Wirjadisastra (pandir) 20 Mai 2019 13.32 (ICT)
Hakun Veracious (pandir) 20 Mai 2019 13.48 (ICT)
Hakun RaymondSutanto (pandir) 20 Mai 2019 13.50 (ICT)
Hakun ‹› ™ 20 Mai 2019 13.58 (ICT)
Hakun Taufiq mauliadi (pandir) 20 Mai 2019 14.08 (ICT)
Hakun Mnam23 (pandir) 20 Mai 2019 14.19 (ICT)
Hakun Mahakam Bahari (pandir) 20 Mai 2019 15.04 (ICT)
Hakun Marwan Mohamad (pandir) 20 Mai 2019 18.50 (ICT)
HakunAlamnirvana (pandir)
Hakun Sriw sw (pandir) 21 Mai 2019 21.30 (ICT)
Hakun Helmy Yunizar (pandir) 21 Mai 2019 22.35 (ICT)
Hakun Max Irwan (pandir) 22 Mai 2019 08.46 (ICT)
Hakun Dikarenakan memang dibutuhkan untuk Wiki ini.--Aldnonymous (pandir) 22 Mai 2019 08.54 (ICT)
Hakun Lya sitiaulia (pandir) 22 Mai 2019 13.51 (ICT)
Hakun Muklas Khusnul Abdillah (pandir) 23 Mai 2019 00.58 (ICT)
Hakun Mudahan kawa maksimal. Rie Mog erZ 25 Mai 2019 01.45 (ICT)

Wikidata Bridge: edit Wikidata’s data from Wikipedia infoboxes[babak asal mulanya]

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

Hello all,

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

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

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

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

Here’s the planned timeline:

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

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

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

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

More ideas will be added on this page along the way

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

Thanks for your attention, Lea Lacroix (WMDE) 24 Juni 2019 20.03 (ICT)

Basa Banjar atawa Banjar[babak asal mulanya]

Sahubungan lawan babarapa Wikipidia basa banua lain nangkaya Jawa wan Minangkabau nang mangganti autonim bahasa Jawa manjadi Jawa, bahaso Minangkabau manjadi Minangkabau, kikira manurut pandapat Pian, apakah kita umpatan jua? Lamun iya, kita bisa haja maubahinya manjadi "Banjar" haja, jadi tarasa labih handap. Tapi ada satu nang tarasa ganjal, sualnya Banjar itu banyak maknanya lamun dilihat wayah ini, kawa barupa suku bangsa, istilah di Bali, wan ngaran kota di Jawa Barat. Lamun sakiranya handak baubah, kaya apa? Ezagren ^{(kirim pasan)} 12 Juli 2019 10.20 (ICT)

Pandapat[babak asal mulanya]

Banjarmasin aja langsung krna mslkan Banjar sma lwan daerah yg ada d'provinsi lain tapi klau Banjarmasin itu org luar daerah psti tau klau kta org Banjar dngn bahasa Banjar na – kumintar kadada tanda tangan ini dibariakan ulih 182.1.193.40 (pandir • kontrib) .

Ini maksudnya lain identitas kota, tapi kita pakai identitas bahasa, apakah handak "Basa Banjar" atawa "Banjar" haja, gasan di Wikipidia. Ezagren ^{(kirim pasan)} 13 Juli 2019 07.52 (ICT)

hakun ai , kada ingat tanda "hakun"

Suara[babak asal mulanya]

Hakun pakai "Banjar", banjar aja sudah cukup karena dari kata banjar ini orang pasti berpikir wiki ini dari banjar dan berbahasa banjar Amang99 (pandir) 24 Juli 2019 19.29 (+07)[balas]
Hakun pakai "Banjar" Rie Mog erZ 15 Juli 2019 08.00 (ICT) -- Amun gasan Brand baik nang handap haja. Wikipedia Banjar, nang maksudnya manyambatakan Wikipedia bahasa Banjar. Istilah wahini tu jadi simple.
Hakun pakai "Basa Banjar", araha nang di navbar higa natap Basa Banjar, tapi judul wikinya barang dihandapi jadi Wikipidia Banjar Mnam23 (pandir) 20 Juli 2019 13.12 (ICT)
Hakun pakai "Basa Banjar", ulun lebih mamilih pakai "basa banjar" supaya labih kaliahatan jua identitas wikipidia kita – kumintar kadada tanda tangan ini dibariakan ulih Volstand (pandir • kontrib) .
Hakun pakai "Banjar" , supaya lebih simpel banar ai :v – kumintar kadada tanda tangan ini dibariakan ulih Muhammad Faisal Ansari (pandir • kontrib) .
Hakun pakai "Basa Banjar", Fikrizero sekira nyaman lawan jua Basa nih ada jua tulisannya dikenal urg – kumintar kadada tanda tangan ini dibariakan ulih Fikrizero (pandir • kontrib) .
Hakun pakai "Basa Banjar", mun banjar aja tuh luas konteksnya bisa daerah bisa bahasa jua jadinya rancu, pakai basa nyaman jelas kalo itu tuh bahasa banjarEsa Gita Shandy (pandir) 23 Juli 2019 13.15 (+07)[balas]
Hakun pakai "Basa Banjar", supaya kawa membedakan banjar banua lawan banjar-banjar lainnya Raxota (pandir) 25 Juli 2019 16.58 (ICT)
Hakun pakai Banjar haja, tapi rasanya ada jua Banjar lainnya, etnik Banjar di India.Alamnirvana (pandir)

Editing News #1—July 2019[babak asal mulanya]

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

Did you know?

Did you know that you can use the visual editor on a mobile device?

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

Edit Cards

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

Welcome back to the Editing newsletter.

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

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

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

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

Follow these instructions and share your experience:

📲 Try Edit Cards.

Recent releases[babak asal mulanya]

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

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

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

New and active projects[babak asal mulanya]

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

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

Looking ahead[babak asal mulanya]

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

Learning more[babak asal mulanya]

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

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

24 Juli 2019 01.32 (ICT)

Panjatuan Suara: Hapus Citakan:Wikipidia dairah matan Tungkaran Tatambaian[babak asal mulanya]

Citakan ngintu kada responsive, malalar taka higa nang maulah kada bungas gasan diitih.
Wikipidia Banjar nginih "malalain", marga Wikipidia dairah lain kadada nang mamasang citakan kaya ngintu lagi.
Pandiran ulun lawan pambakal Wikipidia Banjar Ezagren, sidin hudah hakun citakan ngintu dihapus, tapi ulun masih mahandaki kasapakatan matan pamakai nang lain supaya kada tarucau.

Mnafisalmukhdi1 (pandir) 24 Uktubir 2019 19.03 (+07)[balas]

Nang hakun[babak asal mulanya]

Hakun Ezagren ^{(kirim pasan)} 30 Disimbir 2019 08.26 (+07)[balas]
HakunAlamnirvana (pandir) 30 Disimbir 2019 22.06 (+07)[balas]

Nang kada[babak asal mulanya]

Pandapat nang lain[babak asal mulanya]

Editing News #2 – Mobile editing and talk pages[babak asal mulanya]

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

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

Help[babak asal mulanya]

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

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

Talk pages project[babak asal mulanya]

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

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

Mobile visual editor[babak asal mulanya]

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

Edit Cards[babak asal mulanya]

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

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

Toolbar[babak asal mulanya]

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

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

Wikimania[babak asal mulanya]

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

Looking ahead[babak asal mulanya]

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

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

29 Uktubir 2019 18.12 (+07)

Wikipedia Asian Month 2019[babak asal mulanya]

Tolong bantu terjemahkan ke bahasa Anda

Wikipedia Asian Month is back! We wish you all the best of luck for the contest. The basic guidelines of the contest can be found on your local page of Wikipedia Asian Month. For more information, refer to our Meta page for organizers.

Looking forward to meet the next ambassadors for Wikipedia Asian Month 2019!

For additional support for organizing offline event, contact our international team on wiki or on email. We would appreciate the translation of this message in the local language by volunteer translators. Thank you!

Wikipedia Asian Month International Team.

MediaWiki message delivery (pandir) 31 Uktubir 2019 23.57 (+07)[balas]

Extension of Wikipedia Asian Month contest[babak asal mulanya]

In consideration of a week-long internet block in Iran, Wikipedia Asian Month 2019 contest has been extended for a week past November. The articles submitted till 7th December 2019, 23:59 UTC will be accepted by the fountain tools of the participating wikis.

Please help us translate and spread this message in your local language.

Wikipedia Asian Month International Team

--MediaWiki message delivery (pandir) 27 Nupimbir 2019 21.16 (+07)[balas]

Wiki Loves Folklore[babak asal mulanya]

Hello Folks,

Wiki Loves Love is back again in 2020 iteration as Wiki Loves Folklore from 1 February, 2020 - 29 February, 2020. Join us to celebrate the local cultural heritage of your region with the theme of folklore in the international photography contest at Wikimedia Commons. Images, videos and audios representing different forms of folk cultures and new forms of heritage that haven’t otherwise been documented so far are welcome submissions in Wiki Loves Folklore. Learn more about the contest at Meta-Wiki and Commons.

Kind regards,
Wiki Loves Folklore International Team
— Tulsi Bhagat (contribs | talk)
sent using MediaWiki message delivery (pandir) 18 Januari 2020 13.14 (+07)[balas]

Editing news 2020 #1 – Discussion tools[babak asal mulanya]

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

Screenshot showing what the Reply tool looks like

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

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

Reply tool improved with edit tool buttons

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

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

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

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

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

9 April 2020 02.24 (+07)

Editing news 2020 #2[babak asal mulanya]

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

Mockup of the new reply feature, showing new editing tools

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

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

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

– Whatamidoing (WMF) (talk)

18 Juni 2020 03.32 (+07)

Editing news 2020 #3[babak asal mulanya]

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

A gold star with a blue ribbon, and the text 50m

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

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

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

Whatamidoing (WMF) (talk)

9 Juli 2020 19.55 (+07)

Wadah ngaran Portal wan Portal talk kadada di Wikipidia Banjar[babak asal mulanya]

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)

Wikipidia Banjar kadada baisi Portal wan Portal talk. Padahal ngintu salah sabuting wadah ngaran nang panting.

Manurut ulun, istilah nang bagus adalah Lawang gasan Portal lawan Pamandiran Lawang gasan Portal talk. Bagus lah kikira?

Ulun sudah maajuaakan di Phabricator soalnya. Panjatuan suara babanaran parlu disini sakalinya.

Lawang for Portal, Pamandiran Lawang for Portal talk.

Panjatuan suara[babak asal mulanya]

Hakun Mnafisalmukhdi1 (pandir) 3 Agustus 2020 16.03 (+07)[balas]
Hakun Semoga portalnya dapat berkembang dan tetap terjaga. Medelam (pandir) 3 Agustus 2020 17.08 (+07)[balas]
Hakun Satuju haja, tagal ulun masih ada pamikiran, jaka sakiranya dirasa cocok lamunnya "Portal" diganti Palawang kata dasar Lawang gasan membeda'akan Lawang nang artinya pintu dalam basa Banjar. Alamnirvana (pandir) 3 Agustus 2020 18.28 (+07)[balas]
Hakun Volstand amunnya palawangan pang kaya apa
Hakun lawan "Palawang" gasan mambidaakan wan 'lawang' Ezagren ^{(kirim pasan)} 4 Agustus 2020 08.05 (+07)[balas]
Hakun Muhammad Faisal Ansari ulun satuju haja pang ka ai..
Hakun RaymondSutanto (pandir) 6 Agustus 2020 14.26 (+07)[balas]
Hakun Blue Sonic (pandir) 8 Agustus 2020 19.36 (+07)[balas]

Hasil[babak asal mulanya]

Total 8 suara per 10 Agustus 2020. 5 setuju dengan "Lawang", 3 memilih "Palawang"
Palainan pandapat baarti masih balum sapakat. Amun handak “Palawang” kita maajuakan baasa.

Mnafisalmukhdi1 (pandir) 10 Agustus 2020 20.17 (+07)[balas]

Panjatuan suara lanjutan[babak asal mulanya]

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)

Latar Belakang[babak asal mulanya]

Kasapakatan balum kawa dihaga.
Palawang tamasuk di akal marga jamaknya Portal yakni Portals bisa diartiakan "Palawangan"

Kaputusan[babak asal mulanya]

Ulun sawagai nang maugai panjatuan suara, mamutusakan gasan manjatu baasa yakni:
Palawang for "Portal" dan Pamandiran Palawang for "Portal talk"

Peraturan[babak asal mulanya]

Nang hakun harus labih matan 5.
Ditutup 17 Agustus 2020.

Nang hakun[babak asal mulanya]

Hakun Palawang Ezagren ^{(kirim pasan)} 13 Agustus 2020 08.13 (+07)[balas]

Hakun Palawang Muhammad Faisal Ansari

Hakun Palawang Volstand tapi amun nang portal talk tu ngarannya palawang pamandiran kaya apa?

Hakun Palawang Aas kim