Vun Wikipedia
Hubs uff: Nawigadzion, Nochgugge

Uf dere Seit gibts Neiischkeide zur Teschnig un zur Software


VisualEditor global newsletter—June 2014[Om Gwelltegschd schaffe]

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

The character formatting menu

Did you know?

The character formatting menu, or "Text gestalten" 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

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 weekly updates detailing recent work.

  • They have moved the "Taschdaduakeazl" link out of the "Seitenoptionen" menu, into the "Hilf" 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 "Seitenoptionen" menu, rounding out the full set of page options currently planned.
  • The tool to insert special characters is now wider and simpler.

Looking ahead[Om Gwelltegschd schaffe]

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

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[Om Gwelltegschd schaffe]

Please read VisualEditor/Citation tool for information on configuring the new citation template menu, labeled "Zidaad". 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

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

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

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

Updates related to VisualEditor[Om Gwelltegschd schaffe]

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

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

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

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

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

VisualEditor global newsletter—July and August 2014[Om Gwelltegschd schaffe]


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

Screenshot of VisualEditor's link tool
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 "Zidaad" menu, including the "Änzlnochwees" (manual formatting) footnotes and the ability to re-use an existing citation, both of which were previously accessible only through the "Oifiesche" menu. The "⧼visualeditor-dialogbutton-referencelist-tooltip⧽" is still added via the "Oifiesche" 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[Om Gwelltegschd schaffe]

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

Feedback opportunities[Om Gwelltegschd schaffe]

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

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

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

VisualEditor News #8—2014[Om Gwelltegschd schaffe]

11:49, 13. Ogd 2014 (CEST)

VisualEditor News #9—2014[Om Gwelltegschd schaffe]

00:29, 15. Nov 2014 (CET)

VisualEditor News #10—2014[Om Gwelltegschd schaffe]

19:59, 26. Dez 2014 (CET)

VisualEditor News #1—2015[Om Gwelltegschd schaffe]

19:30, 5. Feb 2015 (CET)

VisualEditor News #2—2015[Om Gwelltegschd schaffe]

21:48, 10. Abr 2015 (CEST)

VisualEditor News #3—2015[Om Gwelltegschd schaffe]

12:44, 13. Jun 2015 (CEST)

VisualEditor News #3—2015[Om Gwelltegschd schaffe]

16:02, 13. Jun 2015 (CEST)

Content Translation beta feature is now available[Om Gwelltegschd schaffe]

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

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

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

Since this is the first time we have installed the tool on this Wikipedia, there are chances that there may be some problems or service disruptions which we are not yet aware of. We will be monitoring the usage to check for any failures or issues, but please do let us know on the Content Translation talk page or through Phabricator if you spot any problems that prevent you from using the tool. For more information, please read the information available in the User Guide. Our announcement is written only in English, and we would really appreciate if this message can be translated to reach more users of this Wikipedia. Thank you. On behalf of the Wikimedia Foundation's Language Engineering Team:--Runa Bhattacharjee (Gbabbl) 18:20, 18. Jun 2015 (CEST)

VisualEditor News #4—2015[Om Gwelltegschd schaffe]

Elitre (WMF), 00:28, 15. Aug 2015 (CEST)

VisualEditor News #4—2015[Om Gwelltegschd schaffe]

Elitre (WMF), 02:05, 15. Aug 2015 (CEST)

Tech News: 2015-34[Om Gwelltegschd schaffe]

18:17, 17. Aug 2015 (CEST)

Tech News: 2015-35[Om Gwelltegschd schaffe]

15:02, 24. Aug 2015 (CEST)

Tech News: 2015-36[Om Gwelltegschd schaffe]

23:36, 31. Aug 2015 (CEST)

Tech News: 2015-37[Om Gwelltegschd schaffe]

19:29, 7. Seb 2015 (CEST)

Tech News: 2015-38[Om Gwelltegschd schaffe]

18:17, 14. Seb 2015 (CEST)

Tech News: 2015-39[Om Gwelltegschd schaffe]

20:29, 21. Seb 2015 (CEST)

Tech News: 2015-40[Om Gwelltegschd schaffe]

17:15, 28. Seb 2015 (CEST)

Tech News: 2015-41[Om Gwelltegschd schaffe]

20:32, 5. Ogd 2015 (CEST)

Tech News: 2015-42[Om Gwelltegschd schaffe]

18:28, 12. Ogd 2015 (CEST)

Tech News: 2015-43[Om Gwelltegschd schaffe]

18:02, 19. Ogd 2015 (CEST)

Tech News: 2015-44[Om Gwelltegschd schaffe]

19:04, 26. Ogd 2015 (CET)

VisualEditor News #5—2015[Om Gwelltegschd schaffe]

Elitre (WMF), 19:18, 30. Ogd 2015 (CET)

Tech News: 2015-45[Om Gwelltegschd schaffe]

17:42, 2. Nov 2015 (CET)

Tech News: 2015-46[Om Gwelltegschd schaffe]

18:18, 9. Nov 2015 (CET)

Tech News: 2015-47[Om Gwelltegschd schaffe]

20:39, 16. Nov 2015 (CET)

Tech News: 2015-48[Om Gwelltegschd schaffe]

21:26, 23. Nov 2015 (CET)

Tech News: 2015-49[Om Gwelltegschd schaffe]

17:16, 30. Nov 2015 (CET)

Tech News: 2015-50[Om Gwelltegschd schaffe]

18:52, 7. Dez 2015 (CET)

Tech News: 2015-51[Om Gwelltegschd schaffe]

18:41, 14. Dez 2015 (CET)

Tech News: 2015-52[Om Gwelltegschd schaffe]

19:29, 21. Dez 2015 (CET)

VisualEditor News #6—2015[Om Gwelltegschd schaffe]

Elitre (WMF), 01:06, 25. Dez 2015 (CET)

Tech News: 2016-02[Om Gwelltegschd schaffe]

17:59, 11. Jan 2016 (CET)

Tech News: 2016-03[Om Gwelltegschd schaffe]

18:55, 18. Jan 2016 (CET)

Tech News: 2016-04[Om Gwelltegschd schaffe]

17:39, 25. Jan 2016 (CET)

Tech News: 2016-05[Om Gwelltegschd schaffe]

22:02, 1. Feb 2016 (CET)

Tech News: 2016-06[Om Gwelltegschd schaffe]

19:58, 8. Feb 2016 (CET)

Tech News: 2016-07[Om Gwelltegschd schaffe]

17:16, 15. Feb 2016 (CET)

Tech News: 2016-08[Om Gwelltegschd schaffe]

19:22, 22. Feb 2016 (CET)

VisualEditor News #1—2016[Om Gwelltegschd schaffe]

Elitre (WMF), 20:21, 26. Feb 2016 (CET)

Tech News: 2016-09[Om Gwelltegschd schaffe]

21:12, 29. Feb 2016 (CET)

Tech News: 2016-10[Om Gwelltegschd schaffe]

21:24, 7. Mäa 2016 (CET)

Tech News: 2016-11[Om Gwelltegschd schaffe]

19:37, 14. Mäa 2016 (CET)

Tech News: 2016-12[Om Gwelltegschd schaffe]

17:04, 21. Mäa 2016 (CET)

Hi, a minor correction: The MediaWiki deployment dates are March 22–24, not 21–23. My apologies. /Johan (WMF) (Gbabbl) 09:45, 22. Mäa 2016 (CET)

Tech News: 2016-13[Om Gwelltegschd schaffe]

21:43, 28. Mäa 2016 (CEST)

Tech News: 2016-14[Om Gwelltegschd schaffe]

00:13, 5. Abr 2016 (CEST)

Tech News: 2016-15[Om Gwelltegschd schaffe]

22:44, 11. Abr 2016 (CEST)

Tech News: 2016-16[Om Gwelltegschd schaffe]

22:40, 18. Abr 2016 (CEST)

Tech News: 2016-17[Om Gwelltegschd schaffe]

23:02, 25. Abr 2016 (CEST)

Tech News: 2016-18[Om Gwelltegschd schaffe]

22:09, 2. Mai 2016 (CEST)

Tech News: 2016-19[Om Gwelltegschd schaffe]

01:22, 10. Mai 2016 (CEST)

Tech News: 2016-20[Om Gwelltegschd schaffe]

18:01, 16. Mai 2016 (CEST)

Tech News: 2016-21[Om Gwelltegschd schaffe]

20:40, 23. Mai 2016 (CEST)

Tech News: 2016-22[Om Gwelltegschd schaffe]

18:18, 30. Mai 2016 (CEST)

Tech News: 2016-23[Om Gwelltegschd schaffe]

22:51, 6. Jun 2016 (CEST)

Tech News: 2016-24[Om Gwelltegschd schaffe]

20:41, 13. Jun 2016 (CEST)

Tech News: 2016-25[Om Gwelltegschd schaffe]

21:14, 20. Jun 2016 (CEST)

Tech News: 2016-26[Om Gwelltegschd schaffe]

17:42, 27. Jun 2016 (CEST)

Editing News #2—2016[Om Gwelltegschd schaffe]

m:User:Elitre (WMF), 19:20, 3. Jul 2016 (CEST)

Tech News: 2016-27[Om Gwelltegschd schaffe]

21:45, 4. Jul 2016 (CEST)

Tech News: 2016-28[Om Gwelltegschd schaffe]

17:14, 11. Jul 2016 (CEST)

Tech News: 2016-29[Om Gwelltegschd schaffe]

22:18, 18. Jul 2016 (CEST)

Tech News: 2016-30[Om Gwelltegschd schaffe]

21:54, 25. Jul 2016 (CEST)

Tech News: 2016-31[Om Gwelltegschd schaffe]

23:48, 1. Aug 2016 (CEST)

Tech News: 2016-32[Om Gwelltegschd schaffe]

17:41, 8. Aug 2016 (CEST)

Tech News: 2016-33[Om Gwelltegschd schaffe]

21:36, 15. Aug 2016 (CEST)

Tech News: 2016-34[Om Gwelltegschd schaffe]

23:18, 22. Aug 2016 (CEST)

Tech News: 2016-35[Om Gwelltegschd schaffe]

17:59, 29. Aug 2016 (CEST)

Tech News: 2016-36[Om Gwelltegschd schaffe]

19:12, 5. Seb 2016 (CEST)

Tech News: 2016-37[Om Gwelltegschd schaffe]

20:04, 12. Seb 2016 (CEST)

Tech News: 2016-38[Om Gwelltegschd schaffe]

00:08, 20. Seb 2016 (CEST)

Tech News: 2016-39[Om Gwelltegschd schaffe]

20:07, 26. Seb 2016 (CEST)

Tech News: 2016-40[Om Gwelltegschd schaffe]

23:30, 3. Ogd 2016 (CEST)

Tech News: 2016-41[Om Gwelltegschd schaffe]

22:30, 10. Ogd 2016 (CEST)

The Wikimedia Developer Summit wants you[Om Gwelltegschd schaffe]

The Wikimedia Developer Summit is the annual meeting to push the evolution of MediaWiki and other technologies supporting the Wikimedia movement. The next edition will be held in San Francisco on January 9–11, 2017.

We welcome all Wikimedia technical contributors, third party developers, and users of MediaWiki and the Wikimedia APIs. We specifically want to increase the participation of volunteer developers and other contributors dealing with extensions, apps, tools, bots, gadgets, and templates.

Important deadlines:

  • Monday, October 24: last day to request travel sponsorship. Applying takes less than five minutes.
  • Monday, October 31: last day to propose an activity. Bring the topics you care about!

More information:

Subscribe to weekly updates:

MKramer (WMF) (talk) 21:07, 14. Ogd 2016 (CEST)

Editing News #3—2016[Om Gwelltegschd schaffe]

19:49, 15. Ogd 2016 (CEST)

Tech News: 2016-42[Om Gwelltegschd schaffe]

18:42, 17. Ogd 2016 (CEST)

Tech News: 2016-43[Om Gwelltegschd schaffe]

19:39, 24. Ogd 2016 (CEST)

Tech News: 2016-44[Om Gwelltegschd schaffe]

17:18, 31. Ogd 2016 (CET)

Tech News: 2016-45[Om Gwelltegschd schaffe]

00:01, 8. Nov 2016 (CET)

Tech News: 2016-46[Om Gwelltegschd schaffe]

20:17, 14. Nov 2016 (CET)

Tech News: 2016-47[Om Gwelltegschd schaffe]

16:33, 21. Nov 2016 (CET)

Tech News: 2016-48[Om Gwelltegschd schaffe]

22:16, 28. Nov 2016 (CET)

Tech News: 2016-49[Om Gwelltegschd schaffe]

19:07, 5. Dez 2016 (CET)

Tech News: 2016-50[Om Gwelltegschd schaffe]

20:29, 12. Dez 2016 (CET)

Tech News: 2016-51[Om Gwelltegschd schaffe]

21:33, 19. Dez 2016 (CET)

Tech News: 2017-02[Om Gwelltegschd schaffe]

20:12, 9. Jan 2017 (CET)

Tech News: 2017-03[Om Gwelltegschd schaffe]

00:24, 17. Jan 2017 (CET)

Developer Wishlist Survey: propose your ideas[Om Gwelltegschd schaffe]

At the Wikimedia Developer Summit, we decided to organize a Developer Wishlist Survey, and here we go:

The Wikimedia technical community seeks input from developers for developers, to create a high-profile list of desired improvements. The scope of the survey includes the MediaWiki platform (core software, APIs, developer environment, enablers for extensions, gadgets, templates, bots, dumps), the Wikimedia server infrastructure, the contribution process, and documentation.

The best part: we want to have the results published by Wednesday, February 15. Yes, in a month, to have a higher chance to influence the Wikimedia Foundation annual plan FY 2017-18.

There's no time to lose. Propose your ideas before the end of January, either by pushing existing tasks in Phabricator or by creating new ones. You can find instructions on the wiki page. Questions and feedback are welcome especially on the related Talk page.

The voting phase is expected to start on February 6 (tentative). Watch this space (or even better, the wiki page) - SSethi_(WMF) January 21st, 2017 3:07 AM (UTC)

Tech News: 2017-04[Om Gwelltegschd schaffe]

21:14, 23. Jan 2017 (CET)

Tech News: 2017-05[Om Gwelltegschd schaffe]

19:45, 30. Jan 2017 (CET)

Developer Wishlist Survey: Vote for Proposals[Om Gwelltegschd schaffe]

Almost two weeks ago, the Technical Collaboration team invited proposals for the first edition of the Developer Wishlist survey!

We collected around 77 proposals that were marked as suitable for the developer wishlist and met the defined scope and criteria. These proposals fall into the following nine categories: Frontend, Backend, Code Contribution (Process, Guidelines), Extensions, Technical Debt, Developer Environment, Documentation, Tools (Phabricator, Gerrit) and Community Engagement.

Voting phase starts now and will run until February 14th, 23:59 UTC. Click here on a category and show support for the proposals you care for most. Use the 'Vote' and 'Endorse' buttons next to a proposal to do so.

What happens next?
Proposals that will gather most votes will be included in the final results which will be published on Wednesday, February 15th. These proposals will also be considered in the Wikimedia Foundation’s annual plan FY 2017-18 - SSethi_(WMF) (talk) 04:41, 6 February 2017 (UTC)

Tech News: 2017-06[Om Gwelltegschd schaffe]

20:45, 6. Feb 2017 (CET)

Tech News: 2017-07[Om Gwelltegschd schaffe]

19:06, 13. Feb 2017 (CET)

Tech News: 2017-08[Om Gwelltegschd schaffe]

20:25, 20. Feb 2017 (CET)