Wikipedia:VisualEditor/Opinie/Archiwum/2

Updates related to VisualEditor

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

• Thursday, August 14, 9:00 UTC;
• Thursday, September 18, 16:00 UTC.

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

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

• VisualEditor — helping users edit more easily, Saturday, August 9;
• VisualEditor — engineering against the odds, Sunday, August 10.

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

Podgląd zmian i płynne przejście z VE do edytora kodu

Przydałaby się możliwość podglądu wprowadzonych zmian (oprócz możliwości ich kontroli), podobnie jak w części powyżej edytora tekstowego. Niby wszystko widać, bo edytujemy na "widocznym" artykule, ale jednak nie ma to jak podgląd końcowej wersji, gdzie nie trzeba kombinować jak uruchomić linki i można na spokojnie przeczytać poprawiony artykuł (zwłaszcza gdy ktoś nie używa domyślnej skórki do czytania, tak jak ja), a potem wrócić do edycji lub zatwierdzić zmiany. Np. w postaci przycisku "Podgląd" w głównym menu edytora, czy nawet poziom wyżej, obok zakładki edytuj.

Druga rzecz - płynne przejście z VE do edytora tekstowego, kwestia wspomniana tu, znana jako bugzilla:47779. Jak najbardziej popieram. Spider55555 (dyskusja) 01:31, 4 sie 2014 (CEST)

Hi Spider55555, as for your first request, this will happen when bugs https://bugzilla.wikimedia.org/show_bug.cgi?id=37931 and https://bugzilla.wikimedia.org/show_bug.cgi?id=60535 are fixed. For the time being you can preview changes by using the button at the bottom left of the Save dialog. Best, --Elitre (WMF) (dyskusja) 13:38, 28 sie 2014 (CEST)

Dla początkujących

Wątek założony przed: 21:04, 5 sie 2014 (CET)

VisualEditor jest dobrą pomocą dla początkujących wikipedystów nieznających jeszcze dobrze wikikodu. Jednak myślę, że większość bardziej zaawansowanych wikipedystów nadal będzie korzystaćz tradycyjnego edytora.

VisualEditor Office Hours

Wątek założony przed: 21:04, 5 sie 2014 (CET)

Cześć. :) Apologies for writing in English. Translation assistance is appreciated. :)

The WMF engineering department has planned office hours to discuss VisualEditor. The first is on January 15th, at 2300 UTC; the second is a week later, on January 22nd, at 2300 UTC. Product Manager James Forrester will discuss VisualEditor and upcoming plans. Logs will be posted on Meta after each office hour completes. If you want to ask a question or provide feedback but can't attend, don't use Internet Relay Chat, or don't speak English, please post your question or comment here or on my talk page or email me, and I or a community liaison will present it among possible discussion topics. I’ll post a reminder closer to the office hours.

Dziękuję, Anna Koval (WMF) (talk) 30 december 2013 kl. 19.28 (CET)

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 "Wstaw" menu. The "⧼visualeditor-dialogbutton-referencelist-tooltip⧽" is still added via the "Wstaw" 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. Work to support Internet Explorer is ongoing.

Feedback opportunities

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 sie 2014 (CEST)

Internet Explorer 11

Hi, sorry this message is not in Polish. I'm writing to let you know, in case you have missed this announcement in the Tech News during the last weeks, that IE 11 users will soon be able to use VisualEditor as well. I don't anticipate any visible consequences since this browser version is not so popular among Wikipedia users (should be ~5% globally); you might just notice edits revealing the editors' inexperience with VE or with editing in general. Please let us know of any unknown bugs or sudden issues, of course. Thanks a lot, --Elitre (WMF) (dyskusja) 18:08, 10 wrz 2014 (CEST)

sołectwo

Sołectwo obecnie nalezy do Zwartowa a nie do Zwartówka to tyle 83.25.82.66 (dyskusja) 17:59, 25 wrz 2014 (CEST)

TemplateData editor soon available on this Wikipedia

Hello, my apologies for writing this announcement in English. A tool for editing TemplateData will be deployed to this wiki on Thursday, 9 October. This tool makes it easier to add TemplateData to the template's documentation (or to change it). You will be able to use it by editing the template's documentation page and clicking the Zarządzaj dokumentacją szablonu button at the top. You can test the TemplateData editor now in a sandbox at Mediawiki.org. Please see more detailed instructions at Mediawiki.org (those can be translated there, and also imported on this wiki later if you need to). Don't hesitate to contact me if you need further information. Best, --Elitre (WMF) (dyskusja) 13:12, 7 paź 2014 (CEST)

Błąd w zdaniu .

Warstwy systemu komputerowego>Opragramowanie użytkowe - początek zdania . Zamiast "określają" powinno być "określa". 193.150.47.10 (dyskusja) 22:20, 8 paź 2014 (CEST)

ts

vfff Rafalle201013 (dyskusja) 12:05, 10 paź 2014 (CEST)

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 "Zarządzaj dokumentacją szablonu" 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)

11:49, 13 paź 2014 (CEST)

link w rozdz. "Organizacja Kościoła za czasów Bolesława"

Link prowadzi do strony opisującej duże miasto Lubin, w obecnym (2014r.) województwie dolnośląskim. Rzeczony klasztor znajduje się w małej wsi Lubiń, ok. 50 km prosto na południe od Poznania. 194.165.48.1 (dyskusja) 12:06, 23 paź 2014 (CEST)

Anastasis zespół muzyczny

Wszelkie informacje na temat zespołu zostały wprowadzone bez uzgodnienia z zespołem. Informacje i zdjęcia są nieaktualne i także opublikowane bez zgody zespołu. Prosimy o kontakt w celu wyjaśnienia edycji artykułu w Wikipedia. Kontakt: anastasisband@wp.pl Irymar (dyskusja) 20:23, 23 paź 2014 (CEST)

Prośba o pomoc

proszę o pomoc w publikacji strony Adrian Lipa Adrian Lipa (dyskusja) 13:47, 26 paź 2014 (CET)

Ilustrowanie stron Wikipedii

Problemy z ilustrowaniem stron. Do infoboxa nie można wkleić pliku, pliki w artykułach ciężko lokalizować. Piotr Matyga (dyskusja) 21:23, 26 paź 2014 (CET)

Hi Piotr Matyga! Can you please explain a bit what you can't do, maybe providing some examples? (mediawiki.org has a guide about editing with VE - it's not completely updated for Polish, unfortunately). It seems to me you managed to do what you wanted in your last edits. In the first one you added some pictures correctly. You can change all the relevant options when you do so (or later), through the Advanced settings. Here instead you added a picture and a caption. You included the File: prefix, but I think the instructions there specify to avoid this? They read: Nazwa pliku ze zdjęciem. Zdjęcie pojawi się zaraz pod nazwą góry. If I'm wrong and this actually means the File: bit needed to be included, or if it is unclear anyway, please tell me so we can fix this. I don't see anything in your edits which a bit of practice can not fix; you're simply not used to this yet :) Best, --Elitre (WMF) (dyskusja) 12:50, 27 paź 2014 (CET)

jak przesłać zdjęcie 193.200.51.142 (dyskusja) 09:53, 10 lis 2014 (CET)

If you want to upload a file, the first guide I found in Polish is c:Commons:Jak_przesłać_grafikę_własnego_autorstwa. To know how to add it later to an article with VE, see mw:Help:VisualEditor/User_guide/pl (unfortunately, not 100% translated: can someone help with this?). Best, --Elitre (WMF) (dyskusja) 19:49, 10 lis 2014 (CET)

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 "Więcej" item, such as "Podkreślenie" 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 "Zarządzaj dokumentacją szablonu" 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 "sugerowany" or "opcjonalny" 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)

00:29, 15 lis 2014 (CET)

witam

Jest jeden problem i na waszej stronie jest nie prawdziwa informacja. Kiedy wpisze się do wyszukiwarki google "martina stoessel" w ramce z podstawowym jej opisem jest informacja zm. 17 listopada 2014 co jest nie prawda gdyż to jedyne takie źródło, a poza tym Martina nadal jest aktywna na portalach społecznościowych, dlatego proszę o usunięcie tej informacji. Z góry dziękuje 31.179.249.2 (dyskusja) 22:23, 18 lis 2014 (CET)

Piszesz podwójnie pod niewłaściwy adres. Po pierwsze ta strona wikipedii nie służy do zgłaszania błędów merytorycznych lecz do komentowania edytora wizualnego. Od tego mamy stronę wp:zb Po drugie w artykule Wikipedii Martina Stoessel nie ma podanej daty śmierci. Błąd leży po stronie google i do nich należy się zgłosić w sprawie poprawki. Marek Mazurkiewicz (dyskusja) 23:49, 18 lis 2014 (CET)

• Przez jakiś czas była podana data śmierci. "Dowcipniś" się jakiś znalazł. Ciacho5 (dyskusja) 23:53, 18 lis 2014 (CET)

Wyemitować serial "Ben 10" do Polsat i ATM Rozrywka

Proszę wyemitować serial "Ben 10" do Polsat od soboty do niedzieli o godz. 8:45 i do ATM Rozrywka dzisiaj o 17:30 88.199.93.31 (dyskusja) 14:49, 24 lis 2014 (CET)

Brak związku z edytorem wizualnym. Skąd pomysł żeby tu o tym pisać? Marek Mazurkiewicz (dyskusja) 15:05, 24 lis 2014 (CET)

It's because of the link in the VE toolbar which redirects here: it's meant for people to give feedback about the editor itself, but it's commonly misused because, as far as I know, no Wikipedia has a clear page where people can list their remarks about article contents (experienced users know they have to use the talk page for that, new users don't). --Elitre (WMF) (dyskusja) 15:04, 25 lis 2014 (CET)

Przypisy

Witam, po wstawieniu przypisu do książki, VE nie dodał szablonu {{Przypisy}} na końcu strony - przypisy zostały dodane pod ostatnią sekcją artykułu, w tym przypadku pod linkami zewnętrznymi. Spider55555 (dyskusja) 01:19, 26 lis 2014 (CET)

Yes, you would need to create a "References" section containing the references list, exactly how you would do when editing wikitext. Instructions here (sorry they're not fully translated, please help with that if you can). Best, --Elitre (WMF) (dyskusja) 17:00, 26 lis 2014 (CET)

Psucie kategorii

Edycje w VE obcinają końcowe fragmenty artykułu, psując kategorię: raz, dwa. Barcival (dyskusja) 22:13, 29 lis 2014 (CET)

Now reported here, thank you. --Elitre (WMF) (dyskusja) 18:05, 1 gru 2014 (CET)

Dziwne zmiany

Chyba jakaś aktualizacja oprogramowania jest nie do końca udana: [2], [3], [4], [5]. Wszystkie te edycje miały polegać jedynie na dodaniu przecinków, spacji, ewentualnie pojedynczych słów, a zamiast tego masakrowały kod artykułów. Szczególnie zmiana w banshee - zamiana szablonu na kod html - wygląda niedobrze. Barcival (dyskusja) 21:49, 2 gru 2014 (CET)

This is known; any related issue which wasn't fixed on that very same day should be fixed ASAP. Thanks a lot for reporting, Barcival. Would you please ping/shout if you see this again? Thank you so much! --Elitre (WMF) (dyskusja) 18:55, 4 gru 2014 (CET)

Linkowanie pod ramką ze zdjęciem

Podczas linkowania do innego artykułu w tekście pod ramką nie mogłem zastosować zmian (w ramce, nie całej edycji). Dopiero po wpisaniu dowolnej litery i jej usunięciu pojawiła się możliwość zapisu. Problem zdaje się dotyczyć linkowania do artykułu o tytule zgodnym z formą linkowanego wyrazu, typu: laryngektomia --> laryngektomia (kod: laryngektomia --> [[laryngektomia]]), przy innej formie jest już możliwość zapisania, np. laryngektomii --> laryngektomii (kod: laryngektomii --> [[laryngektomia|laryngektomii]]). Tak jakby VE 'nie uznawał' tego typu linkowania za zmianę w ramce. Problem pojawił się podczas tej edycji. Spider55555 (dyskusja) 00:20, 3 gru 2014 (CET)

Also known I think. Thanks for stopping by! --Elitre (WMF) (dyskusja) 18:57, 4 gru 2014 (CET)

Software Inbox

Witam,

Nie wiem jak zmodyfkować w/w dziale. Powinna znaleźć się informacja o nowej wersji oraz istnieniu na platformę Linux aktualnej wersji. 94.254.192.180 (dyskusja) 14:34, 13 gru 2014 (CET)

Hi, I don't really understand whether this is actually related to VisualEditor or not. Please let me know if it is, in this case a summary of the issue in English is much appreciated :) --Elitre (WMF) (dyskusja) 19:11, 13 gru 2014 (CET)

usuwanie

kiedy próbuje 95.160.103.28 (dyskusja) 20:05, 14 gru 2014 (CET)

Zgłoszenie niezrozumiałe. Proszę wyrazić się precyzyjniej. Marek Mazurkiewicz (dyskusja) 21:25, 14 gru 2014 (CET)

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 "Akapit" into a "Cytat blokowy".

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 "Pogrubienie" and "Kursywa" 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)

19:59, 26 gru 2014 (CET)

Kolejne podejście

Niestety, nie dane mi jest przekonać się do VE. Za pierwszym podejściem klikanie w "edytuj" przy odpowiedniej sekcji w ogóle nie powodowało żadnej reakcji, dopiero po kilku próbach i minutach zaczęło działać (może pomogło testowe uruchomienie edytora wizualnego na innej stronie, nie wiem). Koniec końców literówkę udało się poprawić klik, ale trwało to znacznie, znacznie dłużej niż przy użyciu kodu źródłowego. Po edycji strona (nie wersja, strona) pokazała się jako nieprzejrzana, ale może to bug niezwiązany z VE? W każdym razie po 1,5 roku (?) problemów wciąż jest dużo (łącznie na kilkanaście moich prób z VE może jedna była bezproblemowa, a testuję go do tych najprostszych edycji! z tego co wiem w moich doświadczeniach nie jestem odosobniony) i wciąż uważam, iż prezentowanie wadliwego narzędzia jako podstawowego dla newbie przynosi więcej szkody niż pożytku: jest raczej przyczyną spadającej liczby nowych userów, a nie remedium na ten stan rzeczy... Nedops (dyskusja) 02:08, 28 gru 2014 (CET)

It took me 4 seconds to open the article you mention in VE, and then when I tried again it took 1 second to open its first section. What browser/operating system/skin are you using? I haven't really heard complaints about speed/performance in a long time. It is quite understandable if wikitext users do not like it the first times they use it, but it is a completely different software from the one which was launched in July 2013. If you have more specific issues to discuss about, I'd be interested in hearing them. On the other hand, it's also OK if you just want to stick to the wikitext editor, of course. Thank you. --Elitre (WMF) (dyskusja) 15:48, 29 gru 2014 (CET)

Wybacz polski język :) Nie chodzi o sam fakt wgrywania strony, ale też np. o to, że nie ma domyślnych opisów edycji itp. Dziś kolejna edycja [6] i znowu po niej strona ma znak "Brak wersji przejrzanej" (ale na dole strony widać, że aktualna wersja jest przejrzana). Windows 8.1, Opera 26, Książka. Nedops (dyskusja) 18:48, 30 gru 2014 (CET)

@Elitre (WMF), perdonami l'italiano. Nedops si lamenta del fatto in VE non c'è la possibilità di aggiungere una descrizione di default alla modifica che si sta facendo. Mi spiego meglio perchè su itwiki non esiste (ancora) questa funzionalità. Prova a editare ad es. questo codice: in fondo, sotto alla casella per l'inserimentom dell'oggetto della modifica, ci sono una serie di bottoni verdi, che se cliccati, aggiungono una descrizione di default. Ad es. grafica, commento, ort., categoria... Spero di essere stato chiaro. Per quando riguarda il flag delle modifiche: non puoi segnare come verificate le tue stesse modifiche se non possiedi lo status di autoreviewers o editor. Qui ho fatto richiesta affinchè ti venga assegnato. --ThePolish 18:20, 31 gru 2014 (CET)

Come avrai visto il flag ti è stato assegnato, possiamo dare il via ai lavori :D --ThePolish 18:24, 31 gru 2014 (CET)

I'll take a closer look...next year :D Thank you all, --Elitre (WMF) (dyskusja) 18:33, 31 gru 2014 (CET)

Co do nieprzejrzanych, zgłoszono już buga // as for FlaggedRevs, there's a bug reported already.

For the edit summary, looks like there is a gadget on en.wiki, which is described as "Adds two new dropdown boxes below the edit summary box with some useful default summaries", if someone wants to try it. --Elitre (WMF) (dyskusja) 13:31, 6 sty 2015 (CET)

• No to jeszcze jeden bug – moim zdaniem mało istotny, no ale zgłaszam :) Przy edycji hasła Sandra Perković za pomocą VE sekcja bibliografia zaczyna się od gwiazdki (tzn. nie asterysku, ale tego czym stosowanie gwiazdki skutkuje na wiki: usłużnego wikipedystę proszę o podmiankę w tekście na właściwe słownictwo – po raz kolejny wychodzą moje braki w typografii :( ) – dla czytelników niewidocznej. Ma to miejsce we wszystkich (tysiącach?) artykułów które korzystają z Szablon:IAAF name i tenże szablon poprzedza gwiazdka. Szablon jest tak ustawiony, iż gwiazdka (i to jedna) pokazuje się niezależnie od tego czy jest ona użyta w haśle czy nie, więc ewentualne usunięcie nie będzie dramatem – ale edycje polegające na usuwaniu takiej gwiazdki – przy użyciu VE wydające się koniecznością – z punktu widzenia czytelnika nie zmieniają niczego. Może wystarczy pogrzebać w kodzie szablonu? Malarz, Mateusz – da się to zrobić? Nedops (dyskusja) 00:56, 9 sty 2015 (CET)
  • W szablonach linków nie powinno być gwiazdek na początku, bo w różnych sytuacjach są wstawiane. ~malarz pl ^PISZ 09:52, 9 sty 2015 (CET)

fota...

jak mam wstawic fotke, do tego co napisalem?... Blekitnyskarabeusz. 777 (dyskusja) 06:20, 11 sty 2015 (CET)

@Blekitnyskarabeusz. 777 Najpierw musisz przesłać plik graficzny (Wikipedia:Prześlij plik)), a następnie wstawić go do artykułu (Pomoc:Ilustrowanie). Jeśli coś na tych dwóch stronach jest niejasne, daj znać :) Matma Rex dyskusja 22:43, 11 sty 2015 (CET)

przyroda

niewystarczające spożycie........przed dzieci i młodzież opóżnia ich wzrost i rozwój Agata Kafar (dyskusja) 16:20, 11 sty 2015 (CET)

@Agata Kafar jaki twój powyższy wpis ma związek z edytorem wizualnym? I czego dotyczy? Marek Mazurkiewicz (dyskusja) 17:06, 11 sty 2015 (CET)

VisualEditor News #1—2015

Od czasu wydania ostatniego newslettera zespół Editing naprawił wiele bugów, pracował nad wyglądem VisualEditora, nadchodzącym narzędziem cytowania Citoid oraz nad zastosowaniem VisualEditora do skomplikowanych systemów pisma. Raporty o stanie obecnym są zamieszczane na on mediawiki.org. Planowane działania opisuje się w harmonogramie.

Wikimedia Foundation określiła priorytetowe zadania na ten kwartał (od stycznia do marca). Pierwszym jest przygotowanie VisualEditora na włączenie go wszystkim nowym użytkownikom oraz niezalogowanym na dużych Wikipediach. Możesz pomóc w określaniu wymagań tego kroku. Od środy, 11 lutego o godz. 12:00 PST (20:00 UTC) rozpoczną się cotygodniowe spotkania, otwarte dla wolontariuszy. Powiedz Wiceprzewodniczącemu Engineering Damonowi Sicore, Product Managerowi Jamesowi Forresterowi oraz reszcie zespołu, które bugi i funkcje są dla ciebie najważniejsze. Decyzje podjęte w trakcie tych spotkań rozstrzygną, jaka praca jest potrzebna do realizacji zadań przyjętych na ten kwartał. Szczególnie mile widziana jest obecność wolontariuszy edytujących w wikikodzie. Informacje o sposobach dołączenia do spotkań będą ogłaszane na portalu na krótko przed rozpoczęciem spotkań.

Z powodu istotnych zmian w MobileFrontendzie i VisualEditorze, przez kilka dni na początku stycznia VisualEditor nie działał poprawnie w wersji mobilnej. Zespoły przepraszają za problem.

Ostatnie poprawki

Nowy design VisualEditora jest zgodny ze frontendowym standardem określonym przez zespół Design. Opublikowano kilka nowych wersji dokumentacji OOjs UI, zastosowanej w VisualEditorze i innych rozszerzeniach MediaWiki. Większość zmian była drobna, jak zmiana wielkości tekstu i ilości pustej przestrzeni w niektórych oknach. Przyciski mają spójnie określony kolor, zależny od akcji:

• rozpoczęcie nowego zadania, jak otwarcie okna ⧼visualeditor-toolbar-savedialog⧽: niebieski ,
• podjęcie konstruktywnej decyzji, jak wstawienie przypisu: zielony ,
• usunięcie albo rezygnacja z zadania, jak usunięcie linku: czerwony , albo
• neutralna akcja, jak otwarcie linku w nowym oknie: szary .

Edytor TemplateData został napisany od nowa w celu użycia innego designu, korzystającego z tego samego systemu OOjs UI, co VisualEditor. (T67815, T73746.) Ta zmiana naprawiła kilka bugów i polepszyła użyteczność. (T73077, T73078.)

Narzędzie Znajdź i zamień w długich dokumentach jest szybsze. Nie podświetla każdego trafienia, jeżeli jest ich ponad sto na ekranie.(T78234.)

Twórcy hebrajskiej i rosyjskiej Wikipedii wystąpili z wnioskami o włączenie VisualEditora w przestrzeni nazw Brudnopis. (T86688, T87027.) Jeżeli twoja społeczność chce, aby VisualEditor był włączony w następnej przestrzeni nazw na twojej wiki, możesz zgłosić wniosek w Phabricatorze. Prosimy, załącz link do dyskusji na temat wnioskowanej zmiany.

Patrząc w przyszłość

Zespół Editing niedługo włączy funkcję autouzupełniania cytowań. Citoid pobiera URL lub DOI rzetelnego źródła i zwraca uzupełniony, sformatowany przypis bibliograficzny. Po dodaniu przypisu będzie można zmienić lub dodać dane w przypisie w taki sam sposób, w jaki edytuje się w VisualEditorze każdy istniejący przypis. Planowane jest wsparcie ISBN, PMID i innych identyfikatorów. W późniejszym czasie użytkownicy będą mogli zmieniać dane każdej strony zapamiętywane przez Citoid, poprawiając precyzję i zmniejszając potrzebę każdorazowego ręcznego poprawiania.

Będziemy potrzebowali pomocy użytkowników w testowaniu nowego designu wstawiania znaków specjalnych, szczególnie jeżeli znasz walijski, bretoński albo inny język, który często używa znaków diakrytycznych lub znaków specjalnych. [Przyp. tłum.: wydaje się, że polski też się zalicza.] Nowa wersja powinna być dostępna do testowania za kilka tygodni. Skontaktuj się z Whatamidoing (WMF), jeżeli chcesz być powiadomiony o terminie. Po tym, jak zostaną zakończone prace nad narzędziem do znaków specjalnych, VisualEditor zostanie włączony wszystkim użytkownikom na Wikipediach fazy 5. Dotyczy to ok. 50 średnich i małych Wikipedii, w tym Afrikaans, azerbejdżańskiej, bretońskiej, kirgijskiej, macedońskiej, mongolskiej, tatarskiej i walijskiej. Termin włączenia nie został jeszcze ustalony.

Pracujmy razem

• Podziel się pomysłami i zadaj pytania na stronie mw:VisualEditor/Feedback.
• Prosimy, pomóż dokończyć tłumaczenie instrukcji użytkownika.
• Dołącz do cotygodniowych spotkań rozpoczynających się w środę, 11 lutego o 12:00 (w południe) PST (20:00 UTC); informacje o sposobach dołączenia do spotkań będą ogłaszane na portalu na krótko przed rozpoczęciem spotkań. Możesz się też skontaktować z Jamesem F., jeżeli chcesz się dowiedzieć więcej o tej inicjatywie.
• Rozmawiaj z zespołem Editing w czasie office hours na ircu. Następne spotkanie w czwartek, 19 lutego o 19:00 UTC.
• Dopisz się do listy otrzymujących newsy na Meta. Jeżeli chcesz pomóc w tłumaczeniu newslettera, dopisz się na listę mailową tłumaczy albo skontaktuj się bezpośrednio, żebyśmy mogli cię powiadomić, kiedy następne wydanie będzie gotowe. Dziękujemy!

— Elitre (WMF)

19:30, 5 lut 2015 (CET)

kategorie

User agent: Mozilla/5.0 (Windows NT 5.1; rv:34.0) Gecko/20100101 Firefox/34.0

Otwieram do edycji za pomocą VisualEditora. Wybieram Kategorie. Widzę wtedy 7 kategorii: Członkowie stanu rycerskiego I Rzeczypospolitej, Pisarze ziemscy bielscy, Podkomorzowie bielscy, Posłowie na Sejm I Rzeczypospolitej (ziemia bielska), Posłowie na sejm 1786, Sędziowie ziemscy bielscy, Urzędnicy ziemscy I Rzeczypospolitej. NIE WIDZĘ kategorii "Hryniewieccy herbu Przeginia". W trybie VE nie mogę jej usunąć. W trybie VE nie mogę zmienić przypisanego do niej klucza sortowania.

WTM (dyskusja) 20:06, 31 mar 2015 (CEST)

Uzupełnienie do powyższego: Otwieram do edycji za pomocą VisualEditora stronę Paweł Hryniewiecki. Oczekiwałem, że formularz do wysyłania opinii pobiera i zapisuje informację na temat bieżącego URL (tak jak pobiera i zapisuje login użytkownika i identyfikator User Agenta), ale tak nie jest. --WTM (dyskusja) 20:12, 31 mar 2015 (CEST)

WTM, the missing category has {{PAGENAME}} in its wikicode, I'll check why that doesn't work in VE. Thanks a lot for your suggestion about the feedback tool too. --Elitre (WMF) (dyskusja) 14:19, 1 kwi 2015 (CEST)

What's the purpose of that magic word there, anyway? --Elitre (WMF) (dyskusja) 14:27, 1 kwi 2015 (CEST) PS: for the tool, see here.

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 "Pogrubienie" and "Kursywa" 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)

21:48, 10 kwi 2015 (CEST)

Znaki specjalne

Aplikacja klienta: Mozilla/5.0 (Windows NT 5.1; rv:36.0) Gecko/20100101 Firefox/36.0

Znów zniknęły najważniejsze znaki specjalne z menu, za to są takie, których praktycznie nigdy się nie używa. Nie ma takich znaków jak półpauza, pauza czy polski cudzysłów, natomiast pionowa kreska, mimo że dostępna z klawiatury, jest nawet 2 razy. O co chodzi?

::Daroooo:: ^(dyskusja) 09:56, 10 kwi 2015 (CEST)

@Daroooo, niedawno zmienił się system określania listy znaków specjalnych. Zauważono, że dobrze jest ujednolicić znaki w VE z tymi zawartymi pod polem edycji. Do tego samego wniosku doszedłem wcześniej, co zauważyłeś Ty i WTM, jednak ja uzgodniłem listę z naszym zbiorem znaków specjalnych. Zbiór wdrożony globalnie jest większy, dlatego zawiera znaki, których nam tak bardzo nie potrzeba (ale OK, niech będą, Word też zna o wiele więcej znaków niż statystyczny użytkownik potrzebuje, a edytując obce wiki dobrze jest wiedzieć, że tu znajdę taki a taki znak). Przy tej zmianie zmieniono też sposób określania najczęściej używanych znaków. Nie zauważyłem tego, ale dziś dowiedziałem się co i jak, poprawiłem, czekam na Twój komentarz (może coś dodać albo odjąć). Tar Lócesilion|queta! 00:22, 12 kwi 2015 (CEST)

{{odn}}

Wątek założony przed: 21:03, 11 kwi 2015 (CET)

Nie mogę sobie poradzić z wstawianiem szablonu {{odn}}. Po dodaniu przypisu w ten sposób wygląda to mniej więcej tak

---

---

---

Lorem ipsum dolor sit amet, consectetur adipisicing elit. Proin nibh augue, suscipit a, scelerisque sed, lacinia in, mi. Cras vel lorem. Etiam pellentesque aliquet tellus. Phasellus pharetra nulla ac diam. Quisque semper justo at risus. Donec venenatis, turpis vel hendrerit interdum, dui ligula ultricies purus, sed posuere libero dui id orci. Nam congue, pede vitae dapibus aliquet, elit magna vulputate arcu, vel tempus metus leo non est. Etiam sit amet lectus quis est congue mollis. Phasellus congue lacus eget neque. Phasellus ornare, ante vitae consectetuer consequat, purus sapien ultricies dolor, et mollis pede metus eget nisi. Praesent sodales velit quis augue. Cras suscipit, urna at aliquam rhoncus, urna quam viverra nisi, in interdum massa nibh nec erat.

 

Bibliografia

• Geographie, Klima und Vegetation. W: Gabriele M. Knoll: Heidelberg, Darmstadt und die Bergstrasse. Kolonia: DuMont, 1994. ISBN 3-7701-3148-7. (niem.).

---

---

---

Przypis w postaci odnośnika pojawia się o jedną (albo dwie) linijki za nisko Zwiadowca²¹ 14:30, 11 kwi 2015 (CEST)

@Zwiadowca21, czy możesz podać diffa do takiej edycji? jeżeli nie masz w artykułach, to może zrób w brudnopisie. Przeanalizujemy jak Ci to wychodzi, bo ja nie mam tego efektu (w diffie jest czysto, chociaż faktycznie w trybie edycji wygląda jakby było źle). Tar Lócesilion|queta! 00:29, 12 kwi 2015 (CEST)

zdjęcie wnętrza kolegiaty

Aplikacja klienta: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0

stare zdjęcie - z czasu remontu (renowacji?); patrz www.pultusk.pl/historia-miasta/zabytki - sklepienie pułtuskie

89.78.230.75 (dyskusja) 18:41, 12 kwi 2015 (CEST)

"Wstaw znak specjalny" -- znowuuu...

Aplikacja klienta: Mozilla/5.0 (Windows NT 5.1; rv:37.0) Gecko/20100101 Firefox/37.0

Tak wspaniale doglajchszaltowano tą opcję do wersji angielskiej, że znikła gdzieś ledwo co udostępniona przy poprzednich poprawkach półpauza, a razem z nią pauza, minus i kto wie, co jeszcze (w ang. orginale wszystkie są w sekcji "Symbole")

176.221.120.203 (dyskusja) 23:54, 12 kwi 2015 (CEST)

This is weird. I think that the lack of MediaWiki:Visualeditor-special-characters-group-other was not the reason (because if I use English as interface language, I can see the Often used section then), but I'll check better and will let you know ASAP. Thanks a lot for reporting. --Elitre (WMF) (dyskusja) 20:33, 27 maj 2015 (CEST)

I can see the Często używane section today, Tar Lócesilion! Feel free to customize it furtherly, --Elitre (WMF) (dyskusja) 18:01, 28 maj 2015 (CEST)

cite web

Widzę, że pojawiła się nowa opcja automatycznego wstawiania szablonu cytowania. Niestety w pl wiki nie mamy szablonu cite web, jest {{cytuj stronę}}. Zob.: podgląd zmian Zwiadowca²¹ 20:34, 2 cze 2015 (CEST)

Hi there

First, sorry to write in English. I'm a new community liaison at the Wikimedia Foundation, and I work with Elitre on VisualEditor.

I've tried to reproduice your bug: I just type "http://pl.wikipedia.org" in the text area and insert the link. I didn't get the {{Cite web}} template, but {{Cytuj pismo}}, without the URL as a variable. If I read correctly, {{Cytuj pismo}} can display a website but don't.

I've tried an other time, and the template {{Cytuj stronę}} has been used but the URL parameter is not taken into account.

I'll try to find out what happens.

Kontaktować się, Trizek (WMF) (dyskusja) 23:15, 2 cze 2015 (CEST)

@Zwiadowca21, to jest zdaje się Citoid, a jeżeli tak, to w gestii społeczności jest dostosowanie szablonu i parametrów do tego mechanizmu. Czego nie zrobimy, to magicznie samo się nie zrobi. Sprawa wygląda analogicznie do templatedata. Tar Lócesilion (queta) 02:52, 3 cze 2015 (CEST)

Z serii zgłoś błąd: Działało już poprawnie i znowu jest wstawiany angolski szablon cite web. Zwiadowca²¹ 15:03, 5 lip 2015 (CEST)

Cały czas część działa, część nie działa. Problem nie do końca jest po naszej stronie, a to co jest, może naprawić każdy użytkownik. Tar Lócesilion (queta) 15:27, 5 lip 2015 (CEST)

Hi Zwiadowca and Tar Lócesilion!

Translation tool is not very good for the last two messages. Can you explain me what happens in English, please ? =}

Trizek (WMF) (dyskusja) 15:17, 6 lip 2015 (CEST)

VisualEditor News #3—2015

Wątek założony przed: 21:03, 14 cze 2015 (CET)

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, "Przykład", 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)

12:44, 13 cze 2015 (CEST)

Citoid

Hello. I wanted to make sure you all had seen this list of the most referenced domains at this wiki. It could be useful to check how the top sources in your language are doing in VisualEditor's auto-filled citation generator. HTH, --Elitre (WMF) (dyskusja) 17:54, 11 sie 2015 (CEST)

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 "Pogrubienie" and "Kursywa" 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), 00:28, 15 sie 2015 (CEST)

Please read: a proposal to centralize VisualEditor feedback on www.mediawiki.org

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.

Aplikacja klienta: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0

URL: https://pl.wikipedia.org/wiki/Northrop_YF-23?veaction=edit

93.176.205.150 (dyskusja) 10:50, 26 wrz 2015 (CEST)

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 "Przełącz na edycję w edytorze wizualnym".

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 "Wstaw Grafika i multimedia" 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 "Usuń" 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 "Edytuj" and "Edytuj kod źródłowy" tabs into a single "Edytuj" tab, similar to the system already used on the mobile website. The "Edytuj" 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), 19:17, 30 paź 2015 (CET)

Your attention please: feedback about the visual editor will soon be centralized on www.mediawiki.org

Hello again. Please excuse the English. Pomóż przetłumaczyć na Twój język. Dziękujemy!

This is an update from the Editing team about redirecting local pages for feedback about the visual editor to the board on mediawiki.org. This is now technically feasible and will happen in early 2016. It applies to several wikis where such pages are inactive or have low traffic, including this wiki. We think this will help us in being more effective while processing feedback from a larger pool of wikis, not just the biggest ones. Please read our previous announcement from late August for more information; we thought we would double-check that this community is informed and agrees with the change. Please notice that if at least one community member here expressly commits to taking care of the local page, the redirect will not be necessary at this time, though. If you'd like to step up and be that person, please let me know within one week: we'll need to establish a clear process as soon as possible so that this person knows when and how to escalate issues to Phabricator or to Community Liaisons, and can receive useful tips based on our experience.

Thanks for your understanding, Elitre (WMF) 19:50, 14 gru 2015 (CET)

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 "Edytuj" and "Edytuj kod źródłowy" tabs into a single "Edytuj" tab, like the system already used on the mobile website. (T102398, T58337) Initially, the "Edytuj" 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 Edycja tab of Special:Preferences in the drop-down menu about "Tryb edycji:".

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:
  • Zapamiętaj ostatnio używany edytor,
  • Zawsze uruchamiaj edytor wizualny, gdy to możliwe,
  • Zawsze uruchamiaj edytor kodu źródłowego, and
  • Pokaż obie zakładki edycji. (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. Dziękujemy!

Elitre (WMF), 01:06, 25 gru 2015 (CET)