User talk:Elitre (WMF)/Archive 1

Benvenuto/a!

Ciao Elitre (WMF)! Un benvenuto da parte mia sulla Meta-Wiki di Wikimedia! Questo sito serve a coordinare e discutere di tutti i progetti Wikimedia. Potrebbe esserti utile leggere le nostre policy (in inglese). Se sei interessato a fare traduzioni, visita Meta:Babylon. Puoi anche lasciare un messaggio su Meta:Babel o Wikimedia Forum (ma per favore, leggi le istruzioni che si trovano all'inizio della pagina prima di scrivere). Se vuoi, puoi lasciarmi un messaggio nella mia pagina di discussione. Buona fortuna!

--Ricordisamoa 12:32, 25 June 2013 (UTC)

Ciao, Elitre: ti spiego le mie possibilità e forze..

Ciao, cara Elitre,.. che forza "essere parlate" da un'altra umana, collega emiliana, per di più donna, qua dentro!!.. Perchè oramai credevo di essere l'unica, scusa se mi esprimo così, secchiona imbranata, attaccata a 'valori' semplici, ma forse non poi così tanto condivisibili.. Pazienza,.. Ti spiego in poche parole la mia posizione, se avrai la bontà di non annoiarTi: ultimamente mi sento ispirata, oltre che dalla voglia di incrementare gli artt. della 'mia' eml.wikipedia, dalla obiettiva e personale necessità di approfondire l'argomento troppo nuovo della 'nanotecnologia' e di quello che gli ruota intorno, bisogno (dovrei farcela) dovuto alla ahimè forse incauta promessa della mia figlia grande (15 years old) alla sua prof di eseguire, durante la pausa estiva, una tale relazione scritta, per di più in inglese.. Ora chiaramente lei teme di non farcela, e la mamma credo che dovrà aiutarla almeno a presentare una ricerchetta anche solo per non smentirsi davanti alla prof...: mio obiettivo nr 1: la ricerchetta sulle nanotech; a pari merito, al 2°) posto, gli artt. in eml e la traduzione che mi hai chiesto; il tutto chiaramente al di fuori dell'orario di lavoro, dei lavori di casa, dei nonni da accudire dovutamente senza molti altri aiuti.. Il tempo che potrò dedicare alla traduzione che mi ciedi? Diciamo 3 o 4 paragrafi ogni 12 ore.. soprattutto se prima l'hanno già tradotta i francesi, visto che in Francia mi sento molto più ferrata!! Ma com' è la Tua storia? Scusa l' invadenza (simpa la Tua foto nella Tua pagina), ma quindi Te lavori per la Foundation? Inevitabile, visto che siamo in argomento: stipendiata? Perdonami, a presto, --Gloria sah (talk) 21:20, 12 July 2013 (UTC)

Ciao, carissima, sai che cliccando sul collegamento del collega italiano Kirk39, non mi sembra di trovare riferimenti alla pagina del manuale cui Ti stai riferendo? Hai qualche collegamento più diretto, oppure dovrò chiedere a lui, di spartire con me quella traduzione? A presto, --Gloria sah (talk) 22:09, 15 July 2013 (UTC)

traduzione e VisualEditor

Ti devo confessare che nel corso che ho fatto il 16 e 17 scorsi non ho dato bella prova sull'editor; ma prometto che per il corso della prossima settimana mi preparo meglio. Ho notato per esempio che dopo aver inserito un link non è esplicito cosa fare? non c'è bottole da clickare, ma se non ho capito male si deve solo dare invio. Per le traduzioni quando hai bisogno segnalamele. Ciao Susanna --Giaccai (talk) 06:07, 18 July 2013 (UTC)

Reply

Hai un nuovo messaggio alla mia pagina di discussione. Ciao, --Smihael (talk) 15:03, 19 July 2013 (UTC)

VisualEditor updates

Please help translate this message.

We recommend that community champions translate the newsletter and post it to local Village Pumps or relevant noticeboards.

• The Wikimedia Foundation's engineering department holds monthly office hours to discuss VisualEditor. Please join Product Manager James Forrester to discuss the products and upcoming plans in April.

Saturday 2014-04-19, at 20:00 UTC.

The discussion will be on IRC (w:Internet Relay Chat) at irc://irc.freenode.net/wikimedia-office. For more information on office hours, including how to attend, please see m:IRC office hours. Logs will be posted at Meta afterwards.

If office hours are heavily attended, it can be difficult to get to all questions, but if you want to ask a question and cannot attend or do not speak English, then please let us know your question on mediawiki.org by the day before, and someone will add it to possible discussion topics.

• VisualEditor has changed a lot recently, and you didn't notice it? You can be alerted to major updates on your own talk page, thanks to the newsletter! Less "technical" than the regular status updates delivered at mediawiki.org, it's a good way to keep up to date with changes. Sign up now to make sure you get the next issue.
• Did you know? There are just 2 URLs to check if you want to learn how your language is doing with regards to translation for VisualEditor's interface or help pages. Is it in the green (good!) area, or in the red (baaad!) one? Find out now, then click on your language code to update the translations!

Interface

Help pages

--Elitre (WMF) (talk) 16:31, 7 April 2014 (UTC)

VisualEditor newsletter, 23 April 2014

Did you know?

You can use VisualEditor to make a redirect. First, remove any unwanted content from the page. Then go to the "Page options" menu (next to "⧼visualeditor-toolbar-cancel⧽") and choose the "Page settings" item. Click the box to "Redirect this page to". In the box, type in the name of the page that you want to redirect this page to.

You can also set or remove categories for the redirect in the "Page options" menu. Read the user guide for more information.

Since the last newsletter, the VisualEditor team has mostly worked on performance improvements, image settings, and preparation for a simplified citation template tool in its own menu.

• In an oft-requested improvement, VisualEditor now displays red links (links to non-existent pages) in the proper color. Links to sister projects and external URLs are still the same blue as local links.
• You can now open templates by double-clicking them or by selecting them and pressing  ↵ Return.  This also works for references, images, galleries, mathematical equations, and other "nodes".
• VisualEditor has been disabled for pages that were created as translations of other pages using the Translate extension (common at Meta and MediaWiki.org). If a page has been marked for translation, you will see a warning if you try to edit it using VisualEditor.
• When you try to edit protected pages with VisualEditor, the full protection notice and most recent log entry are displayed. Blocked users see the standard message for blocked users.
• The developers fixed a bug that caused links on sub-pages to point to the wrong location.
• The size-changing controls in the advanced settings section of the media or image dialog were simplified further. VisualEditor's media dialog supports more image display styles, like borderless images.
• If there is not enough space on your screen to display all of the tabs (for instance, if your browser window is too narrow), the second edit tab will now fold into the drop-down menu (where the "Move" item is currently housed). On the English Wikipedia, this moves the "Edit beta" tab into the menu; on most projects, it moves the "Edit source" tab. This is only enabled in the default Vector skin, not for Monobook users. See this image for an example showing the "Edit source" and "View history" tabs after they moved into the drop-down menu.
• After community requests, VisualEditor has been deployed as an opt-in feature at Meta and on the French Wikinews.

The drop-down menu is on the right, next to the search box.

Looking ahead:  A new, locally controlled menu of citation templates will put citations immediately in front of users. You will soon be able to see the Table of Contents while editing. Support for upright image sizes (preferred for accessibility) is being developed. In-line language setting (dir="rtl") will be offered as a Beta Feature soon. Looking further out, the developers are also working on support for viewing and editing hidden HTML comments. It will be possible to upload images to Commons from inside VisualEditor.

If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at mw:VisualEditor/Feedback or by joining the next office hours on Monday, 19 May 2014 at 18:00 UTC.

If you'd like to get this on your own page, subscribe at m:VisualEditor/Newsletter for any project (or at w:en:Wikipedia:VisualEditor/Newsletter for English Wikipedia only).

Thank you! -- Elitre (WMF), 17:24, 24 April 2014 (UTC)

VisualEditor global newsletter—June 2014

Did you know?

The character formatting menu, or "Style text" 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 "Keyboard shortcuts" link out of the "Page options" menu, into the "Help" 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 "Page options" menu, rounding out the full set of page options currently planned.
• The tool to insert special characters is now wider and simpler.

Looking ahead

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

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

Supporting your wiki

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

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

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

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

To change your subscription to this newsletter, please see the subscription pages on Meta or the English Wikipedia. Thank you! --Elitre (WMF) 14:57, 25 June 2014 (UTC)

VisualEditor global newsletter—July and August 2014

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

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

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

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

Looking ahead

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

Feedback opportunities

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), 17:53, 11 August 2014 (UTC)

Mediaviewer Edit

Thank you for reverting that, it was probably a poor idea. I'm just very frustrated. I'm in the minority of users who like Mediaviewer, but think that WMF should implement the consensus for the RfCs. I think its a great tool though and the focus of Talk:Community Engagement (Product)/Media Viewer consultation needs to be on how to improve it not how much everyone hates it. If you can think of a better way to get that across to people, I'd really love that. I usually ignore all drama, but between Meta, en.wp, de.wp, Commons, and wikitech-l its been hard to do. Frustrated sleep deprived person is frustrated. Zellfaze (talk) 11:15, 30 August 2014 (UTC)

Traduzioni

Semplicemente perché non trovo accettabile che pagine così importanti non siano tradotte in italiano. L'altro giorno entrando nella wikipedia italiana ho visto l'avviso della consultazione e l'ho seguito per curiosità. Ho visto che mancava poco al completamento allora ho cominciato, un paragrafo qui, uno là, ... e dalle traduzioni in Meta sono finito in Media. Spero che la voglia non mi passi, sono un pò umorale... Aquatech (talk) 16:45, 2 September 2014 (UTC)

Grazie! E grazie anche per la segnalazione. No, non mi ero iscritto perché all'inizio non credevo che avrei continuato a tradurre. A questo punto lo farò molto volentieri! Ciao! Aquatech (talk) 12:13, 19 September 2014 (UTC)

No, ho deciso di dedicarmi alle pagine più basilari di questa wiki, tipo Wikimedia Foundation, sua struttura, eccetera e di procedere un argomento alla volta (per esempio tra qui e Media ho tradotto tutto (credo) quello che riguardava Media Viewer prima di passare oltre). Ciao! Aquatech (talk) 06:21, 9 October 2014 (UTC)

VisualEditor available on Internet Explorer 11

VisualEditor will become available to users of Microsoft Internet Explorer 11 during today's regular software update. Support for some earlier versions of Internet Explorer is being worked on. If you encounter problems with VisualEditor on Internet Explorer, please contact the Editing team by leaving a message at VisualEditor/Feedback on Mediawiki.org. Happy editing, Elitre (WMF) 07:25, 11 September 2014 (UTC)

PS. Please subscribe to the global monthly newsletter to receive further news about VisualEditor.

You have new messages

Hello, Elitre (WMF). You have new messages at Ralgis's talk page.
You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.

Ping

You asked on ru:, " did you get a notification of this ping?" - no. The last notifications are dated Sep. 11, 6 and 4 (not pings), the last ping was Aug. 20. - Retired electrician (talk) 13:48, 25 September 2014 (UTC)

You have new messages

Hello, Elitre (WMF). You have new messages at Ralgis's talk page.
You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.

Ovtober VisualEditor Newsletter translation

Ciao Elitre, non ho ancora finito la traduzione tedesca: Qual'è la differenza tra "reference" e "citation"? Grazie, --Gnom (talk) 11:52, 10 October 2014 (UTC)

Inoltre, siccome non sono un wiki-traduttore con tanta esperienza, son so tanto bene come fonzionano le espressioni "$"... --Gnom (talk) 12:07, 10 October 2014 (UTC)

Okay, fatto! --Gnom (talk) 13:47, 10 October 2014 (UTC)

VisualEditor News #8—2014

Did you know?

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

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

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

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

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

Increased support for devices and browsers

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

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

TemplateData editor

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

Other changes

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

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

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

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

Looking ahead

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

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

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

Supporting your wiki

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

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

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

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

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

09:41, 13 October 2014 (UTC)

VisualEditor News #8—2014

Did you know?

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

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

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

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

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

Increased support for devices and browsers

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

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

TemplateData editor

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

Other changes

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

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

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

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

Looking ahead

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

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

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

Supporting your wiki

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

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

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

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

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

09:46, 13 October 2014 (UTC)

VE newsletter

We, the Korean Wikipedia has own venue for technology-related VP (VPT) at ko:백:기술 - please send newsletter to there next time. — revi^☏ 09:56, 13 October 2014 (UTC)

Sorry, I forgot to tell you that kowiki VPT uses monthy-subpage (so delivery page should be (main page)/2024년 11월). Sorry for the mess created by miscommunication! — revi_msg 00:49, 15 November 2014 (UTC)

Why VE

Hi, on plwiki, we have a serious problem related to VE. Personally, I'm enthusiastic about the changes, but more and more experienced contributors ask me: why VE? if we don't need this, why do you claim the newbies do? Is there any research, any verifiable, detailed data that would confirm or deny following theses?

1. The newbies prefer VE than the source editor and they are more likely to stay after some experience with VE.
2. VE as default while clicking on a red link (veaction=edit instead of action=edit, 1st link over there) with no expressed local consensus = POV and violation of rules.
3. VE should be linked from pages like ↑ that (MediaWiki namespace, helppages etc.), otherwise it won't work despite its technical availability (won't be used often enough by the newbies, who btw find the interface to be quite confusing).
4. If enwiki doesn't let IPs to create new articles and some other big wikis have red links with action=edit as default everywhere, there's no need to act in another way.
5. Only local community is allowed to accept or reject every software change.

If you think someone else has better knowledge/more links etc., ping her/him, please. Thanks a lot. Tar Lócesilion|queta! 19:55, 13 October 2014 (UTC)

Thanks for the link, it is very helpful. I'll be extremely grateful for any more data. Like a big corporation: we don't have to hide info, we just don't communicate effectively. Maybe we report few our actions, maybe we report it wrong, maybe we promote the existing reports insufficiently. I have this problem locally: to keep working and doing my best, or to report (oh no, personally) and work more slowly (= waste my time?).

A funny fact, despite keeping in touch with Bartosz Dziewoński (we often collaborate) I had no idea about, for instance, the impact expectations and default in 2015 (Q1 review, slide 7). So VE is not default yet. But still (I ask myself) is it main/primary on our wiki (ofc in main ns), or is it just linked in the 1st tab? (As 'Edit', before 'Edit source'). So should we recommend it broadly? Many power users 'appreciate the choice', prefer wikicode and their compromise is to put both links. Their argument is: VE doesn't aim to encourage newbies at the expence of existing users. Meanwhile, I suppose, newbies don't like too much choice situations, because they get into a labyrinth^{[research needed]}. Well, there we have our goals and generally #moreresearch. Btw, Abbey's survey results suprised me. Only 39 responses? it was so easy! even I, a single local volunteer, can get more responses, it's just matter of... communication :>

As for the office hours, I'll come. Tar Lócesilion|queta! 00:16, 15 October 2014 (UTC)

Some kind of research needs only a few participants, but sometimes, there might be slight differences between users of different wikis. I don't know whether all significant research are done with representative sample. I took part in the survey, btw. During James' presentation, I was in the audience and remember that most of all, the presentation answered general questions (no surprise). The team improves VE and it's +1, but as you can see, what interests me is how to deal with VE. I'm planning to ask our VE-sceptics for their feedback. We'll see... Tar Lócesilion|queta! 10:59, 15 October 2014 (UTC)

Yup, actually, I've sent her one e-mail on Saturday, it was about research tools. Without payment, I can set max 30 cards in the programme she uses, and I need more than 50. Ofc I don't want to pay $1000.

Well, there are many ways to contact me. Wikis, e-mail, IRC, Facebook, as you wish. Tar Lócesilion|queta! 12:33, 15 October 2014 (UTC)

Look at this. I asked the most experienced users for feedback about VE. 1. Do you use VE (ofc mostly, we don't), 2. if you prefer to have it opt-out in prefs, why, 3. what are your remarks, what disturbs you. Answers are interesting from their very beginning. Tar Lócesilion|queta! 13:01, 16 October 2014 (UTC)

True, many users know nothing about changes in VE. Yesterday one of our most productive tech-power users was complaining about editing infoboxes, because... he had no idea about changes in TemplateData. But some concerns actually exclude VE, e.g. editing offline, HotCat and similar tools, find and replace & regexes. Too much dialogs, choosing and clicking vs. copy and paste some code. Besides, habits and no need to learn sth new that is in beta phase. Tar Lócesilion|queta! 14:27, 16 October 2014 (UTC)

Fellow Tar missed several other important issues reported during discussion at Look at this above, so I will put them here. Acceptance for VE among experienced editors is low, as we put simplicity yet versatility and speed of editing wikicode over visual editing. The issues raised were: poor or very poor performance on slower machines or using slower connections, much higher resource use (on my computer up to tenfold compared to a medium class text editor with highlighting), no or limited support for several major citing templates (like Odn, R or classic HTML ref, which does not obscure the results in search results, contrary to the R reference template), limited support for less popular, but still major Web browsers as Opera, no toolbox with special but useful signs (different styles of hyphens, Celsius etc., available in classic wikitext editor). Last but not least: usability without a mouse drops substantially. As wikieditor is an immanent part of Mediawiki software, there is no need to switch it off, as long there are contributors willing to make use of it (and there are). Bonvol (talk) 19:18, 25 October 2014 (UTC)

Visual Editor News Posting on Occitan Wikipedia

Ciao,

Our Occitan-language "Tavèrna" (community discussion) is getting news in English about VE. We'd really appreciate you post those news to the "Tavèrna dels non-occitanofòns" instead. Thanks in advance.

Regards, --Jfblanc (talk) 09:02, 23 October 2014 (UTC)

Thanks for the move. As of today, the few of us active editors on the Occitan wp do not have the necessary "bandwidth" to translate this newsletter. This is the reason why I requested the move ;( Grazie mille. Saluti cordiali, --Jfblanc (talk) 10:00, 23 October 2014 (UTC)

Bug description at Romanian Village pump

Hi, Elitre. Here are the details of the bug I want to report. Thank you!–Minisarm (talk) 20:41, 5 November 2014 (UTC)

Ready for translation: VisualEditor News #9—2014

Ti ringrazio per l'invito (e di esserti ricordata di me!), ma ultimamente ho veramente poco tempo a disposizione e ho ridotto all'osso la mia presenza sulle wiki. Spero di essere più utile in futuro. Ciao! Aquatech (talk) 10:06, 11 November 2014 (UTC)

About research program

Hey! :)

I saw that there's a research program announcement at VisualEditor/Newsletter/2014/November. Do you know is it the same research program that was made at the time (or the end) of Wikimania? I remember that I answered that kind of questions earlier, so I don't want to make it again, if it's the same. Thanks! --Stryn (talk) 18:14, 11 November 2014 (UTC)

You have new messages

Hello, Elitre (WMF). You have new messages at Ralgis's talk page.
You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.

RE

Addirittura? :D *blush*--Nnvu (talk) 19:32, 14 November 2014 (UTC)

VisualEditor News #9—2014

Did you know?

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

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

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

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

Recent improvements

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

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

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

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

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

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

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

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

TemplateData

The tool for quickly editing TemplateData has been deployed to all Wikimedia Foundation wikis on Thursday, 6 November. This tool was already available on the biggest 40 Wikipedias, and now all wikis will have access to it. This tool makes it easier to add TemplateData to the template's documentation. When the tool is enabled, it will add a button above every editing window for a template (including documentation subpages). To use it, edit the template or a subpage, and then click the "Edit template data" 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 "suggested" or "optional" in TemplateData instead.

Looking ahead

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

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

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

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

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

23:23, 14 November 2014 (UTC)

RE: traduzione

Ciao Elitre, mi scuso ma pensavo che funzionasse come il wiki. Starò più attenta la prossima volta. Ciao --93.45.105.58 14:46, 15 November 2014 (UTC)

Visual Editor Newsletter

Hi Elitre, I read in the newsletter that the documentation pages in several languages are outdated. I just noticed that even the English one is outdated. It is essential that the English version is complete. All the options for type in the template documentation editor should be described because it is now a mystery when to use for example "line", etc. In the past I have noticed this multiple times, the basic English documentation is not updated. Something in the workflow is not working...
Also the English type names are vague, a number of the Dutch type names are even worse. I can't solve that as I do not understand the English ones, which aren't described either.
So if I may give you a suggestion, please solve these two issues. Thanks! Romaine (talk) 08:24, 17 November 2014 (UTC)

Greetings and... request

Greetings Elitre. I'd be grateful if you could please delete the page I just created by mistake (Translations:Community Engagement (Product)/Product Surveys/1/qqq) when tweaking the survey page in Spanish (or arrange for it to be deleted). Many thanx. Regards, --Technopat (talk) 19:50, 16 December 2014 (UTC)

RE: Nesletter

Oh, niente di che. Non è necessario specificare l'accento se la parola non può essere confusa in italiano. Diciamo che Chrome mi ha quasi obbligato a togliere l'accento xD.--Nnvu—α†Ω 12:26, 22 December 2014 (UTC)

Oh, sì, vero anche questo. Possiamo anche rimetterlo, allora :D Ops, ho fatto copia-incolla di itwiki e non ho cambiato i link. Grazie per l'avvio ;)--Nnvu—α†Ω 12:33, 22 December 2014 (UTC)

Newsletter translator

As stated in the newsletter I can contact you for direct notifications about the newsletter translation. Please notify me, and please feel free to do so for any other high priority (or not) VisualEditor related translations, @meta, @el.wiki or @el.wikisource. Thank you. —Ah3kal (talk) 07:03, 23 December 2014 (UTC)

VisualEditor News #10—2014

Did you know?

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

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

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

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

Recent improvements

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

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

You can now create and edit simple <blockquote> paragraphs for quoting and indenting content. This changes a "Paragraph" into a "Block quote".

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

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

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

You can again create and edit galleries as wikitext code.

Looking ahead

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

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

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

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• Translations of the user guide for most languages are outdated. Only Ukrainian, Portuguese, Spanish, French, and Dutch translations are nearly current. Please help complete the current translations for users who speak your language.
• Talk to the Editing team during the office hours via IRC. The next session is on Wednesday, 7 January 2015 at 22:00 UTC.
• File requests for language-appropriate "Bold" and "Italic" 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)

18:56, 26 December 2014 (UTC)

Happy new years 2015

Happy New Year Elitre (WMF)/Archive 1 --Grind24 (talk) 23:48, 31 December 2014 (UTC)

VisualEditor su Wikibooks

Buondì! Sono un utente di Wikibooks. Volevo sapere se fosse possibile richiedere l'implementazione di funzionalità di VisualEditor specifiche per un progetto: tempo fa la comunità di Wikibooks si è organizzata per far "rifiorire" il progetto, sistemandolo per una campagna di pubblicizzazione che dovrebbe portarvi nuovi utenti. Volevamo puntare sulla scuola, facendo diventare Wikibooks un luogo dove trovare anche eserciziari e libri di testo aggiornati. Tuttavia abbiamo un grosso problema: l'editing richiede tantissimo tempo e non è per nulla intuitivo. Rimuovendo questo problema renderemmo Wikibooks un sito perfetto per la pubblicazione di esercizi, appunti ecc. e ci stiamo adoperando per creare template e testo preformattato, rivedere le pagine di aiuto, creare video tutorial ecc. ma ora come ora il sito è molto difficile da usare.
VisualEditor per ora è impostato per Wikipedia, ma sarebbero necessarie altre funzioni (che sulla tabella di marcia sono lasciate ultime) come cambiare sfondo alle celle di una tabella, cambiare font, utilizzare intuitivamente span e div ecc. e sarebbe utilissimo automatizzare l'inserimento di template come Template:Ese, ancora in fase di programmazione ma indispensabile per creare gli eserciziari (esempio).
Saluti. --Riccardo R. 18:45, 3 gen 2015 (CET)

Scusa il ritardo di risposta. Sfortunatamente non conosco nessun programmatore ma mi sto adoperando da tempo per cercare e coinvolgere gente. Da un po' sto cercando anche di informarmi bene su VE ma non essendo pratico di Meta (e l'inglese non mi aiuta) ci sto impiegando un po'.

Le migliorie che richiedevo avevano due scopi: il primo è rendere veloce ed intuitivo fare quelle piccole e semplici cose che favorirebbero l'uso scolastico di WB, sfavorito invece dal lungo ed ostico lavoro di scrittura dei codici HTML.

In secondo luogo c'è una grande importanza didattica nel poter formattare il testo in modo da evidenziare le informazioni più importanti, isolare i concetti ed enfatizzarli, rendere più leggera la lettura e più facile l'assimilazione delle informazioni, nonché attirare l'attenzione degli studenti e rendere il materiale di Wikibooks più simile anche graficamente ai veri libri di testo. Pensa per esempio ad una tabella del genere con come sfondo di ogni cella la foto o il colore del risultato della reazione avvenuta, invece che la descrizione letterale. Con altri strumenti come Word o PowerPoint ciò è facilmente possibile mentre su Wikibooks costerebbe settimane di lavoro. --Riccardo R. 16:20, 7 gen 2015 (CET)

Grazie mille delle informazioni! Appena avrò una richiesta sufficientemente numerosa ti ricontatterò, nel frattempo mi sentirò anche coi membri attivi di Wikibooks. Grazie ancora! --Riccardo R. 20:47, 9 gen 2015 (CET)

How to remove the mandatory "load to commons" image feature from the oc wikipedia?

Hello,

In France it is the last day for new year wishes, so all the best to you :)

I have lost the track of the message from some administrative user that explained we were no more needing the file upload feature in the Occitan wikipedia, and that we would now directly upload to commons. I'd like to revert this, as we are stick by some "copyright limitations" that do not apply to the en wikipedia, and that are not applicable, either, in the countries where Occitan is used.

For a specific example, we are unable to re-use the African Union symbols that are visible, for instance, in the English wikipedia, as they are local files not available in Commons.

I'm not sure you'll be able to perform the operation, but I'm pretty sure you will redirect this to the proper person. Isn't it?

Thanks in advance,

--Jfblanc (talk) 09:49, 31 January 2015 (UTC)

VisualEditor News #1—2015

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

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

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

Recent improvements

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

• starts a new task, like opening the ⧼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

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

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

Let's work together

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

— Elitre (WMF)

18:08, 5 February 2015 (UTC)

ca.wikiquote

Hi! The name of the ca.wikiquote village Pump is not q:ca:Viquidites:La tavernas. Is q:ca:Viquidites:La taverna (Without the ending s). Thanks for the reports! --Unapersona (talk) 19:07, 5 February 2015 (UTC)

Well, maybe I can help... I'm not en-5, but I can translate a text :)--Unapersona (talk) 19:14, 5 February 2015 (UTC)

The translation is: La Fundació Wikimedia ha decidit les seves prioritats per aquest trimestre (De Gener a Març). La primera és preparar l'Editor Visual per activar-lo per defecte a tots els usuaris nous i anònims a tota la resta de Viquipèdies. Hi hauràn reunions setmanals obertes als voluntaris que començaràn el Dimecres 11 de febrer de 2015 a les 12:00 (noon) PST (20:00 UTC). Comunica al vice-president de la Engineering Damon Sicore, Product Manager James Forrester i altres membres de l'equip quins bugs i funcionalitats són més importants per tu. Les decisions preses en aquestes reunions determinaran quina feina és necessària per l'objectiu d'aquest trimetre. La presència de voluntaris que gaudeixen contribuïnt en el codi MediaWiki és especialment apreciada. La informació sobre com formar part de la reunió serà publicada a mw:Talk:VisualEditor/Portal en breu, abans de que les reunions començin.

I don't know how to trandlate "Engineering Damon Sicore, Product Manager", but I whink that it is not necessary.--Unapersona (talk) 19:34, 5 February 2015 (UTC)

Some questions

Hello,

1. Where are the list of community page you deliver your messages?
2. The owners of related projects to mediawiki seems not accepting patches from individuals, why is that? Is it because they think no-wikimedia employees shouldn't commit to projects?

Thank you. Mjbmr (discussion • contribs) 19:40, 5 February 2015 (UTC)

Re:

Like I had a problem with a wiki and since no one is willing to resolve bugs I tried to make a patch myself. Code review #186762 was reviewed and was issued some problem and after I fixed them in #186817 the person didn't try to review I know the person was active even I opened a ticket and didn't respond. The other issue I had and patched in #184290 the person tried to ignore it and vote down without any good reason. Mjbmr (discussion • contribs) 20:41, 5 February 2015 (UTC)

1. #186762 #186817 (T88396)
2. #184290 (T85959)

I know you're busy so I provided links for you. Also these might be interested for you T87646, T87140. Mjbmr (discussion • contribs) 21:16, 5 February 2015 (UTC)

T86505 and T86504 was closed unresolved. T78776 was also helpless. Mjbmr (discussion • contribs) 22:14, 5 February 2015 (UTC)

Hi Mjbmr, thanks for your comment. As this covers more the engineering community aspects, I will try to answer here (I'm part of the mw:Engineering Community Team).

Looking at the 32 tasks that you have created in Maniphest (thanks for your help in making Wikimedia better!), 23 are closed as fixed and 4 are open. That's not too bad, congratulations! :)

Looking at phab:T78776#933965, you received feedback and the issue was investigated and resolved within a 52 hours. Could you elaborate why you considered it "helpless"? Regarding phab:T86504 you could ask again on the ticket if the problem has not been resolved for all pages, or ask for steps how to fix this yourself. In general, you can receive faster and better answers by providing exact steps to reproduce problems.

Looking at the patch review situation, you wrote that "in #184290 the person tried to ignore it and vote down without any good reason". Looking at that patchset, the comment for the -1 says "Missing message Qqq". To me that sounds like a reason; is something unclear with that message? If so, you might want to ask in Gerrit for clarification, or talk to the reviewer in person (e.g. on IRC). Also, the next comment states that a setting already exists. Just for your interest, both these commenters do not work for the Wikimedia Foundation (as you mentioned "no-wikimedia employees" before). And the latest revision of one of those other two changesets (#186762) is only three days old, so I kindly ask you for some more patience here.

In general, regarding the code review of patches, there is an ongoing debate how to prioritize code review of patches submitted by volunteers (and that also covers technical aspects that are related to the "Gerrit" tool that Wikimedia currently uses for code review, for example that Gerrit does not know the concept of one specific owner for a code area, so it could happen that several people are added as reviewers to a patch in Gerrit but every reviewer assumes that another reviewer will review the patch, which is not good). These are problems that we need to discuss and solve together. That debate also links to a graph that shows the age of open changesets by affilation (volunteers vs. involved companies]. While reviewing patches by volunteers indeed does take a bit longer currently, personally I would not say that Wikimedia does not accept patches from individuals at all. Contributions are very welcome in free and open source software projects, but some areas are "more" maintained than others. I'm not sure if this covers all of your questions and concerns but I encourage you to not hesitate and ping on your patches (or in addition ask reviewers on IRC) when a review has not happened within one or two weeks. Thanks! --AKlapper (WMF) (talk) 14:02, 6 February 2015 (UTC)

@AKlapper (WMF): In T78776 you be like, meh! it was solved by it self we don't have to debug anything! cool! we pray it won't happened again! is that it? shouldn't just wait for people who are behind these servers what exactly happened and how they can resolve this? I had the same exact problem four years ago, but all I just hear is everything is getting better and better. "Missing message Qqq" is not my problem shouldn't that person wait till Siebrand respond? I said "Is it because they think no-wikimedia employees shouldn't commit to projects?" I've been talking about a type thoughts that might be avoiding this, not even mentioned they're wikimedia employees, in my opinion they're getting hired by wikimedia in the future because I talked to one of them recently. I'm already aware of wikimedia's blog about developing always says "we", I'm not sure what this "we" refers to, like when BBC interviewer asked Wales how do you verify the accuracy of news articles, he said we have those people, but I saw people were publishing non-NPOV articles when I was absent. things always just being said performing of them is not what always happens. Mjbmr (discussion • contribs) 14:48, 6 February 2015 (UTC)

Mjbmr: "We" is everybody - you, me, everybody in the Wikimedia movement. It is a shared responsibility. Regarding T78776, if you are not sure whether the underlying problem has been identified and fixed, you could explicitly ask on the task. Sometimes time and priority constraints indeed do not allow deeper investigation, but I don't know if that was the case in that specific task. Regarding the Gerrit patch, "Missing message Qqq" is maybe not your problem, but anybody interested in getting the patch closer to getting it merged could and should fix the patch to include the missing Qqq message. I'm not sure why a response from Siebrand should be needed here? The general comment that such functionality might already exist still stands though (I cannot comment on that one as I don't know the codebase) and might be a reason to not accept that patch in the end if someone thinks that the patch does not offer the "right" solution to the problem. --AKlapper (WMF) (talk) 19:46, 6 February 2015 (UTC)

@AKlapper (WMF): Please see phab:T95009#1181035. Mjbmr (discussion • contribs) 22:30, 5 April 2015 (UTC)

@Mjbmr:: Hi, I have seen that (I am subscribed to that task). If something is unclear you could bring that up in that task where there's a bit more audience to help explain and improve than on Elitre's talk page I guess. :) --AKlapper (WMF) (talk) 13:33, 7 April 2015 (UTC)

VisualEditor/Newsletter/2015/April

I am translating this page, but links targets are often given as <tvar> variables without language support. For example, if I use the variables, the DOI explanation is the English Wikipedia article, the documentation for TemplateData is the English one (there are many translations here). How are you planning to integrate languages here? Should I ignore variables and adapt links (which seems preferable for English Wikipedia articles) or will you use something like Special:MyLanguage (which seems preferable for translated documentation)? — Ltrlg (talk) – 08:48, 6 April 2015 (UTC)

Ltrlg, I'm not sure how to change those tvars to point to more useful pages. Usually, when I'm linking to encyclopedia articles, I specify en.wp because I know that the page exists under that name. For example, w:en:Arm and w:fr:Arm are not the same subjects, so linking to the second would not be helpful. But for mediawiki.org, I will always want them to go to the best language for the reader. If you know how to fix it, to do something more sensible for everyone, then please do (and please leave the diff on my talk page, so I can learn how to do it). Otherwise, please translate the links however you think is best. I trust your judgment. Whatamidoing (WMF) (talk) 18:45, 7 April 2015 (UTC)

Hi Elitre, I'm having a hard time translating "Q4 blocker" - what is that? Thanks, --Gnom (talk) 16:02, 6 April 2015 (UTC)

I was wondering the same yesterday. Is there some meaning for Q4 or is it just a random name for the project (as said "Q4 blocker project")? Elitre seems to be out of office so let's try @Whatamidoing (WMF): any help? :) --Stryn (talk) 16:43, 6 April 2015 (UTC)

Hi Stryn and Gnom, thanks for pinging me. I apologize for the confusion (and it is my fault, because I wrote that). "Q4" is "fourth quarter in the fiscal year", or if you're speaking "human" rather than "bookkeeping", it means "April, May, and June". Please translate it rather freely, into whatever you think will make sense to editors. Whatamidoing (WMF) (talk) 18:37, 7 April 2015 (UTC)

Thanks for the clarification, Whatamidoing (WMF)! You probably know that fiscal years vary greatly internationally, and fourth quarter of the official U.S. fiscal year consists of the months of July through September, if I understand the according Wikipedia article correctly... --Gnom (talk) 22:16, 8 April 2015 (UTC)

Every business has its own fiscal year. It doesn't even need to align with a month. Most big retailers have a fiscal year that ends sometime in January, perhaps two weeks after Christmas or on the Saturday or Sunday closest to their chosen date, etc. You can choose anything you want, as long as you stick with it. Most American non-profits (including the WMF) have a fiscal year that ends on 30 June, ultimately because the (tax) accountants aren't as busy then (which means that they can get cheaper audits). Whatamidoing (WMF) (talk) 18:58, 10 April 2015 (UTC)

VisualEditor News #2—2015

Did you know?

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

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

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

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

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

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

Recent improvements

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

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

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

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

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

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

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

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

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

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

Looking ahead

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

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

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• Can you translate from English into any other language? Please check this list to see whether more interface translations are needed for your language. Contact us to get an account if you want to help!
• The design research team wants to see how real editors work. Please sign up for their research program.
• File requests for language-appropriate "Bold" and "Italic" 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)

19:45, 10 April 2015 (UTC)

Re: my edit in Arwiki

according to this message, I think there are a misunderstanding because your message was in wrong page, the Village pump discussions should be in the month page not in the main page, so I fix this mistake and transfer your message from:

https://ar.wikipedia.org/wiki/ويكيبيديا:الميدان/تقنية

to

https://ar.wikipedia.org/wiki/ويكيبيديا:الميدان/تقنية/04/2015

thank you :) --Ibrahim.ID »» 18:43, 24 April 2015 (UTC)

I think this link is wrong :), could you send me the right link? thanks

Done, thank you--Ibrahim.ID »» 12:04, 26 April 2015 (UTC)

Re: MassMessage e interwiki

phabricator:T59464. Il trucco è sempre il solito: [2]. --Nemo 14:27, 29 April 2015 (UTC)

in esWiki village pump

Hi. I have asnwered you in es:Wikipedia:Café/Archivo/Técnica/Actual#Votaci.C3.B3n. I do not know if you have notifications, so I prefer to notify it to you here. Greetings. Albertojuanse (talk) 15:09, 1 May 2015 (UTC)

VisualEditor News #3—2015

Did you know?

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

The link tool has been re-designed:

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

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

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

Recent improvements

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

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

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

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

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

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

Let's work together

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

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

— Elitre (WMF)

10:45, 13 June 2015 (UTC)

Early invitation: join VisualEditor's 2015 Translathon

Hello!

You are invited to join the 2nd edition of the VisualEditor Translathon! It is a translation rally, focused on interface messages and help pages related to VisualEditor.

In order to participate, you need to sign up on the Translathon page. The top 3 contributors will each win a Wikipedia t-shirt of their choice from the Wikipedia store. Translations made between July 15th and July 19th (CDT time zone) qualify.

If you are attending Wikimania Mexico this year, you are also welcome to join a related sprint during the Hackathon in Workplace 1 - Don Américo, Thursday 16 July at 4:00 p.m (CDT) at the conference venue, so you can meet other fellow translators and get support if you need some.

Interface messages have the priority. You will need to create an account at translatewiki.net in order to work on them, if you don't have one. It is recommended to create the account ASAP, so that it can be manually confirmed in time.

You can also help translate documentation pages about VisualEditor on mediawiki.org. You can use your Wikipedia account there. You will find instructions, links and other details on the Translathon page.

Thanks for your attention, and happy translating! Elitre (WMF) 02:27, 11 July 2015 (UTC)

VisualEditor News #4—2015

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

Did you know?

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

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

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

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

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

Wikimania

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

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

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

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

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

Recent improvements

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

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

Future changes

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

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

Let's work together

• Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page is now using Flow instead of LiquidThreads.
• Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mediawiki.org if you can help.
• If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
• Please file requests for language-appropriate "Bold" and "Italic" 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), 22:27, 14 August 2015 (UTC)

Re: A proposal to centralize VisualEditor feedback on www.mediawiki.org

Hi! I don't know are you checking local Wikipedia user talk pages how frequently, so I report here that I gave you an answer on fiwiki. :) --Stryn (talk) 20:09, 27 August 2015 (UTC)

From slovenian wikipedians - I am the only one that deals with Visual editor in :sl wiki and I agree, for now this is a good idea. --Pinky sl (talk) 07:46, 28 August 2015 (UTC)

For Minangkabau Wikipedia, I do think this is a good idea as well. Thanks, XoXo (talk) 13:35, 28 August 2015 (UTC)

Wikipedia 15

Ciao, troveresti 5 minuti per trasformare il mio inglese penoso in inglese normale qui Wikipedia_15/Events/Grenoble ? Grazie.--Patafisik (talk) 16:24, 21 October 2015 (UTC)

Ok, scusa per l'invasione della mail sbagliata, non mi ero resa conto. L'ho vista nella pagina e ho preso la scorciatoia. Buon lavoro,--Patafisik (talk) 16:30, 21 October 2015 (UTC)

VE Newsletter

Ti scrivo qui perché (per qualche strana ragione) non riesco a rispondere direttamente alla mail. La frase
"Now, all devices regardless of size can use it if they wish."
Dovrebbe essere modificata in qualcosa tipo
"Now, editors can use it on all devices regardless of size if they wish."
Dato che è chi modifica a decidere, non il dispositivo :D--Fringio – α†Ω 18:03, 26 October 2015 (UTC)

VisualEditor News #5—2015

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

Did you know?

You can use the visual editor on smartphones and tablets.

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

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

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

Since the last newsletter, the VisualEditor Team has fixed many bugs, added new features, and made some small design changes. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving support for languages like Japanese and Arabic, making it easier to edit on mobile devices, and providing rich-media tools for formulæ, charts, galleries and uploading.

Recent improvements

Educational features: The first time ever you use the visual editor, it now draws your attention to the Link 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 "Insert Images and 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 "Delete" button, so that these things can be removed if the keyboard hides. (T62110) You can also edit table cells in mobile now.

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

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

Future changes

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

Let's work together

• Share your ideas and ask questions at VisualEditor/Feedback. This feedback page uses Flow for discussions.
• Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).
• Local admins can set up the Citoid automatic reference feature for your wiki. If you need help, then please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
• The weekly task triage meetings are open to volunteers. Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

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

—Elitre (WMF), 18:18, 30 October 2015 (UTC)

VisualEditor (partial) approval on es:wiki

Informing you that polling on es:wiki is over, and VE has been approved por registered users. Check w:es:Wikipedia:Votaciones/2015/Sobre el Editor Visual--Ninovolador (talk) 12:39, 1 November 2015 (UTC)

Content translation

Ciao, per caso tu rispondi anche a richieste di informazioni su mw:Content translation e mw:Wikimedia Language engineering? Nemo 11:36, 20 November 2015 (UTC)

Grazie per l'informazione. Nemo 11:43, 20 November 2015 (UTC)

User:Elitre (WMF)/Sandbox2 / User:Elitre (WMF)/Sandbox3

Hi! This is still needed? --Kaganer (talk) 19:50, 23 November 2015 (UTC)

No problem, but these pages is generate some red links to unexists categories ;) Ok, i unmark this page from translation and mark to delete. User:Elitre (WMF)/Sandbox3 also unneeded?

NB: You may reply in this talkpage, by include link to my userpage in your text (Then I see a message in the notification bar). As example, "Kaganer, Thanks to ..."

--Kaganer (talk) 07:11, 24 November 2015 (UTC)

Deletion request - diff --Kaganer (talk) 07:26, 24 November 2015 (UTC)

Citoid e siti vari

Ho visto che ci sono vari compiti di Citoid in GCI.[3] Secondo me sono ottimi, se ne potrebbero fare facilmente anche a centinaia. Potresti proporre a suggerire a Marielle di aggiungerne altri per alcuni dei siti che pensi dovrebbero esserci. Se anche fosero solo pull request in GitHub che poi non possiamo approvare noi, sarebbero comunque utili. Nemo 17:42, 13 December 2015 (UTC)

About bnwp's VisualEditor feedback page

Hey Erica, You wanted to let you know that if someone commits to taking care of the local page of VisualEditor feedback. Well, I'd like to keep an eye on bnwp's feedback page and would like to opted out from centralization. Regards, ~ Nahid ^Talk 21:37, 14 December 2015 (UTC)

Please follow

Hi. Please check here. Thanks.—Teles «Talk to me ˱_{C L @ S}˲» 20:57, 19 December 2015 (UTC)

VisualEditor feedback page on huwiki

Hi Elitre,

I've seen your message on huwiki about the VE feedback centralization. I presume that refers to Wikipédia:VisualEditor/Visszajelzés. I can handle feedback on that page and forward to Phabricator as needed. If you'd prefer to not have a local feedback page, that's fine with me either. (TBH the page is pretty useless; almost all the feedback is about article content.)

In unrelated news, I made a proposal to open red links in VisualEditor by default, which was accepted. This was shortly before the VE team announced the single-tab feature, so it was formulated slightly differently, but I think the consensus extends to that, in case that's something you intend to do on a per-wiki opt-in basis. --Tgr (talk) 05:23, 20 December 2015 (UTC)

VisualEditor News #6—2015

Did you know?

A new, simpler system for editing will offer a single Edit button. Once the page has opened, you can switch back and forth between visual and wikitext editing.

If you prefer having separate edit buttons, then you can set that option in your preferences, either in a pop-up dialog the next time you open the visual editor, or by going to Special:Preferences and choosing the setting that you want:

The current plan is for the default setting to have the Edit button open the editing environment you used most recently.

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

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

Since the last newsletter, the visual editor team has fixed many bugs and expanded the mathematics formula tool. Their workboard is available in Phabricator. Their current priorities are improving support for languages such as Japanese and Arabic, and providing rich-media tools for formulæ, charts, galleries and uploading.

Recent improvements

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

Future changes

The single edit tab project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab, like the system already used on the mobile website. (T102398, T58337) Initially, the "Edit" 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 Editing tab of Special:Preferences in the drop-down menu about "Editing mode:".

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

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

Testing opportunities

• Please try the new system for the single edit tab on test2.wikipedia.org. You can edit while logged out to see how it works for logged-out editors, or you can create a separate account to be able to set your account's preferences. Please share your thoughts about the single edit tab system at the feedback topic on mediawiki.org or sign up for formal user research (type "single edit tab" in the question about other areas you're interested in). The new system has not been finalized, and your feedback can affect the outcome. The team particularly wants your thoughts about the options in Special:Preferences. The current choices in Special:Preferences are:
  • Remember my last editor,
  • Always give me the visual editor if possible,
  • Always give me the source editor, and
  • Show me both editor tabs. (This is the current state for people already using the visual editor. None of these options will be visible if you have disabled the visual editor in your preferences at that wiki.)
• Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).

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

Elitre (WMF), 00:03, 25 December 2015 (UTC)

VisualEditor huwiki reloaded

Hi! I left a message for you here: [4]. And thank you for considering our problems. Best, --Burumbátor (talk) 18:35, 22 February 2016 (UTC)

VisualEditor News #1—2016

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

Did you know?

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

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

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

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

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

Recent changes

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

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

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

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

Future changes

The single edit tab project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab. This is similar to the system already used on the mobile website. (T102398) Initially, the "Edit" 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 Editing tab of Special:Preferences:

• Remember my last editor,
• Always give me the visual editor if possible,
• Always give me the source editor, and
• Show me both editor tabs. (This is the state for people using the visual editor now.)

The visual editor uses the same search engine as Special:Search to find links and files. This search will get better at detecting typos and spelling mistakes soon. These improvements to search will appear in the visual editor as well.

The visual editor will be offered to all editors at most "Phase 6" Wikipedias during the next few months. This will affect the following languages, amongst others: Japanese, Korean, Urdu, Persian, Arabic, Tamil, Marathi, Malayalam, Hindi, Bengali, Assamese, Thai, Aramaic.

Let's work together

• Please try out the newest version of the single edit tab on test2.wikipedia.org. You may need to restore the default preferences (at the bottom of test2wiki:Special:Preferences) to see the initial prompt for options. Were you able to find a preference setting that will work for your own editing? Did you see the large preferences dialog box when you started editing an article there?
• Can you read and type in Korean, Arabic, Japanese, Indic, or Han scripts? Does typing in these languages feels natural in the visual editor? Language engineer David Chan needs to know. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org.
• Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Join the Tech Talk about "Automated citations in Wikipedia: Citoid and the technology behind it" with Sebastian Karcher on 29 February 2016.

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

Elitre (WMF), 19:22, 26 February 2016 (UTC)

Quero falar com alguém

Preciso que alguem me esplica como coversar em wiki ao vivo. E como ver se um usuario esta no chat.--105.172.65.194 16:51, 24 March 2016 (UTC)

See es:Wikipedia:Canal_de_IRC or related guides. --Elitre (WMF) (talk) 17:01, 24 March 2016 (UTC)

RE:senza parole

Nessun problema, io mi diverto :D--Fringio – α†Ω 17:35, 14 May 2016 (UTC)

Corsi di laurea in lingue e letterature straniere moderne :) Magari trovi qualche altro "particolare" :D--Fringio – α†Ω 09:06, 15 May 2016 (UTC)

Allora se qualcuno ci ha già pensato, di sicuro è la soluzione più semplice :D--Fringio – α†Ω 09:10, 15 May 2016 (UTC)

😂😂😂😂😂😂--Fringio – α†Ω 09:12, 15 May 2016 (UTC)