text:
Wikivoyage:RDF Expedition Collection of wanted features

This is step 1 of the RDF Expedition.

Here go brain-storming like collections of all features that would be nice to have and maybe could be provided by RDF meta data. You should not too much concern about how to build them, just enlist what you ever have dreamed about. Try to describe your wishes as exact as possible. Everybody is welcome to contribute here.

If you already have some ideas about how to represent the information, note that on the step 2 page.

License info
(sweapt in from Project:RDF)

Adding multi-licensing information using "cc:licence".

Notes about derivated Work
(swept in from Project:RDF)

Noting that a Wikivoyage article is derived from another article on the Web (like the CIA Factbook, say) and information about who wrote it.==

Listing related articles
(sweapt in from Project:RDF)

Articles about similar places, linking destinations with the phrasebook for the language spoken there, linking itineraries to a destination guide==

Describing places
(swept in from Project:RDF)

Are they cities, countries, regions or whatever?

Geographical relationships
(swept in from Project:RDF)

Describing geographical relationships of some place to each other (nearby cities, bordering countries, ...)

 * bordering countries : Countries that have a political border. OK.
 * bordering regions : If some regions realy border to each other, OK.
 * partly overlapping regions : Regions of a country may overlap. Should this be treated as bordering or separately?
 * nearby cities of same importance : Are San Francisco and Los Angeles nearby cities by this meaning?
 * geographicaly nearby cities : Then Long Island and NYC are nearby cities.
 * natural park : Is a natural park nearby to the region(s) it is in?

Article status
(sweapt in from Project:RDF)

Quality: maybe: alpha, beta, stub, (ok), good, excellent, outstanding.

Completeness: maybe a level per section: poor ... (ok) ... rich.

Precision of geographical coordinates: maybe: radius = kilometers (the point is surely within this radius)

Quality rating: maybe: rating = percent (just xx % of the articles are of better quality)

Geo-spatial lat/long information
(swept in from Project:RDF)

 * including GPS data
 * lat/long information for a point, like a attraction.
 * Several latitude/longitude points connected to a area, like a region or country. Might be useful for automatic Interface with mapping sites like Google Maps or Yahoo Maps.
 * Several lat/long points connected to a line. Itineraries like hiking trails maybe need an option to download these points to a GPS device.

"Bread-crumb" navigation
(swept in from Project:RDF)

Building "Bread-crumb" navigation, like "North America > Canada > Quebec > Montreal".

''Should this apply to the geographical hierarchy only, or even for for other travel topics or meta-articles? -- (WT-en) Hansm''

Presentation for certain kinds of articles
(swept in from Project:RDF)

Special presentation for certain kinds of articles (travel topics, itineraries, destination guides) and destinations (cities, countries, regions)

Presentation for certain groups of readers
Special presentation for certain groups of readers addressed by that article (fishing, backpackers, buisiness travelers, ...).

"Clusters" of articles
(swept in from Project:RDF)

Organizing "clusters" of articles automatically (say, if you wanted to download Italy and all cities and regions in that country). Every point in the geagraphical hierarchie tree should be able to be choosen as the top of a custom guide (say, a Toscana guide).

Maybe some kind of grain or level is possible. If I only traverse some region by bus, I'm not interested in all details of that region, but only in perhaps basic information of larger cities and the region article itself.

Should also work for itinaries as top of the hierarchical tree.

There might be some general travel topics that should be included into a custom guide, like Tips for travel in developing countries into a Peru guide. Maybe only special sections of it? And, of course, the phrasebook in a certain language (say, French) is an other general article that could be part of many different guides.

Interface with mapping sites
(swept in from Project:RDF)

Automatic interface with mapping sites like Google Maps or Yahoo Maps.

Index lists for print versions
This should include alternative spellings or names, famous sights not treated in an own article and usual nouns in names (mountain -> Monte ...).

(WT-en) Unger has manualy made an index list for places in Egypt on de:. A partly translated version is here. For several reasons, this might be used as a reference for this feature:
 * 1) Names had to be romanized, thus several usual spellings are possible.
 * 2) We use diacritics on de:, so we have to care about an alphabetical order. Unger has maped all characters with diacritics onto their non-diacritic version. This would be one way, the other one would be to keep diacritics, but define an alphabet that includes diacritical characters.
 * 3) The Arabic article al is part of many names, but should be ommited for the index list.
 * 4) The Arabic word Om or Umm, respectively, seems to be part of many names. Instead of giving two different spellings for each place which starts with Om, a general redirection "Om ... -> Umm ..." is given in the index.
 * 5) Some names are ambiguous and need to be resolved.
 * 6) Monasteries start with the word Deir in their name. This might be important since somebody might search for Monastery of Abu Mina, what is perhaps the name he knows, but doesn't know the Arabic name Deir Abu Mina.
 * 7) Many sights are better known than the city they belong to, thus even some sights with no own article should be indexed.

Additional remark on (3): One should be able to mark name components, which should not considered for alphabetic sorting. This concerns mostly articles (en: the; de: der, die, das, ar: el-). For instance, _The_ Tower Bridge should be written as "The Tower Bridge" and sorted as "Tower Bridge". (WT-en) Unger 04:36, 22 Nov 2005 (EST)

Searchable keywords
It should be possible to limit a search to titles and keywords. Keywords can be marked words of the article plus just metainfo, marked as keyword.

Sequence of Articles for print versions
In Order to print a real travel guide, we need to provide some information about the sequence of articles. We have to linearize a net.

Customized index lists on the fly
For example, I send a search queue for all scientific museums in northern Italy and want to get a list of them imediately.

Climatical searching criteria
What would be the places in Europe warmer than 10°C average in january? - Which of them is the closest on to me?

Finding nearby places that hold certain criteria
Where is the next golf park?

Navigation
At the top of an article (not at the bottom like with categories in Wikipedia) there should be links (one or more) to the "parent" articles. Or, maybe to the "main" article of the parent category of the current article.

''This is the same as. Or do you see differences? ((WT-en) Hansm)''

It's an example of how to use this hierarchical structure. I'd suggest to have a link on each article page which has a fixed position in the page's layout and points to a "parent" article or several parent articles. --(WT-en) Roland2 15:06, 22 Nov 2005 (EST)

Queries
Examples:

 * What Austrian stubs have been created since my last login?

Opening hours
What museum has opened now? Where can I have a meal in Paris on Friday at 2 o'clock in the morning?

Wanted information
So I've just arrived in the center of London: What information about the center of london is missing in wikivoyage? What missing information has been requested by other readers of wikivoyage?

Categories
Attributes which could be represented by categories:

"thermal spring", "coal mine", "Celtic place of warship", "carnival procession", "national park", "elephant riding", "church", "airport", "suited for children", "suited for disabled people", ...

''What is the goal you want to explain here? -- (WT-en) Hansm''

These are examples to discuss if a certain type of category will/should be supported or not:

 * 1) The example "elephant riding" could raise the question if there should be categories "elephant riding", "horse riding", "camel riding" or if there should be hierarchical categories like "riding > elephant", "riding > horse" and so on. If there are no category pages, I think it will not be easy to build a hierarchical structure of attributes (formerly "categories").
 * 2) The example "suited for children" raises the question if "suited for children" were a useful attribute or whether the attribute "suited for children" should be expressed by a combination of specific attributes like "diaper changing table available", "childcare", "playground" etc.

--(WT-en) Roland2 15:26, 22 Nov 2005 (EST)


text:
Wikivoyage:RDF Expedition Defining templates

This is step 3 of the RDF Expedition.

First things first. This step is still closed.

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


text:
Wikivoyage:RDF Expedition Example 2 for index

Example for an idex list with diacritics. See also RDF Expedition Example for index


text:
Wikivoyage:RDF Expedition Example for index

A copy of de:Ägypten/Orte in Ägypten. Only those things that are necessary to understand the idea behind the list have been translated.


text:
Wikivoyage:RDF Expedition Representation of Information

This is step 2 of the RDF Expedition.

How could information be representated necessary for the aims declared in step 1?

Here we have to think about the RDF information itself: How could it be represented? What is an appropriate vocabulary? What vocabulary is already defined elsewhere? What do we have to define specialy for Wikivoyage? Find good definitions. Where should the information go? Maybe many more questions.

Step 2 is probaby the hardest one, except step 4. If you contribute here, you should have read RDF and Turtle RDF.

How to proceed
Try to find out what kind of information is needed for each goal listed in section (e.g. "Describing places"). Find a handy name for that kind of information (e.g. "placetype"). The only use of that name is that we can talk about. It needs not to be any kind of official. Add this name as a new subsection into section. Describe it precisely in this subsection. Add the name of the information (i.e. "placetype" in our example) to the list of needed information below the header of the coresponding goal in section (i.e. "Describing places" in our example).

If you allready have an idea about an exact vocabulary that is defined somewhere, make a proposal in the corresponding subsection below (i.e. "placetype" in our example).

What Information for which goal?
Here is a list of wishes explained in step 1. The sequence has been changed in order to group related wishes. This list should be kept synchronous with the wishes of step 1. If you add some new wish, try to put it below an appropriate header or open a new one.

Here, we think about the information needed. Do not describe the wish itself again, this has to be done on the step 1 page. The aim of this section is to decide what kind of information is needed for each wish. Maybe, we find out here that some wishes are too complicated to realize.

Please sign with ~ in the discussion part of each wish.

License info
Information needed:

Discussion:

Notes about derivated Work
Information needed:

Discussion:

Categories
Information needed:

Discussion:

Article status
Information needed:

Discussion:

Describing places
Information needed:
 * placetype

Discussion:

Probably, no more info needed. -- (WT-en) Hansm 08:51, 22 Nov 2005 (EST)

Presentation for certain kinds of articles
Information needed:

Discussion:

Presentation for certain groups of readers
Information needed:

Discussion:

Geo-spatial lat/long information
Information needed:

Discussion:

Climatical searching criteria
Information needed:

Discussion:

Listing related articles
Information needed:

Discussion:

Geographical relationships
Information needed:
 * isnearby
 * overlaps ?

Discussion:

"Bread-crumb" navigation
Information needed:
 * isPartOf

Discussion:

The subject might be part of more than one objects, but usually the object should be in the next higher hierarchical level.

Navigation
Information needed:

Discussion:

"Clusters" of articles
Information needed:
 * hasPart
 * hasSupplement

Discussion:

Clustering is done from top to bottom. So, the top article has to define all its parts on the next lower hierarchical level. -- (WT-en) Hansm 14:02, 22 Nov 2005 (EST)

Index lists for print versions
Information needed:
 * indexAs
 * dontIndex
 * wildcardIndex
 * useAlphabet
 * omitInIndex

Discussion:

In printed versions, the index must point to the beginning of a topic. If the topic is an article, this is simply the beginning of the article, no matter where in the article the indexing information is given. But the topic may also be some place with no own article. In that case, it is important where in the article the indexing info stands. For example, the sphinx has no article for itself. So, the indexAs information must be put close to the point where the sphinx is described in an article of Gizeh. That means that indexes must be able to point to sections or subsections of articles.

Different spellings can be marked by several indexAs info. If the article's name should not be indexed (default is indexing), you can mark that with the dontIndex info. Using a combination of indexAs and dontIndex, you can change the index. For example, the article's name is "Scottish Highland", but it must be indexed simply as "Highland" since the adjective "scottish" doesn't make sense in a Scottland guide.

The wildcardIndex and omitInIndex info must be put into the country article or on a special contol page.

UseAlphabet is probably a wiki-wide controlpage that defines the alphabetical order for all indexes made in that wiki.

-- (WT-en) Hansm 14:46, 22 Nov 2005 (EST)

Sequence of Articles for print versions
Information needed:
 * printBefore
 * printAfter
 * dontPrint

Discussion:

Generaly, linearisazion should be done following the sequence in which articles of the same hierarchical level are listed in the higher lever article. For example, regions listed in the "Regions" section of a coutry article are printed in that order. Each region again defines the order of its subregions. The next region begins after the last subregion of the preceeding region.

PrintBefore and PrintAfter can be used to change that default order.

Is dontPrint necessary?

Customized index lists on the fly
Information needed:

Discussion:

Interface with mapping sites
Information needed:

Discussion:

Searchable keywords
Information needed:

Discussion:

Finding nearby places that hold certain criteria
Information needed:

Discussion:

Queries
Information needed:

Discussion:

Opening hours
Information needed:

Discussion:

Wanted information
Information needed:

Discussion:

placetype
Describes the kind of a place (not article). Possible values are: "country", "region", "hugecity", "bigcity", "smallcity", "district", "natpark", ...?

isPartOf
A predicate. Says that subject is part of object.

Defined by the Dublin Core: dcterms:isPartOf

Discussion:

Do subj. and obj. have to be places?

hasPart
A predicate. Says that subject has object as part. S and O can be articles or sections of articles.

Defined by the Dublin Core.

hasSupplement
Like hasPart, but optional. A phrasebook could be a supplement that some travellers don't need in their custom guide.

isnearby
A symetrical predicate. Says that subject is nearby to object. Should by applied to places only.

overlaps
A symetrical predicate. Says that subject and object overlap. Both, subj. and obj. should be regions.

indexAs
Predicate. S is a string, O is an article or a section of an article.

The S is the text that shows up in the index, the O is where it points to.

dontIndex
Predicate. S is an article, needs no O.

Do not index the article's name.

wildcardIndex
Predicate. S and O are strings.

Provides info for an general redirect. S is redirected to O. For example, you can say: '"Om " wildcardIndex "Umm "' what means that all names starting with "Om " can be found in the index with "Umm " instead.

useAlphabet
Probably not an RDF element. A list of characters or character combinations that defines an alphabetical order.

omitInIndex
Predicate. S is a string, no O needed.

The string has to be omitted in indexed names. For example, El-Qalaa would show up in the index as Qalaa if you define '"El-" omitIndex'.

printBefore
Predicate. S is an article, O is an article or pseudo-article that marks the begin of a sequence.

Defines the sequence in linearization for printed versions.

printAfter
Predicate. S is an article, O is an article or pseudo-article that marks the end of a sequence.

Defines the sequence in linearization for printed versions.

dontPrint
Predicate. S is an article, no O needed.

Do not print that article at all.


text: Wikivoyage:Recent changes help

title: Wikivoyage:Recent changes help


text:
Wikivoyage:Recent changes patrol

Recent Changes Patrol is a utility that displays recent changes that require a review by another user.

Use
If your account has patroller rights, a red exclamation mark (" ! ") appears next to the line for any edit that hasn't been reviewed by another editor. If you see this mark, you will see a [ Mark as patrolled ] link when you view the diff for that edit. If you find that edit in order, you may click on the link to mark it as patrolled. That makes the exclamation mark go away for all users, and the edit is now treated as reviewed.

Note that you will need to do this for each edit individually. If you have turned on "Enhanced recent changes" in your preferences, you will be able to review a group of edits made to a page. Unfortunately you cannot mark as patrolled all the edits made to the article on that day at one go (but stay tuned, this should change in the near future). A good alternative, however, is to install the Real Time Recent Changes gadget in your preferences. This will result in a much better interface and patrolling will be much easier.

There is an option to "Hide patrolled edits" in both versions of the Recent Changes utility, which you can use to narrow it down to recent changes that still need attention.

Autopatrolled and patroller users
An admin can give or revoke autopatroller status to any registered user. This status allows their edits to be patrolled automatically.

Administrator accounts automatically have patroller rights. Bureaucrats and administrators can also provide patroller rights to other trusted users who have demonstrated a good understanding of Wikivoyage policies. No nomination process is necessary.

These are two separate permissions which differ in scope:
 * An autopatrolled user has a basic understanding of how Wikivoyage works and has made enough constructive contributions for the community to be reasonably confident their efforts serve the voyager and are not vandalism. Most regular editors fall into this category; there's no need for the system to display bold red exclamation marks ! in Special:Recentchanges to indicate to patrollers that their edits haven't been checked yet by any administrator or patroller.
 * A patroller, on the other hand, is an experienced volunteer who visits Special:RecentChanges often and checks edits from new or unregistered users to verify that they are reasonable – no obvious issues such as broken formatting, self-promotion or vandalism which would require the changes be undone ("reverted"). If the edit appears valid, the patroller then clicks [mark as patrolled] and the ! flag disappears from that edit in the recent changes list so that other patrollers or administrators know that the edit has been checked and need not be verified again. Patrollers are also given the right to roll back multiple changes.

What to mark as patrolled
If the edit is constructive and substantially complies with Wikivoyage policies, mark it as patrolled. Patrolling an edit does not mean that you have verified all the content of the edit as correct. Others familiar with the destination will check this using their watchlist and during subsequent edits.

However, when patrolling, in addition to blatant vandalism, you should also check for edits which
 * 1) Breach Wikivoyage policies, particularly policies on external links,  tours and touting
 * 2) Change existing accommodation listings' URL or phone numbers to those of a consolidator or agent or a competing business (such as a different hotel).
 * 3) Delete information, with no explanation in either the comment or the talk page.
 * 4) Reorder listings in a non-obvious way, without explanation.

If you are in doubt, don't mark the change patrolled. Someone else can double check it later.

Tools and techniques to help with patrolling

 * Start from the Special:Recentchanges, and hide bot edits and patrolled edits. When you have the page looking how you like it, consider bookmarking it for easy access.
 * Open each of the diffs in a new tab (hold down the Control key in both Firefox and Internet Explorer when clicking on the diff). and then use Control-TAB to review each edit in turn. Click to either undo, or mark it as patrolled, and cycle to next tab.  When complete use Control-W repeatedly to quickly close all the tabs, or use the close other tabs menu item on the tab dropdown menu for a keyboard shortcut).
 * If you have decided to revert a change, first mark it as patrolled, and then click the back button on your browser to go back and undo the change. This is much simpler than undoing the change first, and then marking the change as patrolled.  Reverting a change does not automatically mark it as patrolled.
 * If you are using Firefox, consider a extension that supports canned text, for easy revert explanations (such as Paste Email Plus).

title: Wikivoyage:Recent changes patrol


text:
Wikivoyage:Region article template

''Regions are somewhat nebulous organizational groupings we use on Wikivoyage to organize all the many cities in a country into some kind of navigable and comprehensible hierarchy. They can be sub-national political territories, like Minnesota or New South Wales, or more nebulous "tourist" regions like the French Riviera, or the American Southwest. Region articles tend to be more "soft", discussing the people, culture, climate, and cuisine in the region, rather than the legalistic stuff that's in a country article, or the addresses-and-phone-numbers stuff that's in a city article.''

''Before you plunge forward creating a region, keep in mind that we only add a new level of regions when there are too many cities or too much content in the existing breakdown. The regional hierarchy at Wikivoyage doesn't always follow the official breakdown—and frequently is much "flatter" than the official breakdown.''

''Almost always, individual listings (including detailed contact info for restaurants and hotels) do *not* belong in a region or sub-region page. The region-level description is a brief overview only; it will mention that Walt Disney World is near Orlando but not list full contact info. Don't name every hotel and eatery in the area. General descriptions like "many hotels in Orlando accommodate visitors to the Disney park", "multiple restaurants offer patios facing the river" or "various marinas in Ontario and New York rent boats to Thousand Islands visitors" are fine but leave it at that and save the lists of individual hotels, cafés and marinas for the city or local-level articles.''

''Individual listings should be placed at the lowest available level of local page (a district of a huge city or the city page for a small town). If something is in a tiny rural village too small to justify its own local article, alternatives include:''
 * creating a single local-level page for a broad, sparsely populated rural area (such as Rural Montgomery County) with multiple villages on one page,
 * adding the listing in the appropriate main section (see/do, eat/drink, buy, sleep) in the nearest city page if the town is just a suburb of that city, or
 * adding a section "Nearby" in an adjacent city article (before the "Go next" section). Divide this into a subsection named for each village in the surrounding area. Note that "Go next" normally lists the next destination which actually has an article in Wikivoyage.

Also, points of interest (such as those mentioned in "See" sections) should not usually have markers in region articles but should be linked to the bottom-level article where they have full listings.

To quickly insert a complete blank region template, copy-and-paste the quick version into the edit box on the page you are editing, or simply use, which will expand into the region template on save.

''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.]''

''The introduction to a region does not have a heading. This is the place for rhetorical flourish, not a list of dry facts; try to leave detailed information on history, culture, etc, for the Understand section. While some identifying information, rough borders, and links to the surrounding region – like New England in the Connecticut article – are helpful (so that the traveller has some idea what you're talking about), the main purpose of the lead paragraph is to hook the reader's interest.''

Regions
''Regions can have sub-regions, and those can have further sub-regions, and so on and so forth. If this region contains other regions, list them here with brief info about each. If not, leave this section out.''

If the sub-regions have specific names ("county", "state", "province", etc.) feel free to change the name of this header to "Counties", "States", etc.

 * The South - 1-5 sentences describing the highlights of this sub-region.
 * The North - 1-5 sentences describing the highlights of this sub-region.
 * The Coast - 1-5 sentences describing the highlights of this sub-region.
 * Inland - 1-5 sentences describing the highlights of this sub-region.

Cities
''It's usually a good idea, if there are a few prominent cities and towns in the region, to list them here, since that's often all that travellers are looking for. Regions without sub-regions, though, just have cities in them. List links to each city or locality, with a brief description for each. If the region has subregions, don't list more than 9 cities, but list the ones that are most important or most interesting to visitors. If there are more than nine cities in a bottom-level region, grouping them can make sense, such as by having minor towns share a bullet with a nearby city, or splitting the list by subregion; also consider dividing the region into proper subregions. If there really aren't any cities to list, leave out this section.''

''Per One-liner listings, cities and towns should be listed in alphabetical order. If the region corresponds to a political entity (such as a state or a province), always list its capital city first.''

''Lastly, if calling the settlements in this region "cities" is a real stretch – say, for remote or rural areas with only towns or villages – it's OK to rename this section 'Towns' or 'Villages' or 'Settlements' or whatever. But if there are lots of different kinds and sizes of settlements, just leave it as "Cities".''

 * City 1 - 1-5 sentences describing the highlights of this city.
 * City 2 - 1-5 sentences describing the highlights of this city.
 * City 3 - 1-5 sentences describing the highlights of this city.
 * City 4 - 1-5 sentences describing the highlights of this city.

Other destinations
''Sometimes a region has destinations that aren't really cities: for example, large national parks. If so, list them separately here, with descriptions. Otherwise, leave out this section. This section, too, can be renamed if all destinations fall into a nice category, e.g. "Islands" or "Beaches". As with the "Cities" section, if the article is for a region that's subdivided into sub-regions, no more than nine "other destinations" should be listed in this section.''

 * Park 1 - 1-5 sentences describing the highlights of this park.
 * Park 2 - 1-5 sentences describing the highlights of this park.
 * Island 3 - 1-5 sentences describing the highlights of this island.

Understand
This is a more subjective description of the region – what it's like, why someone would want to go there, the culture and atmosphere, the history, the weather, what makes it different and distinct from other regions.

Talk
''If there are any language issues with the region that are different from the country as a whole, or the surrounding region, point them out here. Regional dialects of the national language, for example, are worth listing, as well as large local minority languages. Even local slang or sayings can be helpful to a first-time visitor. Consider linking to the phrasebook for the local language, if it's different from the country's language. If there really aren't any language issues, just leave this section out.''

Get in
''This is where you would note the best arrival points to start exploring this region from. For example, it would be worth listing Phoenix and Albuquerque as good starting points for the American Southwest. You can also give driving directions from large nearby cities that readers might be coming from. Save the nitty-gritty details of how to get to the main entry points for a region for their city pages, though.''

Get around
''This is where you'd give general information about how to get around the region once there. What are ways to see this region: by train, by car, by bus? Are there other options? This is also a good place to list regional travel discount passes or other purchasing options. Save point-to-point details for the individual city articles, though.''

See
''This is for an overview of the types of attractions as well as the principal attractions in the region. Don't give full details about each attraction (use prose, not a listing template); you should have that in the article for the city where the attraction is. If there isn't anything to say about the region's sights that isn't already covered by the descriptions in the Regions/Cities/Other destinations sections, or in the Understand section, then this section can be omitted.''

Itineraries
This is where you can list any relevant itineraries, giving suggested courses of travel through the region with tips of things to see and do.

For example:

 * The Loneliest Road in America is a drive through the remote parts of Nevada.

Do
''This is for a summary of activities in the region, that is, 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. Don't give full details about each activity (use prose, not a listing template); you should have that in the article for the city instead. Not every activity in the region needs to be mentioned – just ones that are so important people expect them to be on the main page for the region. If there isn't anything to say about the region's activities that isn't already covered by the descriptions in the Regions/Cities/Other destinations sections, or in the Understand section, then this section can be omitted.''

Eat
''This is a great place to describe the regional cuisine. Are there any specialties that travellers should try while they're in this region? Immigrant or minority populations with their own cuisine? Try to mention lots of types of food, and keep people on special diets – like vegetarians or people eating kosher – in mind. If one or two linked destinations have especially notable dining scenes, note that here, but don't mention individual restaurants or such in the region article – save that for the individual city articles. Do mention, however, which cities or subregions have an especially notable dining scene. If there isn't anything to say about the region's restaurants and cuisine that isn't already covered by the descriptions in the Regions/Cities/Other destinations sections, or in the Understand section, then this section can be omitted.''

Drink
''This section is for all kinds of nightlife, not just drinking. Are there regional specialties for alcohol, wine, beer, etc.? What about music and entertainment, like honky tonks for Texas or folk music in the Atlantic Provinces? What is there to do in this region that makes it different? If nightlife is concentrated in one or only some of the linked destination articles, note that here. If there isn't anything to say about the region's nightlife or specialty drinks that isn't already covered by the descriptions in the Regions/Cities/Other destinations sections, or in the Understand section, then this section can be omitted.''

Sleep
''The sleep section is optional, and often left out to discourage spammers from adding their hotels here. If included in the article, this section should explain what to expect in terms of accommodations; it should highlight region-specific types of accommodations. It is sometimes appropriate to also explain which cities have the bulk of the accommodations options.''

Stay safe
''If there are any particular safety issues – crime, weather, etc. – for the region in general, describe them here. If one section of the region is much more dangerous than the rest, that is also a good thing to note. If there isn't anything to say about regional safety issues that isn't already covered by the descriptions in the Regions/Cities/Other destinations sections, or in the Understand section, then this section can be omitted.''

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". For really large regions, if it makes no sense to suggest a day trip at such a high level, just leave the section out. But be careful – while California is a big region, it should still have a Go next because Las Vegas is indeed a popular weekend destination for all Californians.''

''At the end of the article, you may find various templates like and interwiki links like Vorgabe für Regionen. These have special functions; please do not change or delete them unless you understand what they mean.''

title: Wikivoyage:Region article template


text:
Wikivoyage:Region article status

This page describes the criteria for determining the article status of Region, State, Continent, and Continental Section guide articles. The criteria for Country guide status are similar but not identical.

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

title: Wikivoyage:Region article status


text:
Wikivoyage:Regions map Expedition

The Regions map Expedition is a Wikivoyage Expedition to promote and coordinate collaboration to improve the quality of the organization of Wikivoyage content by creating regions maps for region and country articles.

If you'd like to join the effort, please add your signature to the section below!

Rationale
Wiki articles, perhaps surprisingly, develop over time into something coherent, most often without any systematic management. Unfortunately, content organization does not. The Project:Geographical hierarchy is an ideal way to organize Wikivoyage destination guides, but the organic process that lends itself well to travel writing does not always work so well for the subdivision of our region articles. Ad hoc subdivisions often overlap, and even serious efforts to subdivide regions can fall afoul of the complexity of the task.

Regions maps (like, for example, this one) solve the problems inherent in dividing geographical units. They make clear to readers and contributors where the exact boundaries of regions fall, and crucially, they help us avoid the problem of overlap.

Goals
The main goal of the Regions map Expedition is to create regions maps for all articles that have subregions. In pursuit of this goal we will:

 * 1) Identify high-priority regions maps that need to be created
 * 2) Identify which articles still need regions maps
 * 3) Link good source material for creating regions maps
 * 4) Assist interested users in learning how to create regions maps (If you're looking for help, ask on an expedition member's talk page.)

Achieving this goal will not happen any time soon, so we have a more narrow current focus: to finish creating regions maps for all articles within specific categories of articles that already have a significant amount of regions maps created. If there is a category of articles you would like to add to the lists below, please bring it up on the talk page.

A secondary goal of the Expedition is to encourage the development of standards in regions maps. In pursuit of this goal we should:

 * 1) Continue experimenting with regions maps, to develop higher standards
 * 2) Discuss here what standards we think we should encourage
 * 3) Eventually develop a section at Project:How to draw static maps that explains precisely how to go about creating a regions map.

Expedition members

 * LtPowers
 * Shaundd
 * Ravikiran
 * Globe-trotter
 * Texugo
 * Saqib
 * SHB2000
 * SelfieCity
 * Sbb1413

Template
To keep our maps somewhat similar, it's necessary that we use similar colors and icons. Hence this template. The template contains the items explained on the right, all in one layer in a simple svg file. To use it in a new map (or an existing one), just import it to the desired svg, under a layer of your choosing

Source files
All of our maps will need to come from somewhere, so you'll need to find a base bitmap or SVG image from which to create the Wikivoyage-style map. The best source of maps in the Public Domain is the Perry Castañeda Collection of maps created by the U.S. Government (mostly by the CIA).

Wikimedia Commons also has a wealth maps in the Public Domain and under other CC-compatible licenses, all of them conveniently sorted into categories, e.g., commons:Category:Maps of Taiwan. Many of the maps available on Commons are already in SVG form, saving our mapmakers some tracing work.

The other very useful site to keep in mind is OpenStreetMap, which can provide great base bitmaps and SVGs (using the site's export function—choose Mapnik → SVG), particularly for smaller regions.

UN maps are exceptionally helpful for country maps, as you can import their pdf files directly into Inkscape, which will convert the map to SVG form! Much of the map will be borderline useless, especially all text, but this is a great way to get a free country outline + roads, rail, and lakes/rivers without having to do any tracing. It's easiest to find (ctrl+f) the paths you want to save (identify them by style from the XML editor (ctrl+x)) and move them to a separate layer. When done moving the useful paths, delete the original layer.

Layers

 * Frame
 * Key (other labels)
 * Region names
 * City/other destination names
 * Transportation labels
 * Transportation (roads, railroads, hiking trails, major camel routes, etc.)
 * Geography (lakes, rivers, parklands, etc.)
 * Cities/Other destinations
 * Regions (colored)
 * Foreground (undivided region image, oceans, bordering countries, etc.)
 * Background

Color scheme/patterns
Different maps will have different needs, but the basic 11-color palette on the Regions Map Template works pretty well. For maps with a lot of detail, however, lower saturation colors may be necessary. See discussion for ideas.

Font

 * Use the DejaVu Sans Compact font on all maps. DejaVu Sans Compact italic, bold, and bold italic are fine too, to show different classes of labels. This is important not just for consistency—the DejaVu font family is very easy to translate into different alphabets.

Route icons
It is always nice to include official route shields on maps. To find route shields not available here, check Route icons.

Ease of translation
A major goal here is that the maps we create be easy to translate into other languages. To do so:

 * Keep text together within sublayers. E.g., if you are using a "city names" layer, create a sublayer "en", which will contain all the English language text. This makes it easy for a translator to add another language sublayer (like "es" for Spanish), duplicate the text in your "en" sublayer and raise it to the "es" sublayer of "city names". This keeps translated info easy to manage, and all on one SVG—we can export PNG map images from that one SVG for each language by turning off the irrelevant language layers and enabling the relevant ones.

 * Limit the number of layers containing text. If text is spread out across loads of layers, it becomes difficult to switch between languages. Also try to keep the text layers next to each other, so that would-be translators don't have to "fish around" to find the necessary text layers.

 * For translators: Don't create separate SVGs for different language versions! This makes non-textual updates to our maps near impossible across language versions (as it would require a separate update of every single SVG file, rather than one). Instead, create sublayers for your language version of each layer containing text, select those, de-select the English layers, and export a PNG file for use in-article.

What to include
A "star-quality" regions map will include all of the following, but anything is far better than nothing! Don't be intimidated by all the guidelines—plunge forward and try creating a map with just the regions and major cities shown; consider whether you want to go further along these guidelines afterward.

 * Key — map name, compass, scale

 * Region boundaries — first and foremost, regions maps should clearly define regional boundaries. It's often useful to show subregions in some manner, to indicate of what the regions are comprised.

 * Linked cities and other destinations — in the region/country article, there should be nine cities and nine other destinations linked. Place these on the map, and label them with text. If you deem it worthwhile, add other cities and other destinations as you see fit for context, but don't include ridiculously long lists of destinations. If the article in question has 30 linked "other destinations," that means it is in violation of policy—leave the other destinations off until the article has been cleaned up.

 * Major modes of transportation between linked destinations — the major highways, railroads, waterways, or what have you that most travelers use to get between the 9 linked cities & 9 linked other destinations.

 * Bordering regions/countries

 * Geography — relevant parklands, rivers, bodies of water, desert, beaches, etc.

Use Template:Regionlist
We recommend mapmakers add the regionlist template to articles containing a regions map, to automatically display regions and their corresponding map colors in a standard format. To see how the template is used, and how the syntax works, check the Africa page for an example. If you have any questions regarding how to use this template, please feel free to ask an expedition member.

Articles lacking regions maps
Below is a quick list of regions currently lack region maps.

If you are working on one, please add your name ( ~ ) to the country/region you are working on, to let others know someone's taking care of it!

If you come across a good map base, that is, a good source for tracing that is compatible with our Copyleft, please add a link to it next to the article title below.

Country top level divisions
{|style="border-spacing:8px;margin:0px -8px"

{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5fffa" !
 * class="MainPageBG" style="width:20%;border:1px solid #cef2e0;background-color:#f5fffa;vertical-align:top;color:#000"|

Africa
 * style="color:#000"|
 * style="color:#000"|

South Africa

 * Free State
 * North West Province
 * Limpopo

Nigeria

 * South West Nigeria
 * South South Nigeria
 * South East Nigeria
 * North East Nigeria
 * North West Nigeria
 * North Central Nigeria
 * }
 * }

{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5faff" !
 * class="MainPageBG" style="width:20%;border:1px solid #cedff2;background-color:#f5faff;vertical-align:top"|

Asia
 * style="color:#000"|
 * style="color:#000"|

Indonesia

 * Maluku
 * Papua

Malaysia

 * West Coast

Philippines

 * Mindanao

Taiwan

 * Northern Taiwan
 * Central Taiwan
 * Eastern Taiwan
 * Southern Taiwan

Turkey

 * Aegean Turkey
 * Black Sea Turkey
 * Marmara
 * Mediterranean Turkey

 * }
 * }

 * class="MainPageBG" style="width:20%;border:1px solid #cedff2;background-color:#f5faff;vertical-align:top"|

 * class="MainPageBG" style="width:20%;border:1px solid #cedff2;background-color:#f5faff;vertical-align:top"|

Belgium

 * Brussels

France

 * Île-de-France
 * Pays de la Loire

Portugal

 * Azores
 * Madeira

Spain

 * Canary Islands

Sweden

 * All regions

{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#faf5ff" !
 * class="MainPageBG" style="width:20%;border:1px solid #ddcef2;background-color:#faf5ff;vertical-align:top"|

Americas
 * style="color:#000"|
 * style="color:#000"|

Bolivia

 * Altiplano
 * Sub-Andean Bolivia
 * Tropical Lowlands

Chile

 * North
 * Central
 * South
 * Patagonia (Chile)

El Salvador

 * All regions

Guatemala

 * All regions

Venezuela

 * Andes
 * Caribbean Islands
 * Central
 * Los Llanos
 * Northeast
 * Northwest

 * }
 * }

 * }

title: Wikivoyage:Regions map Expedition


text:
Wikivoyage:Related articles

Sometimes we want to express loose relationships between destination guides and itineraries, travel topics, phrasebooks, geographic expeditions. The destination guide for a place and a part of that place, like California and Southern California, is a "tight" relationship, but the relationship between California and a travel topic like Off-road vehicles in California is loose.

This gives us the ability to concentrate on "core" travel guides for a general audience and still make space for related articles for more specific use.

For presentation, we have an area in the left-hand nav bar for related itineraries, travel topics, expeditions, region-specific policies and phrasebooks.

Templates
A simple template, Template:Related, defines the relationship to the other article. On Singapore, we'd have:

ja:Project:関連する記事

title: Wikivoyage:Related articles


text:
Wikivoyage:Requests for comment

Policy planning and proposals

 * Wikivoyage talk:Autoconfirmed users – revisiting the criteria for autoconfirmed users. -- SHB2000  (t | c | m) 10:40, 10 July 2024 (UTC)

Articles and travel content

 * Talk:Rochester (New_York): I would like additional input on the state of this article and suggestions for improvements, given how long it's been since I contributed significantly to Wikivoyage. Powers (talk) 01:14, 11 July 2024 (UTC)

 * Talk:Manhattan/Chinatown: Can we please have parts of Chinatown removed without discussion when a dynamic map was substituted for a static map restored to Chinatown and subtracted from Manhattan/Lower East Side? Ikan Kekek (talk) 07:06, 30 June 2024 (UTC)

Banner discussions

 * This section is for listing discussions about changing a banner. For discussions about adding a new banner where none exist, please see Banner suggestions.

District discussions
Put Category:Articles with districts discussion on your watchlist to have new entries show up there.

Region discussions
Put Category:Articles with regions discussion on your watchlist to have new entries show up there.

Merge discussions
Put Category:Articles to be merged on your watchlist to have new entries show up there.

title: Wikivoyage:Requests for comment


text: Wikivoyage:Requests for images

title: Wikivoyage:Requests for images


text:
Wikivoyage:Requests for maps

The following are destinations that need maps. The Mapmaking Expedition is a project to coordinate map development for Wikivoyage; please refer to that Expedition's standards if you're going to work on one of these maps. See How to draw static maps and How to use dynamic maps for instructions for making your own. The Dynamic maps Expedition is aiming to make user-interactive maps which are less customizable but quicker to implement.

If you know of an article that needs a map, add it to the list below. Try to note the type of map, for example, city map, region map, etc. If you start making one of these maps, please remove it from this list.

Also be sure to check out the Regions map Expedition to see whether someone if working on a map in that Expedition.

Africa

 * Modified maps of Africa, East Africa, and Central Africa, putting South Sudan in the East African region, per ongoing discussion at Talk:Africa. The conversation isn't over, but it would be helpful to compare. 22:04, 14 November 2018 (UTC)
 * I don't see South Sudan listed at East Africa. --Comment by Selfie City  ( talk  |  contributions ) 16:18, 19 September 2021 (UTC)

Asia

 * On the trail of Marco Polo has a map, but it isn't in English, nor is it in line with our style.

China

 * city map for Zhuhai
 * city map for Shenzhen

Austria

 * Lower Austria doesn't match our visual style
 * Tyrol doesn't have a static map to accompany its subdivision (but does have a dynamic map)

Belgium

 * Brussels can do with a static map and more diverse colours (too much blue, colour-blind unfriendly)

Finland

 * Southern Finland, West Coast (Finland) and Finnish Lakeland don't have a colour-blind friendly map.

France

 * France's regions were reorganised in October 2017 and still need some region maps. Regions without a (updated) static map are:
 * Bourgogne-Franche-Comté
 * Centre-Val de Loire
 * Grand-Est
 * Hauts-de-France
 * île-de-France
 * Pays de la Loire.

Germany

 * The static region maps for Baden-Württemberg and Bavaria aren't colour-blind friendly
 * Hesse has subdivisions but lacks a static and/or dynamic map that shows them

Greece
https://commons.wikimedia.org/wiki/File:Athens_Greece_street_map_vector_gvl13_svg_free.svg
 * Athens - Districts Map

Hungary

 * Northern Hungary lacks a static map
 * More concerning than this, Hungary as a whole lacks a static map. I am working on creating a new one to fit the regions now. --Comment by Selfie City (talk) (contributions) 15:48, 28 September 2022 (UTC)
 * OK, Hungary as a whole now has a static map accurately representing the regions. As for maps of the individual regions of the country, I won't be able to get to those yet. Most subregions globally don't have static maps yet and there are requests here that deserve higher priority. --Comment by Selfie City (talk) (contributions) 16:17, 28 September 2022 (UTC)

Iceland
https://commons.wikimedia.org/wiki/File:Iceland_road_map.svg
 * Iceland itself has a map with typical colours, but sadly, these aren't colour-blind friendly. Two regions are also missing from the dynamic version

Portugal
High-level mainland regions of Portugal are ✅.

The Wikidata IDs used to produce the dynamic maps may assist in determining boundaries for the static maps.
 * Lisbon — Needs a district map

Slovakia

 * Slovakia has three subregions, all of which have subdivisions and static maps, but two of them Western Slovakia and Central Slovakia don't match our visual style. Eastern Slovakia misses context and has a very large font

Switzerland

 * Berne Region has a dynamic map that is not colour-blind friendly and could also do with a static version
 * Central Switzerland is colour-blind unfriendly and can do with a static map
 * Eastern Switzerland has a static map that lacks context (railroads seemingly end no-where and road infrastructure is missing)
 * Northwestern Switzerland is colour-blind unfriendly and can do with a static map
 * Surselva needs a map that matches our visual style
 * Ticino misses context: Lakes seem to stop at the border of the region and infrastructure is lacking
 * Valais has a static map that lacks context (railroads seemingly end no-where and road infrastructure is missing)
 * Western Switzerland has a static map that lacks context (railroads seemingly end no-where and road infrastructure is missing)
 * Zurich is colour-blind unfriendly and can do with a static map

United Kingdom

 * Both Manchester and Edinburgh have a district map that is not colorblind-friendly.
 * The West Country map has the Isles of Scilly shaded as part of Cornwall, when the article treats them separately. They should be reshaded; not a big change. (mentioned at Talk:West Country). 17:08, 22 November 2018 (UTC)
 * Various maps relating to Scotland need fixing both on the country page and on various region pages. The text of place names is so small that even when the maps are blown up to huge sizes they remain illegible and unusable.--ThunderingTyphoons! (talk) 15:58, 29 March 2014 (UTC)
 * South West doesn't match our visual style
 * Scottish Borders doesn't match our visual style
 * Central Belt doesn't match our visual style
 * Scottish Highlands has a working map, but it is not colour-blind friendly and is overall a busy map
 * North East Scotland doesn't match our visual style
 * Hebrides Have a colour-blind unfriendly static and dynamic map
 * Central Belt doesn't match our visual style
 * Shetland doesn't match our visual style

Canada

 * Edmonton Capital Region

Hello. https://commons.wikimedia.org/wiki/File:Edmonton_Canada_street_map.svg

Mexico

 * Lake Patzcuaro requires a map with the towns surrounding the lake.

United States

 * Manhattan/Chinatown and Manhattan/Lower East Side need adjustments, per Talk:Manhattan/Chinatown. The elimination of areas of Chinatown north of Grand and east of Eldrige were made without discussion, though it would be good to get a consensus for restoring this area that was previously in the static map before the dynamic maps are edited. Ikan Kekek (talk) 07:03, 30 June 2024 (UTC)

Australia

 * Canberra; (WT-en) JRG 05:41, 14 February 2011 (EST)
 * +1 for the districts. -- SHB2000 (talk | contribs | meta.wikimedia) 23:59, 7 May 2022 (UTC)

https://commons.wikimedia.org/wiki/File:Canberra_Australia_street_map.svg
 * Gold Coast; (WT-en) Nathannoblet 00:27, 21 October 2006 (EDT)

Argentina

 * Buenos Aires already has districts in the dynamic map, but lacks a static map

Brazil
https://commons.wikimedia.org/wiki/File:Rio_de_Janeiro_Brazil_street_map.svg
 * Brasilia
 * Rio de Janeiro already has districts in the dynamic map, but lacks a static map

Chile

 * Torres del Paine needs a static trekking map or GPX trace in the dynamic map

Ecuador

 * Quito needs an Old town and Mariscal citymap
 * Baños has a crowded dynamic map and can do with a static one
 * Cuenca has no dynamic or static map

Peru

 * Cordillera Blanca needs a static trekking map or GPX trace in the dynamic map
 * Cuzco has no static map

de:Project:Karten-Wünsche

title: Wikivoyage:Requests for maps


text:
Wikivoyage:Requests for phrasebooks

Requested phrasebooks

 * Aragonese phrasebook One of the minority languages of Spain that need respect --(WT-en) CurvyEthyl 22:12, 24 September 2010 (EDT)
 * Asturian phrasebook
 * Buhi Bikol A language of Albay Bikol which is spoken in Buhi, Camarines Sur, Philippines.
 * Cabo verdian creole. to show respect to those on the cape verdian islands -- [User:(WT-EN)raherist] Raherist (talk) 01:24, 27 August 2022 (UTC)
 * Extremaduran phrasebook One of the minority languages of Spain that need respect --(WT-en) CurvyEthyl 22:12, 24 September 2010 (EDT)
 * Fon phrasebook For a visit to the southern part of Benin. --(WT-en) CurvyEthyl 22:09, 28 September 2010 (EDT)
 * Friulian phrasebook I think that the new orthography can be used over the old one in this phrasebook, but the old one is optional. It's also recognized as a minority language in Italy, I guess. --(WT-en) CurvyEthyl 18:08, 25 September 2010 (EDT)
 * Guarani phrasebook: 5 million speakers and an official language in Paraguay
 * Hassaniya Arabic phrasebook: the main language of Western Sahara
 * Kashubian phrasebook Spoken in the Pomeranian region of Poland. --(WT-en) CurvyEthyl 18:40, 25 September 2010 (EDT)
 * Kenyah phrasebook. This language is spoken in the Apo Kayan, Borneo. -(WT-en) phma 14:05, 20 Apr 2004 (EDT)
 * Khanty phrasebook One of the official and indigenous languages of the Khanty-Mansi Autonomous Okrug. It's endangered and therefore should be used by travelers to the region.
 * Latin phrasebook The official language of the Holy See. It would be both interesting and useful since as far as I know, the ATMs are set to Latin by default there. Xing (talk) 04:58, 9 September 2021 (UTC)
 * I don't think that's true, but in any case, there's no reason to speak anything but Italian in the Vatican City, which is simply a neighborhood of Rome. At most, I could see a topic on Latin masses, but if you want to see the text, just do a web search. I would oppose the creation of Latin phrasebook. Ikan Kekek (talk) 06:07, 9 September 2021 (UTC)
 * I must say I'm truly disappointed by the fact that the creation of phrasebook for any language of our world is met with opposition. Not to mention said language is not just currently official in a contemporary European state but had a great influence on the cultures and languages of Europe. Xing (talk) 06:57, 9 September 2021 (UTC)
 * who is going to use Latin though? A Latin phrasebook is out of scope. No one will use it. Ever. SHB2000 (talk | contribs | meta.wikimedia) 08:20, 9 September 2021 (UTC)
 * In addition to masses, it is used on a lot of monuments. Anyway, the normal phrase list is little use, unless you attend a Latinist conference (we had one in Joensuu, where also all city tourist information was available in Latin), and if you do, you probably know Latin better than that. I don't think an outline Latin phrasebook makes sense, but one with a different set of phrases, or a travel topic, might. However, if created, I think it should be a worthwhile article from start, with a clear scope and vision. –LPfi (talk) 08:24, 9 September 2021 (UTC)
 * Let's not make the mistake with the Sanskrit phrasebook. --SHB2000 (talk | contribs | meta.wikimedia) 09:58, 9 September 2021 (UTC)
 * Xing, this is a travel guide. Where is a tourist going to be speaking Latin? As SHB2000 said, it's out of scope. Sanskrit is spoken by over 2,000,000 people. Hardly anyone speaks Latin. Ikan Kekek (talk) 13:31, 9 September 2021 (UTC)
 * Ok. Xing (talk) 13:55, 9 September 2021 (UTC)
 * Latin is spoken by more people, but they aren't fluent speakers like Sanskrit (i.e. more people can speak Latin with words here and there, but less people can speak fluent Latin, while with Sanskrit, it has more fluent speakers, but less speakers who speak a word here and there). SHB2000 (talk | contribs | meta.wikimedia) 13:58, 9 September 2021 (UTC)
 * Knowing how to say "et cetera", "per se", "status quo" and similar expressions that are used in English doesn't make an English-speaker a Latin-speaker in any sense, nor does knowing the words of the Latin mass. Ikan Kekek (talk) 19:53, 9 September 2021 (UTC)
 * That's my level of Latin, but I have never studied the language. You can study it in many secondary schools (including mine), and of course at university. I suppose the bulk of "speakers" are those who studied it at school. The main use from our perspective is still to understand masses and inscriptions. –LPfi (talk) 20:44, 9 September 2021 (UTC)
 * High schools in Australia mostly used to offer Latin, German and some other European language, but now these days they either offer Mandarin, Japanese, Indonesian and sometimes one European language. SHB2000 (talk | contribs | meta.wikimedia) 22:19, 9 September 2021 (UTC)

 * Learning Arabic script — a complex script used by numerous languages of South Asia and the Middle East, including Arabic, Persian and Urdu. --Sbb1413 (he) (talk • contribs) 17:25, 26 April 2024 (UTC)
 * Leonese phrasebook There's a celebration in the city of León (Leonese: Llión) called the Leonese Language Day (Día de la Llingua Llïonesa). The date for that celebration varies. --(WT-en) CurvyEthyl 15:32, 25 September 2010 (EDT)
 * Libon Bikol A language of Albay Bikol spoken in Libon, Albay, Philippines.
 * Livonian phrasebook This minority language from Latvia needs respect as it struggled for survival during its hard times. --(WT-en) CurvyEthyl 22:38, 25 September 2010 (EDT)
 * Mansi phrasebook One of the official and indigenous languages of the Khanty-Mansi Autonomous Okrug. It's endangered and therefore should be used by travelers to the region.
 * Mirandese phrasebook
 * Miraya Bikol phrasebook or Easten Miraya or Daragueno is spoken in the towns of Guinobatan, Camalig, Jovellar, and Daraga in Albay and Donsol and Pilar in Sorsogon.
 * Nenets phrasebook The official and indigenous language of the Nenets Autonomous Okrug and Yamalo-Nenets Autonomous Okrug. It's still widely used by the Nenets people but is threatened by Russification.
 * Quiché and Cakchiquel phrasebooks, for traveling to the Mayan areas of Guatemala. (WT-en) phma 15:53, 14 April 2008 (EDT)
 * Sambal phrasebook: spoken primarily in the Zambal municipalities of Santa Cruz, Candelaria, Masinloc, Palauig, and Iba.
 * Sardinian phrasebook: The most divergent "dialect" of Italian
 * Seto phrasebook One of the minority languages of Estonia that need respect. --(WT-en) CurvyEthyl 22:38, 25 September 2010 (EDT)
 * Taishanese phrasebook: Language closely related to Cantonese, from Taishan and the surrounding area in Guangdong province, and spoken by many Chinese-Americans. The dog2 (talk) 05:25, 1 February 2020 (UTC)

 * Venetian phrasebook One of the minority languages of Italy that need respect. --(WT-en) CurvyEthyl 21:49, 25 September 2010 (EDT)
 * Võro phrasebook One of the minority languages of Estonia that need respect. --(WT-en) CurvyEthyl 22:38, 25 September 2010 (EDT)
 * Zhuang phrasebook used in Guangxi. --Liuxinyu970226 (talk) 13:52, 11 July 2014 (UTC)

de:Project:Wünsche für Sprachführer ro:Project:Ghiduri de conversaţie dorite

title: Wikivoyage:Requests for phrasebooks


text:
Wikivoyage:Romanian Wikivoyage Expedition

''The text below is obsolete, as the Romanian language version of Wikivoyage has been launched. It is, however, an archive of how the Romanian Wikivoyage Expedition progressed, and a good example for other language versions of WIkitravel.''

The Romanian Wikivoyage Expedition is an expedition to create a Romanian language version of Wikivoyage which would effectively be the first multilingual version of Wikivoyage. Another multilingual version in development is the French Wikivoyage. The Romanian Wikivoyage will also be a trial into seeing how multilingual versions of Wikivoyage develop, and how they ultimately work.

''For more information on Multilingual Wikivoyage Policy, see Project:Language version policy. For past information about the Romanian Wikivoyage, see Project:Romanian Wikivoyage''

Rationale
Wikivoyage can better meet its goals by providing travel information in more languages than English. This will not only create a better, more comprehensive travel guide, it will attract and encourage more and more contributors. Information contributed in one language will, we hope, eventually filter into all language versions.

The Romanian Internet community, and especially the Romanian Wiki-community are getting increasingly larger. As Romanian Wikipedia and other sites grow, the need grows for more Romanian versions of websites. By addressing this need, we can increase goodwill in the Internet and wiki communities.

Goals
The Romanian Wikivoyage has the following goals:

 * To collect a good base of Romanian users willing to take this project further
 * To translate and localize the English Wikivoyage into Romanian.
 * To create quality articles that will appeal to Romanian travellers.
 * To link these articles to English versions and create an integrated multilingual Wikivoyage.
 * To empower other language groups to form their own Wikivoyage.
 * To contribute to English Wikivoyage with quality articles about Romania.

Goals update

As you probably know, there is currently a French Wikivoyage Expedition, which was formed after (and probably inspired from) the Romanian Wikivoyage. As good Wikivoyagers, it is the goal of the Romanian Wikivoyage to:

 * Support the French Wikivoyage, co-operate with them and integrate them into our and English Wikipedia's structure through interlanguage links.

IMPORTANT: Wikivoyage ready to be launched
The Romanian Wikivoyage is ready to be launched. Here are some start details:

 * Go-between: (WT-en) Ronline
 * Other users willing to contribute: (WT-en) Danutz, (WT-en) Jmabel, (WT-en) Snitz, (WT-en) Maero

Timing and deadlines
The following are guides to completing certain tasks of Wikipedia. They are not deadlines in the strict sense, but we should abide by them to get Romanian Wikivoyage going as fast as possible.

'''Update: Thanks to all Romanian Wikivoyage contributors for voting so quickly for a go-between. We achieved this task quicker than the deadline, meaning we will now be doing everything one day before the former time guide. The new timeframes are:'''

23 December 2003: Go-between was voted in.

24-25 December 2003: Period of proofreading the LanguageRo.php file.

26-27 December 2003: Hopefully, by this time, www.wikivoyage.org/ro can be online, with localization and everything.

28-30 December 2003: Translation of necessary files - we need to translate files such as FAQ, About, Help, Welcome, etc in Romanian.

31 December 2003: Write a few important articles so that they're there for the official launch the next day.

1 January 2004: The official launch!!! From now onwards, we can start creating articles and promoting Romanian Wikivoyage.

January 2004: (WT-en) Ronline, the go-between, will make frequent reports in the logbooks of both RO and EN Wikivoyage, we'll make a new Romanian logo, we will make the Project:Multilingual statistics page and also Expediţia Promovării Wikivoyage în limba română - the expedition to promote the Romanian Wikivoyage.

1 February 2004: I know it's setting things a bit too early, but let's try to get 200 articles by February 2004!

Completed progress
We've already done the following:

 * Localized the interface - see file at LanguageRo.php
 * Chosen a team of five users.
 * Voted in a go-between. The go-between is (WT-en) Ronline, with 3 votes for, and none against. All users have voted.
 * Proofread the interface localization - completed file is at LanguageRo.php

Completed: Gathering a team
See also Project:Language version policy for more information about the procedure of forming a Romanian Wikivoyage.

To get this project started, we need at least 5 Romanian-speaking users willing to contribute to Romanian Wikivoyage.

Please add your name below, by editing this page, if you support this project. You must have a valid user account with Wikivoyage.

I agree to forming the Romanian Wikivoyage and am willing to contribute:

(WT-en) Ronline 04:00, 20 Dec 2003 (PST)

(WT-en) Danutz 04:08, 20 Dec 2003 (PST)

(WT-en) Snitz 23:10, 20 Dec 2003 (PST) (I'm willing to translate articles from English to Romanian Wikivoyage, and to help with the set-up as well).

(WT-en) Jmabel 00:07, 22 Dec 2003 (PST) As a native English speaker, I'm somewhat limited in my ability to contribute to translation in that direction, but I offer my services to decipher anything in English or Spanish that may be confusing.

(WT-en) Maero 15:31, 22 Dec 2003 (PST) - As a Romanian tour guide for English and French tourists, I just heard of Wikivoyage recently - and what an amazement it's been to see there's a Romanian language Wikivoyage in development. I'd like to translate articles into Romanian, as well as offer advice and tips on travel to major European destinations.

5 users have already signed up to help Romanian Wikivoyage, thereby letting the project advance to the next step of choosing go-betweens. However, if you are still interested in helping us out, we'd really appreciate it! Either write your name and how you're willing to help here, or make a new user account on the Romanian Wikivoyage when it launches.

Completed: Choosing a go-between
Voting is closed.

In order to make a successful, integrated Romanian Wikivoyage, we need to choose one of the five users who put their names down, and make them a go-between. The role of the go-between will be to act as a liaison between English and Romanian Wikipedia, and therefore, he must be able to:

 * Write English and Romanian well
 * Understand Wikivoyage ideals, guidelines, goals and policies
 * Make monthly reports about Romanian Wikivoyage to English Wikivoyage
 * Make monthly reports about English Wikivoyage to Romanian Wikivoyage
 * Contribute actively in Romanian Wikivoyage

The go-between will be chosen the democratic way: via voting

The five candidates for go-between are the users listed below. If you would like to vote one of these people, please put your username next to their name, in the Votes for section. If you would like to make a vote against someone, please write your username next to their name in the Votes against line and then a reason for this. To win, a go-between must have two votes for them, and no votes against them. Only people who nominated themselves under the "Gathering a team" section can vote. And remember, you cannot vote for yourself.

Pick a user who you would like to see as go-between:

 * I vote for (WT-en) Ronline
 * Votes for: (WT-en) Snitz, (WT-en) Maero, (WT-en) Danutz
 * Votes against:
 * I vote for (WT-en) Danutz
 * Votes for: (WT-en) Ronline
 * Votes against:
 * I vote for (WT-en) Snitz
 * Votes for:
 * Votes against:
 * I vote for (WT-en) Jmabel
 * Votes for:
 * Votes against: (WT-en) Jmabel: I disqualify myself. My Romanian is not good enough for this role.
 * I vote for (WT-en) Maero
 * Votes for:
 * Votes against:

'''Voting will only finish once person listed above has voted - that is, Ronline, Danutz, Snitz, Jmabel and Maero. Therefore, please put in your votes as soon as possible, because the Wikivoyage in Romanian will becoming online sooner.'''

Completed: Proofreading the script
''The text below is obsolete. The proofreading period has ended.''

The proofreading and correction period for the localization file at LanguageRo.php is nearly ended. We've had feedback and correction from some users, and we encourage other Romanian speakers to look over it and contribute. Proofreading ends in 25 December 2003, near the evening. Once that's done, we're ready to launch!

Next Steps
We've completed all of the necessary start steps. Now it's time to launch Wikivoyage in Romanian and:

 * Translate the "base" articles - Help, FAQ, Disclaimer, Privary Statement, License, etc.
 * Make new articles

In the first month, the go-between also needs to make reports, etc.

For more information about the step process in the first month, see Project:Language version policy

Awareness Raising
We can raise awareness of the Romanian Wikivoyage (and at the same time promote Wikivoyage in general) on the Romanian Wikipedia, as well as on Meta-Wikimedia. Also, we can send the site and a description to Romanian IT/technology sites. (WT-en) Snitz 23:33, 20 Dec 2003 (PST)

Multilingual Stats
(WT-en) Ronline will co-ordinate a multilingual stats project similar to Wikipedia's, which can be found at http://www.wikipedia.org/wiki/Wikipedia:Multilingual_statistics. There will be stats on how many articles the English, Romanian and French Wikipedias contain, as well as growth percentages, etc. If other languages join the Wikivoyage list, maybe we will create a Wikivoyage Embassy.


text:
Wikivoyage:Romanization

Romanization is the process of mapping a script into the Latin alphabet used for English. This page provides guidelines for romanization on Wikivoyage.

As a rule of thumb, romanization should aim for allowing the casual reader to guess at the pronunciation, and the expert to pronounce it right.

General

 * For article titles, use the name most commonly used in English for a place, regardless of local character sets. See Naming conventions for details.
 * In article content, use the correct diacritics at least the first time the name is given.
 * When linking to destinations, the local script is unnecessary clutter. That is, the Tokyo article is linked to as "Tokyo", not "Tokyo (東京)"; if somebody wants or needs to know the script and reading, it's just a click away.

Places
The following guidelines apply to any places in listings (See, Do, Eat, Drink, Sleep, etc.)

 * If a place has a common English name, use it, but always provide the local script and correct romanization in parentheses.
 * Example: Xilin Pagoda (西林塔 Xīlíntǎ) ...
 * If a place has no English name at all, use the romanization as the name and give the script in parentheses.
 * Example: Khrop Khrueang (ครบเครื่อง), Ari Samphan Soi 10. Famous for its kuay tiao yam bok rice noodles...

When using listings templates, the alt parameter can be used to specify the local script and its romanization, and they will automatically be formatted correctly. Examples:

Terms
The following guidelines apply to any local terms used in other content (the introductory glosses of any section, cultural coverage, etc.). This is about the place where it is introduced, later on, leave out the parenthesis and its contents.

 * If you want to give the local name of any term, but use its English name, place both local script and romanization in parentheses after the English.
 * Example: One Japanese specialty worth seeking out is eel ( うなぎ unagi) ...
 * If you want to use the romanized term, italicize it and provide the local script in parentheses. If you want to include a literal translation, this can also go within the parentheses, but in quotes.
 * Example: In Thailand, Western-style black tea is known as chaa ron (ชาร้อน, lit. "tea hot") ...

Languages
If you find an article (or phrasebook) that does not follow the conventions below, and you're unable to fix it, please tag it with the tag, which looks like this:

Chinese
Chinese romanization is complicated by the vast variety of dialects used and some intractable political difficulties. Rules of thumb are:

 * For articles about mainland China, use Hanyu pinyin romanization and simplified form Chinese characters.

 * For articles about Hong Kong and Macau, use Cantonese with Yale romanization and traditional Chinese characters. However, if the most commonly used name is under a different system, use that and not Yale.

 * For articles about Taiwan, use Wade-Giles romanization (without the necessary apostrophes) for older and well-known place names and either Hanyu pinyin or Tongyong pinyin for lesser known placenames (depending on which political party is controlling the locality, but we won't delve into that mess here). The Chinese characters included should be in traditional format.

 * Use tone marks, not tone numbers. Use the tone converter if necessary.  If you don't know the tones, leave them out and somebody will add them later.
 * 中国 is Zhōngguó, not Zhong1 Guo2

 * Use space between words, not between every syllable. Don't capitalize each syllable.
 * 南大街 is Nándàjiē (South-Great-Street), not Nan Da Jie or NanDaJie
 * 天河北路 is Tiānhé Běilù (Heaven-Lake North-Road)

 * Do not use tone marks for article titles, but give them in the intro.
 * Shanghai (上海 Shànghǎi) is a city.

 * Place parentheses around Chinese characters and their pinyin readings. Do not use bold or quote marks.
 * Beer (啤酒 píjiǔ) is very common in China.

See also: Wikipedia:Wikipedia:Manual of Style (China-related articles)

Hebrew
Hebrew romanization is highly nonstandard and complicated by the existence of numerous dialects with varying pronunciations. The closest to an official standard is the United Nations romanization (ISO 259), which is particularly useful for the traveller, as it is widely used in maps and signage.

 * Use United Nations romanization, with the following three exceptions:
 * Use "h" for het (ח), not ẖ (h-underscore)
 * Use "tz" for tzadi (ץ צ), not ts or ẕ (z-underscore)
 * Use "ei" for tzeire malei (אֵי), not e

Examples: Petah Tikva (פֶּתַח תִּקְוָה), Bnei Brak (בְּנֵי בְּרַק)

The surrogates above are widely used in Israel itself, and are easily supported by PCs for display and entry.

That said, some places in Israel have well known English names that differ from the Hebrew: thus Jerusalem (not Yerushalayim) and Hebron (not Hevron).

Indic
Romanization of Indic scripts is complicated by the existence of several different romanization systems and the use of Indic scripts by multiple languages.

 * In general, use the ISO 15919 romanization.
 * For anusvara:
 * Use "ṅ" before k, kh, g and gh.
 * Use "ñ" before c, ch, j and jh.
 * Use "ṇ" before ṭ, ṭh, ḍ and ḍh.
 * Use "n" before t, th, d and dh.
 * Use "m" before p, ph, b and bh.
 * Otherwise, use "ṁ".
 * For article titles, use the Hunterian transliteration.
 * In both cases, when the source script does not indicate the removal of the inherent vowel and it is not pronounced in the original source language, such unpronounced inherent vowels should be removed.

However, some places in South Asia (where Indic scripts are used) have well-known English names that differ from the ISO 15919 or Hunterian transliteration: thus Delhi (not Dilli) and Ahmedabad (not Amdavad). All cities of Karnataka should use the pre-2007 names: thus Bangalore (not Bengaluru) and Shimoga (not Shivamogga).

Tamil
Since the Tamil script does not indicate the voicing of certain consonants, they should be romanized as per their general pronunciations in certain words. In native Tamil words, the consonants are always voiced between the two vowels unless it is doubled.

Tamil ச் should always be romanized as c unless it is pronounced as an S, when it should be romanized as s.

Japanese
For Japanese, Hepburn (written by an American for foreigners) has been the de facto standard of romanization for the past 100 years especially in publications geared to foreigners, while official standard Kunrei (written by Japanese for Japanese) is used very little. Thus:

 * Use Hepburn romanization (specifically Modified/Revised Hepburn, which is the most common style).
 * Indicate long vowels with macrons, except in article titles.
 * Always romanize ん as n, but create a redirect from the m form if common. For example, 群馬 is Gunma, but you can still search for Gumma.
 * Syllabic n ん is written  n'  (with apostrophe) when followed by a vowel or y, but not when followed by another n or another consonant.  Hence 山陽 is San'yō, but こんにちは is konnichiwa and 新橋 is Shinbashi.

See also: Wikipedia:Wikipedia:Manual of Style (Japan-related articles)

Korean
Korean romanization is comparatively straightforward.

 * For South Korea, use the Revised Romanization of Korean, officially adopted in 2000 for governmental use in signs etc and widely used elsewhere too.
 * Use Hong's Hangul Conversion Tools to convert hangeul to Revised Romanization and back.
 * Note the McCune-Reischauer form in content and add a redirect if the old form is well known (eg. Pusan→Busan, Inchon→Incheon, Cheju→Jeju)

 * For North Korea, use standard McCune-Reischauer, which remains the country's sole official system. (However, do not use the North Korean variant of MR.)
 * Omit breves and apostrophes from article titles (eg. Pyongyang), but leave them in content (P'yŏngyang).

 * For personal names use the nameholder's preference or common convention (eg. Kim Il-sung, not "Kim Il-sŏng", and Syngman Rhee, not "I Seung-man"). The same applies to Hangul, kimchi and taekwondo.

Lao
There are two main ways to turn the Lao script into the Latin alphabet: either French-style spellings like Houeisay (formally the BGN/PCGN system), or English-style spellings like Huay Xai (Library of Congress aka LC-ALA style). While government documents seem to prefer the French style, Wikivoyage uses the English-style/Library of Congress system, because it's easier for English speakers to pronounce and is becoming more common. Notable exception: the capital is Vientiane, not Viangchan.

Mention the French-style romanization in the article intro. If it's so different that it's unrecognizable, e.g. Oudomxai for Muang Xay, consider adding it in parenthesis next to inbound links as well.

See also: Wikipedia:Romanization of Lao

Russian
Russian romanization is pretty straightforward if you know Russian Cyrillic, which is also phonetic. Like Thai, there are no universally-used transliteration systems, even for transliteration to English. Especially: the transliteration varies by target language; don't use German or Finnish spelling for the transliteration to English. Sometimes transcription is used instead of transliteration.

There are some general commonalities:

 * Although the name most commonly used in English may be close to the transliteration, they are not always the same. For example, Санкт-Петербург is Saint Petersburg in English, not the transliterated version Sankt-Peterburg . Use the English version in the title and in the text, and give the Russian and an accurate transcription (if different from the English name) in parenthesis where the name of the place or term is introduced in the text.
 * The exception is the word Москва. While Москва is the name of the city and the river flowing through it, the standard English use is Moscow for the city and Moskva (the direct transliteration) for the river.
 * Every vowel in Russian is given its own syllable (there are no diphthongs). When the same letter repeats (whether vowel or consonant), in transliterations it must be written as many times as it appears (this is more common with people's names than place names).
 * For example, Пицца would be most accurately transliterated as "Pitstsa". The best transcription – writing words as they are pronounced – would be "Pizza". In scenarios like this, either one works, just be consistent.
 * Romanizing "soft vowels" (Я/я, Е/е, И/и, Ё/ё, Ю/ю): At the start of a word, include the initial "y", except for И.
 * Hence Екатеринбург Yekaterinburg, not Ekaterinburg, but Иркутск Irkutsk, not Yirkutsk.
 * In the middle of words, the only soft vowels always written with an initial "y" are Я and Ю.
 * That is, write Ryazan, not Razan
 * Different systems will write an initial "y" for E in the middle of words or not. Generally, it is not needed (the meaning is not lost between Dostoyevsky and Dostoevsky). If either version is closer to the name commonly used in English, use that.
 * Ё can be written as "yo", "o", or "e" (the latter two in the middle of words). Default to the first except for names that are commonly written in English with an "e" (like Mikhail Gorbachev). This arises from the umlauts usually being omitted in Russian media.
 * The hard vowel Ы is usually written as a "y".
 * Hard sign (Ъ) and soft sign (Ь) are both written as an apostrophe ('), except for titles (e.g. use Kazan for searches but Kazan' in text). If a vowel other than Я or Ю immediately follows a soft sign, write a "y" instead of an apostrophe.
 * The two letters Ш and Щ should be written as "sh" and "shch", respectively. Older sources might use diacritics (š for Ш and šč for Щ). The letter Ц is always written as "ts", never "tz".
 * The letter Ж is always "zh", although older sources might use a diacritic and write ž. In some rare cases, there is an established English transcription that uses "J" (e.g. Nijinsky, not Nizhinsky ).
 * Russian lacks a single letter for the English letter "J". Russian usually writes this sound (which almost always appears in foreign names) with the digraph ДЖ. This can be written either as "Dzh", or as "J". Try to avoid unnecessary confusion.
 * Таджикистан could be written as either Tajikistan or "Tadzhikistan"; use the former as that's what is used in English.
 * When romanizing initials, "Дж." will always romanize to "J".
 * The letter Х should always be written "kh". Russian lacks a sound for "h", so this letter should never appear in isolation. The letter К is always "k". The letter Ч is always "ch" as in "cheese".
 * The letter Й represents the Y consonant (as in "toy"), and is usually omitted from transliterations except for at the start of words or after a vowel (except Ы and И, since these would give a redundant double I or double Y).
 * When at the end of a word and after either Ы or И, only write the letter "y" once. There is no need to write out "yy" or "iy" or "yi", since in Russian these would all be pronounced as "y".
 * For example, Йогурт is written "yogurt" while Чайковский is written either as "Chaykovsky" (which is the direct letter-for-letter transcription) or as "Tchaikovsky" (the common Anglicization).

Thai
Thai romanization is generally a mess, with several incompatible 'standards' and lots of completely nonstandard off-the-cuff attempts. In general:

 * Use the most common English name for article names.

 * When in doubt, use the Royal Thai General System of Transcription (RTGS), used in road signs, time tables and government publications, and the closest thing there is to an official standard.
 * Hence Khao San Road, not "Kao Sarn", and Ayutthaya, not "Ayodhya"
 * In particular, Ko (not Koh) for islands
 * Always use RTGS if providing the pronunciation after a Thai name, eg. กรุงเทพฯ Krung Thep for the city known in English as Bangkok

See also: Wikipedia:Wikipedia:Manual of Style (Thailand-related articles)

Vietnamese
Vietnamese is actually written in the Latin alphabet, but the vast slew of tonal diacritics make handling it a little difficult.

 * Strip diacritics from article titles, but include them in the article body.
 * Hanoi (Hà Nội) is the capital of Vietnam...

 * Syllables should be separated in article titles and content, but include the combined form in the article body if it's a reasonably common alternative.
 * Nha Trang is a nice town and xe om motorbikes are dangerous
 * Ha Long Bay (Halong Bay) is pretty
 * Five exceptions to the rule: Dalat, Danang, Hanoi, Saigon and Vietnam itself

title: Wikivoyage:Romanization


text:
Wikivoyage:Routebox navigation

Routebox navigation is a supplement to the Go next section of an article which allows the user to browse directly from article to article along a given route or combination of routes, and gives the user a quick way to see what destination articles are nearby at a glance. The box contains a logo for each route in the center. To the left and right of the logo are 1) the direction the route follows, 2) the next minor destination, i.e. the next destination for which we have an article, and 3) the next major destination or major thoroughfare junction. More detailed descriptions of how to choose these follows in the sections below.

Templates
The Mediawiki template is used to create the boxes. The template is placed at the end of the Go next section, just before the breadcrumb navigation, geocoding or article status templates, and looks like this:

The above box is produced by the following code:

The 'link' parameter is normally left blank except where a highway is itself the basis for an itinerary such as Route 66. It can also be used to link to a section of a region page detailing the route. The 'caption' parameter can be used to change the text on mouse over when not linking to a dedicated page about the route.

The above box is produced by the following code:

Criteria for route inclusion
Preference should be given to routes which are most often used by travellers in the given area. Disagreements about whether a given route should be included should be addressed on the discussion page of the region or country for which the route applies. The routebox section should not be too cluttered and if possible be limited to the 9 most notable routes through a place (less for minor destinations).

In general, to be included, a route should have at least 4 destinations for which we have articles. Smaller routes such as state highways should be omitted if they duplicate the same access path as another route. Like other sections of our articles, the number of listings should never exceed nine.

Listing order
Preference should be given in the following order:
 * Famous historical routes (the Silk Road, Route 66, Camino de Santiago/Way of St. James)
 * High speed train lines
 * Regular train lines
 * Major national highways, in numerical order
 * Minor national highways, in numerical order
 * State highways, private toll roads, or scenic routes, in numerical order

Obtaining an icon
For numbered highways, official route shields are preferred when available. For many routes, an appropriate image can be found on the Route icon list or at commons:Category:Diagrams of route signs by country. The Wikipedia:WikiProject Highways task forces and subprojects (Canada, India, UK, US) have a good selection of route markers, most of which are directly available through Wikimedia Commons.

If no legally-usable official symbol can be found, you can create an icon by modifying the following .svg files with a program like Inkscape. The recommended font is the free version of Blue Highway by Ray Larabie. The recommended image size for the typical highway shield is 22 pixels.

For national routes, use white text on this shield: Image:blank national shield.svg For subnational routes, use black text over this shield: Image:Blank subnational shield.svg Other types of icons may be custom-created as needed. The preferred icon size is 100 by 25 pixels. Some examples:

If you import or create a new icon for a route, please add it to the appropriate part of the list, so that other users can find it.

Articles referencing an icon that does not exist are listed at Category:Routeboxes needing image.

Assigning directions
Directions should be assigned according to official signage when available. In general, the two directions indicated by the routebox should be consistent for the length of the route when possible. Exceptions can be made when official signage indicates, or for loop lines such as a highway which circumnavigates an island or, for example, Tokyo's Yamanote line. In many countries directions that are just a cardinal direction on the compass make little sense as the route curves and the signage only indicates city names.

 * For consistency's sake, the direction to the left of the icon should always be the westernmost or northernmost direction.

Assigning major destinations
Criteria for what is assigned as a major destination in each direction depends on the relative importance of the route.
 * Disagreements about whether a given city should be considered a major destination should be resolved on the talk page of the city in question.

For highways
For highways, the goal is to have the routebox match the signage the traveller will see along a given road.
 * If the route goes for 2 hours' travel time or more without a major city, the next biggest city in the region should be used to break it up.
 * If the route passes near a major city, that city should still be included as a major city if signage along the route indicates it. For example, Pittsburgh could be included along I-79 because signage for Pittsburgh via Spur I-279 is placed along I-79 in the region.
 * If a major junction point occurs at a place which is not a control city, that place may be used as a major
 * For routes away from large cities, preference for major destinations is given to places which have junctions with more important routes. For example if a less important US Route intersects an Interstate at a smaller city, that city should still be used as a control. Thus, for US-83 in the Texas Panhandle, Shamrock is used as a control city because it has a major junction with I-40.
 * Some routes may pass through many destinations of roughly the same size or importance without passing through any major city at all. Other routes may pass for more than two hours through dozens of smaller places before reaching a place for which we have an article. In these cases, the next destination may be used as the control.

For train lines
Most train lines have designated major destinations which often appear in a larger bold font or with a larger bullet on train route maps. For one route served by multiple types of trains, the routes served by the more "express" trains have a claim to "major" status but those served only by the more "local" trains do not. High speed rail lines sometimes have stops rather outside of established settlements, those should be mentioned if we have an article for them but they are almost invariably "minor" points on the routebox.

Assigning minor destinations
The minor destination in each direction should always be the next place along the route for which we have an article. This should include any national parks or state parks unless the next city is within the park. Care should be taken in assuring that nothing is skipped. Running names from a map into our search engine is generally a good way to ensure complete coverage.

Termini, merging, and rural junctions

 * When a route ends at the next destination, the next destination is listed as minor, and the field for major destination should read "END" (without quotes).
 * When a route ends at the current destination, the minor field is left blank, and the major field should read "END" (without quotes).
 * When a road route ends at a perpendicular route at a place for which we have no article, "Ends at" plus a reduced-size icon of the highway in question is used in place of "END".
 * When a route ends very near a major city, in a suburb for example, and the traveller could reasonably find their way into that city, that city may be used as a major destination.
 * When a route ends at a named destination for which we have no article, the destination name should be left unlinked.
 * When a road route merges with another route going in the same direction, "Merges with" plus a reduced-size icon of the highway in question is used in place of "END".
 * When a route changes name at a city or border in a way that no exit need be taken, "Becomes" plus a reduced-size icon of the highway in question should be inserted in the routeboxes of the adjacent destination articles.
 * When a road route crosses another route of equal or higher importance at a place for which we have no article, an unlinked text note reading "Junction" plus a reduced-size icon of the highway in question should be inserted, along with an arrow and space on the appropriate side. Insert the ← or → characters by entering &larr; or &rarr; as source, copying them from here, or by selecting those arrows in the editing toolbar, under Special characters… Symbols. Unices may have them as <Compose> < - and <Compose> - > respectively.

A fictitious box below illustrates how the above points should look when utilized:

Rest areas, travel information centers, and picnic areas
Rest areas, travel information centers, and picnic areas can be inserted in addition to the two destinations in each direction. They should only be inserted when they fall between the current article and the next destination and should be spaced with a single space and an arrow on the appropriate side in the field of the minor destination. Extra arrows can be produced by using the templates and  for right and left arrows respectively. The fictitious box below provides an example:

Inserting a new article in a pre-existing route
When inserting a new article along a route for which routeboxes are already implemented, don't forget to visit the article for the adjacent minor destinations and adjust the links to include the new article.

title: Wikivoyage:Routebox navigation


text:
Wikivoyage:Routebox navigation/I-90

I-90 [[Image:I-90.svg|22px]] (E to W)

 * End
 * Boston
 * Newton
 * Weston
 * (Rest Area)
 * Framingham
 * Hopkinton
 * Westborough
 * Millbury
 * (Worcester)
 * Auburn
 * (Rest Area)
 * Sturbridge
 * Palmer
 * (Rest Area)
 * Ludlow
 * Chicopee
 * (Springfield)
 * West Springfield
 * Westfield
 * (Rest Area)
 * Lee
 * (Rest Area)
 * West Stockbridge
 * Canaan
 * Chatham
 * Schodack
 * East Greenbush
 * North Greenbush
 * Rensselaer
 * Albany
 * Schenectady
 * Mohawk
 * Utica
 * Syracuse
 * Weedsport
 * Manchester
 * Victor
 * Rochester via [[Image:I-490.svg|22px]]
 * Batavia
 * Clarence
 * Buffalo
 * Eden
 * Fredonia
 * Westfield
 * Erie
 * Conneaut
 * Ashtabula
 * Mentor
 * Euclid
 * Cleveland
 * Lakewood
 * Rocky River
 * Avon
 * Elyria
 * Amherst
 * Milan
 * Fremont
 * Elmore
 * Perrysburg
 * Toledo

title: Wikivoyage:Routebox navigation/I-90


text:
Wikivoyage:Route icons

Also available on Wikimedia Commons at Wikivoyage route icons.

India
See commons:Category:Diagrams of route signs of India

Philippines
See Category:Diagrams of route signs of the Philippines for all numbered highway signs and expressway logos.

South Korea
See also commons:Category:Seoul_Subway_route_icons

Trans-Canada routes
See commons:Category:Highway shields in Canada and commons:Category:Trans-Canada Highway

Provincial and territorial routes
See commons:Category:Diagrams of road signs of Canada by province or territory

National Highways
See Commons:Category:Diagrams of route signs of Mexico

United States

 * See Project:United States route icons.

title: Wikivoyage:Route icons


text:
Wikivoyage:RSS feed

Wikivoyage has an RSS feed for showing updates to the site in RSS readers. The URL for the RSS is http://en.wikivoyage.org/wiki/index.php?title=Special:Recentchanges&feed=rss. The RSS is kind of remedial -- it would be nice to put "featured" items into the RSS page, rather than just anything.

de:Project:RSS Feed fr:Project:Flux RSS

title: Wikivoyage:RSS feed