text:
Wikivoyage:Naming conventions

There are lots of places in the world, with lots of names in lots of languages. The following conventions are intended to make it easier to decide how to write place names, and how to read and find things in Wikivoyage. Most of the following apply to destinations as well as other kinds of articles.

Article naming
This version of Wikivoyage is in English (there are other language versions of Wikivoyage), so articles should use the city, region or country name most commonly used in English-speaking countries. This means that official names are often not appropriate for use as article names.

Examples:

 * Beijing, not Peking
 * Saint Petersburg, not Leningrad or Санкт-Петербу́рг
 * Geneva, not Genf or Genève
 * Mexico City, not México or Ciudad de México
 * Tokyo, not Tōkyō or 東京
 * Bangkok, not กรุงเทพฯ or Krung Thep

If there are other names for a destination — especially the name in the local language — by all means, include that information in the article itself. For example, an English-speaking traveller to Lisbon should know that it's called Lisboa in Portuguese; they may be interested that it was called Olisipo by the Romans. Other examples:

 * Athens (Αθήνα, Athína) is the capital city of Greece.
 * Seoul (서울) is the capital of South Korea.

When there are multiple names
For destinations where multiple names or spellings are in use and there isn't an obviously correct English name, the title should be the most commonly-used name in the local language. For places where the local language doesn't use the English (or Latin) alphabet, try to form a Romanized version. In these cases, it is important to create a redirect for the alternate versions of the name. The guiding principle here is the traveller comes first. Use common sense and consensus to resolve naming conflicts.

Romanization
Use only the characters of the Latin alphabet for all article names (not just place names). Latin characters are the letters A through Z, capitalized or not, with or without accents/diacritics, and including ligatures (such as æ, Æ). Latin characters are much, much easier for English-speaking readers and contributors to "sound out" or to type (say, for the search tool) than non-Latin characters. When using accents/diacritics and/or ligatures, please also create redirects without them (e.g. the article named Ærø should have redirects named Aero and Aeroe). When languages use the Roman alphabet with a small number of additional characters, such as the Icelandic "þ" and "ð" or German "ß", these can be used in article names as well, although again alternatives using substitute spellings should be created as redirects.

See also: Romanization for language-specific conventions.

Examples
When determining an article name, use the following guidelines:

 * 1) Are there multiple names in use for the destination?  If not, the article name is obvious.  Example: Chicago.
 * 2) If there are multiple names for a destination, is one so much more commonly used in English-speaking countries that not using it as the article name would cause confusion?  Example: Geneva instead of Genf or Genève.
 * 3) If there are multiple names for a destination and one does not meet the "so much more commonly used" exception above, use the local name and create redirects for the alternate version.  Example: Ærø is the article name, and redirects should be created for the alternate versions Aero and Aeroe.

Additional examples:

 * São Paulo is the article name. A redirect should be set up for Sao Paulo since both names are used in English-speaking countries and "São Paulo" is the name in local use.
 * Mexico is the article name. A redirect should be set up for México, since the former is always used in English-speaking countries.
 * Þingvellir National Park is the article name. A redirect should be set up for Thingvellir National Park since both names are used in English-speaking countries and "Þingvellir National Park" is the name in local use.

Consistency
All use of a place name throughout any article should be consistent with the article title for that destination. In other words, naming should be consistent, regardless of whether it is the article title, or written anywhere else.

Hierarchy
The shorter we make our URLs, the easier they are to remember and the more likely people are to pass them around. For place names, the basic name of the place, without a whole bunch of localizing addenda, is the best.

In other words, Denver is all you need to find the city of Denver in Colorado. Avoid using Denver, Colorado or Denver, Colorado, United States of America. The place of Denver in the world should be clear from the Denver page, or from the Colorado or even United States of America articles. The Breadcrumbs should resolve any remaining ambiguities.

If, and only if, two or more places have the same name, and each also needs a separate Wikivoyage article, then the article titles should be disambiguated by adding a disambiguator (See below).

Region
Many regions have local names that work well in the Wikivoyage hierarchy, such as the Green Mountains or the Ozarks. In other cases the most common name might use a directional indicator, such as Northeast Ohio; in these cases it is important to remember to use the common name and to avoid the temptation to create a region with a name like "Northeast (Ohio)". In this case, someone visiting Ohio is not going to visit Northeast, they will be visiting Northeast Ohio.

Cities, towns, villages and other destinations
When deciding on the place name to use, avoid using the legalistic terms such as City of, City, Town of, Township, Village of, Village and similar descriptions, unless City, Town, Village, etc. is normally used as part of the place name as in Mexico City.

A good test is to ask if you would still be discussing the same place if the extra term was omitted from the place name.

Districts
An exception to excluding hierarchy from article names is districts in a city. These have names of the form "Name of city/Name of district". Examples:

 * San Francisco/Civic Center-Tenderloin
 * London/Leicester Square
 * Bangkok/Sukhumvit

Keep district names short; in particular, don't repeat the name of the city unless it's offical. Amsterdam/East is as clear as and much shorter than "Amsterdam/East Amsterdam".

Disambiguation
Sometimes different places have the same name, and require disambiguation. In most cases this is easy to solve, using one of the first two rules here. In a few cases, rule 3 or 4 comes into play.

 * 1) If two places are on the same level of the geographical hierarchy (e.g. both are cities), put the country of each in parentheses after their names. Example: Nanao (Japan). In certain countries, a more precise level of disambiguation is necessary or more natural, such as:
 * 2) *Places in Australia use the state or territory as the disambiguator. Example: Stratford (Victoria).
 * 3) *Places in Canada use the province or territory as the disambiguator. Example: Windsor (Ontario).
 * 4) *Places in metropolitan France (i.e. mainland France and Corsica) should use the country as the disambiguator (example: Bayonne (France)), but places in Overseas France, including the five overseas departments, should use the department or collectivity as the disambiguator (example: Saint-Pierre (Martinique)). However, if a place in metropolitan France is disambiguated because a place in Overseas France has the same name, use the official region as the disambiguator (example: Saint-Denis (Île-de-France) or Saint-Louis (Haut-Rhin))
 * 5) *Places in South Africa use the province as the disambiguator. Example: Middelburg (Eastern Cape).
 * 6) *Places in the United Kingdom use the constituent country – not the county or sovereign state – as the disambiguator. Example: Haverhill (England).
 * 7) *Places in the United States of America use the state as the disambiguator. Example: Venice (California).
 * 8) *If two places are on the same level of the geographical hierarchy and they are in the same country, put the highest level of geographical hierarchy unique to each place in parentheses after their names. Example: Ko Chang (Southern Thailand).
 * 9) If two places are on different levels in the geographical hierarchy, put the name of each geographical level in parentheses. Examples: Georgia (state) and Georgia (country); Nakhchivan (city) and Nakhchivan (region). Note that in the US, counties are known as "X County" and shouldn't require this kind of disambiguation from cities of the same name.
 * 10) In a few extremely rare cases it won't be possible to disambiguate places only using these two rules. If and only if this happens, use both the name of the geographical level and the name of the country/state/province. Example: The cities of Durham (North Carolina) and Durham (New Hampshire) can be disambiguated by rule number 1. But there is both a region and a city called Durham in Ontario. Hence Durham (region, Ontario) and Durham (town, Ontario), since the latter is not the only Durham (town) (rule number 2) nor the only Durham (Ontario) (rule number 1).
 * 11) As an exception, if one place is so much more famous than others with the same name that the disambiguation is a hindrance rather than a help, leave it without a disambiguator on the end. This is rare, and if you even have to think about which place is "more famous", go back to rule 1. Examples: Paris is the capital of France; Paris (Texas) is a nice little prairie town in the US. London is the capital of the United Kingdom; London (Ontario) is a mid-sized city in Canada. Peru is the country in South America; Peru (Indiana) is a town in the Midwest of the United States.
 * 12) *When a place meets the "so much more famous" criteria, that non-disambiguated article should include the template at the top of the page, which will automatically provide a link to a disambiguation page for the others.  For example: Paris uses  to automatically create a link to Paris (disambiguation).
 * 13) *Provinces and prefectures surrounding important cities of the same name are common examples of the "so much more famous" rule. When a city X and its surrounding region share exactly the same name, and the city is much better known, the city gets "X" and the province goes in "X (province)".  Examples: Buenos Aires and Buenos Aires (province), Hiroshima and Hiroshima (prefecture), Utrecht and Utrecht (province).

If there are 3 or more places with the same name, use rule 1 first (for places on the same level of hierarchy) before using rule 2 (for places on a different level of hierarchy).

You can use a single vertical-bar "pipe" character to hide disambiguators in the text of an article. For example, type Georgia (state) and it will be automatically expanded to Georgia, and appear in articles as simply Georgia.

When two places share the same name a disambiguation page should be created, and added to Project:Links to disambiguating pages. The name of this page should usually be the common name, for example Georgia. If one place meets the "so much more famous" exception, the disambiguation page should be named "X (disambiguation)" where "X" is the common name. Example: Buenos Aires (disambiguation). Links in other articles that point to the disambiguation page should be updated to point to the appropriate disambiguated page.

See Project:How to rename a page for details on how to disambiguate an existing topic.

Capitalization
Most place names are capitalized in English. Short words like "of", "and", and "the" usually are not. So, for example, United States of America is the preferred capitalization.

For articles that aren't place names, capitalize the first word, and then don't capitalize things that don't need to be capitalized. For example, Discount airlines in Europe rather than "Discount Airlines In Europe", and Manual of style rather than "Manual of Style".

"The"
If a destination name normally starts with the word "the", leave it off for the article name.

Examples:
 * The Channel Islands
 * The French Alps
 * The Gambia
 * The Grand Canyon
 * The Northern Territory
 * The Yukon

Exceptions: The Hague, The Rocks or The Catlins, where "The" is a fixed part of the name.

Abbreviations
Places called Saint or Mount something or other often have the name abbreviated as St., Mt., St or Mt something or other. To avoid confusion and multiple articles, the abbreviation should be avoided and the words spelled out in full, unless the official place name spelling (such as Cradle Mountain-Lake St Clair National Park) uses the abbreviation.

Note: By convention, St. John's in Newfoundland is always abbreviated to distinguish it from Saint John in New Brunswick.

Also avoid contractions like Turks & Caicos Islands but spell the conjunction too, so the article is named Turks and Caicos Islands.

Separating words
Separate words with a single space character rather than apostrophes, dashes or hyphens, unless the place name is normally spelled that way.

Numbers
Spell numbers out, unless they are actually part of the name. For example, use Eight mile junction instead of 8 mile junction as the number is spelled out on signs, though Route 66 or E8 should be used if the names are normally displayed that way or if the number is routinely displayed on its own.

Non-alphabetic characters
Try to avoid using non-alphabetic characters, even when they are actually part of the name.

The following characters should be avoided if possible:
 * # – Hash or pound mark: Used in web page address to indicate a section.
 * ? – Question mark: Used in web page address to indicate the start of a query string.
 * / – Slash: Separates a major page from a sub page.
 * : – Colon: Separates the wiki article namespace from an article name. Should only be used with valid name spaces.
 * & – Ampersand: Used in web page addresses to separate the parameters of a query string. Shows up as "&amp;" in markers in the mapframe.

For example, should never be used at the title of an article about Hash browns, as # is used to link to a section heading on a page. In this case the link goes to the Browns section on this page, which doesn't exist.

These and other special characters in article names had produced unexpected results in the past:
 * . – Period: Used in web addresses to separate domain names.
 *  '  – Single Quote: Used in HTML to enclose strings.

You could find the article to be unlinkable or tricky to move, or pages that link to the article may produce errors.

Section headings
Section headings in articles should follow most of the same formatting conventions as article titles. Section headings should usually come from the appropriate article skeleton for a destination.

Official names
An alternative policy for article naming is to use the destination's official name. Often, the official name is also the most common English name, so there's no problem. But there are often difficulties with official names.

 * They are overly long: for example, the official name for Bangkok is 163 Roman characters!
 * They have lots of extra words that no one uses: "City and County of San Francisco", "Hong Kong Special Administrative Region of the People's Republic of China", "Urban agglomeration of Montreal", etc.
 * They are obscure and unknown.

title: Wikivoyage:Naming conventions


text:
Wikivoyage:News Expedition

The News Expedition is a Wikivoyage Expedition to promote the creation of higher quality news on the Main Page and on Travel news.

Rationale

 * Organic processes that result in high-quality articles do not always work with our news items; rather, the result tends to be uneven news coverage.
 * High visibility of the news on the Main Page justifies a bit of extra attention

Goals
This expedition is under development; please update the goals as needed, or discuss on the talk page.
 * Promote the creation of regularly-updated high-quality news items of worldwide interest.

Members
To join the expedition, add your name below. Joining confers neither privileges nor responsibilities; it's just a way of letting others know you're interested.

 * (WT-en) JYolkowski
 * (WT-en) Stefan
 * (WT-en) PerryPlanet
 * (WT-en) AHeneen
 * (WT-en) ChubbyWimbus
 * (WT-en) Dazzla

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

title: Wikivoyage:News Expedition


text: Wikivoyage:News Expedition/Travel news proposal


text:
Wikivoyage:News Expedition/Travel news proposal/Template

 * Travel news


text:
Wikivoyage:No advice from Captain Obvious

When visitors arrive from far away, locals usually love to give them advice. Unfortunately, this often leads to a temptation to offer advice for everything under the sun. On Wikivoyage, this translates to Respect and/or Stay safe sections a mile long, with the result that actual useful information is buried in an avalanche of platitudes and things most of us learned in kindergarten.

To prevent this, Wikivoyage's rule of thumb is No advice from Captain Obvious. In other words, if the piece of advice is true for every city and country on the planet (and can be assumed to be common knowledge among well-travelled people) it does not bear repeating in every single article on Wikivoyage.

Actual examples of advice from Captain Obvious include:

 * Don't flash your valuables in areas which may be targeted by pickpockets.
 * Wear a condom if engaging in sex with a partner you don't know well.
 * A bottle of water costs more at a convenience store than at a supermarket.
 * Locals don't take kindly to their country, customs, language or food being mocked by foreigners.
 * Never speed on the roads.
 * Avoid anyone who appears to be drunk, and avoid drinking too much yourself.
 * As long as you avoid going outside when a storm is forecast, or when you hear thunder, you'll be fine.

That said, remember that obviousness must be considered from the traveller's point of view, not a local's. Leaving 15% tips in restaurants is obvious to Americans and never sticking your left hand in communal dishes is obvious to Ethiopians, but visitors should be told about both.

Several travel topics, such as the Respect, Stay safe and Stay healthy articles, cover a wide range of more universally applicable information. If it's in any of these, it's unlikely to be needed anywhere else.


text:
Wikivoyage:Non-administrator tasks

On many kinds of community Web sites, most participants have a very limited set of tasks they can accomplish. On those sites, special participants called administrators do most of the rest of the jobs to keep the site going. Although this keeps "normal" users from maliciously or inadvertantly messing up the site, it also makes a bottleneck where important jobs aren't done until an overworked administrator finds the time to do them.

Wikivoyage, like most other Wiki sites, is not like that. We have administrators, but the list of things they can do that other contributors can't is really really short; mostly they're things that can't be easily undone. But most jobs that would traditionally be done by "admins" or "sysops" on other sites are done by regular contributors here. Wikivoyage works better if every Wikivoyager participates in the "janitorial" jobs that need to get done to keep the site going.

This page lists some important jobs that need to get done that new Wikivoyagers may think they're not allowed or not supposed to do. Probably the fact that a lot of administrators are also "old hands" who know what jobs need being done, so they get them done, makes it seem like only administrators should do them. Not true at all! Please feel free to plunge forward and make these things happen: Wikivoyage needs all the help we can get!

 * Welcome new users. When new users come onto Wikivoyage, it's nice to leave them a brief welcome message pointing them to important parts of the site. We normally wait until folks have created a user account and possibly set up their own user page or made their first contribution. Welcome messages let new contributors know that they're part of a community, and also make sure they have pointers to important tools for contributing.

 * Clean up the travellers' pub. The travellers' pub, as the default place to put discussions about Wikivoyage, tends to get a little crowded at times. For this reason people take turns moving discussions out of the pub and into the archives or to more specific talk pages. It only takes a few minutes, it helps make discussions more clear, and it's easy to do.

 * Make or edit policy and style guidelines. The policies and manual of style define how we work together to make a great travel guide. If you're working on Wikivoyage and think there's ways we can make a better guide, or we can work together better to achieve our goals, by all means start a new policy or guideline page! We try to make decisions by consensus, so there's no guarantee that your idea will be accepted, but it definitely won't be if you don't suggest it in the first place!

 * Effectuate and archive VFD nominations for which the 14-day discussion period has expired and the outcome is "Keep", "Merge" or "Redirect" (those for which the outcome is "Delete" can only be effectuated by an admin).

 * Resolve broken redirects, double redirects, dead-end pages, and orphaned pages.

 * Review the Upload log - uploads that conflict with the Copyleft rules and/or the Image policy and/or the Goals and non-goals guidelines should be VFD'd, and those with no licence should be tagged.

de:Project:Aufgaben aller Benutzer it:Project:Compiti che non competono agli amministratori ja:Project:誰でも行える管理作業

title: Wikivoyage:Non-administrator tasks


text:
Wikivoyage:Non-compliant redistribution

Non-compliant redistribution is the use of Wikivoyage content without following the conditions required by the Wikivoyage copyleft license.

Why it's bad

 * Non-compliant redistribution defeats the point of open content. Other people who see the unlicensed content will not know who wrote it, will not know that they have the right to obtain the source, will not know that the content comes from Wikivoyage and will not be able to contribute their knowledge.

 * Non-compliant redistribution violates the copyrights of the original authors. They have agreed to license their work under the specific conditions of the CC by-sa 3.0 license only, and the copyright holder can, legally speaking, sue offenders for copyright violation.

What to do
Non-compliant redistribution should be addressed by contacting the distributor in question and gently and politely noting their obligations under the license. Pointing to the how to re-use Wikivoyage guides page is a good way of showing them what to do and how to do it, and most people are happy to comply if asked nicely.

Only the authors have any right to demand compliance. If a re-user has copied all or large parts of Wikivoyage, you can probably find a page for which you are the main author, or for which you have contributed significant content that hasn't been edited much by others. The content must reach the threshold of originality to earn you a copyright, so if you use a page as an example, choose one in which you haven't just added standard wordings (such as in most listings). Most photos and other images would also qualify. If you cannot find such a page, leave the action to somebody else.

Please report sites you find that may potentially infringe any of our copyrights, whether intentionally or unintentionally, on this page's discussion page or send an email to legal@wikimedia.org@undefined where the Wikimedia Foundation's legal team may be able to promptly respond to the matter.

title: Wikivoyage:Non-compliant redistribution


text: Wikivoyage:Norwegian Wikivoyage Expedition


text:
Wikivoyage:Not an article

This is, in fact, not an article. The point of having this page here is that it makes it easier to demonstrate formatting techniques when there's a real page at the end of a link.

title: Wikivoyage:Not an article


text:
Wikivoyage:Offline Expedition

The Offline Expedition is a Wikivoyage Expedition to make it possible to use Wikivoyage offline (while not connected to the Internet).

Reading articles offline

Kiwix is the standard offline reader for Wikivoyage. It is available for Android, iOS, Windows 10, Windows, Mac, Linux, and others. See Kiwix for installation details.

Note about the Android and iOS apps: Check when the app has been last updated. If it is too old (for instance more than a year), then you might prefer to install the Kiwix app and then download the Wikivoyage .zim file within the Kiwix app.

You can also download individual Wikivoyage pages in PDF format. On desktop, click on "Download as PDF" in the fourth section from top of the sidebar. On mobile, tap the three dots at the top of any page; "Download PDF" will be the bottom option.

Maps offline
Any smartphone can display Wikivoyage listings on maps, and provide GPS directions:

 * 1) Install OsmAnd,
 * 2) Within OsmAnd, download the map(s) for each area you plan to visit,
 * 3) On GpxMap, select the area you plan to visit and click the download icon,
 * 4) Open the resulting .gpx file in OsmAnd to show all listings.

Let the GPS guide you to the listing you want to visit. GPS navigation does not require any Internet connection.

Since version 3.0, OsmAnd has integrated support for Wikivoyage which simplifies the above process.

Paper/e-book
Special:Book lets you get started creating your own books, which can be exported to PDF, EPUB or ordered as bound paper books. See the illustrated tutorial.

An e-book reader is a tablet-sized device intended for single-purpose use displaying text from books stored on a flash memory card. Most are of limited capability compared to general-purpose Android or its rival platforms; the screens are often monochrome and designed to only take power when turning to the next page. This extends battery life at the expense of no colour or backlighting. File size which can be handled as one "volume" of an electronic book is limited - it may be best to split the guide into ten-megabyte sections where each is a guidebook to one region or one large country, much like printed encyclopaedias are shelved as multiple volumes. Wikipedia has been adapted to this platform by taking a 5000-article subset, replacing images with small thumbnails and splitting the collection into 15 volumes. The devices are small, lightweight and portable.

 * .epub Used by Nook and Kobo, among others. Each book volume in this file format is basically an oversize .zip file which contains a web page for each chapter of the book and some XML to provide a table of contents. Sigil is one good, free editor to create .epub books from individual web (html) files.
 * .pdf Convenient for laptops, but inconvenient for mobile due to incessant scrolling.

Comparison of all offline readers
Sorted by last data update:

Desirable features
There are several levels of UI we could provide.

 * Download a single article. The user would be able to download a single article in Plucker format. The link for Plucker download would be next to the "Printable version" link.
 * Download a group of articles. Most travellers won't be going to just one place. It'd be nice if they could add articles to a "shopping cart" of some kind, and then download all the articles in their "cart" at once.
 * Download a prepackaged country or region guide. An entire region of Western Europe or one large country like US or Russia as an e-book, sized to fit on a device (such as a portable e-reader) on which the entire world in one huge file would be unmanageable.
 * Update articles offline. Of course, the dream scenario is that Wikivoyagers could download articles to their local computer or PDA, edit the articles on the road, and then upload the edited versions when they get back to an Internet connection. This is probably a little pie-in-the-sky, but it sure would make sure we had up-to-date info.

The normal Wikivoyage home page is too crowded and fast-changing for offline readers, instead here is the home page used by the Kiwix-based app.

Other formats that could be used
Other format could theoretically be used:
 * TomeRaider http://www.tomeraider.com/ Shareware program. There's already been some work to make Wikipedia available in TomeRaider format, but it's the entire database and adds up to close to one gigabyte of data. Wikivoyage will be a much smaller database, though. There are 2 different versions of the Wikipedia database available - with images and without.
 * Plucker http://www.plkr.org/ Free Software. This has some nice features, including better support of images. It also has software included for generating new Plucker pages, which might be useful for Wikivoyage.
 * HWiki http://www.hexlet.com/Products/hwiki.html Proprietary Software. This is PalmOS version of Wiki browser/editor. It understands TWiki flavor of Wiki syntax.
 * DICT http://www.dict.org/links.html together with Wik2dict. Several free (as in speech) servers and clients available. Plain text, no images, though includes links.
 * Encyclopodia http://encyclopodia.sourceforge.net/en/ Free software. Encyclopodia is a Linux-based package which runs on 1st through 4th generation Apple iPods.  Its source-tree includes a tool to convert Mediawiki dumps offline for easy parsing on the iPod.
 * .mobi Used by Kindle; calibre can convert .epub to this and other formats once any copy protection has been removed from the data (and an .epub generated locally from open-source text should be fine in this respect as it's already free).
 * Raw XML As outputted by MediaWiki. Can be converted to a number of formats, imported to a local MediaWiki install, or used directly (as done by Wikifilter.  http://wikifilter.sourceforge.net/)
 * Wiki2Touch http://www.infodisiac.com/Wikipedia/Wiki2Touch/DownloadFilesW2T.html Free application for Jailbroken iPod touches and iPhones. Takes an xml.bz2 dump of wiki databases and turns it into it own format not much larger than the original file. Works exceptionally well.
 * WikiTaxi is an offline reader, viewer, and browser for MediaWiki wikis. WikiTaxi works extremely well on huge Wikipedias (English, German, Japanese, etc) *.xml.bz database dumps. Multi-language support makes sure it works with Wikivoyage also. For Windows. Freeware.
 * Evopedia Free open source offline dump reader and browser for MediaWiki wikis using devices default web browser to display results. Target devices include Linux tablets and smartphones using Nokia Maemo OS, OpenMoko SHR, and devices and computers running Ubuntu and Arch Linux distros.  Evopedia requires processed dumps available at their website or custom databases which can be made with free tools. Wikivoyage, Wikipedia and Wiktionary dumps are available on Evopedia's site.

title: Wikivoyage:Offline Expedition


text:
Wikivoyage:One-liner listings

One-liner listings are the default for Cities, Other destinations, and Go next sections. They are also used in other sections, as appropriate. Regions and Districts sections typically use a similar format unless the template is being used.

One-liner listings are primarily for navigation in the "Regions," "Cities," and "Other destinations" sections; they allow the reader to quickly identify and get to the specific travel guide they want to read. They should generally be limited to just 1–5 sentences that provide an overview of the destination, rather than including detailed descriptions or long lists of attractions.

One-liner listings use the following format:

 * Alphabetical order — preferred, if appropriate and there's no reason not to
 * Bold for the caption — optional if it's an internal wikilink; if mixed, consistency preferred
 * Capitalise — first word of caption, but not the description (except proper nouns, etc.)
 * Description — a concise, 1–5 sentence description of the main draws a destination has for a traveller
 * Em dash, not a hyphen — with one space at each end. If your keyboard doesn't have it, then just enter
 * Forgo blank lines — for accessibility by people using a screen reader

Alphabetical order should be used whenever there's no more appropriate logical order (e.g. price, distance, north–south, day of the week, etc.). Where a non-alphabetical order is used, it should be explained if necessary.

A universal exception to completely alphabetical order is in Cities sections, where capital cities/towns always go at the top of the list.

For high-level regions or country articles, a shorter description (generally a single phrase with no full stop) is typically used for the "Cities" and "Other destinations" section since at the highest level these sections are simply a navigational shortcut that contains well-known destinations that most travelers to the area will likely already be familiar with; use your best judgement to determine the level of detail required.

title: Wikivoyage:One-liner listings


text:
Wikivoyage:Other ways of seeing travel

The geographical hierarchy is one way to think about and organize travel articles - breaking down big areas on Earth's spherical surface into smaller and smaller areas until you get to areas too small to be worth writing an article about. But it's just one of many ways of thinking about travel articles, and to form meta-articles that group other articles together. Some other ways are listed below; there are probably more.

Itineraries
An itinerary views a group of destinations as a linear division rather than a spatial locality or region. For example, one could retrace a real or fictional historic voyage (such as Jules Verne's Around the World in Eighty Days), a well-known pilgrimage (such as the Hajj) or a famous road or rail line (like the Orient Express).

Itineraries may cross geographical regions, but should have a well-defined path. The Appalachian Trail and Route 66 are good examples here.

An itinerary normally provides less detail than the individual city articles for each town on the route. As a purely local itinerary (like One Night in Bangkok) risks pointless duplication of information already in the main city article (Bangkok), creation of these pages is best avoided if the information fits just as easily in the destination article. See Itineraries.

Travel topics
Not all travellers are looking for general adventure and art museums. It also makes sense to think about travel issues - Disabled travellers, First aid kit for travellers, LGBT travel, Honeymoon travel, Travelling with children, or travel activities - golf, scuba diving, etc. Some information on these issues may go into geographical descriptions, but other more general info might be valuable in its own article. Bodies of water aren't given city-level articles (Lake Placid describes the town, not the lake itself) but cruising on small craft on those waters could be a suitable travel topic.

title: Wikivoyage:Other ways of seeing travel


text:
Wikivoyage:Outline articles

An outline article is a status rating for any article in Wikivoyage that has template sections but still does not address its subject sufficiently to be very useful for other travellers.

In general, outline articles are incomplete articles. Subjects worth having an article about are usually worth having at least a paragraph written or at least a few listings in each of the standard template sections. If only some of the sections of a standard template are filled, then the subject is not covered fully or it may not merit its own article and should be incorporated into another one. See What is an article? for details on what deserves its own article on Wikivoyage.

Of course, length doesn't guarantee completeness or even usability. An article about a destination can go on for pages and pages and still not give enough information for you 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.

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

Pros and cons of outlines
Outlines have their bad sides. Readers can get confused by too many empty sections. Is that all there is to say about the article? Is that the expected length of articles for Wikivoyage? Where's all the info? Outlines can give a bad first impression if people haven't seen other Wikivoyage articles.

Mostly, though, outlines are a good thing. An outline is the framework that allows an article that started its life as a stub to grow and evolve into a full blown article. One Wikivoyager can start with an introductory paragraph with a bare outline, and other Wikivoyagers will come along and add more information to it. Someone else comes in and reformats the information according to the Manual of style, and someone else adds photos. Eventually, the bare outline becomes a healthy, useful guide.

Identification
If you set the Threshold for stub link formatting value to something other than 0 in your preferences under Misc, links to short articles will be shown in a different color than links to complete articles or to non-existent articles. The threshold value is a number of characters in the article; somewhere around 500 characters should give you a good idea of whether an article is long enough or not. (The basic template alone is around 150 characters.)

Note that this only shows short articles, and so it's a very rough approximation of an "outline". An article with lots of unformatted information is not yet an "outline", but may exceed the character count of a bare outline article. We don't have the software yet to decide if an article covers its subject well, so we have to manually add Article status disclaimers.

What to do with them
If you make an outline article, or see one that someone else has made (but not tagged), you can either tag it or upgrade it.

Tag
If you add template sections to an article that doesn't have them, or see one that someone else has made, it's good to add a little disclaimer that says that the article isn't really usable yet. It gives a bit of extra impetus to readers to add what they know to an article.

There's special markup in our software to mark something as an outline. 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 outline about a city looks like this:   which makes this appear on the page:

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

You can add the outline message at the bottom of the page. This reassures readers that we know the article is not complete, and that it's not indicative of the overall quality expected out of Wikivoyage articles. Also, it invites them to add whatever they can to make the article better.

Upgrade
It's trivially easy to upgrade an article from "stub" to "outline"; upgrading an article past "outline" can sometimes take a bit more work. In fact, many generally well-developed articles get stuck at this stage because they're missing some key information. The specific criteria vary depending on the kind of article (i.e. city, country, etc.) but the general theme of a better-than-outline article is that it contains enough specific information that a traveler would know how to get there, where to sleep, where to eat, and what to see there. Which actually isn't all that hard to do, with a little bit of research. Upgrading a region article is a bit more work, as the most important cities and other destinations need to be usable, but is well within reach.

At that point it's not an outline any more, and the disclaimer can be changed to be a, , , , , , etc. article (depending on which kind of article it is).

Improving a city article

 * Cleaning up existing information
 * Convert entries in the see, do, buy, eat and sleep sections to listings format. (Listings icons on top bar of editor)
 * Any inline links to external pages showing as numbers ("footnote style"), place description text inside link brackets after web address ("frontlinks"). If multiple information or in bullet point change to a listing.
 * Any phone numbers not clickable to dial, see if can move into a listing.
 * Does the page have a Wikipedia link in "In other projects"? If not on Wikipedia page press Wikidata item on sidebar and add the Wikivoyage page.
 * Validate existing information
 * Check all external links are still valid. Check if listings in do, eat, buy and sleep are still in business. If not remove.
 * (Enable the "ErrorHighlighter" gadget from your user preferences. After enabling the gadget, invalid links will display followed by a very noticeable "dead link" warning. It's best to remove the dead listings before the domains are cybersquatted by others or "parked" as spam.)
 * If a link is broken, first try a web search; the page may have been renamed or replaced with a new website. If a search yields nothing (or only outdated information) check whether the venue is still open.
 * Not having a web site is not proof of closure but if web sites such as TripAdvisor, Google Maps and Yelp abruptly stopped receiving user reviews for the venue a few years ago, indicate the venue as not open or reassign the company's contact info to some other business, assume closed and remove. If a venue which used to get good reviews gets a string of negative reviews, then falls silent, that's not a good sign. Often new management or ownership will allow standards to slip, putting a once-viable business out of business or allowing it to decline until it's not worth listing.
 * If all else fails, unbundled Internet telephony is a cheap and easy way to call the venue directly (a penny or two a minute to most landlines) to ask for the address of their website. If a call yields "the number you have reached is out of service" or a wrong number, the venue has closed. Contacting a visitors' bureau or local destination marketing organisation is another option; they have "boots on the ground" locally and would know if that once-impressive annual festival or gathering was last held five years ago.
 * Add additional listings to cities. Recommend to have at least two sleep and two eat listing and at least either one see or one do listing.
 * Add any attractions (see or do), hotels and restaurants you are aware of.
 * If still not enough listings in each section look on Google Maps, TripAdvisor, Yelp, the towns own website and other websites and guide books you may have for recommendations. Just type "attractions in", "restaurants in" and the town name in search engine.
 * Check the Wikipedia page for any other points of interest.
 * Enhance the page information
 * Identify listings that have Wikipedia pages, copy and paste the Wikidata Q number (on the Wikipedia page click "Wikidata item" in the side bar) into the wikidata field of the visual listings editor, press "Update shared fields using values from Wikidata". (pays to check the results, not always correct url or coords).
 * Add web links, phone numbers to listing if do not exist.
 * If required add address and possibly telephone number to listings
 * Add lat/long coordinates for listings.
 * Expand the content description of listings.
 * Improve the get in section.
 * Search the web to check on bus and rail connections.
 * Review map pages to describe the road connections.
 * If there is an airport add the IATA code.
 * Improve the get around section. Search the web to check on bus connections. What other means of getting about such as bicycle or taxi.
 * Is the geo zoom value correct for the location area covered?
 * Add adjacent locations to the go next section.
 * Not a must but consider looking on Commons, or even better in your own photo collection, for some good pictures to add to the page.
 * Also not a must, but if page does not have a banner image then look at making one from your own photos or from images on Commons.

Improving a region article

 * Move listings in region article to city pages (if necessary, and enough information to justify, create new city pages).
 * Check all location pages in a bottom level region are listed on the region page (go to one of the city pages, if you display hidden categories you can click on the region category to see all pages associated to it).
 * Add red link entries to any important locations of the region not currently mentioned.
 * For the region article (and maybe some of the city articles) are the airport references and connects up to date?
 * Add or clean up entries in see and do sections, should mention important attractions but reference the corresponding city or park page rather than be a listing.
 * Provide some overview text about type of food and style of accommodation in the region, maybe listing the key towns.
 * Add any relevant Travel topics or Itineraries to the see and do (or even eat) sections.
 * Is there a local dialect or regional language worth mentioning in the talk section?

title: Wikivoyage:Outline articles


text:
Wikivoyage:Page history help

For each page on Wikivoyage, you can use the Page history feature to review the changes that have been made to the page.

Changes are listed with the most recent first; if there have been more than 50 changes for the page, the changes are grouped in chunks of 50 (or another value that you choose). You can view older changes by navigating to older chunks.

Each change in the list has the following information associated with it:

 * Date and time of the change
 * Name of the user who made the change, or IP address if changed by an anonymous user
 * Summary of the change, if any
 * Whether or not it's a minor change ("m" in bold)

The timestamp of the change is linked to a copy of the page as it was after the change was made. The name of the user is linked to their user page.

There are also two difference links for each change. The cur link shows the difference between the contents of the page at the time stated and its current contents. The prev link shows the difference between the contents of that version of the page and the contents of the previous version of the page (usually the one current just before it was changed, but page merges and revision deletions may confuse this).

You can customize the way the Page history page works using the Preferences page.

The page history is useful for reviewing the changes that have been made to a page; it is also used to revert a page to a previous version.

title: Wikivoyage:Page history help


text:
Wikivoyage:Park article template

''Use the structure outlined in this template when creating articles about national parks and other natural areas that are large enough to be destinations in their own right. It is not meant to be used for city parks, amusement parks and areas that do not fit the Project:What is an article? criteria.''

''To quickly insert a complete blank park template, copy the quick version into the edit box on the page you are editing. You can also just type in, and the template will be included when you save.''

''Text in italics below is editorial comment, with suggestions for what should go in each section. You should plan on ruthlessly eliminating if you copy this code to a new park article.]''

''The first section of the park article does not have a heading. This is a where you give a quick descriptive overview of the park. Be sure to include some context so readers know where and what they are reading about. Links to the region and country that the park is in can be useful here, too.''

''Also give a high-level description of the park and why people would want to visit (i.e. Yellowstone National Park was the world's first national park, created to protect an amazing array of geothermal features and a vast amount of wildlife). Keep the description here brief, as most information will be included in the Understand section.''

Understand
This is a more subjective description of the park -- what it's like, why someone would want to go there, the scenery and geology, the history, the weather, what makes it different and distinct from other areas.

History
An overview of how and why the park came into existence.

Landscape
If the park is known for its mountains, caves, canyons, or other natural features, provide a brief description of those features and why they are unique.

Flora and fauna
Some of the more common plants and animals that people may be interested in.

Climate
''What is the weather like? When is the best time to visit?''

Get in
''Arrival details. How do most people reach the park? Are there any special considerations (bad road conditions, multiple isolated entrances, etc.?) If the park is accessible by car, give driving details and directions for getting to it from the nearest one or two large cities. Try to include the names of major highways and rough travel times.''

Fees and permits
Entrance fees, camp site fees, hiking permits and fees along with any notable rules and regulations.

Get around
How to get around once you are there: bus, train, bicycle, foot, car, boat, etc. Describe any special concerns such as bad road conditions, limited available fuel, etc.

See
List attractions that people come to this park for, such as common points of interest, backcountry sights, visitor centers, geologic formations, etc. You can also note here general information about attractions, such as need for a guide, weather warnings, good walking routes, general areas to hang out in, etc.

Do
''This is for things that travellers will do themselves. More active participation is needed for Do things than for See things. For example, going to see a river goes under See; kayak trips down the river go under Do.''

Buy
''Where can supplies such as gas, bug repellent, outdoor gear, etc. be purchased within the park? Are souvenirs sold anywhere?''

Eat
''For restaurant listings and other food-related stuff. Are there restaurants in the park? Grocery stores? Any way to obtain food?''

Drink
''For sources of liquid refreshment, alcholic and non-alcoholic. Are there any bars or coffeehouses in the park? Do some of the hotels have lounges?''

Lodging
''List hotels, hostels, etc. within the park. In addition, if there are viable lodging options located outside (but nearby) the park, consider mentioning those as well.''

Camping
Listing of developed campsites within the park.

Backcountry
Blurb on backcountry description, rules, etc. What is required for an overnight trek?

Stay safe
''Safety guidelines for survival within the park. Include information on dangerous animals, poisonous plants, weather hazards, etc.''

Go next
''Information about nearby destinations that would serve as a good "next stop." Provide a brief description of other nearby destination suggestions, neighboring cities or day-trip ideas. Don't duplicate information that's up in "Get in."''

es:Wikiviajes:Modelo de parque zh:Project:公園條目模板

title: Wikivoyage:Park article template


text:
Wikivoyage:Park article status

This page describes the criteria for determining the article status of National Park guide articles.

Insert the wiki markup listed below in order to display a guide's maturity rating:

title: Wikivoyage:Park article status


text:
Wikivoyage:Phone numbers

For most listings, it's helpful to have a phone number for making contact.

We format phone numbers as they would be dialled internationally but in a way that separates the country code, area code, and part that can be dialled locally.

+

For example:

A Canadian number should be listed like:

+1 867 959-5000

Where "1" is the country code, "867" is the area code and "959-5000" can be (optionally) dialled locally using abbreviated dialling (as designated by the two groups of digits con-joined with a hyphen). In most countries the zero is omitted from the area code when prefixed by country code, there are however some exceptions such as Italy.

 * Numbers should generally begin with + and a country code. The exception is numbers that cannot be dialled from outside the country, which should be listed in their local style. For instance, 1-1-2 and 9-1-1 distress calls, and New Zealand Freephone numbers (e.g. 0800 737-000 for the Air New Zealand Freephone number only valid within NZ).
 * When an area code is required for local dialling, or an area code requires a prefix for local dialling (say a '0'), note that in the Connect section of the guide.
 * For North American Numbering Plan (NANP) numbers, which all start with +1, there is a list of area codes that require 10-digit or 11-digit dialing. (Additional area codes are affected starting in 2021.)
 * Information on freephone/toll-free, caller-paid mobile and premium rate prefixes should also go in the Connect section. Consider whether a warning is necessary in the actual listing if premium rate numbers are used.
 * The number group(s) that can be (optionally) dialled locally are con-joined with hyphens.
 * Parentheses or brackets are not used in numbers. If the digits are needed when calling from abroad, include them with no brackets (so +1-800-555-0199 and not 1 (800) 555-0199). If the digits are not needed on international calls, omit them (so +44 20 7777-7777 and not +44 (0) 20 7777-7777).
 * Our formatting method may differ from that seen most in the country concerned. We prefer to use hyphens to only indicate the (con-joined) abbreviated part of the whole telephone number that can be utilised for local dialling. We do not use italics or parentheses within the phone number.
 * In most countries, all the digits of mobile phone numbers should be dialled and there will be no (con-joined) abbreviated part of the whole mobile phone number that can be used for local dialling. Mobile phones are only given standard, landline-style geographic numbers in areas where mobile users pay airtime to receive calls (such as Canada/USA and China). This resource is useful for deciding which are mobile numbers. Wikipedia contains a good list of phone numbers formats by countries.
 * The listing template provides three fields (phone, tollfree, fax) for telephone numbers.
 * Additional numbers (such as TTY/TDD numbers for deaf users) may be added in the phone field separated by a comma. Reason for the other number can be stated in brackets.
 * Numbers that cannot be dialed from outside the country should not begin with a country code. Some examples of these are unified local emergency numbers (like 1-1-2 or 9-1-1) and national freephone numbers in many countries (e.g. 0800 737-000, the Air New Zealand Freephone number, is valid only within NZ).
 * The following number prefixes will not be flagged as having a missing country code: 0508, 0800, 1300, 1800, 01800. Adding a description in brackets after the number of one of the following: "high cost", "extra charge", "premium", "local rate", "in country only", "domestic" or "non-geographic number", will also stop it being flagged as an incorrect format needing country code.

title: Wikivoyage:Phone numbers


text:
Wikivoyage:Phrasebook Expedition

The Phrasebook Expedition is a Wikivoyage Expedition to work out travel-related language guides for Wikivoyage (see the list of phrasebooks for what we've got so far).

Rationale
Contrary to popular belief, English-speaking travellers in other countries often need to use the local language. It's a common part of travel guides to include a mini-phrasebook for the local language(s) with important phrases for travellers.

Goals

 * Determine the place of phrasebooks in Wikivoyage as a whole
 * Explore how to use phrasebooks from other articles
 * Define a phrasebook template to give phrasebooks a consistent look and feel, and to make starting new phrasebooks easier
 * List the important phrases that should be included, to make sure all phrasebooks cover important topics for travelers, and to make it easier to do a new phrasebook

Phrasebooks in Wikivoyage
Because the same language can be used in multiple countries (for example, Spanish or Arabic) and more than one language used in one country, phrasebooks in Wikivoyage will be separate articles from country, city or regional articles. Those articles can link to the appropriate phrasebook for local languages, and may also include small micro-phrasebooks for local deviations. For example, the article for Quebec would link to the French phrasebook, but might also include some variations for Quebecois French.

Phrasebook articles shouldn't be tutorials, comprehensive grammars, or dictionaries for the target language. The goal is to define just enough of the language so that an English-speaking traveller can "get by" in an area where that language is spoken. External links for further study can and should be provided.

Phrasebook article names
An article for a language phrasebook should have a title like "Name of language phrasebook". Examples: French phrasebook, Arabic phrasebook, Greek phrasebook.

Structure of phrasebooks
Each Wikivoyage phrasebook should have the following parts:

 * 1) An overview of the language, giving a brief history, scope (where it's spoken, how many speakers), alphabet or symbol set, and any other general info on the language.
 * 2) A pronunciation guide, with a description of each written symbol in the language (that is, its alphabet), and a pronunciation note for each symbol ("like the 'e' in 'yes'", "like 'ch' in Scottish 'loch'", etc.).
 * 3) A phrase list. Each entry in the phrase list should include the English word or phrase being translated ("Hello"), the spelling in the local language symbol set as it would be seen written down ("Bonjour"), and a pronunciation cue for English speakers ("bawn ZHOO-er").

The format of the phrasebook should follow the Phrasebook template.

Phrases in phrase lists
For most languages, the phrase list should contain at least the phrases in the phrase list section of the phrasebook template. Sometimes this won't be practical; for example, some very remote destinations just won't have restaurants, hotels, or Internet cafes, and the local language may not have words for them. In these cases, more appropriate local terms ("visitor's hut" or what have you) should be substituted, or the phrases can be left out.

For many if not most languages, there will also be culture- or country-specific words and phrases that should also be included. A reasonable number -- twenty to thirty, say -- of these can and should be included in the phrasebook.

For example, local means of transportation (rickshaws, tuk-tuks, cyclos), local dishes, or local entertainment or cultural traditions should be listed if a traveller is likely to run into them. In addition, the grammar of the language may require more forms than are present in English. For example, French has two ways of saying "Goodbye" -- one that's temporary, and one that's more permanent.

Pronunciation
Each phrase in the phrase list should have a pronunciation cue. This is an illustration in an English-like syntax that allows readers to sound out the phrase.

For the most specificity -- showing exactly how to pronounce a phrase -- we could use an official phonetics symbol set, like the International Phonetic Alphabet (IPA) or SAMPA. However, the baroque symbol sets used in IPA and SAMPA would make using the Wikivoyage phrasebooks almost impossible for casual readers. In addition, it would burden many Wikivoyagers contributing to the phrasebooks with the task of learning these phonetic systems.

In addition, exact pronunciation of words isn't really all that important for travel phrasebooks. It's more important that most travellers can make themselves understood, than that some travellers with a knowledge of IPA and a knack for languages get the language down exactly. Moreover, formal IPA descriptions already exist on the internet for those who wish to use them. Getting things "close enough" for most students is more important than getting any one student's accent perfect.

Most commercially-available phrasebooks use a pseudo-phoneticization, that is, English-like sentences using simple rules for showing pronunciation and emphasis. Some examples:

 * French Bonjour → bawng-ZHOO
 * Dutch een → ayn
 * German  Wie geht's? → vee GAYTZ?

To maintain consistency across phrasebooks, and to avoid needless edit wars, and to make it easier for contributors to add pseudo-phoneticization to articles, there's a pseudo-phoneticization guide which helps contributors phoneticize phrases. This is not a guide for readers of the phrasebooks; the goal is to have English-speaking readers "intuitively" understand the phoneticized text.

See also: Requests for phrasebooks, List of phrasebooks

title: Wikivoyage:Phrasebook Expedition


text:
Wikivoyage:Phrasebook status

This page describes the criteria for determining the article status of phrasebooks.

Insert the Wiki Markup listed below in order to display a guide's status:

title: Wikivoyage:Phrasebook status


text:
Wikivoyage:Phrasebook article template

''[NOTE: This is a skeleton for creating a phrasebook article. Phrasebooks are intended to provide some basic guidance about a language.''

To quickly insert a basic blank phrasebook template, copy-and-paste the quick version into the edit box on the page you are editing.

''Stuff in italics below is editorial comment, with suggestions for what should go in each section. You should plan on ruthlessly eliminating if you copy this code to a new region article.''

''When creating a new phrasebook, it's also helpful to create a redirect to the phrasebook using just the name of the language. This makes it easy to wikilink to the phrasebook from other articles.]'' -

''The introduction to a phrasebook does not have a heading. This is where you would put an overview of the language, giving a brief history, scope (where it's spoken, how many speakers), and any other general info on the language. It might also be useful to list some difficulties of the language for English speakers, such as, but not restricted to, polite vs. familiar forms, declension of nouns, genders, tones, etc. It's preferable not to give a full grammar of the language -- just give some tips on why it might be hard.''

Pronunciation guide
''This is where you put a full list -- if possible -- of the alphabet or symbol set of the language. For languages that use pictograms -- like Chinese or Japanese -- you can simply give a pronunciation of the most common Romanized script. It will be a good start, at least.''

''Here follows an (inexpert) guide to the English alphabet; note that it doesn't make a lot of sense, since it's describing many English letters in terms of themselves. This is just an example. Note also that it's split up into vowels, consonants, and diphthongs; these may be appropriate for most European languages, but might not work for others. Split the alphabet up in accordance with the language you're describing.''

Vowels

 * A (a) : as in father
 * E (e) : as in ten
 * I (i) : as in machine
 * O (o) : as in open
 * U (u) : as in rule
 * ai : as in Thailand
 * ui : as in Louie

Consonants

 * b : like 'b' in "bed"
 * c : like 's' in "supper", 'k' in "kid"
 * d : like 'd' in "dog"
 * f : like 'ph' in "phone"
 * g : like 'g' in "go", 'j' in "jello"
 * h : like 'h' in "help" (often silent in the UK and other Commonwealth countries)
 * j : like 'dg' in "edge"
 * k : like 'c' in "cat"
 * l : like 'l' in "love"
 * m : like 'm' in "mother"
 * n : like 'n' in "nice"
 * p : like 'p' in "pig"
 * q : like 'q' in "quest" (with "u", almost always)
 * r : like 'r' in "row", like 'r' in "feather" (often silent in the UK and other Commonwealth countries at end of word)
 * s : like 'ss' in "hiss", like 'z' in "haze"
 * t : like 't' in "top"
 * v : like 'v' in "victory"
 * w : like 'w' in "weight"
 * x : like 'cks' in "kicks", like 'z' in "haze" (at beginning of a word)
 * y : like 'y' in "yes", like 'ie' in "pie", like 'ee' in "flee"
 * z : like 'z' in "haze"

Common digraphs

 * ay : like 'ay' in "say"
 * ai : like 'ay' in "say"
 * au : like 'awe'

 * ee : like 'ee' in "see"
 * ei : like 'ay' in "say"
 * ey : like 'ay' in "say", like 'ee' in "see"

 * ie : like 'ee' in "see"

 * oi : like 'oy' in "boy"
 * oo : like 'oo' in "food", like 'oo' in "good"
 * ou : like 'ow' in "cow", like 'oo' in "food", like 'o' in "cot"
 * ow : like 'ow' in "cow"
 * oy : like 'oy' in "boy"

 * ch : like 'ch' in "touch"
 * sh : like 'sh' in "sheep"
 * th : like 'th' in "this", like 'th' in "those"
 * gh : like 'f' in "fish"
 * ph : like 'f' in "fish"

Phrase list
''An overview of phrases can go here. Note that the phrases sections listed below are in a general order of how important they are, and how a traveler would need them. Thus, transportation comes before hotels, which in turn come before restaurants. This ordering is arbitrary but may be helpful. See also Project:Phrasebook Expedition for more details on choosing different phrases.''

''Do not translate phrases word for word; instead, give the nearest common equivalent in the language. Keep sentences polite, but as short as possible. Give alternatives if a traveler is likely to encounter them.''

The following is a phrase guide from English to English; in a real phrase guide, the second part of each entry would be in the target language, and the third part would be an English-like pronunciation suggestion.

Basics

 * Hello. : Hello. (HEH-low)
 * Hello. (informal) : Hi. (HIGH)
 * How are you? : How are you? (HOW ah YOO?)
 * Fine, thank you. : Fine, thank you. (FIGHN, then KYOO)
 * What is your name? : What is your name? (WUT iz yer NAYM?)
 * My name is ______ . : My name is ______ . (Migh NAYM iz _____ .)
 * Nice to meet you. : Nice to meet you. (NIGHSS t' meet YOO)
 * Please. : Please. (pleez)
 * Thank you. : Thank you. (THANK yoo)
 * You're welcome. : You're welcome. (yuhr WEL-kuhm)
 * Yes. : Yes. (YESS)
 * No. : No. (NOH)
 * Excuse me. (getting attention) : Excuse me. (ehkz-KYOOZ mee)
 * Excuse me. (begging pardon) : Excuse me. (ehkz-KYOOZ mee)
 * I'm sorry. : I'm sorry. (IGHM SAW-ree)
 * Goodbye : Goodbye. (GUHD-bigh.)
 * Goodbye (informal) : Bye. (BIGH)
 * I can't speak name of language [well]. : I can't speak English [well]. (IGH cant speek ING-lush [wehl])
 * Do you speak English? : Do you speak English? (doo YOO speek ING-lush?)
 * Is there someone here who speaks English? : Is there someone here who speaks English? (IZ thayr SUM-wun heer hoo speekz ING-lush?)
 * Help! : Help! (HEHLP!)
 * Look out! : Look out! (look OWT!)
 * Good morning. : Good morning. (guhd MOAN-ing)
 * Good evening. : Good evening. (guhd EEV-ning)
 * Good night. : Good night. (guhd NIGHT)
 * Good night (to sleep) : Good night. (good NIGHT)
 * I don't understand. : I don't understand. (IGH doan UHN-dur-STAND)
 * Where is the toilet? : Where is the toilet? (WAYR iz thuh TOY-leht?)

At this point, the fake phoneticizations of English are going to stop, and be replaced by ellipses.

Problems

 * Leave me alone. : Leave me alone. (...)
 * Don't touch me! : Don't touch me! (...)
 * I'll call the police. : I'll call the police. (...)
 * Police! : Police! (...)
 * Stop! Thief! : Stop! Thief! (...)
 * I need your help. : I need your help. (...)
 * It's an emergency. : It's an emergency. (...)
 * I'm lost. : I'm lost. (...)
 * I lost my bag. : I lost my bag. (...)
 * I lost my wallet. : I lost my wallet. (...)
 * I'm sick. : I'm sick. (...)
 * I've been injured. : I've been injured. (...)
 * I need a doctor. : I need a doctor. (...)
 * Can I use your phone? : Can I use your phone? (...)

Numbers

 * 0 : zero (...)
 * 1 : one (...)
 * 2 : two (...)
 * 3 : three (...)
 * 4 : four (...)
 * 5 : five (...)
 * 6 : six (...)
 * 7 : seven (...)
 * 8 : eight (...)
 * 9 : nine (...)
 * 10 : ten (...)
 * 11 : eleven (...)
 * 12 : twelve (...)
 * 13 : thirteen (...)
 * 14 : fourteen (...)
 * 15 : fifteen (...)
 * 16 : sixteen (...)
 * 17 : seventeen (...)
 * 18 : eighteen (...)
 * 19 : nineteen (...)
 * 20 : twenty (...)
 * 21 : twenty one (...)
 * 22 : twenty two (...)
 * 23 : twenty three (...)
 * 30 : thirty (...)
 * 40 : forty (...)
 * 50 : fifty (...)
 * 60 : sixty (...)
 * 70 : seventy (...)
 * 80 : eighty (...)
 * 90 : ninety (...)
 * 100 : one hundred (...)
 * 200 : two hundred (...)
 * 300 : three hundred (...)
 * 1000 : one thousand (...)
 * 2000 : two thousand (...)
 * 1,000,000 : one million (...)
 * 1,000,000,000 : one thousand million in UK, one billion in USA
 * 1,000,000,000,000 : one billion in UK, one trillion in USA
 * number _____ (train, bus, etc.) : number _____ (...)
 * half : half (...)
 * less : less (...)
 * more : more (...)

Time

 * now : now (...)
 * later : later (...)
 * before : before (...)
 * morning : morning (...)
 * afternoon : afternoon (...)
 * evening : evening (...)
 * night : night (...)

Clock time

 * one o'clock AM : one o'clock AM (...)
 * two o'clock AM : two o'clock AM (...)
 * noon : noon (...)
 * one o'clock PM : one o'clock PM (...)
 * two o'clock PM : two o'clock PM (...)
 * midnight : midnight (...)

Duration

 * _____ minute(s) : _____ minute(s) (...)
 * _____ hour(s) : _____ hour(s) (...)
 * _____ day(s) : _____ day(s) (...)
 * _____ week(s) : _____ week(s) (...)
 * _____ month(s) : _____ month(s) (...)
 * _____ year(s) : _____ year(s) (...)

Days

 * today : today (...)
 * yesterday : yesterday (...)
 * tomorrow : tomorrow (...)
 * this week : this week (...)
 * last week : last week (...)
 * next week : next week (...)

 * Sunday : Sunday (...)
 * Monday : Monday (...)
 * Tuesday : Tuesday (...)
 * Wednesday : Wednesday (...)
 * Thursday : Thursday (...)
 * Friday : Friday (...)
 * Saturday : Saturday (...)

Months
''If speakers of the language commonly use a calendar other than the Gregorian, explain it here and list its months. See Hebrew phrasebook for an example.''

 * January : January (...)
 * February : February (...)
 * March : March (...)
 * April : April (...)
 * May : May (...)
 * June : June (...)
 * July : July (...)
 * August : August (...)
 * September : September (...)
 * October : October (...)
 * November : November (...)
 * December : December (...)

Writing time and date
Give some examples how to write clock times and dates if it differs from English.

Colors

 * black : black (...)
 * white : white (...)
 * gray : gray (...)
 * red : red (...)
 * blue : blue (...)
 * yellow : yellow (...)
 * green : green (...)
 * orange : orange (...)
 * purple : purple (...)
 * brown : brown (...)

Bus and train

 * How much is a ticket to _____? : How much is a ticket to _____? (...)
 * One ticket to _____, please. : One ticket to _____, please. (...)
 * Where does this train/bus go? : Where does this train/bus go? (...)
 * Where is the train/bus to _____? : Where is the train/bus to _____? (...)
 * Does this train/bus stop in _____? : Does this train/bus stop in _____? (...)
 * When does the train/bus for _____ leave? : When does the train/bus for _____ leave? (...)
 * When will this train/bus arrive in _____? : When will this train/bus arrive in _____? (...)

Directions

 * How do I get to _____ ? : How do I get to______? (...)
 * ...the train station? : ...? (...)
 * ...the bus station? : ...the bus station? (...)
 * ...the airport? : ...the airport? (...)
 * ...downtown? : ...downtown? (...)
 * ...the youth hostel? : ...the youth hostel? (...)
 * ...the _____ hotel? : ...the _____ hotel? (...)
 * ...the American/Canadian/Australian/British consulate? : ...the American/Canadian/Australian/British consulate? (...)
 * Where are there a lot of... : Where are there a lot of... (...)
 * ...hotels? : ...hotels? (...)
 * ...restaurants? : ...restaurants? (...)
 * ...bars? : ...bars? (...)
 * ...sites to see? : ...sites to see? (...)
 * Can you show me on the map? : Can you show me on the map? (...)
 * street : street (...)
 * Turn left. : Turn left. (...)
 * Turn right. : Turn right. (...)
 * left : left (...)
 * right : right (...)
 * straight ahead : straight ahead (...)
 * towards the _____ : towards the _____ (...)
 * past the _____ : past the _____ (...)
 * before the _____ : before the _____ (...)
 * in front of the _____ : in front of the _____ (...)
 * behind the _____ : behind the _____ (...)
 * Watch for the _____. : Watch for the _____. (...)
 * intersection : intersection (...)
 * inside : inside (...)
 * outside : outside (...)
 * north : north (...)
 * south : south (...)
 * east : east (...)
 * west : west (...)
 * uphill : uphill (...)
 * downhill : downhill (...)

Taxi
get to _____? (...)
 * Taxi! : Taxi! (...)
 * Take me to _____, please. : Take me to _____, please. (...)
 * How much does it cost to get to _____? : How much does it cost to
 * Take me there, please. : Take me there, please. (...)

Lodging

 * Do you have any rooms available? : Do you have any rooms available? (...)
 * How much is a room for one person/two people? : How much is a room for one person/two people? (...)
 * Does the room come with... : Does the room come with... (...)
 * ...bedsheets? : ...bedsheets? (...)
 * ...a bathroom? : ...a bathroom? (...)
 * ...a telephone? : ...a telephone? (...)
 * ...a TV? : ...a TV? (...)
 * May I see the room first? : May I see the room first? (...)
 * Do you have anything quieter? : Do you have anything quieter? (...)
 * ...bigger? : ...bigger? (...)
 * ...cleaner? : ...cleaner? (...)
 * ...cheaper? : ...cheaper? (...)
 * OK, I'll take it. : OK, I'll take it. (...)
 * I will stay for _____ night(s). : I will stay for _____ night(s). (...)
 * Can you suggest another hotel? : Can you suggest another hotel? (...)
 * Do you have a safe? : Do you have a safe? (...)
 * ...lockers? : ...lockers? (...)
 * Is breakfast/supper included? : Is breakfast/supper included? (...)
 * What time is breakfast/supper? : What time is breakfast/supper? (...)
 * Please clean my room. : Please clean my room. (...)
 * Can you wake me at _____? | Can you wake me at _____? (...)
 * I want to check out. : I want to check out. (...)

Money

 * Do you accept American/Australian/Canadian dollars? : Do you accept American/Australian/Canadian dollars? (...)
 * Do you accept British pounds? : Do you accept British pounds? (...)
 * Do you accept credit cards? : Do you accept credit cards? (...)
 * Can you change money for me? : Can you change money for me? (...)
 * Where can I get money changed? : Where can I get money changed? (...)
 * Can you change a traveler's check for me? : Can you change a traveler's check for me? (...)
 * Where can I get a traveler's check changed? : Where can I get a traveler's check changed? (...)
 * What is the exchange rate? : What is the exchange rate? (...)
 * Where is an automatic teller machine (ATM)? : Where is an automatic teller machine (ATM)? (...)

Eating

 * A table for one person/two people, please. : A table for one person/two people, please. (...)
 * Can I look at the menu, please? : Can I look at the menu, please? (...)
 * Can I look in the kitchen? : Can I look in the kitchen? (...)
 * Is there a house specialty? : Is there a house specialty? (...)
 * Is there a local specialty? : Is there a local specialty? (...)
 * I'm a vegetarian. : I'm a vegetarian. (...)
 * I don't eat pork. : I don't eat pork. (...)
 * I don't eat beef. : I don't eat beef. (...)
 * I only eat kosher food. : I only eat kosher food. (...)
 * Can you make it "lite", please? (less oil/butter/lard) : Can you make it "lite", please? (...)
 * fixed-price meal : fixed-price meal (...)
 * a la carte : a la carte (...)
 * breakfast : breakfast (...)
 * lunch : lunch (...)
 * tea (meal) : tea (...)
 * supper : supper (...)
 * I want _____. : I want _____. (...)
 * I want a dish containing _____. : I want a dish containing _____. (...)
 * chicken : chicken (...)
 * beef : beef (...)
 * fish : fish (...)
 * ham : ham (...)
 * sausage : sausage (...)
 * cheese : cheese (...)
 * eggs : eggs (...)
 * salad : salad (...)
 * (fresh) vegetables : (fresh) vegetables (...)
 * (fresh) fruit : (fresh) fruit (...)
 * bread : bread (...)
 * toast : toast (...)
 * noodles : noodles (...)
 * rice : rice (...)
 * beans : beans (...)
 * May I have a glass of _____? : May I have a glass of _____? (...)
 * May I have a cup of _____? : May I have a cup of _____? (...)
 * May I have a bottle of _____? : May I have a bottle of _____? (...)
 * coffee : coffee (...)
 * tea (drink) : tea (...)
 * juice : juice (...)
 * (bubbly) water : water (...)
 * water : water (...)
 * beer : beer (...)
 * red/white wine : red/white wine (...)
 * May I have some _____? : May I have some _____? (...)
 * salt : salt (...)
 * black pepper : black pepper (...)
 * butter : butter (...)
 * Excuse me, waiter? (getting attention of server): Excuse me, waiter? (...)
 * I'm finished. : I'm finished. (...)
 * It was delicious. : It was delicious. (...)
 * Please clear the plates. : Please clear the plates. (...)
 * The check, please. : The check, please. (...)

Bars

 * Do you serve alcohol? : Do you serve alcohol? (...)
 * Is there table service? : Is there table service? (...)
 * A beer/two beers, please. : A beer/two beers, please. (...)
 * A glass of red/white wine, please. : A glass of red/white wine, please. (...)
 * A pint, please. : A pint, please. (...)
 * A bottle, please. : A bottle, please. (...)
 * _____ (hard liquor) and _____ (mixer), please. : _____ and _____, please. (...)
 * whiskey : whiskey (...)
 * vodka : vodka (...)
 * rum : rum (...)
 * water : water (...)
 * club soda : club soda (...)
 * tonic water : tonic water (...)
 * orange juice : orange juice (...)
 * Coke (soda) : Coke (...)
 * Do you have any bar snacks? : Do you have any bar snacks? (...)
 * One more, please. : One more, please. (...)
 * Another round, please. : Another round, please. (...)
 * When is closing time? : When is closing time? (...)
 * Cheers! : Cheers! (...)

Shopping

 * Do you have this in my size? : Do you have this in my size? (...)
 * How much is this? : How much is this? (...)
 * That's too expensive. : That's too expensive. (...)
 * Would you take _____? : Would you take _____? (...)
 * expensive : expensive (...)
 * cheap : cheap (...)
 * I can't afford it. : I can't afford it. (...)
 * I don't want it. : I don't want it. (...)
 * You're cheating me. : You're cheating me. (...)
 * I'm not interested. : I'm not interested. (..)
 * OK, I'll take it. : OK, I'll take it. (...)
 * Can I have a bag? : Can I have a bag? (...)
 * Do you ship (overseas)? : Do you ship (overseas)? (...)
 * I need... : I need... (...)
 * ...toothpaste. : ...toothpaste. (...)
 * ...a toothbrush. : ...a toothbrush. (...)
 * ...tampons. : ...tampons. (...)
 * ...soap. : ...soap. (...)
 * ...shampoo. : ...shampoo. (...)
 * ...pain reliever. (e.g., aspirin or ibuprofen) : ...pain reliever. (...)
 * ...cold medicine. : ...cold medicine. (...)
 * ...stomach medicine. : ...stomach medicine. (...)
 * ...a razor. : ...a razor. (...)
 * ...an umbrella. : ...an umbrella. (...)
 * ...sunblock lotion. : ...sunblock lotion. (...)
 * ...a postcard. : ...a postcard. (...)
 * ...postage stamps. : ...postage stamps. (...)
 * ...batteries. : ...batteries. (...)
 * ...writing paper. : ...writing paper. (...)
 * ...a pen. : ...a pen. (...)
 * ...English-language books. : ...English-language books. (...)
 * ...English-language magazines. : ...English-language magazines. (...)
 * ...an English-language newspaper. : ...an English-language newspaper. (...)
 * ...an English-English dictionary. : ...an English-English dictionary. (...)

Driving

 * I want to rent a car. : I want to rent a car. (...)
 * Can I get insurance? : Can I get insurance? (...)
 * stop (on a street sign) : stop (...)
 * one way : one way (...)
 * yield : yield (...)
 * no parking : no parking (...)
 * speed limit : speed limit (...)
 * gas (petrol) station : gas station (...)
 * petrol : petrol (...)
 * diesel : diesel (...)

Authority

 * I haven't done anything wrong. : I haven't done anything wrong. (...)
 * It was a misunderstanding. : It was a misunderstanding. (...)
 * Where are you taking me? : Where are you taking me? (...)
 * Am I under arrest? : Am I under arrest? (...)
 * I am an American/Australian/British/Canadian citizen. : I am an American/Australian/British/Canadian citizen. (...)
 * I want to talk to the American/Australian/British/Canadian embassy/consulate. : I need to talk to the American/Australian/British/Canadian embassy/consulate. (...)
 * I want to talk to a lawyer. : I want to talk to a lawyer. (...)
 * Can I just pay a fine now? : Can I just pay a fine now? (...)

zh:Project:會話集條目模板

title: Wikivoyage:Phrasebook article template


text:
Wikivoyage:Plunge forward

Being a traveller requires courage, self-confidence, passion and perseverance. Being a Wikivoyager requires the same qualities. We expect you to plunge forward into the task of authoring, editing, and illustrating articles on Wikivoyage. You can edit any article on Wikivoyage (even this one!), and we hope that you do. We need your knowledge, your experience, your talent, and your attention.

Plunging forward means:

 * Being assertive. Your knowledge and experience count! There are few (if any) "travel experts" working on Wikivoyage (if they exist anywhere), so don't worry about not being good enough. We want your help.
 * Experimenting. There's really not much permanent damage you can do to Wikivoyage. If things get really broken, other Wikivoyagers will come in and fix them.
 * Doing what's OK right now. You don't have to create a perfect, fully-formed article the first time around. Just make a quick contribution or add a basic outline if an article about your favorite town that doesn't yet exist. Get your thoughts down and let others expand on them. That's how a wiki works!
 * Go ahead. You have as much right to add, change and improve anything you see on Wikivoyage as anyone else has. You don't need to ask anyone or even to have an account, if you can fix or improve anything. If you make a change, other people here will often help. So don't bother asking whether it's all right to plunge in – it probably is!

So plunge forward! You will enjoy it!

...But don't be reckless!!
Don't be afraid of making mistakes, but at the same time, be aware that there are certain cases where you might find that your edit receives extra scrutiny or may be reverted by others:

 * Changes to policy. Pages in the Wikivoyage namespace represent agreed-upon consensus of the editor community, so non-trivial changes should be discussed first on the policy's talk page.
 * Changes to Wikivoyage style. Wikivoyage uses the same standard section headings for all articles, so changes to top-level headings (for example, changing "Sleep" to "Accommodation") will normally be reverted.
 * Changes to high-visibility articles. An article like United States of America, or any of the star articles, is the result of potentially thousands of edits by hundreds of users, so edits to these articles will receive more scrutiny than those made to less prominent articles.
 * Changes to regional organization. A lot of effort goes into splitting up huge cities into districts, or splitting up larger regions into smaller ones, so in cases where the regional breakdown was the result of lengthy discussion changes should usually be proposed on the article talk page first.
 * Controversial edits. Political disputes, promotional material, and personal causes don't belong in a travel guide.
 * Changing banners. Unlike other language Wikivoyages, banner changes need to be discussed on the talk page first. Exceptions are when it's changing it to fit our banner policy, 7:1 or when the banner is just in the completely wrong location

While everyone is encouraged to plunge forward, if someone else undoes your edit, you can view the article's history; there will usually be an explanation in the edit summary to indicate why the edit was reverted. If you still don't understand, ask for clarification on the article's talk page.

title: Wikivoyage:Plunge forward


text:
Wikivoyage:Poland Expedition

The Poland Expedition is a Wikivoyage Expedition to promote and coordinate collaboration to improve Wikivoyage's articles pertaining to the European country Poland.

Goals
The main goal of the Poland Expedition is to achieve Guide status for the Poland article. In pursuit of this goal, we must:

 * 1) Improve the quality of the Poland article itself, by adding images, graphics, and prose
 * 2) Improve all linked destinations to at least usable status

Linked destinations
Featured collaboration: Kraków

 * We need to figure out which districts to include.
 * We need to move listings to the respective districts and only highlighting the most important listings.
 * Overall, rewrite information that is already in the guide to make it easier and more enjoyable to read.
 * In district articles, we need to add specific information to listings (i.e. addresses, phone numbers, prices, etc.).
 * Add photos, images, and maps.

By no stretch of the imagination could one Kraków consider Kraków to be near "guide" status, however, with a little sweat and likely a lot of blood, it could be accomplished.

Article status chart
The following chart shows the current status of Poland's most important destinations, which must be at least usable status in order for the Poland article to achieve guide status.

Expedition members

 * (WT-en) Sapphire • (Talk) • 20:14, 11 March 2008 (EDT)
 * (WT-en) Texugo 05:47, 13 March 2008 (EDT)

title: Wikivoyage:Poland Expedition


text:
Wikivoyage:Polish Wikivoyage Expedition

The Polish Wikivoyage Expedition is an expedition to create a Polish language version of Wikivoyage.

For more information on multilingual Wikivoyage policy, please see Project:Language version policy.

Rationale
The WikiPedia:Polish language is spoken by 46 million people worldwide. Providing a Polish language Wikivoyage would make travel information easier to access for those people. In addition, Polish speakers can add information in their own language which can be translated into other languages.

Goals
This Expedition has the following goals:

 * To collect a good base of Polish-speaking users willing to take this project further.
 * To choose a go-between who can keep users on the English-language site up-to-date on developments on Polish Wikivoyage, and vice-versa
 * To translate the interface files for Wikivoyage into Polish
 * To launch the new Polish-language Wikivoyage.
 * To translate the pages and create the infrastructure necessary to make Polish Wikivoyage useful and friendly for new Polish-speaking contributors.
 * To make Polish Wikivoyage an integrated part of the Wikivoyage family.

Steps
The Language version policy lists the steps necessary to get a Polish-language Wikivoyage in place.

Gathering a team of users
To get this project started, we need at least 5 Polish-speaking users willing to help start the Polish Wikivoyage. This means helping to translate the interface files, create content on the new Wikivoyage, and to create the necessary infrastructure to make Wikivoyage welcoming and useful for the next wave of contributors.

If you're interested, please create a user account on this (English) Wikivoyage, and sign the list below. To sign, edit this page and just type ~ 4 times, like "~".

 * (WT-en) Michal 08:58, 10 Oct 2004 (EDT)
 * (WT-en) Wikipawel 08:27, 29 Jan 2006 (EST)
 * (WT-en) S0568354 07:58, 12 Feb 2006 (EST)
 * (WT-en) MD 11:48, 23 Feb 2006 (EST)
 * (WT-en) JanSlupski 22:08, 23 February 2006 (EST)

More than 5 users are welcome to sign up, but we need at least 5 to get started.

Go-between
Part of the process of having a language version is having a single person responsible for reporting on issues in the larger Wikivoyage community to the Polish language version, and reporting on issues in the Polish language version to the larger community.

The go-between should be conversant in English and Polish, experienced with Wikivoyage in other languages, and willing to make monthly reports and be an active participant in the Polish Wikivoyage community.

Previous language versions have picked a go-between by voting. See Project:Romanian Wikivoyage Expedition and Project:French Wikivoyage Expedition for details.

Language interface file
MediaWiki, the software that runs Wikivoyage, uses a language interface file to make the links and names and prompts and stuff readable in other languages. We need to customize a new version to work for Polish Wikivoyage.

We can collaboratively do this at Project:LanguagePl.php. It's started off with the Wikipedia language file, and we can use the English Project:Language.php file as a reference for things that need to be changed. It's mostly just changing the name of the site (Wikipedia -> Wikivoyage), the name of the license, and the names of some important pages.

Wikivoyage in Polish has started

 * March 31, 2006, Polish Wikivoyage has been launched!

title: Wikivoyage:Polish Wikivoyage Expedition


text:
Wikivoyage:Portuguese Wikivoyage Expedition

This page intends to organize efforts to make a Portuguese version of Wikivoyage. Until the version is created, all discussions should be in English, so others Wikivoyagers may join the discussion.

Rationale
Portuguese (português) is a Romance language spoken in 23 countries, including Portugal, Brazil, Angola, Mozambique and East Timor. With more than 200 million native speakers, Portuguese is the fifth or sixth most popular mother-tongue language in the world (depending on how you count), and the second-largest Romance language, outnumbered only by Spanish.

These speakers could be well-served by travel guides in their own native language. In addition, contributions by Portuguese speakers could be translated to existing Wikivoyage language versions to give better local coverage of Portuguese-speaking destinations.

Goals

 * To create and maintain a Portuguese-language version of Wikivoyage.

Steps
According to the language version policy, these are the steps needed to start the new Wikivoyage version.

 * 1) Get three (3) Portuguese-speaking users to commit to helping with the project. Status: Complete. There are more than 3 users signed up below.
 * 2) Choose a go-between who can keep users on the other Wikivoyage sites up-to-date on developments on Portuguese Wikivoyage, and vice-versa. Status: Blocking . See below.
 * 3) To translate the interface file for Wikivoyage into Portuguese. Status: Unknown. One or more of the Expedition members need to review and approve the interface file.
 * 4) To launch the new Portuguese-language Wikivoyage. Status: Pending. Waiting for the above steps to be finished.
 * 5) To translate the pages and create the infrastructure necessary to make Portuguese Wikivoyage useful and friendly for new Portuguese-speaking contributors. Status: Pending launch. This has been prematurely started on the English-language Wikivoyage; the above steps should be finished first.
 * 6) To make Portuguese Wikivoyage an integrated part of the Wikivoyage family with frequent go-between reports and good interlanguage links. Status: Pending launch.

Members
Expedition members are listed below. You can volunteer to help by creating a user account on English Wikivoyage (see Project:how to create a user account) and adding your signature below using four tildes ( * --~ ).

 * ---(WT-en) Avsa
 * ---(WT-en) Paulino Michelazzo
 * ---(WT-en) Fábio Soldá
 * ---(WT-en) Livia Luccas
 * ---(WT-en) Guaka 15:59, 21 Jun 2005 (EDT)
 * ---(WT-en) Rmx
 * ---(WT-en) Erico Koerich
 * ---(WT-en) Robert Friedrick Martim

Go-between
The go-between will be responsible for keeping Portuguese Wikivoyage users informed of developments on other language versions and vice versa. They should:

 * 1) Be able to read and understand Portuguese and write Portuguese well enough to be understood.
 * 2) Be able to read and understand English and write English well enough to be understood.
 * 3) Be familiar with Wikivoyage's community policies and manual of style.

The main responsibilities are to be a point of contact between Portuguese Wikivoyage and the English one; principly this means making a go-between report once a month on the state of Portuguese Wikivoyage. Most go-between reports are a few sentences left in the Project:Logbook.

Choosing a go-between has been left up to the Expedition members for previous language Expeditions. Most have used a voting system (see Project:German Wikivoyage Expedition) but for some a volunteer has stepped forward and taken the job without opposition.

Translations
The interface file for Portuguese needs to be matched to Wikivoyage. References to Wikipedia should be changed to and reference to the GFDL should be changed to the CC by-sa 1.0.

Expedition members can edit the file here: Project:LanguagePt.php. It may be worthwhile to compare here: Project:Language.php for the English version.

Launch
Launching the new site will be extremely quick once the above two steps are finished.


text:
Wikivoyage:Go-between reports/Portuguese/Portuguese Wikivoyage Report for 2 April 2006

Progress in general

 * Article count: 154. Mostly outlines but a few significant contributions have been made and there are 3 new usable articles (although we haven't established article rating there yet) and a few new images too.
 * Translation of core policies and help pages has advanced and is almost finished. A Translation Expedition has been started but had no concrete results yet.
 * Had our first deleted images (copyvios) after the due voting
 * Detected a few positive reactions towards the Portuguese-language version on weblogs and Linux communities but nothing on the big media yet.
 * Decided to postpone upload of country templates until they get proper discussion

New users
19 new registered users (58 now, a 50% increase) but only 2 or 3 making actual contributions and only on specific articles (except for the very helpful User:Episteme who's been interlanguage-ing articles in all versions). Apparently there are no regular anonymous contributors.

Focus during the next month

 * Translate more of the Manual of style
 * Keep on promoting pt: especially in Wikipedia (I'm using a special MediaWiki template for that there) and towards lusophone countries other than Brazil
 * Bulk upload of flags to Wikivoyage Shared would still be useful, though I don't know how to do it myself

Special issues

 * When interlanguage links to a pt: user page are placed on other language versions, the software won't suppress the namespace only for Portuguese. Check it (WT-en) here and (WT-es) here
 * I've tried editing the system message but can't make a wiki link out of the html on link on the top of pt:Especial:Watchlist
 * Fixed. (WT-en) Ricardo (Rmx) 18:22, 10 April 2006 (EDT)

Conclusion

 * Pt: is operating quite smoothly
 * There is still no real community in activity but as the number of users and articles increases, we can expect to have one.

Comments
Thanks for your incoming comments. (WT-en) Ricardo (Rmx) 17:14, 2 April 2006 (EDT)

 * First, thanks for your excellent work on pt:. I'm very proud and appreciative of what you've done there, and I think pt: is a great example of a Wikivoyage language version.

 * Second, please hang in there. It takes time to build up a new wiki. When en: started, we had an initial rush and some frenetic activity, and then about 3-6 months of torpor before we started growing again. New language versions can kind of benefit from each others' experience, but I think the main thing is persistence and patience.

 * Lastly, if I recall correctly User:(WT-en) Jpatokal said something about doing a mass upload of flags and maps to shared. Maybe check with him? --(WT-en) Evan 09:55, 5 April 2006 (EDT)

 * Mr. Roboto is uploading maps and flags right now. It should be finished by the end of today.  (WT-en) Jpatokal


text:
Wikivoyage:Go-between reports/Portuguese/Portuguese Wikivoyage Report for 2 March 2006

Progress in general
Although we had 7 people signed up to help with with the Portuguese Wikivoyage Expedidition, only two of them (myself included) have in fact answered to that call and started working on pt:, even though I've sent them e-mails and left messages on their user pages. Nevertheless, significant progress has has been achieved in this first month of this language version of Wikivoyage.

We have put a lot of effort into creating the the basic set of guidelines for the contributors' work. This means translating important bits of the manual of style (including templates) and setting up some of the most relevant policies. If you check our help page you'll see that a lot of stuff already has its Portuguese version. Unfortunately, there hasn't been much discussion about those pages, which we expect to get when pt: achieves a larger user base.

Copyright has also been a major issue: lots of people tend to copy-and-paste articles from Wikipedia and/or other websites. We'd probably benefit from having more users that understand Wikivoyage's copyleft in this case too.

New contributors
We currently have 41 registered users and counting. Only 4 or 5, however, have been contributing on a more or less erratic basis. Apparently there are no regular anonymous contributors.

Focus during the next month

 * Translate/set up more policies (including image deletion), help pages and so forth
 * Promote pt: - we understand that more collaborators should lead to a better guide
 * Try to get someone to run a bot to upload country templates and flags (or will those be placed in Wikivoyage Shared soon?)

Special issues

 * In the footer where it says "Based on work by Wikivoyage user(s)", the names that come after this bit are conected by the English word "and" (Evan and Rmx and...) instead of Portuguese "e". I've tried changing the "and" entry on Allmessages to "e" but that didn't work, so I don't know how to solve it.

Conclusion
Portuguese wikivoyage seems to have great potential for organised growth but won't go too far if we don't get more people working on it.

Comments
Your comments and suggestions will be appreciated. (WT-en) Ricardo (Rmx) 14:02, 2 March 2006 (EST)

 * First, pt: has been having a fantastic first month -- I'm really excited about it.

 * As for flags, I'm going to try to upload the OpenClipart.org flag collection to shared real soon now.

 * For getting more contributors, all I can suggest is looking at Project:Ways to promote Wikivoyage, being patient, and keeping momentum going. I also might point out that having some time to acclimatize new members is a good way to build a sustainable community.

 * As to the "and" thing... I'll take a look. Changing pt:MediaWiki:And should work, but... oh, wait, now that I think of it, it may not. I'll see if I can fix things on the server end. --(WT-en) Evan 14:22, 2 March 2006 (EST)

 * OK, I think it's fixed. Let me know. --(WT-en) Evan 14:25, 2 March 2006 (EST)

 * Fixed it is. Thanks for your comments and encouragement. (WT-en) Ricardo (Rmx) 14:30, 2 March 2006 (EST)