Wikivoyage:Reizigerscafé/2016

Wikimania 2016 Scholarships - Deadline soon!

Help met het vertalen in uw taal

A reminder - applications for scholarships for Wikimania 2016 in Esino Lario, Italy, are closing soon! Please get your applications in by January 9th. To apply, visit the page below:

• Wikimania 2016 Scholarships

Patrick Earley (WMF) via MediaWiki message delivery (overleg) 5 jan 2016 02:49 (CET)

Treinreis-sjabloon van Wikipedia

Zie w:Sjabloon:Tabel treinseries. Ik probeerde het net te gebruiken op Zaandam, maar het blijkt hier niet te werken. Volgens mij is het een heel handig sjabloon om naar Wikivoyage te kopiëren. Het zou hier wel eens nuttiger kunnen blijken te zijn dan op Wikipedia zelf. De Wikischim (overleg) 17 jan 2016 21:53 (CET)

Op zich wel een aardig idee, maar het is een nogal treinofiele benadering en niet een voyageofiele. Ook is er nogal wat onderhoud nodig, wat natuurlijk kan worden gedaan door degene(n) die dit nu doet/doen. Maar of daar nog animo voor is als het treinofiele karakter verdwijnt ... ik vraag het me af. --FredTC (overleg) 19 jan 2016 03:48 (CET)

{{pagebanner}}

Het sjabloon {{pagebanner}} werkt al geruime tijd niet goed meer!! De kopjes worden niet naast elkaar weergegeven, maar onder elkaar, overlappen daarbij de paginatitel en zijn ook niet allemaal meer zichtbaar/aanklikbaar. Pogingen van mij met het terugzetten van oude versies haalden helaas niks uit. Is er iemand die dit ZO SNEL MOGELIJK kan repareren? Ischa1 (overleg) 17 jan 2016 22:59 (CET)

Op 22 dec 2015 12:26 (CET) is op mijn OP door PAvdK melding gemaakt van dit probleem. Ik had dit probleem zelf niet ervaren, en er waren ook geen wijzigingen in het {{pagebanner}}-sjabloon gemaakt. Daarom heb ik het vervolgens met een paar browsers geprobeerd en toen bleek het op mijn laptop alleen met Chrome fout te gaan. Diep onder de motorkap in browser-afhankelijke code moet dus iets gewijzigd zijn. Met het idee dat er wellicht werk-in-uitvoering gaande was heb ik PAvdK gezegd even een paar dagen te wachten tot het werk voltooid zou zijn. Na die paar dagen heb ik op Wikipedia op de OP van onze technische specialist Romaine melding gemaakt van het probleem. Ik heb net even gekeken op die OP, maar heb geen nadere info aangetroffen. --FredTC (overleg) 18 jan 2016 03:37 (CET)

NB Ischa1, zou je een wijziging eerst willen testen voor je hem opslaat? Als het niet werkt, dan ook niet opslaan! Overigens, voordat jij met je wijzigingen begon, was de laatste wijziging van 25 mei 2015 om 11:24; had je al zo lang last van dat probleem (PAvdK maakte er 2e helft december melding van)?

Het klopt, verhip zeg. Ik werk inderdaad algemeen op Chrome, maar daar was het voordien ook niet zo. In andere browsers werkt 'ie wel naar behoren. En opvallend genoeg: als je een pagina bekijkt op een anderstalige Wikivoyage, werkt {{pagebanner}} ook gewoon prima, zelfs in Chrome! Ik kon het sjabloon overigens niet testen zonder het eerst op te slaan; zoals het sjabloon gewoon op Sjabloon:Pagebanner staat zie je namelijk alléén de titel en niet de inhoudsopgave, het gedeelte waar het misgaat. Dus ik moest eerst opslaan, dan een andere pagina openen om te kijken of het werkte... en helaas was dat niet zo (in Chrome athans). Ischa1 (overleg) 19 jan 2016 09:05 (CET)

Beste Ischa1, ik heb het nog even voor alle zekerheid bekeken met Chrome, maar daar werkt het testen van een sjabloon net zo als met IE. Als je een sjabloon wijzigt, heb je naast het bekende grote broncode-tekstvak en het (voor jou kennelijk niet erg bekende) tekstvak "Samenvatting:", ook een tekstvak "Voorvertoning weergeven met dit sjabloon" waarin je de naam van een pagina kan aangeven waarin dat sjabloon wordt gebruikt. Met de knop "Voorvertoning weergeven" kun je dan zien wat de gewijzigde broncode doet in de opgegeven pagina. --FredTC (overleg) 19 jan 2016 11:16 (CET)

2016 WMF Strategy consultation

Help met het vertalen in uw taal

Hello, all.

The Wikimedia Foundation (WMF) has launched a consultation to help create and prioritize WMF strategy beginning July 2016 and for the 12 to 24 months thereafter. This consultation will be open, on Meta, from 18 January to 26 February, after which the Foundation will also use these ideas to help inform its Annual Plan. (More on our timeline can be found on that Meta page.)

Your input is welcome (and greatly desired) at the Meta discussion, 2016 Strategy/Community consultation.

Apologies for English, where this is posted on a non-English project. We thought it was more important to get the consultation translated as much as possible, and good headway has been made there in some languages. There is still much to do, however! We created m:2016 Strategy/Translations to try to help coordinate what needs translation and what progress is being made. :)

If you have questions, please reach out to me on my talk page or on the strategy consultation's talk page or by email to mdennis@wikimedia.org.

I hope you'll join us! Maggie Dennis via MediaWiki message delivery (overleg) 18 jan 2016 20:06 (CET)

Zusterprojecten in het zonnetje

Beste Wikimedianen/ Wikivoyage bewerkers,

Wat mij betreft zouden de zusterprojecten van Wikipedia wel eens wat meer in het zonnetje gezet kunnen worden. Om dit voor elkaar te krijgen ben ik op Part-up een initiatief gestart met dit doel. Zelf ben ik sinds 2011 actief op de Nederlandstalige Wikiversiteit, maar ik hoop dat jullie me willen helpen de zusterprojecten op de agenda te zetten.

Steun mij alsjeblieft door je als supporter aan te melden voor onderstaande part-up:

https://part-up.com/partups/wikimedia-zusterprojecten-szSaH6CFsRBvWyxCG

En denk met me mee over mogelijke acties.

Met vriendelijke groet,

Tim Ruijters, Timboliu (overleg) 18 feb 2016 22:55 (CET)

Maps for Wikivoyage

Dear Wikivoyage community, I would like to update you on the progress with our Maps efforts, and make a small request.

Our maps service has been running without problems for many months. It is a stable and secure map tile platform, capable of much higher web traffic than our current labs OSM service, which is slow, unmaintained, and has crashed on numerous occasions. You may include new maps on every Wikivoyage page without causing any server overload problems.

Very soon we plan to roll out Kartographer extension to Wikivoyage. You can try it here. Kartographer supports many styles of marks, with icons and auto-numbering. Kartographer also has Visual Editor support.

While we are getting ready for the release of Kartographer, we are asking the community to help switch to this new maps tile service. The English and Russian Wikivoyage projects have already moved to this service (Here's an example - Albany). With the benefits we mentioned, we are asking projects to switch for one important reason. Right now, any visitor viewing a page that contains a map not hosted by the WMF sends information to a third-party (for example, Mapquest). This violates our privacy policy. Visitors may choose to switch to an external map, but they should be aware of that decision. For more information, please see the discussion below about this important topic at the English Wikivoyage.

The Wikimedia Maps service may not be perfect, but we think it is important to not compromise user's privacy by just visiting a page.

There are two places that need to change:

• In the Template:Mapframe, change data-layer="{{{...|O}}}" to data-layer="W".
• In the Template:PoiMap2, change &layer={{{...|M}}}& to &layer=W&.

The new maps service will be further improved with the upcoming Kartographer extension. While we are not ready to deploy Kartographer just yet, we also ask to help review the extension ahead of time. Please help review Kartographer extension documentation and our demo, and see if it meets your needs, or if anything should be changed. Please leave us a note on the Kartographer extension talk page if you have any feedback.

Relevant discussions at English Wikivoyage

• Grayed-out maps - Discussion on how to make Template:PoiMap2 point to the right default.
• Announcing the launch of Maps - Initial announcement of the new maps service with a long discussion.

CC: CKoerner (WMF). --Yurik (talk) 02:27, 24 February 2016 (UTC)

REMARK: We do not have data-layer="{{{...|O}}}", but instead we have data-layer="{{{layer|M}}}"

I found out that doing the proposed change would change the map-layer from Mapnik to Wikimedia. It also causes making an overrule impossible.

On Wikivoyage the Mapnik layer is the best choice because it shows details important to voyagers, while the Wikimedia has practicly no info at all. In a few exceptional cases it is better to instruct mapframe to use another layer, making it impossible to overrule the default is an unwanted feature.

--FredTC (overleg) 24 feb 2016 08:33 (CET)

FredTC, I agree that it is not ideal. This has came up in the previous discussion at the en wikivage. But there are several things to consider: we are working on the maps, so with the community's feedback, we will be add any missing features, especially with help. The second issue is that we are currently violating our own privacy policy (the very first link at the very bottom): whenever user visits any of WMF sites, they expect their data browsing to be well protected, because we legally promised that. And lastly, when you use WMF labs (mapnik), that service cannot scale to more users, and is much less reliable. Several times it was out for weeks until someone could take a look at it. This is far from the reliability one would expect from our wiki sites. --Yurik (overleg) 24 feb 2016 11:48 (CET)

I think right now the differences are too big to switch to Wikimedia maps, see picture below. --FredTC (overleg) 24 feb 2016 12:40 (CET)

FredTC, what in your opinion are the specific features that are absolutely "must have" for the map? Keep in mind that once we are done with the Kartographer (hopefully within the next few weeks), you will be able to add any of these marks yourself. --Yurik (overleg) 24 feb 2016 15:48 (CET)

I would say adding things myself is nice, but what the traveler sees is much more important. Switching from Mapnik to Wikimedia is an enormous loss of important/usefull information. In the example below relatively few things are missing, but if you look at here you will see much more types of information (housenumbers, shops, supermarkets, pharmacies, and more) that will be missing. So a better starting situation would be after importing all the information that is already available at Mapnik. --FredTC (overleg) 25 feb 2016 08:37 (CET)

The same Map discussion on the german WV: . --Bernello (overleg) 25 feb 2016 17:08 (CET)

FredTC, please take a look at my response here. I do want to make it better, but it is more of a legal issue and following the rules we have imposed on ourselves than about showing the best picture. Basically we either have to change the privacy policy or remove anything that does not match it. And by we I mean the whole movement. --Yurik (overleg) 26 feb 2016 03:48 (CET)

Yurik, the present situation exists for several years now. I suggest that you give priority to adding the missing info to the Wikimedia version. Then after finishing this, we can change from Mapnik to Wikimedia. It means that we only have to accept the situation a little bit longer. How difficult is it to do this conversion? You have to read all data from the Mapnik database, convert the descriptors to the Wikimedia format, then add them to the Wikimedia database. --FredTC (overleg) 26 feb 2016 07:05 (CET)

PS Maybe you can explain this privacy policy you refer to, because it is not available in Dutch language. Maybe by giving some links to relevant parts of the text. I find the text as it is quite unaccessable for me as Dutch speaking.

The privacy policy is the very first link at the bottom of every page, translated into many languages. I think this is the Dutch version - meta:Privacy_policy/nl. The problem is very simple - in the privacy policy, we say what we will and will not do with the visitor's data. If a wiki page includes a frame from another web site, such as Mapquest or Google, WMF cannot control what they do with the information, and cannot force another web site to use our policy. Which means that we cannot use any non-WMF site. The MapFrame template existed since 2013 - over two years, although I doubt there were that many embedded maps from the start. Regardless, this was not caught and stopped and time, but now it has been, and we have semi-ok alternative, and we need to fix it as soon as possible. Please read the discussion in the English wikivoyage for the context - we are working as fast as we can with the very limited resources we have - we have 2 staff members working on this project about 70% of our time. The technology that was Mapnik uses cannot be easily scaled to our level of usage, so we had to upgrade it, and it is a work in progress. But while we work on it, we simply cannot continue breaking our promises to the world. --Yurik (overleg) 26 feb 2016 19:07 (CET)

Yes, meta:Privacy_policy/nl gives a Dutch text. However the link at the bottom of the Wikivoyage pages as well as the one on Wikipedia pages gives English.

However I do not understand why this change needs to be done in such a hurry, after having the situation tolerated for several years. The remark "and we have semi-ok alternative" is certainly not valid for Wikivoyage, it is a "not-at-all-ok alternative" missing so much info!!! It is as if such a statement was given by a blind person. But not only for the traveler there is info missing. Also for the contributors who want to put a {{see ...}}-item on the map it makes things difficult.

Example: Having this map on your screen, how do you find the Church of San Andrea della Valle, knowing it is not far from the Piazza Navona? The Wikimedia map shows at zoom level 16 clearly where Piazza Navona is. But now, where is the church? I can zoom in to level 18, but still no churches. Moving the map up a little I do see a busstop with the name "C.so Vittorio Emanuele/S.A. della Valle", but it still does not show which building is the church! With Mapnik I see at zoom level 16 already churches in the Piazza Navona area, and only zooming in to level 17 brings me to the location (lat=41.8961 | long=12.4743). So without Mapnik I need a second mapping souce to find the exact location.

So I think it is unacceptable for both travelers and contributers to miss the Mapnik info. The Wikimedia maps should have the information it now misses. So the download-convert-upload with Mapnik must be done before switching to Wikimedia maps. The Wiki's are there to give info to a large public and not only to give people who like to Wikify info something to do. For Wikivoyage the switch before adding the info is a downgrade. --FredTC (overleg) 27 feb 2016 04:32 (CET)

FredTC, thanks, the privacy policy link is a bug (see phab:T128281). The situation with maps was not tolerated for several years, the situation was not noticed for several years, and it is sad that noone noticed it at first - if they did, the maps would not have been allowed at all. At the last Wikimania Doc James showed me this cool map feature, and I realized that it was grossly violating one of the most important pillars of our movement - user's privacy. I raised this as a major concern, and it was quickly changed from Mapquest to Mapnik, because Mapnik runs on WMF Labs, and, at least in theory, has a slightly better privacy protection. This was an interim solution until we get at least some map solution ready. Please also notice that Mapnik is actually not as good as Mapquest - which has much more professional maps, but we had to make that switch too, despite the hard to the users, simply because the privacy harm outweighs the slight inconvenience of an imperfect map.

FredTC, have you had a chance to look through this discussion? Many of the concerns you raise have been raised there as well, and I would love to address them. Lets figure out what we can fix in a short term, and what we should set as a longer term goals. Some things are easier to fix than others. But we really cannot have this continue, and I am pretty sure the stewards will agree on this.

Lastly, please remember that I am the biggest proponent of maps in wiki. I started this whole project, and I am doing everything in my power for this project to improve and become available everywhere. But it is a work in progress, and I do hope that soon we will be able to provide very good quality, mulitlingual, multi-styled, client-side (WebGL) rendered maps with amazing features. User's participation in this project is critical to its success - I have to justify that my project is needed by the community, or else it will be underfunded or shutdown outright. "dogfooding" is very important, otherwise there will be no active participation and no community-driven improvements. Again, please read the discussion on en-wikivoyage in the link above - we have discussed that there as well. Thanks! --Yurik (overleg) 27 feb 2016 19:02 (CET)

Pharmacy

Yurik, after taking a better look at the privacy policy link in Dutch, I found out that it is only partly translated, and that quite a lot is still in English. Probably that is the reason that the present link at the bottom of the pages points to the full English version.

I do not agree with the prefering of Mapquest over Mapnik. Mapnik has so many points of orientation, like the earlier mentioned pharmacies, which are often very visible in the Streets as you can see on the photo I just added. Also the † at most churches are missing at Mapquest, they are also important orientation points. Mapnik on my smart Phone is also more helpfull than the Android Maps App, I experienced. How do you define "much more professional maps"?

Yes, I had a look at "previous discussion at the en wikivage", but did not realise it was at en:Wikivoyage at that first moment (because of wikivage). I tought, because of "The English and Russian Wikivoyage projects have already moved to this service", I will take a look at the en:Pub. For some reason the page and also the archive page did not load completely, and I could not find any discussion having the word "map". Then I did put a question on the discussion page of Seligne who is or was an admin on en:Wikivoyage, because I could not imagine that it was introduced without any discussion. By then I learned that the discussion via your wikivage-link was in fact a WikivOYage discussion and after loading the page again (complete this time) I learned that in fact the wikivage-link was to the en:Pub.

From the discussion I learned that it was dated over 5 months ago. What has been done since then? In 5 months a conversion of the Mapnik data could have been done. Why did this not happen?

My biggest fear is that by saying "OK we can temporarily live with maps that have very little info", at Wikimedia they will say "yippy, everybody is OK with it, the project is finished", and then never spend time on completing the map info with the Mapnik info.

By looking around at mapframe examples on en:Wikivoyage, I noticed that with the menu button (upper right corner) I can still get Mapnik maps. Will this remain like this? In that case, at least I can do the {{see ...}} with map positions in an efficient way. And the link to the full screen version could link to the Mapnik layer as long as the Wikimedia maps are not complete.

I could not find something like a project plan, showing when what to do. So I can not see when the conversion of the Mapnik info will be done.

--FredTC (overleg) 1 mrt 2016 03:41 (CET)

VisualEditor News #1—2016

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

Did you know?

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

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

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

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

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

Recent changes

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

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

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

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

Future changes

The single edit tab project will combine the "Bewerken" and "Brontekst bewerken" tabs into a single "Bewerken" tab. This is similar to the system already used on the mobile website. (T102398) Initially, the "Bewerken" tab will open whichever editing environment you used last time. Your last editing choice will be stored as an account preference for logged-in editors, and as a cookie for logged-out users. Logged-in editors will have these options in the Bewerken tab of Special:Preferences:

• Laatste tekstverwerker onthouden,
• Waar mogelijk de visuele tekstverwerker gebruiken,
• Altijd wikitekst bewerken, and
• Beide bewerkingstabbladen weergeven. (This is the state for people using the visual editor now.)

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

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

Let's work together

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

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

Elitre (WMF), 26 feb 2016 20:21 (CET)

Externe links midden in teksten

Ik heb dit meen ik vorig jaar al een aangekaart; waarom wordt dit hier overal zo gedaan? Het ziet er egr onverzorgd uit. Wikipedia en alle andere Wikimediaprojecten werken standaard met verwijzingen in een Appendix-sjabloon. Dit geeft een tekst in zijn algemeenheid een veel netter voorkomen. De Wikischim (overleg) 1 mrt 2016 10:35 (CET)

Ja, je hebt er hier ruim een jaar geleden een melding over gedaan. Wat is het precies dat maakt dat de externe links voor jou een erg onverzorgde aanblik hebben? --FredTC (overleg) 3 mrt 2016 16:22 (CET)

Maps trial has began!

We just enabled the new maps support for WikiVoyage. Please see (and help translate) documentation. This is a new functionality, it does not change any existing funcionality. This is a test version, and has many bugs, please do not use it for real pages yet. The goal of this release is for the community to experiment with the early release and steer our development efforts towards what you really need. If you have any requests, please create them here (login by clicking the MediaWiki button).

New features:

• add maps to pages using <mapframe>
• add map links to pages using <maplink>
• add markers and polygons to maps using Visual Editor
• edit geojson and see how it changes the map on each keystroke
• add auto-numbered markers (either numbers or letters), and have multiple counters
• have multiple "groups" of markers/polygons and showing them on the same map or on separate maps (e.g. all food and all drink maps and one combined map)
• markers and polygons can be of any color
• markers and polygons can be clicked and will show popups with wiki text and images
• fast full screen popup maps

--Yurik (overleg) 8 mrt 2016 04:12 (CET)

I'm still waiting for answers at Wikivoyage:Reizigerscafé#Maps for Wikivoyage --FredTC (overleg) 8 mrt 2016 13:56 (CET)

First impressions by FredTC

To the right a screenprint of Missing features I experienced after a first inspection. Red arrows, counter clock wise, starting at the top:

1. An available switch to Mapnik is very important because Mapnik gives very important reference points. Also the switches like "Points of interest", "Cycling", "Hiking", etc. are very usefull.
2. Showing the current zoom level is a great help when defining the "zoom=" with mapframe.
3. The POIs button shows destination pages of other destinations in/near the area of the map. Gives the answer to "is there a described destination not far from here?"
4. This button shows all markers defined on the page. Very helpfull if some makers are relatively far away.
5. The missing of the right-click feature is needed very much in order to make new markers.

Clicking the button in the upper right corner brings you to a full screen, but does not allow you to open it on a separate tab. If you use the right-click on this button, it is not the map, but the whole page containing that map appearing in the new tab. This is not practical, because the {{see ...}} and {{sleep ...}} are not close together, you have to scroll the text and you cannot switch to another tab to see the map.

With the mobile version of this page on a Full HD phone screen in portrait orientation, the map takes more than the 1080 pixels the screen is wide, but is defined with "width="400"". Because of this width, it is not easy to scroll down past the map.

--FredTC (overleg) 9 mrt 2016 14:16 (CET)

FredTC, thanks for reviewing and for excellent points. I expanded your ideas into discussion sections, and moved them to MediaWiki maps page. Lets continue there so that we can have more involvement from a wider audience. --Yurik (overleg) 9 mrt 2016 16:41 (CET)

CC: FredTC
The first attempt at implementing map layers feature for Wikivoyage community has been posted at EN-Wikivoyage. There are some improvements that still need to be made, but hopefully it will be a good way to migrate wikivoyage off of the unstable wmflabs-based solution and solve the privacy issue. As always, any feedback is welcome. --Yurik (overleg) 18 mei 2016 06:14 (CEST)

Reisbeurzen voor deelname aan Wikimania 2016

Wikimania, de jaarlijkse bijeenkomst van de wereldwijde Wikimedia-beweging, is dit jaar van 24 tot 26 juni in Esino Lario, Italië. Wikimedia Nederland stelt weer reisbeurzen ter beschikking voor actieve leden van de gemeenschap. Meer informatie over aanvraag en toekenning van deze reisbeurzen is te vinden op deze pagina.SRientjes (overleg) 15 mrt 2016 13:26 (CET)

Drentse Aa

Hi, sorry for the English :) I saw Drentse Aa and it does not say what it is. This one, this one or something else? --Superchilum (overleg) 19 mrt 2016 12:17 (CET)

It is not this one because it describes a brook, and a brook has never an own article on nl:Wikivoyage. It also is not This one because it describes a w:en:Water board (Netherlands) that does not exist anymore. I guess Drentse Aa is an invention of gebruiker:Ischa1, maybe you shoul address him/her directly with this question. --FredTC (overleg) 19 mrt 2016 13:49 (CET)

FredTC thank you, I wrote him and I'm waiting for an answer. What about Orval? I see there is a deletion procedure but still open since 2013. --Superchilum (overleg) 28 mrt 2016 14:47 (CEST)

Hi Superchilum and FredTC! It's definitely not an invention, but it seems to be considered an actual region of Drenthe, as you can see here. Ischa1 (overleg) 30 mrt 2016 18:54 (CEST)

Hi Superchilum, as you can see by Ischa1's answer, this one and this one on Wikipedia are not the same as Drentse Aa on Wikivoyage. The answer also shows that the area name is not an invention of Ischa1, but an invention of some touristic websites. So for tourists/travelers it is a valid area name, supported by touristic websites. --FredTC (overleg) 31 mrt 2016 08:05 (CEST)

For Orval I gave a recommandation, but I did not follow what happened after that. I still think that the info should be combined with another article. --FredTC (overleg) 31 mrt 2016 08:05 (CEST)

Thank you both for your assistance :) --Superchilum (overleg) 31 mrt 2016 09:04 (CEST)

Open Call for Individual Engagement Grants

Help met het vertalen in uw taal:

Greetings! The Individual Engagement Grants (IEG) program is accepting proposals until April 12th to fund new tools, research, outreach efforts, and other experiments that enhance the work of Wikimedia volunteers. Whether you need a small or large amount of funds (up to $30,000 USD), IEGs can support you and your team’s project development time in addition to project expenses such as materials, travel, and rental space.

• Submit a grant request or draft your proposal in IdeaLab
• Get help with your proposal in an upcoming Hangout session
• Learn from examples of completed Individual Engagement Grants

With thanks, I JethroBT (WMF) 31 mrt 2016 17:47 (CEST)

No editing two times this week

De Wikimedia Foundation gaat haar nieuwe datacenter in Dallas testen. Dit datacenter moet ervoor zorgen dat Wikipedia en andere Wikimediaprojecten beschikbaar blijven, ook als er een servercrash heeft plaatsgevonden. Om zeker te weten dat alles goed werkt, zal de Wikimedia Foundation een experiment uitvoeren met het nieuwe datacenter. De Wikimedia Foundation wil met behulp van dit experiment kijken of dit nieuwe datacenter goed werkt. Er staat een groot team klaar voor dit experiment, ook om plotselinge problemen op te lossen.

Zij zullen al het internetverkeer naar het nieuwe datacenter sturen op dinsdag 19 april.
Op donderdag 21 april wordt al het internetverkeer weer terug naar het huidige datacenter gestuurd.

Vanwege beperkingen in MediaWiki is het echter wel noodzakelijk om de wiki's op alleen-lezen te zetten. Het spijt ons voor deze maatregel, en wij zullen trachten om de impact te verminderen in de toekomst.

U zult in staat zijn om artikelen te lezen, maar niet te bewerken voor een korte periode. Dit geldt voor alle Wikimediaprojecten.

• U zult niet in staat zijn om bewerkingen uit te voeren voor ongeveer 15 tot 30 minuten op dinsdag 19 april en donderdag 21 april vanaf 14:00 UTC (16:00 CEST, 10:00 EDT, 07:00 PDT).
• U zult een foutmelding zien als u probeert te bewerken. Wij hopen dat er geen bewerkingen verloren gaan, maar hier zijn wij niet zeker van. Als u deze foutmelding krijgt, raden we u aan om te wachten totdat deze korte maatregel weer opgelost is. Dan kunt u uw bewerking opslaan. Toch raden we het ten zeerste aan dat u een kopie van uw bewerkingen maakt.

Extra impact:

• Het uitvoeren van achtergrondtaken zal langzamer gaan, en sommige taken kunnen ook worden geannuleerd. Roodgekleurde links zullen niet zo snel bijgewerkt worden als gebruikelijk. Als u een artikel aanmaakt waar ergens anders al naar verwezen wordt, zal de link langer roodgekleurd blijven dan gebruikelijk. Sommige scripts die lang uitgevoerd worden, zullen worden gestopt.
• Er zal een 'code freeze' ingelast worden voor de week van 18 april. Alleen urgente code deployments zullen plaatsvinden.

Deze test zou eigenlijk al op 22 maart uitgevoerd worden. De nieuwe datums zijn 19 en 21 april. U kunt de planning lezen op wikitech.wikimedia.org. Wij zullen veranderingen aan de planning daar posten. Er zullen meer notificaties omtrent de switch worden gestuurd. Deel deze informatie alstublieft met de gebruikersgemeenschap van uw (thuis)wiki's. /Johan (WMF) (overleg) 18 apr 2016 00:38 (CEST)

Pagebanners

Beste gebruikers,

Even een opmerking over de pagebanners, deze falen keihard qua weergeven in de Safari browsers, de tekst die onder de pagebanner staat loopt dwars door de afbeelding heen, valt hier iets aan te doen? BerendWorst (overleg) 29 apr 2016 12:27 (CEST)

You can switch between wikitext and visual editing

Help met het vertalen in uw taal

Hello,

Editors at this Wikivoyage have access to both the wikitext and visual editors. You can switch between the two systems in the middle of an edit. These images show where to find the button to do this:

• 
  In the wikitext editor, the pencil icon allows you to switch to the visual editor.
• 
  In the visual editor, the [[ ]] (square brackets) icon allows you to switch to the wikitext editor.

I've asked the devs to turn on an option in Special:Preferences for all of the Wikivoyages. They will probably do this on Monday, 6 June 2016.

For people who use both editing systems, this preference setting will let you choose whether to have two tabs (how it works today) or just one. I like having two tabs, but many editors want just one, to always open their favorite editing system. They can use these buttons to temporarily switch to the other whenever they want. This option works well for most people. However, experience on other wikis shows that a few people who are used to two tabs usually get "stuck" in one and can't figure out how to switch to the other editing system. So please look for these icons the next time you open an article to edit; they're available to you today, and they'll help if anyone gets stuck next week.

Here are the three things that I want you to know about this:

• If you haven't enabled the visual editor, then you already have just one "Bewerken" tab, and this change should not affect you.
• If you have two editing tabs now ("Bewerken" and "Brontekst bewerken"), then on Monday, you will only have one. (Don't worry!) As soon as the second editing tab disappears, the new prefs setting will appear. You can go to Special:Preferences#mw-prefsection-editing, find the drop-down menu named "Editing mode", and choose whatever you want. (You won't see this option if you have the visual editor disabled.)
• If you get stuck, remember that you can use those two buttons to switch to the other editing system.

There is more information about this feature at mw:VisualEditor/Single edit tab. I'll be around Monday when this happens, so please ping me if you encounter any unexpected problems.

By the way, for those of you who want to try out the visual editor, please remember it will be easier to add templates in the visual editor if you've added TemplateData information to their documentation pages.

Happy editing, Whatamidoing (WMF) (overleg) 3 jun 2016 19:23 (CEST)

JavaScript

Hi. I can see that this project has old JavaScript that needs to be updated. I would happily make the required updates myself, but I would have to – at least temporarily – become an admin here to do that (because the relevant pages are in the MediaWiki namespace). I have already made these updates on a number of other projects, so it would be very easy for me to do this. If no one does anything, some JavaScript-related tools will break later this year. If you want me to make these updates, you can grant me admin rights and I will make the updates as soon as I can. Nirmos (overleg) 4 jun 2016 08:08 (CEST)

The visual editor is coming to this wiki soon

Help met het vertalen in uw taal. Bedankt!

Hello, Wikivoyagers!

The visual editor is coming to this Wikivoyage soon. The visual editor allows people to edit Wikivoyage articles as if they were using a typical word processor. The target date is 14 June 2016. After the deployment, everyone will automatically have the option to use either the visual editor or the current wikitext editor. For more information about how to use the visual editor, see mw:Help:VisualEditor/User guide.

Here's what the two editing systems look like:

You can use the visual editor right now. To turn it on, select "Bèta" in your preferences. Choose "Visuele tekstverwerker" and click save. When it is enabled, press the "Bewerken" button to edit an article in the new software. When the visual editor is open, you can switch to the wikitext editor any time you want. Just click the [[ ]] icon in the toolbar, next to the "Save" button. Inside the wikitext editor, click the pencil icon () in the upper right corner to switch to the visual editor. If you prefer having two tabs, or if you want to change the editing system that opens first, go to Special:Preferences#mw-prefsection-editing and choose your favorite option for the "Editing mode".

There is a short guide at mediawiki.org that has some tips about getting the best value out of the visual editor for your project.

• It's much easier to add templates if you've added TemplateData information. This is particularly important for popular templates, such as Template:Eat.
• If you think that 14 June 2016 is not a good date for your wiki, then please contact me as soon as possible.
• Please let me know if you find any problems. You can report issues in Phabricator, the new bug tracking system or on the central feedback page on MediaWiki.org. If you notice major issues affecting your project, please leave a note on my talk page.
• Sign up for the visual editor's multilingual newsletter if you want to hear about new features.

Thank you, and happy editing! – Whatamidoing (WMF) (overleg) 8 jun 2016 07:48 (CEST)

Compact Language Links enabled in this wiki today

Help met het vertalen in uw taal

Screenshot of Compact Language Links interlanguage list

Compact Language Links has been available as a beta-feature on all Wikimedia wikis since 2014. With compact language links enabled, users are shown a much shorter list of languages on the interlanguage link section of an article (see image). Based on several factors, this shorter list of languages is expected to be more relevant for them and valuable for finding similar content in a language known to them. More information about compact language links can be found in the documentation.

From today onwards, compact language links has been enabled as the default listing of interlanguage links on this wiki. However, using the button at the bottom, you will be able to see a longer list of all the languages the article has been written in. The setting for this compact list can be changed by using the checkbox under User Preferences -> Appearance -> Languages

The compact language links feature has been tested extensively by the Wikimedia Language team, which developed it. However, in case there are any problems or other feedback please let us know on the project talk page. It is to be noted that on some wikis the presence of an existing older gadget that was used for a similar purpose may cause an interference for compact language list. We would like to bring this to the attention of the admins of this wiki. Full details are on this phabricator ticket (in English).

Due to the large scale enablement of this feature, we have had to use MassMessage for this announcement and as a result it is only written in English. We will really appreciate if this message can be translated for other users of this wiki. Thank you. On behalf of the Wikimedia Language team: Runa Bhattacharjee (WMF) (talk) 22 jun 2016 09:39 (CEST)

Editing News #2—2016

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

Did you know?

It's quick and easy to insert a references list.

Place the cursor where you want to display the references list (usually at the bottom of the page). Open the "Invoegen" menu and click the "Referentielijst" icon (three books).

If you are using several groups of references, which is relatively rare, you will have the opportunity to specify the group. If you do that, then only the references that belong to the specified group will be displayed in this list of references. Finally, click "Invoegen" in the dialog to insert the Referentielijst. This list will change as you add more footnotes to the page.

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

Since the last newsletter, the VisualEditor Team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Arabic and Indic scripts, and adapting the visual editor to the needs of the Wikivoyages and Wikisources.

Recent changes

The visual editor is now available to all users at most [[Wikivoyage:|Wikivoyages]]. It was also enabled for all contributors at the French Wikinews.

The single edit tab feature combines the "Bewerken" and "Brontekst bewerken" tabs into a single "Bewerken" tab. It has been deployed to several Wikipedias, including Hungarian, Polish, English and Japanese Wikipedias, as well as to all Wikivoyages. At these wikis, you can change your settings for this feature in the "Bewerken" tab of Special:Preferences. The team is now reviewing the feedback and considering ways to improve the design before rolling it out to more people.

Future changes

The "Pagina opslaan" button will say "Pagina publiceren". This will affect both the visual and wikitext editing systems. More information is available on Meta.

The visual editor will be offered to all editors at the remaining "Phase 6" Wikipedias during the next few months. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including: Arabic, Hindi, Thai, Tamil, Marathi, Malayalam, Urdu, Persian, Bengali, Assamese, Aramaic and others.

The team is working with the volunteer developers who power Wikisource to provide the visual editor there, for opt-in testing right now and eventually for all users. (T138966)

The team is working on a modern wikitext editor. It will look like the visual editor, and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices around September 2016. You can read about this project in a general status update on the Wikimedia mailing list.

Let's work together

• Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor? Please sign up for the new VisualEditor Community Taskforce.
• Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Watch the Tech Talk by Sebastian Karcher for more information.

If you aren't reading this in your preferred 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. Bedankt!

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

Open call for Project Grants

Help met het vertalen in uw taal:

Greetings! The Project Grants program is accepting proposals from July 1st to August 2nd to fund new tools, research, offline outreach (including editathon series, workshops, etc), online organizing (including contests), and other experiments that enhance the work of Wikimedia volunteers.

Whether you need a small or large amount of funds, Project Grants can support you and your team’s project development time in addition to project expenses such as materials, travel, and rental space.

• Submit a grant request or draft your proposal in IdeaLab
• Get help with your proposal in an upcoming Hangout session
• Learn from examples of completed Individual Engagement Grants or Project and Event Grants

Also accepting candidates to join the Project Grants Committee through July 15.

With thanks, I JethroBT (WMF) 5 jul 2016 17:25 (CEST)

Save/Publish

The Editing team is planning to change the name of the “Pagina opslaan” button to “Pagina publiceren” and “Wijzigingen publiceren”. “Pagina publiceren” will be used when you create a new page. “Wijzigingen publiceren” will be used when you change an existing page. The names will be consistent in all editing environments.

This change will probably happen during the week of 30 August 2016. The change will be announced in Tech News when it happens.

If you are fluent in a language other than English, please check the status of translations at translatewiki.net for “Pagina publiceren” and “Wijzigingen publiceren”.

The main reason for this change is to avoid confusion for new editors. Repeated user research studies with new editors have shown that some new editors believed that “Pagina opslaan” would save a private copy of a new page in their accounts, rather than permanently publishing their changes on the web. It is important for this part of the user interface to be clear, since it is difficult to remove public information after it is published. We believe that the confusion caused by the “Pagina opslaan” button increases the workload for experienced editors, who have to clean up the information that people unintentionally disclose, and report it to the functionaries and stewards to suppress it. Clarifying what the button does will reduce this problem.

Beyond that, the goal is to make all the wikis and languages more consistent, and some wikis made this change many years ago. The Legal team at the Wikimedia Foundation supports this change. Making the edit interface easier to understand will make it easier to handle licensing and privacy questions that may arise.

Any help pages or other basic documentation about how to edit pages will also need to be updated, on-wiki and elsewhere. On wiki pages, you can use the wikitext codes {{int:Publishpage}} and {{int:Publishchanges}} to display the new labels in the user's preferred language. For the language settings in your account preferences, these wikitext codes produce “Pagina publiceren” and “Wijzigingen publiceren”.

Please share this news with community members who teach new editors and with others who may be interested.

Whatamidoing (WMF) (talk) 9 aug 2016 20:03 (CEST)

RevisionSlider

From September 13th on, RevisionSlider will be available as a beta feature in your wiki. The RevisionSlider adds a slider view to the diff page, so that you can easily move between revisions. The feature fulfills a wish from the German Community’s Technical Wishlist. Everyone is invited to test the feature and we hope that it will serve you well in your work!

Birgit Müller (WMDE) 12 sep 2016 17:08 (CEST)

Wikitravel database / XML dumps

This is the complete database dump / back up of WT in all 21 languages. This includes all pages in all namespaces. Download here. The file is compressed using 7zip it's 370 MB in size. XML's are plain text files that can be edited in Notepad. I also have a list of pages from WT that are missing here. I placed it on my userspace for reference. If there is interest in porting those pages I can generate a specific XML for that purpose. Acer (overleg) 17 sep 2016 17:40 (CEST)

Grants to improve your project

Help met het vertalen in uw taal:

Greetings! The Project Grants program is currently accepting proposals for funding. There is just over a week left to submit before the October 11 deadline. If you have ideas for software, offline outreach, research, online community organizing, or other projects that enhance the work of Wikimedia volunteers, start your proposal today! Please encourage others who have great ideas to apply as well. Support is available if you want help turning your idea into a grant request.

• Submit a grant request
• Get help: In IdeaLab or an upcoming Hangout session
• Learn from examples of completed Individual Engagement Grants or Project and Event Grants

I JethroBT (WMF) (talk) 30 sep 2016 22:10 (CEST)

Change to OpenStreetMap template

Greetings and sorry for the English,

We have a change to this template that we would like your help with.

Right now the template uses a tile service on Wikimedia Labs. This is not a service that can scale for wider use. We would like to stop using it for maps on the wikis. Instead, we would like to change the template to use the Wikimedia tile service. This is a new system that the Discovery department has developed over the last year. The Wikimedia tile service has much better support in terms of hardware, software, and active development.

Additionally the Labs service does not use the privacy policy. Moving to the Wikimedia tile server will better protect our users rights.

We would like to remove the <slippymap> tag and update the template with <mapframe>. With your help we will stop using the Labs tile service a month from now, on Monday, October 24th.

We encourage members of the community to update the template. We want to make this change with community involvement and are available to help with implementing the new tile service in this template.

You can learn more about what this change means, including example code, in this Phabricator task. If you have questions, please leave them below or at the Maps talk page on MediaWiki.org.

Thank you for your time. CKoerner (WMF) (overleg) 4 okt 2016 23:59 (CEST)

I don't see any <slippymap> in the many Wikivoyage pages I have visited. It also does not appear in templates that deal with maps like {{mapframe|...}}, {{see|...}} and more. There has been a conversation between user Yurik and me about a new version of maps in Wikivoyage. What I did see of this new version was not very positve.

So, there is not much that I can do in reaction to this posting.

Another remark: "a month from now, on Monday, October 24th" is not exactly a month from now.

--FredTC (overleg) 5 okt 2016 04:00 (CEST)

However CKoerner (WMF), I found this: "...{{#tag:slippymap||lat={{{breite|51}}}|lon={{{laenge|0}}}..." in the openstreetmap template. Not exactly <slippymap>, but the word slippymap appears in it. I tried to change "...{{#tag:slippymap||lat={{{breite|51}}}|lon={{{laenge|0}}}..." into "...{{#tag:mapframe||lat={{{breite|51}}}|lon={{{laenge|0}}}...", but that caused error messages. There is no <slippymap> that I can change into <mapframe>. --FredTC (overleg) 6 okt 2016 14:51 (CEST)

Thank you FredTC for your reply. I originally posted this message on the template talk page about a week ago. I was trying to not make so much noise here, but didn't get any response in the last week. :) You're right, that template is the only instance of the <slippymap> being used, and not on many pages. That said, I didn't want to go making changes to the template and be seen as interfering. As for making the change to the template, I think we need to look at the #tag:slippymap and change it to something like this:

{{#tag:mapframe| | latitude={{#iferror:{{#expr:{latdegdec}+0}}|0|{latdegdec} }} | longitude={{#iferror:{{#expr:{londegdec}+0}}|0|{londegdec} }} | zoom={{#iferror:{{#expr:{osmzoommap}+0}}|0|{osmzoommap} }} | width=360 | height=360 | frameless= | align=center }}

Pinging Gebruiker:MaxSem to see if this is correct. CKoerner (WMF) (overleg) 6 okt 2016 16:06 (CEST)

Done with Gebruiker:MaxSem/Sandbox. Does that look good? FredTC, {{#tag:slippymap}} is the same tag, just added in a way that allows its parameters to be processed as wikitext, see mw:Help:Magic_words/nl#Diversen. MaxSem (overleg) 7 okt 2016 01:31 (CEST)

Creative Commons 4.0

Hello! I'm writing from the Wikimedia Foundation to invite you to give your feedback on a proposed move from CC BY-SA 3.0 to a CC BY-SA 4.0 license across all Wikimedia projects. The consultation will run from October 5 to November 8, and we hope to receive a wide range of viewpoints and opinions. Please, if you are interested, take part in the discussion on Meta-Wiki.

Apologies that this message is only in English. This message can be read and translated in more languages here. Joe Sutherland (talk) 6 okt 2016 03:35 (CEST)

Editing News #3—2016

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

Did you know?

Did you know that you can easily re-arrange columns and rows in the visual editor?

Select a cell in the column or row that you want to move. Click the arrow at the start of that row or column to open the dropdown menu (shown). Choose either "Move before" or "Move after" to move the column, or "Move above" or "Move below" to move the row.

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 mainly worked on a new wikitext editor. They have also released some small features and the new map editing tool. Their workboard is available in Phabricator. You can find links to the list of work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, releasing the 2017 wikitext editor as a beta feature, and improving language support.

Recent changes

• You can now set text as small or big.
• Invisible templates have been shown as a puzzle icon. Now, the name of the invisible template is displayed next to the puzzle icon. A similar feature will display the first part of hidden HTML comments.
• Categories are displayed at the bottom of each page. If you click on the categories, the dialog for editing categories will open.
• At many wikis, you can now add maps to pages. Go to the Insert menu and choose the "Maps" item. The Discovery department is adding more features to this area, like geoshapes. You can read more at mediawiki.org.
• The "Save" button now says "Save page" when you create a page, and "Save changes" when you change an existing page. In the future, the "Pagina opslaan" button will say "Pagina publiceren". This will affect both the visual and wikitext editing systems. More information is available on Meta.
• Image galleries now use a visual mode for editing. You can see thumbnails of the images, add new files, remove unwanted images, rearrange the images by dragging and dropping, and add captions for each image. Use the "Options" tab to set the gallery's display mode, image sizes, and add a title for the gallery.

Future changes

The visual editor will be offered to all editors at the remaining 10 "Phase 6" Wikipedias during the next month. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including Thai, Burmese and Aramaic.

The team is working on a modern wikitext editor. The 2017 wikitext editor will look like the visual editor and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices in October 2016. You can read about this project in a general status update on the Wikimedia mailing list.

Let's work together

• Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor? Please sign up for the new VisualEditor Community Taskforce.

• If you aren't reading this in your preferred 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. Bedankt!

—Elitre (WMF)

15 okt 2016 19:49 (CEST)

Typografie/vet

Ik val hier iedere keer over het vele vet midden in teksten, zie bijvoorbeeld Nationaal park Volcán Arenal. Voor gewone subkoppen is dit uiteraard prima, maar elke aparte naam afzonderlijk hoeft toch niet in het vet? Cursiveren kan eventueel als alternatief, maar zelfs dat is vaak niet nodig. De Wikischim (overleg) 15 okt 2016 23:39 (CEST)

Ja, het is kennelijk de schrijfstijl van enkele bijdragers. Het zijn vooral de gebruikers Gebruiker:WiDi (al heel lang niet meer actief) en Gebruiker:Hein56didden (heel actief met Italië-artikelen en artikelen in de omgeveng van zijn woonplaats) die dit doen. Ik heb trouwens jouw linkje naar Nationaal park Volcán Arenal zodanig aangepast, dat je opmerking daar ook is te zien. --FredTC (overleg) 16 okt 2016 05:16 (CEST)

Pictogrammen

Begin oktober hebben gebruiker Rodejong en ik een overleg gevoerd over het eventueel invoeren van (meer) pictogrammen in de resultaten van sjablonen als {{see|...}}. In onderstaande tabel staan de pictogrammen die door ons beiden zijn gevonden en potentiele kandidaten zijn. Omdat wijzigingen de presentatie van de gegevens wijzigt, leek het ons wenslijk er meer bijdragers bij te betrekken. In de tabel kan de voorkeur worden aangegeven op de volgende wijze:

• Voorkeur "3/15" is 3e pictogram bij 15px.
• Voorkeur "niet" is geen pictogram gebruiken.
• Voorkeur "-" is geen voorkeur, ik vind alles goed.

Ook kunnen meer pictogrammen worden voorgesteld.

Parameter	Voorgedragen pictogrammen	Tekst mouse-over	Voorkeur Rodejong	Voorkeur FredTC	Voorkeur Abeona	Voorkeur ...	Voorkeur ...	Voorkeur ...
adres	15px 1: , 2: 18px 1: , 2:	Bezoekadres	2/15	2/15	2/15	-	-	-
phone	15px 1: ☎ 18px 1: ☎	Telefoonnummer	1/15	1/15	1/15	-	-	-
tollfree	15px 1: 18px 1:	Gratis telefoonnummer	niet	-	niet	-	-	-
fax	15px 1: 18px 1:	Telefoonnummer Fax	niet	-	1/15	-	-	-
e-mail	15px 1: 2: 18px 1: 2:	e-mail adres	2/15	2/15	2/15	-	-	-
price	15px 1: €, 2: , 3: , 4: , 5: , 6: , 7: 18px 1: €, 2: , 3: , 4: , 5: , 6: , 7:	www: Prijs(-indicatie) www: Prijs (zie website voor actuele prijs-info)	6/15	3/15	6/15	-	-	-
hours	15px 1: 🕘, 2: , 3: , 4: 18px 1: 🕘, 2: , 3: , 4:	Openingstijden	3/15	3/15	3/15	-	-	-
checkin	15px 1: 18px 1:	Vroegste checkintijd	1/15	1/15	1/15	-	-	-
checkout	15px 1: 18px 1:	Uiterste checkouttijd	1/15	1/15	1/15	-	-	-
content	15px 1: 2: 18px 1: 2:	Verdere omschrijving	2/18	1/15	1/15	-	-	-

Als sjabloon {{listing|...}} op onderstaande wijze wordt gebruikt:

* {{listing
| name=Naam | alt=alt | url= | email=info@site.com
| address=Adres | lat= | long= | directions=directions
| phone=+12 34567890 | tollfree=+98 76543210 | fax=+55 12344321
| hours=hours | price=prijs | checkin=checkin | checkout=checkout
| content=content.
}}

Dan zou het resultaat er met de gedane voorstellen, zo uitzien:

Wens van ...	Resultaat
Huidig	Naam (alt), Adres (directions), ☏ +12 34567890, tolvrij: +98 76543210, fax: +55 12344321, info@site.com. hours. Check-in: checkin, check-out: checkout. content. prijs.
Rodejong	Naam (alt), Adres (directions), ☎ +12 34567890, gratis nummer: +98 76543210, fax: +55 12344321, info@site.com. hours. checkin, checkout. content. prijs.
FredTC	Naam (alt), Adres (directions), ☎ +12 34567890, gratis nummer: +98 76543210, fax: +55 12344321, info@site.com. hours. checkin, checkout. content. prijs.
Abeona	Naam (alt), Adres (directions), ☎ +12 34567890, gratis nummer: +98 76543210, +55 12344321, info@site.com. hours. checkin, checkout. content. prijs.

Behalve een keuze voor het al dan niet toevlogen van welke pictogrammen, moet ook worden overlegd hoe e.e.a. zal worden geïmplementeerd. Allen ineens, of om de paar dagen een pictogram. Wel of niet een "mouse over" tekst bij een pictogram, die tekst wel of niet afhankelijk maken van de aanwezigheid van de "url=" om te wijzen op mogelijk actuelere info op de website, etc.

--FredTC (overleg) 20 okt 2016 08:35 (CEST)

Een "mouse over" tekst bij elk pictogram lijkt me wel een goed idee. Abeona (overleg) 24 okt 2016 13:04 (CEST)

Wikimedia Nederland Conferentie 19 november

Op zaterdag 19 november 2016 organiseert Wikimedia Nederland de jaarlijkse Wikimedia Conferentie Nederland in Utrecht. Doel van de conferentie is om deelnemers de wereld achter Wikipedia te presenteren. Wat wordt er gedaan om meer kennis vrij toegankelijk te maken? Wie doet dat? Wat betekent Wikipedia voor instellingen? Keynote-spreker Prof. dr. Maarten de Rijke is expert op het gebied van zoekmachines en taaltechnologie. Hij bespreekt hoe Wikipedia faciliteert in onderzoeken op dit gebied.

Er zijn presentaties over samenwerkingen met musea, universiteiten en er worden ervaringen gedeeld over de diverse activiteiten om de inhoud van Wikipedia en andere Wikimedia-wiki’s uit te breiden. Daar hebben we jullie hulp bij nodig. Is er iemand die het leuk zou vinden om tijdens de conferentie een korte presentatie te geven over Wikivoyage? Meer informatie over de conferentie is hier te vinden. Bij interesse (uiterlijk 1 november doorgeven) of vragen kan er contact met mij worden opgenomen via: info@wikimedia.nl SindyM3 WMNL (overleg) 20 okt 2016 15:30 (CEST)

Password reset

I apologise that this message is in English. ⧼Centralnotice-shared-help-translate⧽

We are having a problem with attackers taking over wiki accounts with privileged user rights (for example, admins, bureaucrats, oversighters, checkusers). It appears that this may be because of weak or reused passwords.

Community members are working along with members of multiple teams at the Wikimedia Foundation to address this issue.

In the meantime, we ask that everyone takes a look at the passwords they have chosen for their wiki accounts. If you know that you've chosen a weak password, or if you've chosen a password that you are using somewhere else, please change those passwords.

Select strong passwords – eight or more characters long, and containing letters, numbers, and punctuation. Joe Sutherland (overleg) / MediaWiki message delivery (overleg) 14 nov 2016 00:59 (CET)

Adding to the above section (Password reset)

Please accept my apologies - that first line should read "Help with translations!". Joe Sutherland (WMF) (talk) / MediaWiki message delivery (overleg) 14 nov 2016 01:11 (CET)

Problem user

We have a vandal at English Wikivoyage who seems active here. Suggest that you examine their edits.

Speciaal:Bijdragen/Sterlabot . Andrewssi2 (overleg) 21 nov 2016 03:05 (CET)

New way to edit wikitext

Summary: There's a new opt-in Beta Feature of a wikitext mode for the visual editor. Please go try it out.

We in the Wikimedia Foundation's Editing department are responsible for making editing better for all our editors, new and experienced alike. We've been slowly improving the visual editor based on feedback, user tests, and feature requests. However, that doesn't work for all our user needs: whether you need to edit a wikitext talk page, create a template, or fix some broken reference syntax, sometimes you need to use wikitext, and many experienced editors prefer it.

Consequently, we've planned a "wikitext mode" for the visual editor for a long time. It provides as much of the visual editor's features as possible, for those times that you need or want wikitext. It has the same user interface as the visual editor, including the same toolbar across the top with the same buttons. It provides access to the citoid service for formatting citations, integrated search options for inserting images, and the ability to add new templates in a simple dialog. Like in the visual editor, if you paste in formatted text copied from another page, then formatting (such as bolding) will automatically be converted into wikitext.

All wikis now have access to this mode as a Beta Feature. When enabled, it replaces your existing wikitext editor everywhere. If you don't like it, you can reverse this at any time by turning off the Beta Feature in your preferences. We don't want to surprise anyone, so it's strictly an opt-in-only Beta Feature. It won't switch on automatically for anyone, even if you have previously checked the box to "Automatisch de meeste bètafuncties inschakelen".

The new wikitext edit mode is based on the visual editor, so it requires JavaScript (as does the current wikitext editor). It doesn't work with gadgets that have only been designed for the older one (and vice versa), so some users will miss gadgets they find important. We're happy to work with gadget authors to help them update their code to work with both editors. We're not planning to get rid of the current main wikitext editor on desktop in the foreseeable future. We're also not going to remove the existing ability to edit plain wikitext without JavaScript. Finally, though it should go without saying, if you prefer to continue using the current wikitext editor, then you may so do.

This is an early version, and we'd love to know what you think so we can make it better. Please leave feedback about the new mode on the feedback page. You may write comments in any language. Thank you.

James Forrester (Product Manager, Editing department, Wikimedia Foundation) --14 dec 2016 20:31 (CET)

Let op: ISBN wijziging

Hi allen, In het komende jaar gaat het magisch woord ISBN verdwijnen. Tot heden was het mogelijk om achter de vier letters ISBN de 10- of 13-cijferige code van het ISBN-nummer te plaatsen. Die optie gaat komen te vervallen. In plaats daarvan zullen we dit via een sjabloon moeten gaan linken, namelijk: {{ISBN|...}} Op alle pagina's waar dit nog op de ouderwetse manier gebeurde is het ondertussen omgezet. Groetjes & fijne dagen - Romaine (overleg) 25 dec 2016 22:43 (CET)

Externe links openen in een nieuwe tab/scherm

Wanneer een link naar een externe website (hotel, museum,...) aangeklikt wordt vanuit een nl Wikivoyage-artikel opent deze momenteel in dezelfde tab, waardoor het Wikivoyage-artikel 'verdwijnt'. Lezers van Wikivoyage-artikelen worden op die manier als het ware 'weggevoerd' van Wikivoyage en keren daarna mogelijk niet meer terug. Dit is jammer voor gebruiksstatistieken en het vermindert ook de kans op nieuwe potentiële bijdragers. In verschillende andere taalversies van Wikivoyage (en, fr,...) bestaat de mogelijkheid om in de persoonlijke voorkeuren aan te duiden dat externe links moeten openen in een nieuwe tab/scherm, bij sommigen (o.a. en) is dit zelfs de standaardinstelling, ook voor niet ingelogde gebruikers. Is dit iets wat hier ook geïmplementeerd zou kunnen worden?
Een prettig eindejaar voor iedereen! Mvg, Abeona (overleg) 27 dec 2016 00:34 (CET)

Mee eens. Ik gebruik op Wikipedia die instelling al jaren. Door het ontbreken van deze instelling in Wikivoyage moet ik met de rechter muisknop werken om het in een nieuw tabblad te krijgen. Door deze routine ben ik nog we eens geneigd dit nodeloos ook in Wikipedia te doen. --FredTC (overleg) 27 dec 2016 06:42 (CET)

Nieuw welkomstbericht

Beste Wikivoyage-collega's, Ik heb het welkomstsjabloon voor nieuwe gebruikers van een lichte facelift voorzien (geïnspireerd op dat van Wikipedia). Het bericht is nu bovenaan voorzien van een titelkopje. Daarnaast wordt de gebruiker nu persoonlijk aangesproken met "Hallo <naamgebruiker>". Inhoudelijk is er praktisch niets veranderd. Tot slot wordt er automatisch een handtekening toegevoegd, zelf afsluiten met tildes is niet meer nodig. Je kan dus voortaan {{subst:Salut}} gebruiken ipv het gebruikelijke {{Welkom}} Mocht er nog iets verbeterd kunnen worden, zowel op vlak van layout als inhoudelijk (tekst) dan hoor ik het graag. Of verbeter het gerust zelf. Voor alle duidelijkheid: het oude sjabloon blijft nog steeds bruikbaar. Nog een fijn eindejaar toegewenst. Groetjes, Livenws (overleg) 27 dec 2016 22:21 (CET)

Beste Livenws, Dat ziet er prima uit, een persoonlijke toets en een beetje kleur in het welkomstbericht kan nooit kwaad :)

Misschien kan het sjabloon dan best ook toegevoegd worden op Wikivoyage:Sjabloon-index, ter vervanging van de huidige {{Welkom}}? (of als extra sjabloon ingeval iemand de huidige {{Welkom}} daar graag wil behouden).

De pagina Wikivoyage:Welkomstboodschap bevat vrees ik ook nogal wat verouderde info; voor mocht iemand (veel) zin hebben om deze wat te actualiseren...

Groetjes, Abeona (overleg) 28 dec 2016 00:37 (CET)

Op de pagina Wikivoyage:Hoe een afbeelding uploaden staat er ook nog Wikivoyage Shared, bestaat dat nog of is alles nu op Commons? Livenws (overleg) 28 dec 2016 15:42 (CET)

Alles verloopt nu via Commons (Shared dateert nog van voor de migratie van WT) - Abeona (overleg) 29 dec 2016 22:14 (CET)

Stel ik ben een nieuwe gebruiker en zie dit bericht, ik wil je bedanken en klik op bewerken. Vervolgens krijg ik een brei aan code waarvan mij de moet in de schoenen zakt. Of dat een goed idee is betwijfel ik. Een tweede aspect, dat BASEPAGENAME ongesubstitueerd gebruikt werd is in ieder geval niet een goed idee, dat heb ik al aangepast. Romaine (overleg) 28 dec 2016 11:36 (CET)

Misschien kan de visual editor in de toekomst hier antwoord op bieden? blijkbaar werkt deze nog niet voor overlegpagina's, dat wist ik niet. Alvast goede opmerkingen, bedankt daarvoor. Voor gebruikers die overkomen van een ander wikiproject kan het wel gebruikt worden zonder problemen. Misschien de keuze openlaten? Livenws (overleg) 28 dec 2016 15:42(CET)