Wikipedia:Visuele tekstverwerker/Feedback/Archief/feb 2015

Koppelingen toevoegen
Uit Wikipedia, de vrije encyclopedie

VisualEditor News #1—2015[bewerken | brontekst bewerken]

VisualEditor

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.

Recente verbeteringen[bewerken | brontekst bewerken]

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.

Toekomstplannen[bewerken | brontekst bewerken]

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.

Laten we samenwerken[bewerken | brontekst bewerken]

— Elitre (WMF)

5 feb 2015 19:30 (CET)

New tests performed[bewerken | brontekst bewerken]

Earlier the Dutch community had a voting in what they said that as long as the as major problems considered issues aren't solved, the Visual Editor is not ready to be implemented in the Dutch Wikipedia. Before the voting a wiki wide test had been done in how well the Visual Editor is working and to see if the software is ready for full implementation. The problems that came out of this test have been presented to the community in the voting, and community made clear that while these problems still occur, the Visual Editor is not ready for implementation. It is considered unacceptable that users damage articles just because the software can't handle simple wiki codes.

Today I have been doing the same tests as earlier for the voting, and still a part of the major issues found in the articles on what the community said them to be unacceptable, still exist. Based on the tests and the voting, the visual editor is still not ready to be implemented as default on the Dutch Wikipedia.

The main issue that still exist with the Visual Editor is the problem with white lines. On many many articles white lines are extra added to articles when viewing the article with the Visual Editor. As those lines are very disturbing, users will try to remove the white lines and accidental remove images, infoboxes and other templates aligned to the right with them. Those images, infoboxes and other templates that are deleted, is purely because the Visual Editor can't handle their presence in articles. This concerns thousands of articles. Examples:

  • Bali - still too much white above the first text lines
  • Rijn - also
  • Amstel - also
  • Brussels - still too much white space above the fist text lines and in external links section
  • Antwerpen - also

And removal of these white lines already occured with the VE, like with this edit.
>>> Phabricator?

And something strange is happening here:

And the Visual Editor can't handle our many times used Appendix template, which is in use on 1132190 pages:

References are considered as one of the most important parts of articles!

And let me make clear, I believe that a good working the Visual Editor is highly wanted and needed, and should be implemented as fast as possible, but only when it is ready without any major problems. Romaine (overleg) 11 feb 2015 20:57 (CET)[reageer]

I ran into two cosmetic issues while using VE on nlwp, one of which (the former) perhaps applies specifically to Dutch wikipedia:
Romaine, are the issues you reported above specific to Dutch wikipedia, and/or are they being tracked in Phabricator? –Frank Geerlings (overleg) 13 feb 2015 00:53 (CET)[reageer]
User:Romaine, what Frank says. It is possible to trace all of these bugs and to nominate them on Phabricator as blockers (just add an "Associate Project" comment on the task against the "§ VisualEditor Q3 Blockers" project). I or others could even help with that if there was a current, up-to-date list. Maybe we can also make it happen before the 2nd meeting starts? Elitre (WMF) (overleg) 16 feb 2015 19:29 (CET)[reageer]
I was not able to do that before the next meeting, but should be done soon. Romaine (overleg) 20 feb 2015 01:26 (CET)[reageer]
Overgenomen van "https://nl.wikipedia.org/w/index.php?title=Wikipedia:Visuele_tekstverwerker/Feedback/Archief/feb_2015&oldid=43778067"