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.
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.
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.
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.
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 "Pogrubienie" and "Kursywa" icons for the styling menu in Phabricator.
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!
Please read: a proposal to centralize VisualEditor feedback on www.mediawiki.org[edytuj kod]
Hello. The VisualEditor team would like to inform you of a plan to redirect local pages for VisualEditor feedback to the board on mediawiki.org a few weeks from now. This applies to all the wikis where such pages are inactive or have low traffic, including yours. When this happens, editors will be free to use their own language to write on the mediawiki.org's page - although English is the most popular language there. Even feedback left from within VisualEditor with the built-in tool will be posted to the board on mediawiki.org.
Click on the image to enlarge it: location of the built-in feedback tool in VisualEditor.
Click on the image to enlarge it: screenshot of the new feedback board on mediawiki.org.
Having all the feedback on a single, centralized place mainly means getting faster, more frequent replies and more attention from a higher number of people, including the people who are building the software. It also means chances are high, that editors will find that someone else has already written there about the issues or requests they wanted to post.
Maintaining a local page instead can be cumbersome: it needs to be checked frequently in case someone reports urgent issues. Old threads need to be archived from time to time. Off-topic comments should be removed to keep readability. Feedback left there is sometimes not easily understandable or actionable at all.
If at least one community member per wiki expressly commits to taking care of the local page, the redirect will not be necessary, although we need to establish a clear process with this person as soon as possible so that this person knows when to escalate issues to Phabricator or to Community Liaisons, and can receive useful tips based on our experience. Therefore, if you'd like to volunteer for this task, please leave a message on my talk page within one week. Otherwise, we'll redirect the feedback page and feedback from the built-in tool to mediawiki.org at the given deadline. Thanks for your understanding, Elitre (WMF) 21:23, 27 sie 2015 (CEST)
W artykule pojawia się wymiennie F-22 i YF-22 co może mylić czytających. Należy to ujednoznacznić bądź na F-22 lub YF-22. Właściwiej byłoby YF-22 jako,że był to prototyp a nie finalna wersja Raptora.[edytuj kod]
Aplikacja klienta: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0