text:
Wikivoyage:Travellers' pub/April 2007

Archive for Project:Travellers' pub of conversation started in April 2007. If you can't find the chronicle that interests you here, try Project:Travellers' pub/March 2007 or Project:Travellers' pub/May 2007 for things that may have happened earlier or later, respectively.

Phishing
I don't think Evan posted this, yet, because he was having trouble with the wifi in SJ, but don't answer any emails requesting credit card information from an email purporting to be affiliated with Wikivoyage. This is a scam and several emails were sent out to Wikia users. -- (WT-en) Sapphire • (Talk) • 21:55, 15 April 2007 (EDT)

title: Wikivoyage:Travellers' pub/April 2007


text:
Wikivoyage:Travellers' pub/Archives

Archived discussions from Travellers' pub.

Discussions that have been inactive for one month and are not likely to be pertinent to future discussions should be removed from the pub and archived according to the year the discussion started. Important and or useful discussions should be swept to the appropriate article talk page—not here.
 * Travellers' pub/2024
 * Travellers' pub/2023
 * Travellers' pub/2022
 * Travellers' pub/2021
 * Travellers' pub/2020
 * Travellers' pub/2019
 * Travellers' pub/2018
 * Travellers' pub/2017
 * Travellers' pub/2016
 * Travellers' pub/2015
 * Travellers' pub/2014
 * Travellers' pub/2013 (additional)
 * Travellers' pub/2013
 * Travellers' pub/2012
 * Travellers' pub/2011
 * Travellers' pub/2010
 * Travellers' pub/2009
 * Travellers' pub/2008
 * Travellers' pub/2007

See also: Travellers' pub archives

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Wikivoyage:Travellers' pub/Archives


text:
Wikivoyage:Travellers' pub/May 2009

Admin action needed
Somebody is having fun on our expense moving lots pages. please stop this vandal. --(WT-en) Rein N. 09:14, 2 May 2009 (EDT)

 * Blocked and reverted. Mediawiki's pretty good these days at reverting even attempted redirect loops... (WT-en) Jpatokal 09:24, 2 May 2009 (EDT)

What does Wiki Travel use to Create the add listing popup forms?
Ive searched and searched for this and cannot find what it is that is used to make the really nice looking forms that appear when you click on an "add listing" link at the side. Is this something available as an extra for mediawiki or was it coded especially for wikivoyage/Appreciate any help and im hoping that one of the admins know the answer —The preceding comment was added by 200.105.167.66 (talk • contribs).

This was written specifically for wikivoyage, primarily by me. (WT-en) KevinSours 17:45, 7 May 2009 (EDT)

Is there anywhere on Wikivoyage for odd useful hints?
for example: "if you are in Japan in Golden Week and have no reservations, try a Toyoko-inn in a town which isn't in your guidebook". [Comment added by David Fremlin.]
 * It's case-by-case. Your example would go in Japan.  (WT-en) LtPowers 08:16, 5 May 2009 (EDT)
 * Thanks, I've done that. [DHF]

Travel News
Just a reminder to everyone to please help with updating the news. You don't even have to read lots of stories, simply spending a few minutes browsing headlines...you can spot ones which might affect travelers. You should read the news to begin with...it will give you a better understanding of the world and consequently better understand where you travel. Just spend 5-10 minutes browsing some news websites and then 5-10 min. adding some stories to Travel News (copy the new items before saving, then paste them to the main page). My favorites are: BBC News, France24, & Fox News. A few others that you might want to check out are: Reuters, CNN, Al Jazeera, & RIA Novosti. —The preceding comment was added by (WT-en) AHeneen (talk • contribs).

Do &s in titles break pages?
I ask as I've noticed there is a merge candidate named Free wifi in Brighton & Hove but when I click on the link I get taken to "Free wifi in Brighton". I've tried a couple of things to get around this, and tried it in both Firefox and IE, but have found no way of getting to the real article. Is there a trick to this, or can an admin move the page, or does it need a more brute force method to get the page to be viewable? (WT-en) Nrms 23:56, 10 May 2009 (EDT)
 * Short answer is "yes", ampersands cause problems. Long answer is I remember coming across another article with the same problem but I don't remember if I was able to do anything about it.  (WT-en) LtPowers 08:02, 11 May 2009 (EDT)
 * Okay, I was able to move the page (and its talk page) to Free wifi in Brighton and Hove. I deleted the original page and its talk page.  The trick is, when you go to the delete page, the URL says " http://en.wikivoyage.org/w/index.php?action=delete&title=Free_wifi_in_Brighton ".  I had to change that to " http://en.wikivoyage.org/w/index.php?action=delete&title=Free_wifi_in_Brighton_%26_Hove ", and it worked.  Similar trick with the move operation.  (WT-en) LtPowers 08:07, 11 May 2009 (EDT)

Smartphone apps
Hi. My name's Jon Evans. I'm planning to write a Google Android and (subsequently) an iPhone app that would allow people to easily add to WikiTravel directly from their smartphones - but obviously I don't want to reinvent the proverbial wheel. Do such apps already exist?

The advantages are hopefully obvious: people will be able to write about where they are, rather than relying on memory, and will very easily be able include both on-the-spot pictures and GPS coordinates. (Though it's easier to type on a computer than a smartphone, obviously, so I'm also planning to have a "remind me to write about this place later" feature.)

I'm a software engineer turned adventure traveller turned novelist (see my web site rezendi.com for far more than you ever wanted to know about me) doing this partly for fun, partly to shake the rust off my software skills.

Thanks for any advice/help. (WT-en) Rezendi 15:14, 12 May 2009 (EDT)

 * A few apps along these lines have been built, but I'm sure they could use your help! See Project:Offline Reader Expedition. (WT-en) Jpatokal 23:36, 12 May 2009 (EDT)

Sleep template
A question was asked in the nl:pub about the Sleep template.

How can we use those templates in our wikivoyage version? --(WT-en) Rein N. 06:14, 14 May 2009 (EDT)

 * Which template? --(WT-en) Peter Talk 09:58, 14 May 2009 (EDT)
 * The one that results in: *  and so on.--(WT-en) Rein N. 10:34, 14 May 2009 (EDT)

 * You mean the clickable links at the bottom of the edit window? You can import those to :nl by copying the content from MediaWiki:Edittools to nl:MediaWiki:Edittools. --(WT-en) Peter Talk 10:47, 14 May 2009 (EDT)
 * Thanks, --(WT-en) Rein N. 11:07, 14 May 2009 (EDT)

listings: examples of de-touting and summarizing
I just realized that to de-tout a larger percent of long and flowery listings I see in my watchlist, I would find very helpful to have a reference Wikivoyage: page with a few examples for each of Eat/Sleep/Drink/Do of "before" and "after" de-touting by our gurus of de-touting and summarizing, ideally with a short explanation of why the resulting few words were decided as the best to describe the given establishment.

Anyone else interested in creating this kind of "how-to" page for would-be detouters? --(WT-en) DenisYurkin 15:18, 16 May 2009 (EDT)

 * I think that Project:Don't tout does a good job of explaining what we do and don't want, and points to other useful pages too. Getting a listing to read well and accurately describe the establishment is kind of a work of art, not so much a formula – (WT-en) cacahuate  talk 21:39, 16 May 2009 (EDT)

 * I think an example or two could be helpful. Business owners/promoters often really do seem clueless as to how to write a proper hotel description for a travel guide, even after reading the policy. When they do censor themselves, the descriptions wind up just as useless. I'll try to save some "good ones" next time I clean up after my (WT-en) friends. --(WT-en) Peter Talk 22:00, 16 May 2009 (EDT)

 * Thanks, Peter! Overall, I initially meant a guide to de-touting janitors like myself, but now I agree, for business owners it could be helpful as well. --(WT-en) DenisYurkin 03:42, 17 May 2009 (EDT)

 * There are a bunch of "detouts" in this dif . Perhaps one of them might be a good example? I'll try to look for more. --(WT-en) Peter Talk 19:13, 24 May 2009 (EDT)

 * Here's another . --(WT-en) Peter Talk 04:57, 8 June 2009 (EDT)

 * To start with, I copied "before" and "after" into this page: User:(WT-en) DenisYurkin/Detouting. What we need now is:
 * remove non-changed listing fields (like phone numbers and business hours)
 * organize it into a table(?) to make comparing easier
 * (?) provide an explanation for most arguable removals/rewritings of text (where it may be non-obvious for a novice editor reading the page)
 * more ideas?
 * --(WT-en) DenisYurkin 08:43, 22 July 2009 (EDT)

Sharing pictures for use on Wikivoyage
I've been making a few edits to the Wikivoyage guide for Kyoto and I observed that the "Central Kyoto" section under "See" could use a few more pictures. I have some photographs that might fit the bill, but I'm a little protective of my personal travel album so I'm unwilling to release any of them in their original form under Wikivoyage's prescribed licences. On the other hand, I'd be glad to release smaller, substantially resized versions (say, 800x600 or less) under the prescribed licences or even turn them loose into the public domain, provided I can keep full copyright over the original versions.

So here's the question: if I release reduced-size versions of my photographs under a CC-BY-SA compatible licence (or into the public domain) for use on Wikivoyage - and with the full understanding that anyone can do anything with them in accordance with those licences - will I retain full copyright over the originals?

Many thanks. --(WT-en) Diego de Manila 02:34, 21 May 2009 (EDT)

 * If you are wary of reuse, i'd encourage you NOT to release anything to the public domain, but yes to other question - you only grant permission to reuse the said image, and you can clarify under the license section that you are only granting permission to reuse the low res version. There is an example here: http://shared.wikivoyage.org/wiki/Image:Nenets_reindeer_sledge.jpg#Licensing

 * And thanks for info on my Kyoto Railway map btw, I'll try to get that updated soon. --(WT-en) Stefan (sertmann) Talk 05:46, 21 May 2009 (EDT)

 * Thanks for the advice and the very helpful example. I'll think twice about releasing anything into the PD, but the prescribed licences now look like a viable option. --(WT-en) Diego de Manila 08:29, 21 May 2009 (EDT)

 * I'd still recommend you release the full-sized pictures (at least 3000x2000 or equiv), since 800x600 is too small to be used in print, and we'll just have to dike 'em out once the day comes for Wikivoyage Press to create its Kyoto guide.

 * FWIW, I used to think the same way you did, and only uploaded dinky little 800x600 versions here. Then I realized there was no reason not to share (is your pic worth more gathering dust on a hard disk, or being shared with the whole world via WT?), CC-licensed my entire photo collection some 10+ years in the making, and am slowly and painfully upgrading my old pics here as I stumble into them. (WT-en) Jpatokal 09:18, 21 May 2009 (EDT)

 * I checked out your pictures and noticed it says copyright at the bottom and clicking on the "copyright" says: "All text, pictures and code contained within these pages and their subsidiary servers are copyright 1996-2003 Jani Patokallio. Personal use is generally OK but credit me for it, anything else requires permission.  Link freely but only to addresses under iki.fi (see the tech notes for an explanation), otherwise the links can and will be broken." That doesn't say/resemble CC. (WT-en) AHeneen 20:55, 21 May 2009 (EDT)

Spambots
Going through the recent changes and noticing that 9 of 10 new users are spambots, could we/IB add a captcha to the process of creating a new account? (WT-en) AHeneen 20:26, 21 May 2009 (EDT)

 * Good idea. Should be easy to do using either of these: (WT-en) Jpatokal 03:22, 22 May 2009 (EDT)
 * http://www.mediawiki.org/wiki/Extension:ConfirmEdit
 * http://recaptcha.net/plugins/mediawiki/

 * Man, those bots are out of control. I've mailed IB about this. (WT-en) Jpatokal 06:19, 22 May 2009 (EDT)
 * I could see having a captcha for account creation, or if things got worse and worse maybe even for edits from unregistered accounts, but I'd hate to make the average registered user go through that for every single edit. (WT-en) Texugo 00:42, 10 June 2009 (EDT)
 * My intention was simply to add a captcha for new accounts. (WT-en) AHeneen 15:19, 10 June 2009 (EDT)

Wikivoyage logout
Is it just me or does Wikivoyage sometimes log you out, even right after an edit? (WT-en) edmontonenthusiast [ee] .T.A.L.K. 17:14, 22 May 2009 (EDT).
 * Isn't just you. Happens for me too. Weird. — (WT-en) Ravikiran 03:52, 10 June 2009 (EDT)

Pointer to discussion
I posted a question last week at Project:Article templates. Would appreciate any input. (WT-en) LtPowers 10:21, 23 May 2009 (EDT)

Question
I know it's going to sound really weird but I think the site is a little more complicated than it looks. I have a really important question and have been reading every page I could. Finally decied to ask, and it's probably because of my poor tech skill, but could anybody please tell me how to post a question? Not by editing another one that already exists, but creating a new topic. It says at the bottom of the page, but I cannot find it. 81.214.7.120 06:26, 26 May 2009 (EDT)Banu81.214.7.120 06:26, 26 May 2009 (EDT)
 * Your best bet is to go to the top of a discussion page and click the "+" tab, right between "edit" and "history". =)  (WT-en) LtPowers 09:17, 26 May 2009 (EDT)

Wikivoyage maps question help
Hi there! I'm trying to make a map similar to Pittsburgh's road map by PerryPlanet for Portland (OR) but I have come to an obstacle. Maybe it's just a silly issue but i am very new to the program. Anyways Portland has an interesting river geography, with islands and everything. So I am using the Wikivoyage template and tracing from OpenStreetMaps, and using water. Well the water has a darker layer around the edges, like turquoise-teal, which is fine, but I'm going around an island, and when they meet back up they're two different things now I suppose and there is a big line in what would be the middle of the river and it looks retarded. How do I fix this? (WT-en) edmontonenthusiast [ee] .T.A.L.K. 15:17, 26 May 2009 (EDT).

Why is this website written as if every tourist were white?
It is. You can't deny this; take a look at Germany and the section about Turks/Arabs. Also, I didn't know Russians were non-white, that's news to me (and offensive).

Not only this, my problem with this site is that none of it is sourced. Unlike Wikipedia, there seems to be no sourcing whatsoever. This is potentially critically important on a travel site where people may have printed off a document. One bit of vandalism to a route number and it could cause serious problems to people.--(WT-en) Clyde Cash 18:33, 1 May 2009 (EDT)
 * I am a complete mixture, I look kinda like Tiger Woods if I was to give an example of what I was like racially but taller, broader and more muscular; I was born to an African American-Mexican American father and a Russian-American mother and I have lived in Scotland for 8 years, and my girlfriend is British Chinese. Please don't assume things. I also have Asperger syndrome.--(WT-en) Clyde Cash 18:41, 1 May 2009 (EDT)

 * Well, since I can't deny this, I will have trouble responding to your point. But this website is actually written by some 50,000 people, so it must just be that we've succumbed to group think on a very large scale. More to the point though, if you see something that you think can be improved, plunge forward and fix it yourself!

 * Regarding sourcing, have you ever seen a travel guide that provided footnotes? We try to keep things fair, and the "proofing" mechanism that wikis provide (anyone can correct any error) is generally a lot more foolproof than trusting some drug dealer's second hand information.  --(WT-en) Peter Talk 18:57, 1 May 2009 (EDT)

 * The Stay Safe section of the Germany article certainly could use some editing. Would you be interested in giving it a shot, Clyde?  (WT-en) LtPowers 19:03, 1 May 2009 (EDT)

 * Lest anyone be confused, Clyde is engaged in a silly bit of provocation that doesn't really warrant a response unless you're really bored — and in that event, stimulating alternatives such as alphabetizing your socks might still be preferable. (WT-en) Gorilla Jones 19:05, 1 May 2009 (EDT)

 * Couple comments to this. I'm trying to familiarize myself with Wikivoyage. On the Buenos Aires page I thought there were sections that were irresponsibly written and I also thought sourcing might police the situation, though reading the Style differences note, I agree with the approach. I don't think this comment is not worth (limited) discussion though. I'm not sure how differences in reporting will play themselves out. As for me, I have taken (WT-en) LtPowers invitation to heart and tried to fix inconsistencies, contradictions and so on. Hopefully my efforts will be appreciated rather than annoy.--(WT-en) EKMSID 02:12, 4 July 2009 (EDT)

Well, I can't say to speak for the whole of Germany, I've been there several times. I've also been to Romania and Bulgaria several times, and Finland as well. The problem is with sourcing. Wikipedia relies on accurate sources for every statement. This site, it has NONE of that. None whatsoever! It's bullshit if you believe people should go printing off articles and some person entering bullshit could make people change their route I mean WTF? That shit is not on.-(WT-en) Clyde Cash 19:40, 1 May 2009 (EDT)
 * We are not Wikipedia. Check out Project:Welcome, Wikipedians, which explains how we are different.  If you don't trust our travel guides without references, don't use them.  Plenty of other people do.  (WT-en) LtPowers 21:45, 1 May 2009 (EDT)

 * But seriously. Please show me a travel guide that lists sources. And what sources would we list anyway? Have you actually thought about it? Should we list the local phone book as a source for each hotel listing, Rand McNally for every set of directions we give? (WT-en) Texugo 01:15, 1 August 2009 (EDT)
 * Or we could all just stop beating around the bush and say to clyde that if you don't like the way things are written here and you do not want to plunge forward and make changes, then maybe you should leave and find a different website. Simple. (WT-en) Joshuadrooney 05:25, 18 August 2009 (EDT)
 * Sorry, but I just read this and I fail to see how one could include sources in a travel guide? Eh, what are people supposed to do? The street scape of Prague is a must see... please refer to this for proof? I mean, that's a nonsense comment. (WT-en) LikeThatWillHappen 21:28, 10 October 2009 (GMT)

My problem is that nearly every article assumes that the reader will not like the local cuisine because it is too spicy/salty/sweet/ethnic for them and goes on to recommend a whole bunch of "western" fast food chains. Even for culinary meccas such as Hong Kong, Tokyo and Singapore. I love how Lonely Planet's guide to Beijing says, "There's a lot of Starbucks, we'll leave it up to you to figure out where they are." (WT-en) Rickvaughn 22:24, 23 October 2009 (CST)

 * In general, I agree, but there are exceptions. I live in China and mostly eat Chinese food. When I travel to Yangshuo, I want the guide to tell me where the good Western food is. In Hong Kong, I'm looking for the Indian places, since there are none where I live. If I visit Beijing, I'd like to know where to find good coffee. (For me, Starbucks does not qualify.) Also, there are places where Western fast food may be a good option, see the last paragraph of China for example. (WT-en) Pashley 00:01, 24 October 2009 (EDT)

 * Actually, Singapore doesn't have a single "western" fast food chain listed. It has a couple of local chains offering local food, and it does have a bunch of good Western restaurants, because most travellers start yearning for familiar food after a few solid weeks of nasi goreng or pad thai...

 * I do agree, though, that Wikivoyage's food coverage is generally pretty weak, and I make a point of trying to improve it whenever I can. (WT-en) Jpatokal 09:43, 24 October 2009 (EDT)

 * The reason WikiTravel is good is because it contains LOADS of information and people aren't scared to add their anecdotal information to it. If a page says something like "The train between Algiers and Oran is fast but use 1st class because 2nd class is overcrowded" I'm glad that they've told me the train is fast and second class is overcrowded in some peoples opinions: if I don't mind overcrowded trains, I will use 2nd class anyway, but its interesting to read someone's opinion. The same with the food, its nice to hear someones opinion and very informative, but at the end of the day everyone has different standards, and this is not a problem. If you think this website is too 'posh' for you, read it with a pinch of salt! There's a wealth of great information to be inferred from this site by ANYONE of any social background. (WT-en) Unnachamois 12:21, 17 February 2010 (EST)

title: Wikivoyage:Travellers' pub/May 2009


text:
Wikivoyage:Travellers' pub archives

The Travellers' pub archives show where older discussions from the Travellers' pub have been moved to.

 * AA → Project:Where you can stick it
 * Abbreviated redirects for common policies → Project:Shortcuts
 * about Wikivoyage → Project:About
 * A conversation on spell-check → (in substance) to Project:contributor_tools.
 * Active Contributors → Project:Multilingual statistics
 * A gentle reminder → Project:Ways to help Wikivoyage
 * Airport Codes? → Project:Article templates
 * Alternative license for photos for user pages? → Project:Copyleft
 * Anecdotes or interview subjects wanted for story on Wikivoyage → Project:Press coverage
 * Appropriate to have sleep section in country page? → Project:Country article template
 * A Question (hotel chains etc) → User talk:(WT-en) SLCpunk
 * Arabic and Hindi Wikivoyage → Project:How to start a new language version
 * Article text formatting → Project:Feature requests
 * Article with official name containing a / → Project:Article naming conventions
 * Automated pretty weather reports → Project:Feature requests
 * Awards and mentions → Project:Awards and mentions
 * A way to edit offline → Project:Offline Reader Expedition
 * Azerbaijani Wikivoyage Language Expedition → wts:Talk:Language Expeditions
 * Bots and scripts → Project:Script nominations
 * Bread crumb navigation → Project:Feature requests
 * Breadcrumbs → Project:Milestones
 * Budget/mid range/ splurge? → Project:Accommodation listings
 * Can't get to External Links page → Project:Fixed bugs
 * Car rental company listings → Project:Where you can stick it
 * Cases of repeated vandalism → Project:Vandalism in progress
 * Categories extension wanted → Project:Categories
 * Categories → Project:Categories
 * Cheating → Project:Neutral point of view
 * Checklist for Wikivoyagers on the road? → Project:Ways to help Wikivoyage
 * Chimney Rock spamming → Project:User email help
 * Chinese Language Version → Project:Chinese Wikivoyage Expedition
 * Cities along highways → Project:Itineraries
 * City Centres(sic) and Districts → Project:Where you can stick it
 * City Theme Pages → Project:Other ways of seeing travel
 * Claiming my input → Project:Copyleft
 * Climate and weather → Project:Climate Expedition
 * Collaboration of the week? → Project:Articles needing attention
 * Comments → Talk:Akumal
 * Commons → Project:Copyleft
 * Compliant external use of Wikivoyage → Project:How to re-use Wikivoyage guides
 * Consistency between language versions → Project:Language versions
 * Continent pages → Project:Continent article template
 * Convention and Visitors Bureau → Project:Tourist Bureau Expedition
 * Copyright and buildings/art → Project:Image policy
 * Copyrighted Geo data → Project:Copyleft
 * Copyscape → Project:Copyleft
 * Countries vs. Sovereign States → Talk:Western Sahara
 * Country/region oversight → Project:Docents
 * Creative Commons 3.0 → Project:Copyleft
 * Cuisine pages → Project:What is an article?
 * Data Dumps? → Project:How to re-use Wikivoyage guides
 * Dating information, keeping current → Project:RDF Expedition
 * David's planning a trip → User talk:(WT-en) DavidCary
 * Dedicated pages for hotels and restaurants → Project:Article templates
 * Deletion of Hospitality Club related page → Project:Cooperating with Hospitality Club
 * Depth and the templates → Project:Geographical hierarchy
 * Design of Login page → Project:Feature requests
 * Destination of the month → Talk:Main Page
 * Disambiguating famous places → Project:Disambiguation pages
 * Disambiguation lists → Project:Disambiguation pages
 * Disambiguation pages considered useful → Project:Disambiguation pages
 * Disclaimers? → Project:Terms of use
 * "Discover" page created for Wikivoyagetrivia → Project:Discover
 * Discussion of city article templates → Project:City article templates
 * Discussion of naming conventions → Project:Article naming conventions
 * Discussion page → Project:FAQ
 * distribute Star articles in a printed form? → Project:Star articles
 * Doubts about plagiarism → Project:Copyleft
 * Drink/Locale Beer → Project:Where you can stick it
 * Dump available ? → Project:Offline Reader Expedition
 * Dutch Log in → Project:Language versions of Wikivoyage
 * Dutch Wikivoyage Expedition → Project:Dutch Wikivoyage Expedition
 * Dutch Wikivoyage → Project:Dutch Wikivoyage Expedition
 * Edirectory.com → Project:Copyright details
 * Editing problems → Project:Bug reports
 * E-mail? → Project:Bug reports 1.4.7/Fixed
 * Embassy and consulat → Project:Where you can stick it
 * English Teachers' Wiki → Project:List of related projects
 * Equivalent of wikipedia's reference desk → Project:Help
 * Esperanto version → Project:How to start a new language version
 * Europe to India by Road Expedition? → Talk:Istanbul to New Delhi over land
 * Events → Project:article templates
 * Events → Project:Where you can stick it
 * Exchange rate suggestion → Project:Currency
 * External links discussion → Project:External links
 * External Links - Primary / Secondary Links → Project:External links/What to link to
 * External links → Project:External links/What to link to
 * Factbookectomy → Project:Milestones
 * Failed Sleep-a-thon attempt → Project:Accommodation listings
 * Feature requests → Project:Feature requests
 * First edit, feedback appreciated → User talk:(WT-en) Paul.
 * Formating multiple picture → User talk:(WT-en) JensANDMarian
 * For those of us who are visual learners → Project:Listings
 * GayGuide in Template → Project:Information for gay and lesbian travellers
 * General feature suggestions → Project:Feature requests
 * General ramble and a few questions → Project:Tone
 * German go-between report → Project:Go-between reports
 * German Wikivoyage → Project:German Wikivoyage Expedition
 * Go-between reports → Project:Go-between reports
 * Goodby Factbook → Project:How to de-factbook a country page
 * Google Blog Search → Project:Awards and mentions
 * GPS and other geodata → Project:Geographical data and metadata
 * GPS locations and waypoints → Project:Geographical data and metadata
 * Graffiti wall → Project:Graffiti wall
 * Great source of maps → Project:Mapmaking Expedition
 * Header sizes → Project:Bug reports
 * Hello from (WT-en) Thomas Jefferson → Talk:Bitburg
 * Help regarding the Spam Filter → Project:Local spam blacklist
 * Highway routes → Project:Where you can stick it
 * Hitchhiking → Project:Where you can stick it
 * Hotel Classification → Wikivoyage_talk:Accommodation_listings
 * Hotel Directories → Project:Accommodation listings
 * How should bodies of water be classified? → Project:Bodies of water
 * How to create a new Disambiguation page → Project:Disambiguation pages
 * Huge Citys and Districts - Where do listings go? → Project:Huge city article template
 * Hungarians wanted for the Hungarian Wikivoyage Expedition
 * Icons for kid-friendly attractions → Project:Article templates
 * I don't stay logged in! → Project:Bug reports 1.4.3/Fixed
 * Illegal activities policy? → Project:Illegal activities policy
 * Image bank? → Project:Feature requests
 * Image map → Project:Wiki markup
 * IMAGES → Project:Collaboration of the week
 * Images → Project:Image policy
 * Image thumbs → Project:Feature requests
 * Inactive language versions → Project:Language versions of Wikivoyage
 * Indonesia edits → Talk:Indonesia
 * Internet café → Talk:Accessing email
 * IsIn in other languages → Template_talk:IsIn
 * Is there any way to get an RSS feed of a particular article? → Project:RSS feed
 * Is this still a community? → Project:Internet Brands
 * Jaipur story discussion → Talk:Jaipur
 * Jargon is a barrier to newbies → Project:Jargon
 * Javascript errors? → wts:WtTech:Javascript error (old)
 * Kicking a* and taking names → Wikivoyage_talk:Local_spam_blacklist
 * Language discussion → Project:Language version policy
 * Lessig Blog → Project:Wikivoyage logbook/Feb 2004
 * let's help to find an original author → Project:Requests for comment
 * Link colors → Project:Bug reports
 * Linking from one section to another → Project:Wiki markup
 * Linking to downloads → Project:External links
 * Links from Wikipedia → Project:Cooperating with Wikipedia
 * Lists versus recommendations → Project:Ways to promote Wikivoyage
 * LocalExpertiseWanted template → Project:Articles needing attention
 * Local interest infoboxes → Project:Information boxes
 * Logo/Icon → Project:Project
 * Log out → Project:Bug reports 1.4.7/Fixed
 * Log out times → wts:WtTech:Random logouts
 * Losing the Stub message → Project:Stub articles or Project:Stubs needing attention
 * Marco Polo → Talk:On the trail of Marco Polo
 * Mav's images → Project:Image resources
 * Maxtravelz.com → Wikivoyage_talk:Non-compliant_redistribution
 * Measurements → Project:Measurements
 * MediaWiki Templates → Project:Listings
 * Meetups → Project:Meetups
 * Men, beware those seed-pods! → Project:Tone
 * Merchandise → Project:Ways to promote Wikivoyage
 * Mexican national parks → Talk:Mexico
 * Mexico Accomodation → Talk:Mexico
 * Microformats → Project:Microformats
 * Milestones reached → Project:Milestones
 * More than one way to skin a Wikivoyage → Project:Interface issues
 * Most expensive travel option we have → Project:Discover
 * Movie source? → Project:Where you can stick it
 * Movies → Project:Image policy
 * Moving images to Wikivoyage Shared? → Project:Feature requests
 * Moving Template:hasDocent to Sweedish Wikivoyage → wts:WtTech:HasDocent template - translation, etc
 * Mozilla search plugin → Project:Software tools
 * National Park Service Copyright Notice → Project:Copyleft
 * Navigation bars → Project:Navigation bars
 * New article type suggestion → Project:Article templates
 * New Creative Commons license version → Project:Copyleft
 * New Expedition Idea → Project:Expeditions
 * New Itineraries → Project:Itineraries
 * Newspaper Archives → Project:External links
 * New years wishes → Project:Feature requests
 * Next stop option → Project:Itineraries
 * Non-commercial image license → Project:Image policy
 * Non-Destinations → Project:What is an article?
 * Non-goals: Yellow pages → Project:Goals and non-goals
 * Not a Travelogue → Project:Where you can stick it
 * Not just a Web site → Project:goals and non-goals
 * tags → Project:Listings
 * Nth largest city in the world / Nth largest city in the US → Project:World cities with 100K population or more
 * Numerous things... → Project:Where you can stick it
 * Off-highway vehicles → Talk:Off-road vehicles in California
 * Offline Version → Project:Offline Reader Expedition
 * OpenID Login problems → SHARED:Talk:Technical requests
 * "Open Maps?" → Project:Mapmaking Expedition
 * Oregon Contributor Activity → Talk:Oregon
 * other complementary web sites → Project:List of related projects
 * Other wikis → Project:article templates
 * Pages by contributor → Project:User page help
 * Paper travel guides → Talk:Paper_travel_guides
 * Phillipine Passport Certification Transwiki → Project:Where you can stick it
 * Phone number spam → Project:Vandalism in progress
 * Places to do $WHATEVER → Talk:Travel topics
 * Policy about advertising → Project:Don't tout
 * Portuguese Wikivoyage → Project:Portuguese Wikivoyage Expedition
 * Potential Map ideas... → Project:Mapmaking Expedition
 * Preparing for exponential growth → Project:Multilingual statistics
 * Prices → Project:Currency
 * Printable TravelGuides → Project:How to re-use Wikivoyage guides
 * Problem displaying location hierarchy after a redirect? → wts:WtTech:Breadcrumb navigation does not display on redirected pages
 * Problem with West Midlands, advice appreciated → Talk:West Midlands (region)
 * Proposals to change Washington (state) geographic hierarchy → Talk:Washington (state)
 * Proposed Writers' Expedition → Project:Expeditions
 * Protecting "Archive" pages → Project:Protected page policy
 * Psychology tips → Project:Slippery slopes
 * Public images licensing → Project:Image policy
 * Putting wikivoyage on ipods - lonelyipod.com → Wikivoyage_Talk:Offline Reader Expedition
 * Quickbars on states? → Template talk:Quickbar
 * Quickbar templates - request for comment → Template talk:Quickbar
 * Random chatter → Project:What is an article?
 * Random quesrion → User talk:(WT-en) Sapphire
 * Raw signature → Project:Bug reports
 * RDF Expedition → Project:RDF Expedition
 * Recent changes links → Project:Feature requests
 * Recommended / further reading / destination travel books and publications → Project:Where you can stick it
 * Related Site Project: Wikiscuba → Project:List of related projects
 * Requests for Quickbar-ectomies → Template talk:Quickbar
 * Resources for maps → Project:Mapmaking Expedition
 * Restaurant Classification → Project:Restaurant listings
 * Retaining users → Project:Project
 * Reversion confusion question → Project:How to revert a page
 * Road designations → Talk:United States of America
 * Rockies discussion → Talk:Rockies
 * Romanian Wikivoyage → Project:Romanian Wikivoyage
 * RSS feeds of page-histories → Project:RSS feed
 * RSS Feeds → Project:Bug reports
 * Russia is NOT in Eastern Europe!!! → Project:Breadcrumb navigation
 * Salzburg pictures → Talk:Salzburg (city)
 * Scam Article? → Talk:First and business class discounters
 * Search plugin for Internet Explorer 7 / Firefox 2 → Project:Software tools
 * Seattle wiki → Talk:Seattle
 * See vs Do → Project:Where you can stick it
 * Selected trains → Project:Where you can stick it
 * Shared help → wts:Project talk:Travellers' pub
 * Sharing content with World66 → Project:List of related projects
 * Shotgun Approach To Sleep → Project:Accommodation listings
 * Should I worry about this? → wts:WtTech:Remove page size warning
 * Show changes → Project:Technical details
 * Similar projects → Project:Fellow Traveller Expedition
 * Site Guides → Project:Attraction listings
 * Sites of interest as opposed to the city/region/etc. focus Wikivoyage has so far → Project:Where you can stick it
 * Slate article → Project:Press coverage
 * "Sleep" link-spamming → Project:Accommodation listings
 * Some ideas → Project:Help
 * Spam filter issues → Project:Spam filter
 * Spam links → Project:Local spam blacklist
 * Special:Contributions/63.108.178.2 → Project:External links
 * Stars in the making → Project:Star articles
 * Staying signed in → SHARED:Talk:Technical requests
 * Still on docents → Project:Docents
 * Article Request for comment Peer review → Project:Requests for comment
 * Substubs and skeletons → Project:Stub articles
 * Suggestion: Article Improvment Drive → Project:Collaboration of the week
 * Suggestion: New field for nearby locations → Project:Article templates
 * Swedish WikiTravel inactive? → Project:Language versions of Wikivoyage
 * Taipei and everywhere else in Asia → Talk:Asia
 * Telephones → Talk:Telephone service for travel
 * Template for a very small country → Project:Country article template
 * Templates for User Pages → Project:Using Mediawiki templates
 * Template:Unsigned → Template talk:Unsigned
 * Terms of Service? → Project:Terms of use
 * Text highlighting problems → Project:Bug reports
 * Thank you for your cordial and helpful welcome → Project:Welcome, newcomers
 * Theft → Project:Non-compliant redistribution
 * Theft the Second → Project:Non-compliant redistribution
 * The work of → Project:Copyleft
 * This place sucks → Project:Negative recommendations
 * Thumbnail generation broken → Project:Bug reports 1.3.5
 * Timezone in Quickbar → Project:Dates and times
 * Time zones → Project:Where you can stick it
 * TMI on Airplane Routes → Project:Where you can stick it
 * TOC placement template → wts:Tech talk:Table of contents makes too much whitespace
 * ToDo for articles → Project:Requests for comment
 * Top URLs → Project:Multilingual statistics
 * Tours policy? → Project:Activity listings
 * Towns or Cities, again → Project:Region article template
 * Towns or Cities → Project:Region article template
 * trains in Europe, for example → User talk:(WT-en) TedErnst
 * Translating pages → Project:Feature requests
 * Travel agencies → Project:Where you can stick it
 * Travel by calendar → Project:Other ways of seeing travel
 * Travel companies → Project:Where you can stick it
 * Traveling by Bike → Talk:Denmark
 * Trimming, Pastry, Ice Cream → Project:Where you can stick it
 * TripAdvisor adds wiki → Project:List of related projects
 * Turin, Italy → Project:Collaboration of the week
 * Two Questions → Project:Hebrew Wikivoyage Expedition
 * Two-step confirm process for adding a page to your Watchlist → Project:Watchlist help
 * Unannotated Lists → Talk:Jakarta
 * Uniting Wikivoyage with Wikipedia, Wikiquote, Wikisource, Wiktionary and Wikibooks? → Project:Cooperating with Wikipedia
 * University of Place → Project:Attraction listings
 * Unused images → Project:Ways to help Wikivoyage
 * USA National Parks → Talk:United States National Parks
 * Use of the admin "rollback" functionality → Project:Administrators
 * Using images from commons.wikimedia.org → Project:Image policy
 * Vacation Travel Guides Content Approval → Project:External links
 * Valid values for government type → Project:Manual of style
 * Vandal → Project:Vandalism in progress
 * Vertical whitespace → See discussion on line breaks between list items in Project:bug reports
 * Visa requirements → Project:country article template
 * War zone safety → Talk:War zone safety
 * Watching all the articles within a region → Project:Feature requests
 * We are Time's "Person of the Year" → Project:Wiki
 * Weather → Project:article templates
 * Webby → Project:Awards
 * Weird modern religious structures → Talk:Travel topics
 * We need suggested itineraries → Wikivoyage_talk:Article_templates
 * West page → Project:Article naming conventions
 * What about a new logo? → Project:Logo contest
 * What is an itinerary? → Project:Itinerary article template
 * What's happening with Romanian Wikivoyage? → Project:Romanian Wikivoyage Expedition
 * When is a Country a Country? → Project:Geographical hierarchy
 * Where do I find the Wikivoyage logotypes? → Image talk:Treatment.svg
 * Where to put Marco Polo → Talk:On the trail of Marco Polo
 * Where to stick Annual events → Project:Where you can stick it
 * Why is the Wikivoyage logo T capitalized? → Project:Logo contest
 * Wikimapia → Project:List of related projects
 * Wikipedia articles → Project:Cooperating with Wikipedia
 * Wikipedia fork, Citizendium → Project:List of related projects
 * Wikipedia → Project:External links
 * Wiki software upgrade → Project:Technical details
 * WikiSpam → Project:How to handle unwanted edits
 * Wikivoyage and Wikimedia → Project:Business of Wikivoyage
 * Wikivoyage and Wikipedia → Project:Cooperation
 * Wikivoyage book → Project:How to re-use Wikivoyage guides
 * Wikivoyage Code? → Project:Technical details
 * Wikivoyage dating service? → Project:Non-compliant redistribution
 * Wikivoyage Expedition? Travellers' Tips? - Health → Talk:Travel topics
 * Wikivoyage get-together → Wikivoyage Shared:Get-together - Be there or be square
 * Wikivoyage logo → Image talk:Treatment.svg
 * Wikivoyage on IRC → Project:IRC channel
 * Wikivoyage on PDA → Project:Offline Reader Expedition
 * Wikivoyage ownership announcement →Project:Internet Brands
 * wiki.travel → Project:Technical details
 * Women Wikivoyagers → Project:Gender issues in Wikivoyage participation
 * World66 → Project:List of related projects
 * World Cup 2006 → Talk:World Cup 2006
 * World wide emergency numbers → Project:External links
 * "www.wikivoyage.net"??? → Project:Mirrors
 * WYSIWYG → Project:Feature requests
 * Yahoo! Directory → Project:Logbook
 * Your RSS feed is on Planet Wiki now → Project:RSS feed

de:Project:Stammtisch/Archiv

title: Wikivoyage:Travellers' pub archives


text:
Wikivoyage:Travel topic status

This page describes the criteria for determining the article status of travel topic articles.

Insert the Wiki Markup listed below in order to display a Wikivoyage Topic's maturity status:

title: Wikivoyage:Travel topic status


text:
Wikivoyage:Turtle RDF

Turtle is a plain-text RDF representation, based on NotationThree with only the RDF-ish stuff left in. Since it leaves out a lot of the markup accounting required for RDF/XML, it's a pleasant format for learning RDF and making simple RDF documents. Turtle is nicely supported by tools like Raptor and RAP (RDF API for PHP), among others.

This document gives initial instructions for creating a FOAF document using Turtle.

Lightning intro to Turtle
A Turtle document is a collection of RDF-triples. Each triple has the format:

.

Each statement ends with a period, and each element in the triple is an URI (except the, which can be a bit of text like "string" or a number like 134). For example, to say that a person is interested in FOAF, we could use the triple:

  .

Here, the URL for the FOAF home page stands in for the idea "FOAF", and the person's email address stands for the person. We do that a lot with RDF -- letting URLs stand for "offline" or abstract concepts. We use the FOAF vocabulary to describe being interested in someone. Most of the effort of RDF is making up URLs that have an agreed-upon meaning like "This URI means 'is interested in'". If the person is also interested in Turtle, we can say:

  .

This is pretty much all you need to know to write Turtle, but there are a lot of "shortcuts" that can make                                      your documents shorter and more readable.

Using prefixes
Using the full URI is a kind of unreadable mess. With Turtle, we can define a namespace prefix so that we don't have to write the same long URI prefixes all the time. A prefix definition looks like this:

@prefix pref:.

For example, for FOAF elements, we can use a prefix definition like this:

@prefix foaf: .

Then we can use the topics described above like this:

@prefix foaf: .

 foaf:interest .  foaf:interest .

We can also define a default namespace prefix, in cases where we use the same namespace prefix over and over. To do this, we use the same format without a substitution string:

@prefix :.

Often the "main" namespace for a Turtle document is given a default namespace. If we're working on a FOAF document, for example, we might want to make the FOAF namespace the default one:

@prefix : .  :interest .  :interest <http://www.ilrt.bris.ac.uk/discovery/2004/01/turtle/>.

Commas
When we make two or more statements with the same subject and relationship, we can make the document shorter and more readable by combining the statements and separating the objects by one or more commas. Our topic example above could be written:

@prefix : <http://xmlns.com/foaf/0.1/>. <mailto:person@example.net> :interest <http://www.foaf-project.org/>, <http://www.ilrt.bris.ac.uk/discovery/2004/01/turtle/>.

Note that the meaning is exactly the same; just the number of characters typed is different.

Semicolons
If you have the same subject in more than one statement, but different relationships, you can combine them and separate the relationship + object parts with a semicolon. For example, if we wanted to say that our person's name is "Anne Example-Person", we'd write:

@prefix : <http://xmlns.com/foaf/0.1/>.

<mailto:person@example.net> :name "Anne Example-Person".

We could combine this with our document about Anne's interests to make:

@prefix : <http://xmlns.com/foaf/0.1/>. <mailto:person@example.net> :name "Anne Example-Person" ; :interest <http://www.foaf-project.org/>, <http://www.ilrt.bris.ac.uk/discovery/2004/01/turtle/>.

Note that there's still a period at the end, eventually. The newline isn't particularly necessary, but it makes the document a little more readable.

Types
There's a special relationship between a thing and a category of things, called type (http://www.w3.org/1999/02/22-rdf-syntax-ns#type). If we want to say that Anne is a person, we can write it like this:

@prefix : <http://xmlns.com/foaf/0.1/>. @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>. <mailto:person@example.net> rdf:type :Person.

Because this is such a fundamental relationship, Turtle has a special keyword a, to replace the type relationship:

@prefix : <http://xmlns.com/foaf/0.1/>. <mailto:person@example.net> a :Person.

Our full FOAF document for Anne becomes:

@prefix : <http://xmlns.com/foaf/0.1/>. <mailto:person@example.net> a :Person ; :name "Anne Example-Person" ; :interest <http://www.foaf-project.org/>, <http://www.ilrt.bris.ac.uk/discovery/2004/01/turtle/>.

The advantage here is that you can kind of read this out loud to yourself, and it will make some semblance of sense (in English, at least).

 * This URI represents a person; her name is Anne Example-Person, and her interests are FOAF and Turtle.

Anonymous things
One nice part of FOAF is that you can describe relationships between people. For example, Anne may know a person named Uther Example, who has email address <uther@example.org>. We can write this as:

@prefix : <http://xmlns.com/foaf/0.1/>. <mailto:person@example.net> :knows <mailto:uther@example.org>. <mailto:uther@example.org> a :Person; :name "Uther Example".

When you don't want to define an URL for someone, though, you can use an anonymous object in the object area. Anonymous objects are defined with square brackets "[]" around one or more relationship-object pairs, defining the object, separated by semicolons. You can define all kinds of relationships that that object is the subject of. If we don't want to bother with Uther's email address (or we don't know it), we can just write:

@prefix : <http://xmlns.com/foaf/0.1/>. <mailto:person@example.net> :knows [ a :Person ; :name "Uther Example" ].

This also reads pretty nicely in English: Anne knows a person named "Uther Example".

Using other schemas
A big part of FOAF is creating and using other, extended schemas. With Turtle, we just define a prefix for the other schema, and use the elements with the given prefix. For example, if we want to use the "relationships" schema to show that not only does Anne know Uther, but she is married to him, we can write:

@prefix : <http://xmlns.com/foaf/0.1/>. @prefix rel: <http://www.perceive.net/schemas/relationship/>. <mailto:person@example.net> rel:spouseOf [ a :Person ; :name "Uther Example" ].

You can mix elements from different schemata as long as you namespace them. Unfortunately, you kind of have to skip over the namespaces when reading Turtle FOAF docs out loud.

title: Wikivoyage:Turtle RDF


text:
Wikivoyage:United States route icons

This is a list of route icons for the United States of America. Route icons for other countries can be found on the main Project:Route icons page.

Amtrak routes
An SVG file with all Amtrak icons is available at File:Amtrak icons.svg

US Interstates
See: commons:Interstate shields

US Routes
See: commons:U.S. Route shields

State route icons
See: commons:Category:Diagrams of road signs of the United States by state

Historic highways

 * US 66 (historic).svg for Route 66
 * LincolnHighwayMarker.svg for the Lincoln Highway

Mass transit routes

 * LAMetroLogo.svg for Los Angeles metro routes
 * Bart-logo.svg for Bay Area Rapid Transit routes

title: Wikivoyage:United States route icons


text:
Wikivoyage:Usable articles

A usable article is a status rating for any article in Wikivoyage that has enough information to be useful for an adventurous traveler. That is, by using the information in the article, they can (for example) get to a destination, find good places to sleep and eat there, and have some pointers for what to see or do.

Of course, length doesn't guarantee usability. An article about a destination can go on for pages and pages and still not give enough of the information you need to survive there. Each article should cover its subject with the appropriate depth or breadth. But if you do not know how to get there, or where to stay if you do, then the article is not very useful. Such an article would still be an "outline", even though it has a lot of content.

In general, usable articles are not really complete articles, however. They may not offer many options for where to eat and sleep. They may not contain much information about nightlife or shopping, for example. Or they may be lacking much helpful information about the destination in general, or nearby destinations. This prevents them from being considered true "guide" articles.

See also: Stub articles, Outline articles, Guide articles, Star articles.

Identification
The criteria for what makes a "usable" article varies depending on the subject. A city article is expected to have some hotel and restaurant listings, but that doesn't make sense for an article about an entire region, which should instead have a listing of cities in that region. National parks may be leave-no-trace camping and wilderness; an article for a small, isolated remote village may indicate a lack of hotels (or restaurants) and suggest alternatives. Obviously the criteria for a travel topic or phrasebook would be even more different.

See Article status for an overview of article status criteria, or the following links for usable criteria for specific article types:

 * City article status (also for districts and rural areas)
 * Region article status (also for continents, continental sections, and main city articles for cities with districts)
 * Country article status
 * Itinerary status
 * Travel topic status
 * Phrasebook status
 * Park article status
 * Airport article status

A complete list of all current "usable" articles can be found in Category:Usable articles.

Tag
If you find an article that meets the criteria for "usable" but hasn't been tagged as such, or if you improve an article to the point that it qualifies, please tag it appropriately.

There's special markup in our software to mark something as a usable article. Unlike the "stub" tag, which is generic enough to apply to any kind of article, we have different tags for the different kinds of articles. For example, the tag for a usable article about a city looks like this:   which makes this appear on the page:

The other kinds of "usable" tags are , , , , , , , , , and .

You can add one of these messages at the bottom of the page. This tells adventurous readers that the article might be adequate for them to use, but acknowledges that it's not up to the standard that we hope all Wikivoyage articles will eventually achieve. Also, it invites them to add whatever they can to make the article better.

Upgrade
If you find a "usable" article about a subject you know a bit about, or if you're planning a trip and doing some additional research beyond what you find in the article, you can help upgrade an article to an actual "guide". Find information to add to any missing or sparsely-populated sections. Add more options for places to eat or sleep (especially different kinds: add a budget hostel if the existing listings are all for five-star hotels). Also, if the existing information isn't formatted clearly, or doesn't look like our style guidelines, fix them up.

The specific criteria varies depending on the kind of article (i.e. city, country, etc.) but the general theme of a better-than-just-usable article is that it is more or less complete, covering every subtopic that a good guide should, and with enough detail that people can pick and choose which information to act on. At that point it's a real guide, and the tag can be changed to (or whichever kind of guide it is).

 * Re-evaluate outline to usable upgrade tasks
 * Ensure all listing have coordinates
 * Check all external links are valid.

title: Wikivoyage:Usable articles


text:
Wikivoyage:Creating emphasis

When writing your lively description, it's sometimes good to highlight certain topics or terms for the reader. A good way to do this is through bold and italics. Boldfacing a topic calls it out as important for someone skimming through an article; italicizing a term can emphasize its importance for someone reading the guide in detail.

Use boldface to call out important topics
When you're writing paragraphs about important terms or phrases, use boldface to highlight those words or groups of words. Readers who are skimming an article will be able to find paragraphs that interest them without reading each and every word. They can then read the full paragraph in detail, if they're interested.

Examples:

 * One of the main activities in Vermont during the winter is skiing. Ski resorts are open from Thanksgiving weekend through Memorial Day.
 * There are many taquerias in the Mission district, serving up burritos made to order. This Mexican dish has become a San Francisco specialty.
 * At all Bangkok sites and attractions, be on the lookout for scam artists. A frequent scam is to convince tourists that the site is closed for a "Buddhist holiday", and try to get them to come to a store or market instead.

Note that writing with all-capital letters is frowned upon; on the internet this is considered shouting, which is rude – see wv:capitalization.

Use italics for emphasis
When you're writing prose, it's sometimes necessary to emphasize a term to mirror its emphasis in spoken English. To emphasize a term, use italics.

Examples:

 * It is extremely dangerous to drive on Mexican highways at night.
 * Don't wait until later to report the incident; contact your consulate or embassy immediately.
 * It's not important to pack everything you can think of. What is important is that you pack what you need, and add to your baggage only the minimum of extra weight.

As a rule of thumb, use boldface to address readers who are skimming an article; use italics to address readers who are reading your prose word by word.

title: Wikivoyage:Creating emphasis


text:
Wikivoyage:User ban nominations

__NEWSECTIONLINK__ User bans are put into practical effect by using a Mediawiki software feature to block edits to any page (except pages in that banned user's user talk page) by the banned user.

Add nominations for user blocks to the list below, but please do so only after reviewing How to handle unwanted edits. After a nomination has been made, the nominator is responsible for ensuring that appropriate notice is given on the allegedly delinquent user's talk page of the nomination made here.

In general the preferred way of handling problem users is through the use of soft security. In the case of automated spam attacks the spam blacklist can also be a valuable tool for stopping unwanted edits.

For an archive of older nominations, see User ban nominations/Archive. Nominations are automatically closed and archived after 14 days of inactivity.

The dog2 (topic ban on politics and sensitive issues)
Continuing the discussion from Talk:Israel since there's enough support for this discussion. Pinging all users involved to continue this here:. -- SHB2000  (t | c | m) 23:54, 5 July 2024 (UTC)
 * Support. The dog2 has been wasting the community's time for years with political debates on talk pages and often inaccurate or unnecessary political claims in articles. When The dog2 works on accurate travel advice instead of political controversies, contributions are typically good, so my hope is that this ban will allow  to focus on those contributions and avoid wasting the community's time and misinforming readers with the political stuff. —Granger (talk · contribs) 00:24, 6 July 2024 (UTC)
 * Support per discussion linked above, and a long list of instances of disregarding WV:Tone and engaging in unnecessary encyclopaedism, too well-known to bother mention. Ibaman (talk) 00:31, 6 July 2024 (UTC)
 * Support. This has been going on too long. It shows a deep lack of respect for the commhnity, and is disruptive to our purpose of building a travel guide. Ground Zero (talk) 00:53, 6 July 2024 (UTC)
 * Since I didn't weigh in fully, I'll do so now. The dog2, I echo what Mx Granger said about your contributions elsewhere – however, when multiple users have asked you to step back on politics and sensitive issues, you need to do instead of doing the same thing over and over again. It's gone for several years now; how long is too long?
 * During the duration of your topic ban, I suggest you take a through step back and learn to check what you're adding into mainspace. Take this time to learn why the community feels the way about your contributions to politics and respect sections; by the time your topic ban is over, you should have learned by then what to and what not to do.
 * For everyone else – how long should the topic ban be? I would opt for 3 months given the length of their disruptive behaviour, which is enough time to self-reflect on their behaviour, but it can always be extended if the conditions of the ban are broken or if the disruption continues after the ban ended. -- SHB2000  (t | c | m) 01:56, 6 July 2024 (UTC)
 * I'd say 6 months. And I support. Ikan Kekek (talk) 04:20, 6 July 2024 (UTC)
 * 6 months also works with me (or whatever everyone thinks is enough time for The dog2 to self-reflect). -- SHB2000  (t | c | m) 04:22, 6 July 2024 (UTC)
 * I also support 6 months. Ground Zero (talk) 10:19, 6 July 2024 (UTC)
 * 6 months, no objection. Ibaman (talk) 11:38, 6 July 2024 (UTC)
 * Support. Although some of the additions by The dog2 are warranted, he clearly cannot judge when he should be sceptical toward his sources, how much his observations can be generalised, what conclusions can be drawn and when the warnings just aren't necessary. Please, The dog2, if you think something needs to be mentioned, tell it on the talk page instead and let other editors decide. –LPfi (talk) 09:28, 6 July 2024 (UTC)
 * Ground Zero (talk) 12:30, 6 July 2024 (UTC)

 * See also Talk:Philippines. I'm not sure a ban is warranted; discussion & warnings should be enough. On the other hand, I have not followed things closely & will not raise an objection to the apparent consensus to ban. Pashley (talk) 14:21, 6 July 2024 (UTC)
 * I agree with you that "discussion & warnings should be enough", but they haven't been. You can see on User talk:The dog2 how various editors have been cautioning them about adding false information and controversial opinions back to at least 2017, and have repeatedly asked them to desist from editing Respect and Politics section. The dog2 ignores the warnings and discussion. Ground Zero (talk) 14:58, 6 July 2024 (UTC)
 * One other thing: how long should the ban nomination go for? I think 7 days is enough to form a clear consensus, but I'd be willing to hear to other suggestions. SHB2000  (t | c | m) 11:08, 7 July 2024 (UTC)
 * How_to_handle_unwanted_edits says: "If the proposed suspension of the user's editing privileges is supported by two administrators, and there is a broad consensus for the suspension, after 3 days the suspension will go into effect." This seems to me to be very fast. As The dog2 is an administrator, I would err on the side of a longer discussion period, like the 7 days you suggest, unless they make any edits to Respect or Politics while this discussion is underway. In that case, I would implement it immediately. Ground Zero (talk) 11:27, 7 July 2024 (UTC)
 * Seems reasonable, as he is aware of the discussion. If he thinks that a longer period or more voices are needed, I don't see any problem with that, but I doubt that would change anything. –LPfi (talk) 11:34, 7 July 2024 (UTC)
 * They do, of course, have until then to own up and things may turn around, but LPfi's suggestion is more than reasonable to me. -- SHB2000  (t | c | m) 11:35, 7 July 2024 (UTC)
 * Since there's a consensus that I am to be banned, there is nothing much else I can do but accept it. The dog2 (talk) 20:40, 7 July 2024 (UTC)
 * Since it'll be 7 days by the end of tomorrow, how shall we lay the ban conditions? I'd say:
 * no edits to anything politics-related.
 * no edits to "Respect" sections.
 * no edits to anything that can be deemed sensitive.
 * this ban only applies to mainspace; talk page discussions are still allowed.
 * Does this sound good with everyone? -- SHB2000  (t | c | m) 11:28, 11 July 2024 (UTC)
 * "Sensitive and politics-related issues" is quite vague. I assume "anything sensible" refers to things that could go into Respect, not everything somebody could find sensible.
 * The wording is OK if we trust The dog2 not to try the limits and others not to mind grey-area edits. If somebody at some point feels that his edits are too far across the limit, then there needs to be further discussion. Perhaps we should trust him and the community, so that we don't need to start rule lawyering.
 * –LPfi (talk) 11:47, 11 July 2024 (UTC)
 * Works with me. -- SHB2000  (t | c | m) 12:03, 11 July 2024 (UTC)
 * I support the wording, but I do not trust The dog2 not to try the limits. They have not shown respect for the community's opinions on this so far. If there is a clear violation of our intent here, The dog2 should be subject to escalating blocks. If there is a grey-area edit, it should be reverted with a reference to the topic ban. Ground Zero (talk) 12:15, 11 July 2024 (UTC)
 * That or possibly the topic ban gets extended by 1 month for each violation. If it gets to a breaking point (where it gets extended to, say, end of 2025), possibly a block or desysop nom. -- SHB2000  (t | c | m) 12:28, 11 July 2024 (UTC)
 * I think GS's suggestion is fine. Still, we don't want to argue whether an edit is a step into the grey area. When considering a revert or block on this bases, one should ask oneself "should this be commonly understood to clearly be a step into the grey area or to clearly be a violation of the intent", not "do I think this is …" (somewhat analogous to the "knew or should have known" in Finnish law). –LPfi (talk) 04:22, 12 July 2024 (UTC)

 * yeah, for the record, as of yesterday there were edits about Hong Kong cinema, which IMHO are not "political" or "sensible" per se, but I would call them "encyclopaedic and unneeded", and qualifying as "testing the limits" and "not showing respect for the community's opinions". But maybe I'm being too grumpy here. Opinions? Ibaman (talk) 12:35, 11 July 2024 (UTC)
 * I think they're okay because they aren't political or sensitive and don't exactly waste the community's time the same way their edits to Israel or Russia have been. -- SHB2000  (t | c | m) 12:41, 11 July 2024 (UTC)
 * I think the block is about unreliable information relating to politics and Respect. The encyclopaedic and unneeded stuff may be irritating, but I think we are going too far if we include that. Most of the marginally relevant stuff added has been about sensitivities and is thus covered. I don't see how we can disallow "unneeded additions" without rendering the edit rights unusable – as the premise is that there are problems with the user's judgement. –LPfi (talk) 12:44, 11 July 2024 (UTC)
 * ✅ – the topic ban has now been enacted until January 12, 2025, 23:54 (UTC). -- SHB2000  (t | c | m) 07:59, 13 July 2024 (UTC)

title: Wikivoyage:User ban nominations


text:
Wikivoyage:User ban nominations/Archive

This page is for archiving content from User ban nominations.

This page is split up into several subpages, categorised by year.
 * User ban nominations/Archive 2005-2012
 * User ban nominations/Archive 2013-2014
 * User ban nominations/Archive 2015-2016
 * User ban nominations/Archive 2017-2018
 * User ban nominations/Archive 2019-2022
 * User ban nominations/Archive 2023-2026

107.9.140.157
This user has created several copyvios, hoaxes (for road routes that do not exist), and deliberately misleading information to several articles, demonstrating no sign of change either. I don't see much hope when they have refused to respond to any of the talk page messages directed at them. -- SHB2000  (talk | contribs | meta) 20:22, 3 April 2024 (UTC)
 * Sure, if this requires a formal user ban, rather than just blocking at sight like Brendan. Meanwhile, block for a month. Ikan Kekek (talk) 23:00, 3 April 2024 (UTC)
 * I think I'm subconsciously treating this like an ANU thread, even though this isn't such. I'll change the block later today if there are no other objections. -- SHB2000  (talk | contribs | meta) 23:27, 3 April 2024 (UTC)
 * Welp, they've just earned themselves a 2-week block. -- SHB2000  (talk | contribs | meta) 01:52, 6 April 2024 (UTC)

70.68.168.129
This user is being disruptive and unwilling to listen with their use of AI in discussions. Can someone else look at their behavior since I've been directly involved? -- SHB2000  (talk | contribs | meta) 05:23, 6 April 2024 (UTC)
 * Support Ikan Kekek (talk) 05:34, 6 April 2024 (UTC)
 * I think the incivility on Special:Diff/4860194 and Special:Diff/4860189 are grounds for a ban, but it's best for an uninvolved admin to impose it. Any takers? -- SHB2000  (talk | contribs | meta) 07:11, 6 April 2024 (UTC)
 * I've revdel the revisions. But it's a bit sloppy since I have to redact the text after someone replied to it. OhanaUnitedTalk page 07:30, 6 April 2024 (UTC)
 * Nah, it looks good to me (tho the hammer would be nice). Cheers for that. -- SHB2000  (talk | contribs | meta) 07:32, 6 April 2024 (UTC)
 * Oh, I see already blocked them for a month before. --  SHB2000  (talk | contribs | meta) 07:33, 6 April 2024 (UTC)
 * I now blocked them for three months for the talk page message. I haven't been involved lately, and I don't think my previous comments on their talk page can make me regarded as partial. –LPfi (talk) 08:06, 6 April 2024 (UTC)
 * Thank you, LPfi. -- SHB2000  (talk | contribs | meta) 08:08, 6 April 2024 (UTC)

 * The most recent comment posted by the user at Talk:British Columbia is alone grounds for a ban. Support. --Comment by Selfie City (talk) (contributions) 14:40, 6 April 2024 (UTC)
 * Yes indeed. However, blocking their IP address for more than a few months is probably useless, as addresses get reassigned. –LPfi (talk) 15:18, 6 April 2024 (UTC)
 * Agreed. The ban should be a "permanent" ban in the sense that any reappearances of this editor should be blocked, but for no longer than three months for the reason you stated. --Comment by Selfie City (talk) (contributions) 21:34, 7 April 2024 (UTC)
 * Support. I didn't recall having blocked but went to check the history, which clearly shows that whoever is generating this AI interaction is not here to build a travel guide. Ibaman (talk) 14:50, 6 April 2024 (UTC)

 * Support for the reasons above. Ground Zero (talk) 15:59, 6 April 2024 (UTC)
 * Support - 70 seems to have been trolling from the outset. Gizza ( roam ) 23:27, 7 April 2024 (UTC)

title: Wikivoyage:User ban nominations/Archive