text:
Wikivoyage:French Wikivoyage Expedition

The French Wikivoyage Expedition is an expedition to create a French language version of Wikivoyage which would effectively be the second multilingual version of Wikivoyage. It [//fr.wikivoyage.org/wiki/article/Accueil started] on February 12, 2004.

For more information on Multilingual Wikivoyage Policy, see Project:Language version policy.

Rationale
French is an important international language, being spoken in not only France and neighboring Switzerland and Belgium, but also Québec, several African countries, Laos, and some islands in Polynesia. A travel guide in French will make the world more accessible to Francophones.

Goals
The French Wikivoyage has the following goals:

 * To collect a good base of French users willing to take this project further
 * To translate and localize the English Wikivoyage into French.
 * To create quality articles that will appeal to Francophone travellers, wherever they come from.
 * To link these articles to English and Romanian 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 France, Switzerland, Québec, and anywhere else French is spoken.

Procedure
See also Project:Language version policy for more information about the procedure of forming a French Wikivoyage.

Completed: Gathering a team of users
To get this project started, we need at least 5 French-speaking users willing to contribute to French 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 French Wikivoyage and am willing to contribute:

 * (WT-en) Pierre Abbat 17:07, 22 Dec 2003 (PST)
 * (WT-en) Mark 10:58, 15 Jan 2004 (EST)
 * (WT-en) Yann 14:32, 18 Jan 2004 (EST)
 * (WT-en) Pontauxchats 07:56, 20 Jan 2004 (EST)
 * (WT-en) nikolai35 18:35, 5 Feb 2004 (EST)

Next Steps
After we have gathered a team of five or more users for French Wikivoyage, the interface localization file will be translated (or modified from the one on Wikipedia), checked for correctness, and then we will vote for a go-between.

The localization file is at Project:LanguageFr.php; an initial version based on the French Wikipedia interface file is already at that spot. For comparison, the English file is at Project:LanguageEn.php. Major things to watch for:

 * Replacing "Wikipedia" with "Wikivoyage"
 * Differences in license policy (GFDL versus CC by-sa)

Choosing a go-between
In order to make a successful, integrated French 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 French Wikipedia, and therefore, he must be able to:

 * Write English and French well
 * Understand Wikivoyage ideals, guidelines, goals and policies
 * Make monthly reports about French Wikivoyage to English Wikivoyage
 * Make monthly reports about English Wikivoyage to French Wikivoyage
 * Contribute actively in French 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:

 * Vote for (WT-en) Pierre Abbat
 * Votes for: (WT-en) Yann (WT-en) nikolai35 (WT-en) Mark
 * Votes against:
 * Vote for (WT-en) Mark
 * Votes for:
 * Votes against: (WT-en) Mark
 * Vote for (WT-en) Yann
 * Votes for: (WT-en) Pierre Abbat|(WT-en) Pontauxchats
 * Votes against:
 * Vote for (WT-en) Pontauxchats
 * Votes for:
 * Votes against:(WT-en) Pontauxchats [je ne parle pas assez bien l'anglais]
 * Vote for (WT-en) nikolai35
 * Votes for:
 * Votes against:(WT-en) Pontauxchats (WT-en) nikolai35

'''Voting will finish only once person listed above has voted - that is, Pierre, Mark, Yann, Pontauxchats, and Nikolai. Therefore, please put in your votes as soon as possible, because the Wikivoyage in French will becoming online sooner.'''

It would also be nice, but is not necessary, to have a go-between between the French Wikivoyage and the Romanian Wikivoyage.

Awareness Raising
fr:Project:Expédition Wikivoyage en français

title: Wikivoyage:French Wikivoyage Expedition


text:
Wikivoyage:Full text of the Attribution-ShareAlike 3.0 license

''The following is a copy of the Attribution-ShareAlike 3.0 license from Creative Commons, stored here for archival purposes. In case of any discrepancy between this copy and the one at http://creativecommons.org/licenses/by-sa/3.0/legalcode, the latter will be considered authoritative.''

Attribution-ShareAlike 3.0
CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE LEGAL SERVICES. DISTRIBUTION OF THIS LICENSE DOES NOT CREATE AN ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES REGARDING THE INFORMATION PROVIDED, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM ITS USE.

License

THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CREATIVE COMMONS PUBLIC LICENSE ("CCPL" OR "LICENSE"). THE WORK IS PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED.

BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. TO THE EXTENT THIS LICENSE MAY BE CONSIDERED TO BE A CONTRACT, THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.

1. Definitions

 * a. "Adaptation" means a work based upon the Work, or upon the Work and other pre-existing works, such as a translation, adaptation, derivative work, arrangement of music or other alterations of a literary or artistic work, or phonogram or performance and includes cinematographic adaptations or any other form in which the Work may be recast, transformed, or adapted including in any form recognizably derived from the original, except that a work that constitutes a Collection will not be considered an Adaptation for the purpose of this License. For the avoidance of doubt, where the Work is a musical work, performance or phonogram, the synchronization of the Work in timed-relation with a moving image ("synching") will be considered an Adaptation for the purpose of this License.
 * b. "Collection" means a collection of literary or artistic works, such as encyclopedias and anthologies, or performances, phonograms or broadcasts, or other works or subject matter other than works listed in Section 1(f) below, which, by reason of the selection and arrangement of their contents, constitute intellectual creations, in which the Work is included in its entirety in unmodified form along with one or more other contributions, each constituting separate and independent works in themselves, which together are assembled into a collective whole. A work that constitutes a Collection will not be considered an Adaptation (as defined below) for the purposes of this License.
 * c. "Creative Commons Compatible License" means a license that is listed at http://creativecommons.org/compatiblelicenses that has been approved by Creative Commons as being essentially equivalent to this License, including, at a minimum, because that license: (i) contains terms that have the same purpose, meaning and effect as the License Elements of this License; and, (ii) explicitly permits the relicensing of adaptations of works made available under that license under this License or a Creative Commons jurisdiction license with the same License Elements as this License.
 * d. "Distribute" means to make available to the public the original and copies of the Work or Adaptation, as appropriate, through sale or other transfer of ownership.
 * e. "License Elements" means the following high-level license attributes as selected by Licensor and indicated in the title of this License: Attribution, ShareAlike.
 * f. "Licensor" means the individual, individuals, entity or entities that offer(s) the Work under the terms of this License.
 * g. "Original Author" means, in the case of a literary or artistic work, the individual, individuals, entity or entities who created the Work or if no individual or entity can be identified, the publisher; and in addition (i) in the case of a performance the actors, singers, musicians, dancers, and other persons who act, sing, deliver, declaim, play in, interpret or otherwise perform literary or artistic works or expressions of folklore; (ii) in the case of a phonogram the producer being the person or legal entity who first fixes the sounds of a performance or other sounds; and, (iii) in the case of broadcasts, the organization that transmits the broadcast.
 * h. "Work" means the literary and/or artistic work offered under the terms of this License including without limitation any production in the literary, scientific and artistic domain, whatever may be the mode or form of its expression including digital form, such as a book, pamphlet and other writing; a lecture, address, sermon or other work of the same nature; a dramatic or dramatico-musical work; a choreographic work or entertainment in dumb show; a musical composition with or without words; a cinematographic work to which are assimilated works expressed by a process analogous to cinematography; a work of drawing, painting, architecture, sculpture, engraving or lithography; a photographic work to which are assimilated works expressed by a process analogous to photography; a work of applied art; an illustration, map, plan, sketch or three-dimensional work relative to geography, topography, architecture or science; a performance; a broadcast; a phonogram; a compilation of data to the extent it is protected as a copyrightable work; or a work performed by a variety or circus performer to the extent it is not otherwise considered a literary or artistic work.
 * i. "You" means an individual or entity exercising rights under this License who has not previously violated the terms of this License with respect to the Work, or who has received express permission from the Licensor to exercise rights under this License despite a previous violation.
 * j. "Publicly Perform" means to perform public recitations of the Work and to communicate to the public those public recitations, by any means or process, including by wire or wireless means or public digital performances; to make available to the public Works in such a way that members of the public may access these Works from a place and at a place individually chosen by them; to perform the Work to the public by any means or process and the communication to the public of the performances of the Work, including by public digital performance; to broadcast and rebroadcast the Work by any means including signs, sounds or images.
 * k. "Reproduce" means to make copies of the Work by any means including without limitation by sound or visual recordings and the right of fixation and reproducing fixations of the Work, including storage of a protected performance or phonogram in digital form or other electronic medium.

2. Fair Dealing Rights. Nothing in this License is intended to reduce, limit, or restrict any uses free from copyright or rights arising from limitations or exceptions that are provided for in connection with the copyright protection under copyright law or other applicable laws.

3. License Grant. Subject to the terms and conditions of this License, Licensor hereby grants You a worldwide, royalty-free, non-exclusive, perpetual (for the duration of the applicable copyright) license to exercise the rights in the Work as stated below:

 * a. to Reproduce the Work, to incorporate the Work into one or more Collections, and to Reproduce the Work as incorporated in the Collections;
 * b. to create and Reproduce Adaptations provided that any such Adaptation, including any translation in any medium, takes reasonable steps to clearly label, demarcate or otherwise identify that changes were made to the original Work. For example, a translation could be marked "The original work was translated from English to Spanish," or a modification could indicate "The original work has been modified.";
 * c. to Distribute and Publicly Perform the Work including as incorporated in Collections; and,
 * d. to Distribute and Publicly Perform Adaptations.
 * e. For the avoidance of doubt:
 * i. Non-waivable Compulsory License Schemes. In those jurisdictions in which the right to collect royalties through any statutory or compulsory licensing scheme cannot be waived, the Licensor reserves the exclusive right to collect such royalties for any exercise by You of the rights granted under this License;
 * ii. Waivable Compulsory License Schemes. In those jurisdictions in which the right to collect royalties through any statutory or compulsory licensing scheme can be waived, the Licensor waives the exclusive right to collect such royalties for any exercise by You of the rights granted under this License; and,
 * iii. Voluntary License Schemes. The Licensor waives the right to collect royalties, whether individually or, in the event that the Licensor is a member of a collecting society that administers voluntary licensing schemes, via that society, from any exercise by You of the rights granted under this License.

The above rights may be exercised in all media and formats whether now known or hereafter devised. The above rights include the right to make such modifications as are technically necessary to exercise the rights in other media and formats. Subject to Section 8(f), all rights not expressly granted by Licensor are hereby reserved.

4. Restrictions. The license granted in Section 3 above is expressly made subject to and limited by the following restrictions:

 * a. You may Distribute or Publicly Perform the Work only under the terms of this License. You must include a copy of, or the Uniform Resource Identifier (URI) for, this License with every copy of the Work You Distribute or Publicly Perform. You may not offer or impose any terms on the Work that restrict the terms of this License or the ability of the recipient of the Work to exercise the rights granted to that recipient under the terms of the License. You may not sublicense the Work. You must keep intact all notices that refer to this License and to the disclaimer of warranties with every copy of the Work You Distribute or Publicly Perform. When You Distribute or Publicly Perform the Work, You may not impose any effective technological measures on the Work that restrict the ability of a recipient of the Work from You to exercise the rights granted to that recipient under the terms of the License. This Section 4(a) applies to the Work as incorporated in a Collection, but this does not require the Collection apart from the Work itself to be made subject to the terms of this License. If You create a Collection, upon notice from any Licensor You must, to the extent practicable, remove from the Collection any credit as required by Section 4(c), as requested. If You create an Adaptation, upon notice from any Licensor You must, to the extent practicable, remove from the Adaptation any credit as required by Section 4(c), as requested.
 * b. You may Distribute or Publicly Perform an Adaptation only under the terms of: (i) this License; (ii) a later version of this License with the same License Elements as this License; (iii) a Creative Commons jurisdiction license (either this or a later license version) that contains the same License Elements as this License (e.g., Attribution-ShareAlike 3.0 US)); (iv) a Creative Commons Compatible License. If you license the Adaptation under one of the licenses mentioned in (iv), you must comply with the terms of that license. If you license the Adaptation under the terms of any of the licenses mentioned in (i), (ii) or (iii) (the "Applicable License"), you must comply with the terms of the Applicable License generally and the following provisions: (I) You must include a copy of, or the URI for, the Applicable License with every copy of each Adaptation You Distribute or Publicly Perform; (II) You may not offer or impose any terms on the Adaptation that restrict the terms of the Applicable License or the ability of the recipient of the Adaptation to exercise the rights granted to that recipient under the terms of the Applicable License; (III) You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties with every copy of the Work as included in the Adaptation You Distribute or Publicly Perform; (IV) when You Distribute or Publicly Perform the Adaptation, You may not impose any effective technological measures on the Adaptation that restrict the ability of a recipient of the Adaptation from You to exercise the rights granted to that recipient under the terms of the Applicable License. This Section 4(b) applies to the Adaptation as incorporated in a Collection, but this does not require the Collection apart from the Adaptation itself to be made subject to the terms of the Applicable License.
 * c. If You Distribute, or Publicly Perform the Work or any Adaptations or Collections, You must, unless a request has been made pursuant to Section 4(a), keep intact all copyright notices for the Work and provide, reasonable to the medium or means You are utilizing: (i) the name of the Original Author (or pseudonym, if applicable) if supplied, and/or if the Original Author and/or Licensor designate another party or parties (e.g., a sponsor institute, publishing entity, journal) for attribution ("Attribution Parties") in Licensor's copyright notice, terms of service or by other reasonable means, the name of such party or parties; (ii) the title of the Work if supplied; (iii) to the extent reasonably practicable, the URI, if any, that Licensor specifies to be associated with the Work, unless such URI does not refer to the copyright notice or licensing information for the Work; and (iv), consistent with Ssection 3(b), in the case of an Adaptation, a credit identifying the use of the Work in the Adaptation (e.g., "French translation of the Work by Original Author," or "Screenplay based on original Work by Original Author"). The credit required by this Section 4(c) may be implemented in any reasonable manner; provided, however, that in the case of a Adaptation or Collection, at a minimum such credit will appear, if a credit for all contributing authors of the Adaptation or Collection appears, then as part of these credits and in a manner at least as prominent as the credits for the other contributing authors. For the avoidance of doubt, You may only use the credit required by this Section for the purpose of attribution in the manner set out above and, by exercising Your rights under this License, You may not implicitly or explicitly assert or imply any connection with, sponsorship or endorsement by the Original Author, Licensor and/or Attribution Parties, as appropriate, of You or Your use of the Work, without the separate, express prior written permission of the Original Author, Licensor and/or Attribution Parties.
 * d. Except as otherwise agreed in writing by the Licensor or as may be otherwise permitted by applicable law, if You Reproduce, Distribute or Publicly Perform the Work either by itself or as part of any Adaptations or Collections, You must not distort, mutilate, modify or take other derogatory action in relation to the Work which would be prejudicial to the Original Author's honor or reputation. Licensor agrees that in those jurisdictions (e.g. Japan), in which any exercise of the right granted in Section 3(b) of this License (the right to make Adaptations) would be deemed to be a distortion, mutilation, modification or other derogatory action prejudicial to the Original Author's honor and reputation, the Licensor will waive or not assert, as appropriate, this Section, to the fullest extent permitted by the applicable national law, to enable You to reasonably exercise Your right under Section 3(b) of this License (right to make Adaptations) but not otherwise.

5. Representations, Warranties and Disclaimer

UNLESS OTHERWISE MUTUALLY AGREED TO BY THE PARTIES IN WRITING, LICENSOR OFFERS THE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE WORK, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO SUCH EXCLUSION MAY NOT APPLY TO YOU.

6. Limitation on Liability. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE OR THE USE OF THE WORK, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

7. Termination

 * a. This License and the rights granted hereunder will terminate automatically upon any breach by You of the terms of this License. Individuals or entities who have received Adaptations or Collections from You under this License, however, will not have their licenses terminated provided such individuals or entities remain in full compliance with those licenses. Sections 1, 2, 5, 6, 7, and 8 will survive any termination of this License.
 * b. Subject to the above terms and conditions, the license granted here is perpetual (for the duration of the applicable copyright in the Work). Notwithstanding the above, Licensor reserves the right to release the Work under different license terms or to stop distributing the Work at any time; provided, however that any such election will not serve to withdraw this License (or any other license that has been, or is required to be, granted under the terms of this License), and this License will continue in full force and effect unless terminated as stated above.

8. Miscellaneous

 * a. Each time You Distribute or Publicly Perform the Work or a Collection, the Licensor offers to the recipient a license to the Work on the same terms and conditions as the license granted to You under this License.
 * b. Each time You Distribute or Publicly Perform an Adaptation, Licensor offers to the recipient a license to the original Work on the same terms and conditions as the license granted to You under this License.
 * c. If any provision of this License is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this License, and without further action by the parties to this agreement, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
 * d. No term or provision of this License shall be deemed waived and no breach consented to unless such waiver or consent shall be in writing and signed by the party to be charged with such waiver or consent.
 * e. This License constitutes the entire agreement between the parties with respect to the Work licensed here. There are no understandings, agreements or representations with respect to the Work not specified here. Licensor shall not be bound by any additional provisions that may appear in any communication from You. This License may not be modified without the mutual written agreement of the Licensor and You.
 * f. The rights granted under, and the subject matter referenced, in this License were drafted utilizing the terminology of the Berne Convention for the Protection of Literary and Artistic Works (as amended on September 28, 1979), the Rome Convention of 1961, the WIPO Copyright Treaty of 1996, the WIPO Performances and Phonograms Treaty of 1996 and the Universal Copyright Convention (as revised on July 24, 1971). These rights and subject matter take effect in the relevant jurisdiction in which the License terms are sought to be enforced according to the corresponding provisions of the implementation of those treaty provisions in the applicable national law. If the standard suite of rights granted under applicable copyright law includes additional rights not granted under this License, such additional rights are deemed to be included in the License; this License is not intended to restrict the license of any rights under applicable law.

Creative Commons Notice

Creative Commons is not a party to this License, and makes no warranty whatsoever in connection with the Work. Creative Commons will not be liable to You or any party on any legal theory for any damages whatsoever, including without limitation any general, special, incidental or consequential damages arising in connection to this license. Notwithstanding the foregoing two (2) sentences, if Creative Commons has expressly identified itself as the Licensor hereunder, it shall have all rights and obligations of Licensor.

Except for the limited purpose of indicating to the public that the Work is licensed under the CCPL, Creative Commons does not authorize the use by either party of the trademark "Creative Commons" or any related trademark or logo of Creative Commons without the prior written consent of Creative Commons. Any permitted use will be in compliance with Creative Commons' then-current trademark usage guidelines, as may be published on its website or otherwise made available upon request from time to time. For the avoidance of doubt, this trademark restriction does not form part of the License.

Creative Commons may be contacted at http://creativecommons.org/.

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


text:
Wikivoyage:Full text of the GNU Free Documentation License, Version 1.2

''This is a copy of the GNU Free Documentation License, Version 1.2, also available online here; any discrepancies between this copy and the version there are accidental, and that document is definitive. This copy is provided as a courtesy to those contributors to Wikivoyage who wish to release their work under a dual license.''

GNU Free Documentation License ******************************

Version 1.2, November 2002 Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.    59 Temple Place, Suite 330, Boston, MA  02111-1307, USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

0. PREAMBLE

The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to    assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or    noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a    free program should come with manuals providing the same freedoms that the software does. But this License is not limited to    software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is    instruction or reference.

1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it    can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a    way requiring permission under copyright law.

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document    is in part a textbook of mathematics, a Secondary Section may not     explain any mathematics.)  The relationship could be a matter of     historical connection with the subject or with related matters, or     of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in    the notice that says that the Document is released under this License. If a section does not fit the above definition of    Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A    Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images    composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to    text formatters or for automatic translation to a variety of     formats suitable for input to text formatters. A copy made in an    otherwise Transparent file format whose markup, or absence of     markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is    not Transparent if used for any substantial amount of text. A    copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or    XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title    Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ    stands for a specific section name mentioned below, such as     "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in    this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

2. VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

3. COPYING IN QUANTITY

If you publish printed copies (or copies in media that commonly    have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in    other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit    reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a    machine-readable Transparent copy along with each Opaque copy, or     state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or    retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of    the Document well before redistributing any large number of     copies, to give them a chance to provide you with an updated version of the Document.

4. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to    whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of         previous versions (which should, if there were any, be listed          in the History section of the Document). You may use the same title as a previous version if the original publisher of         that version gives permission.

B. List on the Title Page, as authors, one or more persons or         entities responsible for authorship of the modifications in          the Modified Version, together with at least five of the principal authors of the Document (all of its principal         authors, if it has fewer than five), unless they release you from this requirement.

C. State on the Title page the name of the publisher of the Modified Version, as the publisher.

D. Preserve all the copyright notices of the Document.

E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.

F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in         the Addendum below.

G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's         license notice.

H. Include an unaltered copy of this License.

I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on         the Title Page. If there is no section Entitled "History" in         the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in         the previous sentence.

J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in         the "History" section. You may omit a network location for a         work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.

K. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.

L. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.

M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.

N. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.

O. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or    appendices that qualify as Secondary Sections and contain no     material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be    added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting o n behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to    assert or imply endorsement of any Modified Version.

5. COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a    unique number. Make the same adjustment to the section titles in    the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements."

6. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of    that document.

7. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of    a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.

8. TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a    translation of this License, and all the license notices in the Document, and any Warrany Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a    disagreement between the translation and the original version of     this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to    Preserve its Title (section 1) will typically require changing the actual title.

9. TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is    void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

10. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of    the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See `http://www.gnu.org/copyleft/'.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of    that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If    the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

ADDENDUM: How to use this License for your documents ====================================================

To use this License in a document you have written, include a copy of  the License in the document and put the following copyright and license notices just after the title page:

Copyright (C) YEAR  YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU      Free Documentation License".

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with...Texts." line with this:

with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.

If your document contains nontrivial examples of program code, we  recommend releasing these examples in parallel under your choice of   free software license, such as the GNU General Public License, to   permit their use in free software.


text:
Wikivoyage:Geocoding

It's possible to encode information about the latitude and longitude of a destination, or of individual points of interest at the destination, into the guide itself. This information is used to generate locator maps and special HTML tags (hCards) which relate a Web page to a geographic location.

For a destination
The easiest way to add lat/long information to a destination guide article is to use the Geo template. To do so, add the following code to a page:

Here, lat is the latitude and long is the longitude. Both coordinates must be in decimal form ("45.5", not "45 30 00")--see Converting from traditional format. For example, Montreal contains the code:

which renders the map link in the upper righthand corner of that page.

A world map showing all geocoded destinations in the English-language Wikivoyage appears at https://wikivoyage.toolforge.org/w/artmap.php?lang=en

Note that only one geo instance in a page makes sense.

 * find destination articles without a Geo parameter

For an individual point of interest
To encode GPS information for listings in Wikivoyage, use the lat and long attributes in the listing tags or template. Each listing item displays an icon with a link to a locator map with the supplied decimal co-ordinates.

A listing or marker typically locates a point of interest, such as an individual landmark or building.

or:

gives:

...with an icon linking to an OpenStreetMap-based locator map. The 'type' is normally one of (see, do, buy, eat, drink, sleep, listing); the use of cities as points of interest may occur in itinerary.

As this allows decimal co-ordinates to be specified for every individual listing, it can be useful for pinpointing locations with no street address (such as statues or markers surrounded by parkland). See How to use dynamic maps for details on using geocoded POI's and GPX paths to build dynamic maps.

Metadata
In the past, we used the Resource Description Framework (RDF) format to encode one pair of lat/long co-ordinates into each page; a template generated HTML code like:

<rdf> <> dcterms:spatial [ pos:lat "45.5" ; pos:long "-73.6" ].

to indicate that "this page covers something with lat/long of 45.5/-73.6". Wikivoyage does not currently use RDF, instead using the hCard microformat to encode (lat, long) co-ordinates for each listing in a format which can be read (and downloaded as a .kml file) by the Firefox Operator extension. These also provides a vCard-like format for contact info for each templated listing.

The hCard microformat is generated automatically by the listing template.

Limitations
Because the RDF system assigned a single geographic point to the entire destination guide, it was only suited to locations that were a) big enough to have a whole guide to themselves and b) small enough that a single point is a reasonable approximation for the location; effectively, only city guides were amenable to geocoding in this way.

This functionality corresponded to the current geo tag. Wikivoyage eV now generates world maps based on these co-ordinates, for instance https://wikivoyage.toolforge.org/w/artmap.php?lang=en which uses the geo tags in database dumps.

With the hCard format, it is possible to assign points to individual listings in a guide using Listings. From these, mapframe may be used to place an automatically-generated locator map on-page at the local (city/town destination) level.

Converting from traditional format
To convert from traditional format like lat=N45°30'0", long=W73°36'0", the following can help:
 * X°Y'Z" = X+(Y/60)+(Z/3600)
 * for S, add "-" to lat; for N, assume "+"
 * for W, add "-" to long; for E, assume "+"

title: Wikivoyage:Geocoding


text:
Wikivoyage:Geographical data and metadata

This article is about incorporating geographical data and metadata into Wikivoyage.

What is geographical data?
Geographical data, for this discussion, is information about the latitude and longitude of something on the face of planet Earth. Given a latitude and longitude pair of sufficient precision, a more-or-less exact spot on Earth can be determined.

What is geographical metadata?
Metadata is data about other data. For Wikivoyage, it means adding information about a page or the subject of that page.

There's an informal standard for representing geographical metadata in HTML pages, using the HTML tag. A metatag for latitude and longitude looks like this:

Proposed by GeoURL

The "ICBM" name comes from an old Internet joke that a lat-long pair is an "ICBM address", that is, how you would send an intercontinental ballistic missile somewhere.

or Proposed by geotags

It's unstated whether the ICBM address or geo.position refers to where the Web server is located, where the author of the page is located, or where the subject of the Web page is located. The same tag is used for all these purposes.

Geographical metadata on the Web
Some Web sites use geographical metadata to cluster Web pages according to their geographical metadata. A prominent one is GeoURL. And there are Web sites that help you to create these metadata online. One is Geo-Tag.de.

Uses for Wikivoyage
A few possible uses for geographical metadata exist in Wikivoyage.

 * 1) Giving the location of a city discussed in a city guide. Using a tool like GeoURL, a reader on the Web could find other Web pages related to the city.
 * 2) Giving the location of attractions (restaurants, bars, hotels, etc.). This would make it easier for someone with a GPS device -- a tool to determine one's exact latitude and longitude using information from satellites -- to find their way to attractions.
 * 3) Augmenting Wikivoyage maps. It might be possible to use geographical data to place attractions, cities, or regions on maps automatically.

Reservations
Although this is all pretty nifty stuff, there's some question as to the utility of geographical data and metadata.

 * GeoURL and other metadata aggregators are kinda great for Web usage, but it doesn't do much for printed guides (and printable guides are part of our goals).
 * GPS info for attractions is also useful for those people who have GPS tools. For those who don't, a lot of extraneous numbers are going to clutter up a guide pretty quickly.
 * It's questionable whether GPS information for an attraction is better than the street address and additional directions, as we use now in listings.

Adding geographical metadata
The software we use, MediaWiki, doesn't support adding free-form metadata to articles. There's a proposal for adding some metadata to articles in the next release. This is probably the best bet for getting ICBM meta tags added to articles. de:Project:Geografische Daten und Metadaten


text:
Wikivoyage:Geographical hierarchy

Geography is one way of looking at travel (there are other ways of seeing travel). The geographical hierarchy is the way we arrange Wikivoyage articles according to their geography – what areas they contain, and what area they are contained within. Each level of the geographical hierarchy has an article of its own.

Purpose
The point of the hierarchy is not to nitpick about geographical niceties, but to organize our work. What do we write Wikivoyage articles about? What are the subjects of our discussions? What kind of article do I write about topic X? A hierarchy of geographical units allows us to use them to identify things we write about, and thus how we write about them.

For example, consider Catalonia. By understanding the hierarchy, a contributor can know that Catalonia is a region. From there, they can figure out that the article about Catalonia should start with the region article template; that it should contain links to cities in Catalonia like Barcelona; and that there should be a link to the Catalonia article from its containing country, Spain. They also know what not to put in – that information about money should go up at the country level, and that listings for individual restaurants and hotels should go down at the city level.

By having a hierarchy, we don't have to figure out this stuff over and over again for every region in the world. Sure, there will be exceptions for every place, but by having rough guidelines, we can have a framework to make those exceptions against.

These levels of hierarchy aren't hard and fast, and they're open to revision. But it makes sense for articles at a given level of hierarchy to have links to the next level down in the hierarchy, and for articles at the same level of hierarchy to be about the same.

Given that changes to the regional hierarchy often have a wide-ranging impact, it can be helpful to mention and discuss the proposed changes on the discussion page of the appropriate region.

The hierarchy
The Wikivoyage geographical hierarchy goes like this:

 * The Earth contains
 * Continents, which contain...
 * Continental sections, which contain...
 * Countries, which contain...
 * Regions, which may contain...
 * More regions, which contain...
 * Cities, which may contain...
 * Districts.
 * Other divisions/rural areas.

Levels in the hierarchy can be skipped if they don't make sense. For example, the country of Andorra is only a few square miles in size; it would be laughable to write articles about its different regions.

Continents
Continents are big sections of the globe. We've started with Asia, Africa, North America, etc., and a separate pseudo-continent of Island nations. There's not actually much practical travel information that can be given on, say, Asia, but it does provide a convenient container for the next level of hierarchy.

Continental sections
A section is a division of a continent into a logical travel part. Classic examples include Southeast Asia and Central Europe. Not all continents need to be divided into sections, and sometimes the sections chosen may be equivalent to national boundaries. For example, it's natural to divide North America into Canada, the United States, Mexico, and Central America, even though the first three are all individual countries. In a few cases these can have sub-sections; the Caribbean in North America contains the Lesser Antilles and the Leeward Antilles, which consist of many countries and territories.

Countries
A country is usually a sovereign state territory on the globe, like Djibouti, France, or Brazil. Countries tend to be the level where information about currency, immigration, language, and culture are described. This level cannot be skipped.

Some countries like Monaco or Singapore are so small that they can be considered single cities. In these cases, omit headings like "Cities" and "Other destinations" and add city-level headings like "Go next"; if such an article grows large enough, divide it into city districts.

Regions
A region is a subnational division that is climatically, culturally, geographically, or politically coherent. Regions may lie along subnational borders—like states in the U.S., provinces in Canada, or departments in France—but more often they are above this level. One could divide Vietnam, for example, into the North (Hanoi and environs), the Central Coast (Danang, Hoi An, Nha Trang), the Central Highlands (Dalat and nearby) and the South (Saigon and the Mekong Delta). Due to the diversity of regions, there is no single rule for regionalization, beyond doing our best to use divisions that are useful for the traveler.

Importantly, we only add a level of regions when there is too much content in the existing breakdown. As a result, the regional hierarchy at Wikivoyage doesn't always follow the official breakdown — and frequently is much "flatter" than the official political or administrative breakdown. If there are more than nine cities or other destinations, but splitting into subregions does not otherwise make much sense, they can be grouped in the region article, to avoid overly long lists (see Article_templates/Sections#Cities).

It's not impossible for regions to cross national borders—the Himalayas is a good example—but the idea is to have travel divisions below the nation level. Also, bodies of water are usually not considered regions, but exceptions can be made on a case-by-case basis. Regions that do not follow the hierarchy are labeled extra-hierarchical regions.

For large countries, regions can and should contain other regions, to make it easier to grasp. For example, the United States has 50 legal divisions – more, if you count territories like the District of Columbia or Guam – which is probably too many bits for people to grasp all at once. We've divided the U.S. into 10–12 regions, each of which in turn contains one or more of the American states (which are themselves divided into regions). It may be reasonable to do this in other countries, although (as noted above) it's not always necessary to divide our regions along political boundaries.

Some territories are far from their associated country (French Guiana, Easter Island etc), have special political status (Svalbard, Hong Kong etc), or claim sovereignty without wide recognition (Palestinian territories, Somaliland, Taiwan, Transnistria, etc). Wikivoyage's categorization of these territories should make sense to a visitor from abroad; especially when it comes to transportation and border controls. For instance, French Guiana's location in South America is more relevant to most travellers than its political association with France, so it is described as a "country" in South America. While Svalbard has a free immigration system and is in the Arctic Ocean far from mainland Europe, it is governed by Norway, and all regular flights to Svalbard arrive from Norway where passengers need to clear Norwegian border controls; therefore Svalbard is described as a region of Norway. Taiwan and Transnistria are functionally independent countries with individual border policies, so they are described as countries. The status of an article does not imply any political endorsement; see Be fair.

Cities
A city is, in reality, the unit of travel guide geography. It's where you arrive to, where you go see sights, where you find a hotel, where you eat in restaurants, where you move on from when you're done. Wikivoyage's definition of a "city" is flexible: they may be literal incorporated cities, but they can also be larger metropolitan areas with suburbs and satellite cities, like Los Angeles or Paris, or they can be smaller towns or villages, like Zermatt or Panmunjeom. Occasionally a city-level destination article will cover a large rural area, serving as a container for multiple tiny villages, parks or islands. Whether particular suburbs, satellite cities, and villages deserve their own Wikivoyage entries is a matter of judgement – usually depending on the amount of information about those places. We have different templates to deal with cities of different sizes and complexity.

Most information in Wikivoyage will be about specific cities – the practical dollars-and-addresses info. See What is an article? for help in drawing the line between cities and attractions in cities, as well as dealing with non-settlement destinations like national parks.

Districts
Some cities are so big and diverse that there's too much information for one Wikivoyage article. It would make sense, then, to divide the city again into districts, so that practical info – hotel listings, restaurants, bars, sightseeing attractions – can get their due. Examples of districts in San Francisco would be San Francisco/Golden Gate, San Francisco/Tenderloin, and San Francisco/Mission.

Whether to break a city into districts is a matter of content, not so much the city's land area or population. Lubbock is a big city geographically, but it just doesn't have enough stuff to write about to justify classifying it as a "huge" city and breaking it down into district articles. As a general principle, a city with over a million inhabitants could be considered for districtification, but there are much bigger cities (e.g. Ibadan, Kinshasa or Bangalore) for which districtification does not assist the traveller and some smaller cities (e.g. Canberra, Richmond or Charlotte) that work better with it.

Other divisions
Many attractions, restaurants, and retreats do not fit neatly into the categories listed above. In particular, large rural areas (e.g., Rural Montgomery County or Western Barbados), in which individual towns do not merit their own articles—which would lead to an excess of articles, and content spread across too many separate pages—can benefit from having their own articles. Other divisions are essentially deliberate agglomerations of areas that don't fit into our city articles. Choose names for this section that best represent their nature: "regions" (note that this term in this case does not correspond to the region articles described above, which contain other articles); "rural areas," which obviously suit rural areas well; or "other areas" for cases that are not so neat. In some cases, it may make sense to treat a small city or town and its surrounding rural villages as one entity. If helpful, you may think of other divisions as "bottom level regions," in which listings are allowed.

Most "large, sparsely-populated rural area" articles will fit into the Rural area article template, or in Small city article template as if they were individual towns or cities.

There are a few special categories of article which have their own specific template: the Airport Expedition has an airport article template and a large provincial or national park may use the national park article template.

Examples
Here's an example of the hierarchical levels described above:
 * Asia (continent)
 * Africa (continent)
 * Europe (continent)
 * North America (continent)
 * Canada (country)
 * Mexico (country)
 * United States of America (country)
 * New England (region)
 * Midwest (region)
 * California (region)
 * Sacramento Valley (region)
 * Sierra Nevada (region)
 * Bay Area (region)
 * Berkeley (city)
 * Palo Alto (city)
 * San Francisco (city)
 * Mission-Bernal Heights (district)
 * Golden Gate (district)
 * Castro-Noe Valley (district)

The hierarchy of each article is automatically displayed in the breadcrumb navigation menu at the top of each article. For example, Castro Street's breadcrumb menu shows:

 * North America > United States of America > California > Bay Area > San Francisco > Castro-Noe Valley

Creating these menus requires entering the correct isPartOf tag, see breadcrumb navigation for the details.

Dividing geographical units
Dividing geographical units is something of a dark art. Use caution, consensus, and collaboration when possible. Some of the geographical units in this hierarchy are easy to decide on, in that they have legal boundaries: cities and countries, for example. Others are so well accepted that it's hard to imagine them being controversial, such as continents. But the others – continental sections, regions, and city districts – have fuzzier boundaries and definitions. How, then, do we decide where to define them?

Some guidelines are:
 * The 7 ± 2 rule. Our hierarchies work best with a moderate number of items at each level; a good target is around seven items, plus or minus two. With fewer than five items, the subdivision starts to appear inefficient and excessive; with more than nine, it becomes difficult for the reader to distinguish the individual items.  As such, when the number of subdivisions exceeds nine, it's time to start looking at an intermediate subdivision. That's not to say we never exceed nine! Sometimes there's just no logical alternative division, particularly at the lowest levels of the hierarchy. Remember: when dividing regions, use a breakdown that is most practical from the traveller's viewpoint, even if that creates a hierarchy that violates the 7±2 rule of thumb.
 * Traditional definitions. Some regions or continental sections or districts have traditional definitions: the Benelux countries, The Lake District, the American Southwest. It's best when possible to follow these traditional groupings, as travellers will recognize them.
 * Political or legal definitions. Some countries are divided into states, provinces, counties, cantons or what have you by their governments. It sometimes makes sense to use these if they're the best way to break up a region, and when they're not so numerous they'd grossly violate the 7±2 rule. For example, Mexico has 32 states—far too many to be top level regions.
 * Geography. Some areas have clear geographical features that are recognizable to travellers and dictate the kind of activities can be undertaken there. For example, the Finger Lakes or the Saxon Ore Mountains.
 * Language or cultural definitions. Some countries have clean divisions between language or ethnic lines. So, for example, Belgium might be easy to divide into Dutch-speaking Flanders and French-speaking Wallonia.

Districts in cities
Deciding when the city should be treated as huge and therefore needs districts articles is a bit tricky. It's easy to create dozens of district articles, but from this point it may become a nightmare to keep them organized and synchronized. This is why we have some recommendations on when to districtify:

 * don't start splitting a city into districts before there's enough content
 * don't create district articles until you have proposed a comprehensive districts hierarchy for the city, which has no gaps, no overlap
 * don't start moving out information into districts unless you have at least one contributor who is willing and ready to rewrite the main article sections, to give overviews with pointers to the most important and relevant information within the district articles.
 * avoid creating a separate district article until we have enough content for it
 * to breed content for a district(s), you can create a subsection for that district(s) in the respective section (See, Do, Eat, Sleep) in the main city article

Once we have enough content for creating a district article, we want to make sure it's clear where all the information goes. Prior to adding district articles:
 * define district borders for those districts that we are ready to separate; ideally have a map clearly showing districts and borders
 * post the district borders section on the city article's talk page

Once the new district articles have been created, all listings should be moved to district articles. Consider putting the template movetodistrict at the start of sections that need to be sorted into districts. This adds a message which encourages editors to move the content. Remove movetodistrict when the content has been moved out.

Note on legal names versus travel names
The legal divisions in the geography of the world – nations, provinces, and municipalities – don't necessarily make for reasonable travel divisions. Just because a national government decides it would be easier to administer an area by laying down lines on an official map doesn't mean that the official legal divisions deserve separate articles in Wikivoyage. For example, the island of Bali in Indonesia has 8 regencies, but a different regional structure is used instead.

Overlap
In general, we try to avoid overlap between two destination guides, unless one destination contains the other. If we have overlapping guides, readers don't know where to go to get travel information, and contributors don't know where to put travel information. It's also easier to draw maps for a destination if none of the parts of the destination overlap.

No two regions at the same level of the hierarchy should overlap. Nonetheless, if a subregion is commonly understood as belonging to more than one parent region (e.g., Russia is in both Asia and Europe) it is perfectly fine to list it in both parent regions as long as this does not create significant content overlap. A region's breadcrumb trail, however, will display only a single parent region in a strict hierarchical fashion.

Occasionally a well-defined region will straddle a political boundary between two countries, states, or provinces. It is usually preferable to deal with these instances as a single region, rather than dividing them up into unnatural, small pieces divided by the imaginary lines of borders. We have a template for extra-hierarchical regions, things that are clearly regions but do not fit in our hierarchy; for instance: The extra region template should be used sparingly; not all regions that cross borders require it. Often it is enough to have one article in the main region that mentions the other regions.
 * Niagara Falls on the Canada-US boundary, and Nogales on the US-México border. These are covered by an extraregion plus a city article for each side.
 * Lake Tai in China has an extraregion article, and there are articles for about half a dozen cities around it.
 * Thousand Islands, a highly-rural mix of parkland, tiny cottages and the occasional isolated hamlet, is breadcrumbed to North America as it's split by the Ontario-New York State boundary but is not populous enough to fill a Niagara Falls-style pair of city articles.
 * Mountain ranges often extend across borders, so articles like Himalayas or Appalachian Mountains are tagged as extra regions.
 * Many river systems do not get articles, and some of those that do get itinerary articles such as Along the Yangtze River, but some get extra region articles like Great Lakes.
 * Some geographic regions take up the vast majority of their parent country or region, such as the Lower Peninsula in Michigan and Honshu in Japan. These are tagged as extra regions and regions that divide up these extra regions are used in the hierarchy instead.
 * Lake Tahoe, a region in both California and Nevada, is breadcrumbed to California.
 * Yellowstone National Park spans portions of three US states, but is treated as if it were primarily in Wyoming.
 * Sioux City is primarily in Iowa, although it sprawls into two other US states.
 * Kansas City is divided by the Kansas-Missouri border; there is an article for each side, with Kansas City MO as the main entry.
 * Glenrio, on the Texas-New Mexico border, is too small for two articles as it's a ghost town. It's breadcrumbed to the Texas Panhandle.

Gaps
Regions and districts breakdowns should never leave any gaps. Wikivoyage is a guide to the world, and there should be a space to add content for travel advice on any destination on the planet.

Remote or inaccessible destinations
Some remote destinations, especially oceanic islands and enclaves/exclaves, have no scheduled connections or hospitality venues; entrance might also be legally restricted. These are of little interest to the average traveller, but articles about them can have some trivia value. While these locations can be difficult to fit into the hierarchy, they should still go somewhere. The blurb of the superior article should tell the reader whether the destination is remote or inaccessible.
 * Antarctica, including surrounding islands, is described as a continent.
 * Some remote destinations, especially islands, go under the Other destinations category.
 * Overseas territories, which are distant from their parent country, are placed into regions along geographic (not political) lines. U.S. Virgin Islands is breadcrumbed to Caribbean, not to USA.
 * Crewed space travel, including the Apollo moonshots, is a special case; it might fit other destinations or be treated as a travel topic.
 * A territory not too far from an associated country can be categorized as a region of that country: For example, Jan Mayen is described as a region of Norway.
 * Some places can be described as part of a continental section. Europa Island and the Glorioso Islands are part of the East African Islands region, on a secondary "countries and territories" list.
 * Isolated man-made structures such as Sealand, or very small islets such as ATOW1996 might be less suitable for a separate article, and might be described as a venue within a nearby destination or as an "other destination" of a region (these two in Felixstowe and Northern Greenland respectively).
 * Next-to-impossible destinations is a non-geographic list of many of these places, and that's where e.g. Rockall is described.

Linking articles
Every city or other destination article should be listed in at least one region article, as it should be possible to navigate through the hierarchy to each and every destination article on the site. Cities, Other divisions, and Other destinations should be mentioned under those section headings in at least the surrounding Region article. This should normally be the same article mentioned in the IsIn or IsPartOf template.

Regions should be mentioned in both the next larger region up in the hierarchy and in all the destinations within that region.

When Destinations are close to each other, but not in the same regional hierarchy, it is useful to mention them in each other's Go next section.

Keeping it together
Sometimes it may be better to keep things together rather than subdividing further. Do not create an article about a geographical unit just because someone has given a name to some part of the countryside. Geographical unit articles need to meet the criteria for articles too. There should be enough scope in the article to have at least 4 or 5 good quality destinations or attractions, especially for regions.

title: Wikivoyage:Geographical hierarchy


text:
Wikivoyage:German Wikivoyage Expedition

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

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

Rationale
Germans, Austrians, most Swiss, and others in Europe speak German. About 130 million people world-wide have German as their mother tongue, which means that a German version of Wikivoyage would serve a wide audience.

In addition, contributions in German would help the other Wikivoyage language versions. Many German-speaking parts of Europe are major travel destinations; having locals update information in their native tongue (which could then be translated to other languages) would make for better information in all the Wikivoyage guides. German-speakers are also frequent travelers and would have a lot to contribute on other destinations and topics.

Goals
This Expedition has the following goals:

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

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

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

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

 * (WT-en) Cyril2000 07:31, 14 Mar 2004 (EST)
 * (WT-en) Denisoliver 10:03, 25 Mar 2004 (EST)
 * (WT-en) Hansm 10:00, 2004 Apr 17 (EDT) (not for translating into English.)
 * (WT-en) EBB 15:42, 25 Jul 2004 (EDT)
 * (WT-en) Sabine 09:04, 09 Aug 2004 (CET)
 * (WT-en) Cecil 04:57, 9 Aug 2004 (EDT)
 * (WT-en) Bernie 16:26, 7 Sep 2004 (EDT)
 * (WT-en) A.bendig 00:56, 18 Sep 2004 (EDT)
 * (WT-en) Hedavid 10:54, 27 Sep 2004 (EDT)
 * (WT-en) mo 09:57, Oct 2, 2004 (EDT)
 * (WT-en) Friedjoff 16:31, 3 Oct 2004 (EDT)

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

129.237.252.43 11:55, 18 September 2009 (EDT)

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

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

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

I'd propose the following procedure (differs sightly from the french election mode):
 * 1) I e-mail each of us a personal invitation to the election.
 * 2) The candidates for go-between are the users listed below.
 * 3) Only people who nominated themselves under the "Gathering a team" section can vote.
 * 4) Each team member can give each other either a positive or a negative or a neutral vote. So each of the 11 nominies has 11 votes.
 * 5) If you would like to vote one of these people, please put your username next to their name, in the  "got positive vote from"  section. If you would like to make a vote against someone, please write your username next to their name in the  "got negative vote from"  line and then a reason for this. You also can vote  neutral .
 * 6) The election is over after 4 weeks (13-10-2004) or when all of us have voted.
 * 7) To win, you must have no negative votes and the most positive votes.
 * 8) If any of the candidates feels that there were something wrong with this election system, please contradict as soon as possible.

Example: '''User Egon wants to vote for user Emma. He votes the following way:'''

 * Emma
 * got positive vote from: (WT-en) Egon
 * got negative vote from:
 * got neutral vote from:

Thus, Egon can vote for Emma by writing " " behind the "got positive vote from" section of Emma.

--- (WT-en) Hansm 09:09, 2004 Sep 15 (EDT)

 * Cyril2000
 * got positive vote from: (WT-en) Hansm
 * got negative vote from:
 * got neutral vote from:
 * Denisoliver
 * got positive vote from:
 * got negative vote from:
 * got neutral vote from:
 * Hansm
 * got positive vote from: (WT-en) Cecil, (WT-en) Denisoliver
 * got negative vote from: (WT-en) Hansm, my English is too poor.
 * got neutral vote from:
 * EBB
 * got positive vote from: (WT-en) Hansm
 * got negative vote from:
 * got neutral vote from:
 * Sabine
 * got positive vote from:
 * got negative vote from:
 * got neutral vote from:
 * Cecil
 * got positive vote from: (WT-en) Hansm, (WT-en) Denisoliver, (WT-en) Friedjoff
 * got negative vote from:
 * got neutral vote from:
 * Bernie
 * got positive vote from:
 * got negative vote from:
 * got neutral vote from:
 * A.bendig
 * got positive vote from:
 * got negative vote from:
 * got neutral vote from:
 * Hedavid
 * got positive vote from:
 * got negative vote from:
 * got neutral vote from:
 * Mo
 * got positive vote from:
 * got negative vote from:
 * got neutral vote from:
 * Friedjoff
 * got positive vote from:
 * got negative vote from:
 * got neutral vote from:

Result
A nice trial. (WT-en) Hansm is still "temporary" go-between until someone else is willed to do the honorous job.

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

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

Issues

 * There's already a German-language travel wiki available. http://www.travelopedia.de/ has the beginnings of a good site, but seems to be moving sort of slowly. It's questionable whether we should start a competing site, offer to join forces, or not create a German-language Wikivoyage, instead defering to them per the Fellow Traveller Expedition.
 * I wouldn't defer to them; they don't seem to have the same aims we do. Among the first articles are Lachs and Forellenfische, which are fish, not destinations. -(WT-en) phma 00:24, 11 Mar 2004 (EST)
 * What word can we use to indicate that this is a German-language, and not German-national, travel guide?
 * Deutschsprachige. -(WT-en) phma 19:23, 14 Mar 2004 (EST)
 * It depends a little on context. "German-language Travelguide" -> "Deutschsprachiger Reiseführer" is correct, though. -(WT-en) Nils 20:26, 14 Mar 2004 (EST)
 * I'd propose the following: "German-language Travelguide" -> "Wikivoyage, der globale Reiseführer in deutscher Sprache". -(WT-en) Sabine 09:04, 09 Aug 2004 (CET)

Keep it short -> "Wikivoyage in Deutsch"

 * Please - good German is "Wikivoyage auf Deutsch" --(WT-en) zeno 20:13, Sep 7, 2004 (EDT)

wie wärs mit --> Reise-Wiki ?

Please, discuss all this topics above on the German Wikivoyage, now. The German "Traveler's Pub" is called "Stammtisch". -- (WT-en) Hansm 11:41, 2004 Oct 8 (EDT)

title: Wikivoyage:German Wikivoyage Expedition


text:
Wikivoyage:Go-between reports/German/German Wikivoyage Report for 23 February 2006

News from Germany
Hi! I am not the official go-between but it seems I am the only active admin on German Wikivoyage. Since [http://de.wikivoyage.org/wiki/Benutzer:Steffen_M. Steffen M.] disappeared after some disputes with an other user I am the only one. The other admins haven't been active for a ages. So I should tell you what's going on in the heart of Europe. The German Wikivoyage has creeped very slowly for a couple of month. Recently the edits have been rising slowly. The most users work anonymously. We have only some registered users who work permanently. So almost nobody participates in discussions. And I suppose there is no really good article for our destination of the month - but I think we will pull one out of a hat. This week I have adapted the Templates Geo and hasDocent to the German Wikivoyage. Besides we have been using our Template "Koordinate" to add information about the coordinates of a destination to the article - for the GPS-travellers. I hope to find enough time to look at the English Wikivoyage almost every day. We don't want to fall behind. I hope we haven't missed some other features.

Thats everything at the moment. Tschüß! -- (WT-en) DerFussi 13:31, 23 February 2006 (EST) (Don't hesitate to point mistakes out to me. I speak English only once a year - when I stay at my second home in Cambodia.)

 * DF, thanks for your great work on de:. Admins come and go -- people have different time commitments and interests in Wikivoyage.

 * If you want to stay "up-to-date" on en:, you should probably be able to just read the Project:Logbook. I think if we all work at it we can make the job of keeping Wikivoyage's language versions connected easier. --(WT-en) Evan 14:06, 23 February 2006 (EST)


text:
Wikivoyage:Go-between reports/German/German Wikivoyage Report for 2 July 2006

Progress in general
There have been an estimated 492 articles created on DE since March 3, 2006.

Raw stats register a total of 6937 pages of which 2339 are actual articles. Thus far there have been 42204 views and 51894 edits. There are 765 registered users of which 6 are administrators.

Focus since last report
Unknown

Focus during the next month
Hopefully, a new go-between will be found since the resignation of (WT-en) Hansm from the unofficial go-between and an administrator position.
 * Making the DE site user friendly will need to be a goal over the next few months.
 * Start a program to retain users.
 * Translate various press releases (IB) into German instead of referring users to the English site for details.

Special issues

 * de:Benutzer:(WT-de) Hansm or User:(WT-en) Hansm has requested to no longer have administrator privileges be revoked. Evan followed through with the request.
 * New users are not greeted. This must begin for users to feel like they are wanted.
 * Currently, there is no go-between. (WT-en) Andrew Haggard (Sapphire) has volunteered to become a defacto go-between provided German users will permit his less than par German.
 * Few administrators are still active on the project. One administrator has not been active since August 2005, another since March 2006, and another since April 2006. (WT-en) Evan, (WT-de) DerFussi, and (WT-de) Steffen M. are currently the only administrators that have been active within the past month.

Conclusion
DE has been in some trouble for quite a while with few admins contributing to the project. With help from the EN community and revitalizing the DE base increase in contributions and edits can make DE viable.

Comments

 * It would be great if Evan could introduce these template buttons ( City | Major City | City District | Region | National Park | Phrasebook | Disambiguation | Talk Page ) for new articles on the German-language Wikivoyage, too. -- (WT-en) Steffen M. 05:02, 3 July 2006 (EDT)
 * I'll find that and do it for you. Thanks for correcting my translations and beginners DE mistakes. -- (WT-en) Andrew Haggard (Sapphire) 05:13, 3 July 2006 (EDT)

 * There are still problems with the Template:IstIn. Sometimes the geographical hierarchy or a part of it disappears on the sites. Is this a general problem or just a bug on de? -- (WT-en) Steffen M. 05:02, 3 July 2006 (EDT)
 * It's a general problem. For some odd reason, it's critical that the isIn tag appear before the article status. (WT-en) Jpatokal 05:30, 3 July 2006 (EDT)
 * I never saw a red blinking light as announced on Project:5 March 2006. -- (WT-en) Steffen M. 05:02, 3 July 2006 (EDT)
 * For some reason it doesn't work in Konqueror. I haven't looked at Evan's code, so I don't know why. -- (WT-en) Mark 00:57, 6 July 2006 (EDT)
 * My guess is that it's a JavaScript difference. --(WT-en) Evan 01:10, 6 July 2006 (EDT)
 * My guess is that it has something to do with the period at the end of your username. There have been some others who have problems -- User:(WT-en) Ravikiran r posted a bug on Project:Bug reports. --(WT-en) Evan 01:10, 6 July 2006 (EDT)
 * It would be a good idea to separate the ToC discussion from the German-language Wikivoyage. -- (WT-en) Steffen M. 05:02, 3 July 2006 (EDT)
 * What does this mean? I thought that German-speakers wanted to be part of this conversation. --(WT-en) Evan 01:03, 6 July 2006 (EDT)
 * from -> for. I think he wants to say that the German users want to decide for themselves whether or not to adopt the ToC on the right for de:Wikivoyage independent of whether en: users accept the change or not. — (WT-en) Ravikiran 02:51, 6 July 2006 (EDT)
 * That's how I understood his comments too. I have no problem with DE users deciding themselves the ToC issue. I'm going to propose a few changes to policy over there, which will reflect EN's policy. I especially think the external links policy on DE needs to be changed. -- (WT-en) Andrew Haggard (Sapphire) 02:56, 6 July 2006 (EDT)
 * I agree with that, then! --(WT-en) Evan 08:55, 6 July 2006 (EDT)
 * According to Stammtisch#Neuer Go-Between gesucht, I'm currently not interested in superseding Hansm as an official go-between, so we have to wait until there is a volunteer. -- (WT-en) Steffen M. 05:02, 3 July 2006 (EDT)
 * After thinking about it I'll do it full time provided you can help me a little bit. I'll resign if someone does come along and wants to take the position. -- (WT-en) Andrew Haggard (Sapphire) 05:15, 3 July 2006 (EDT)
 * I think that sounds great. --(WT-en) Evan 01:03, 6 July 2006 (EDT)
 * Andrew, thanks a lot for taking care of this report; it's been needed for a while. I've started emailing the admins who haven't participated in a while and I'll start downgrading their accounts as I hear from them, per policy. I'd like to see some more admins come up, but we can take it as they come. --(WT-en) Evan 01:14, 6 July 2006 (EDT)
 * You're welcome. I'll keep these coming within the first week of every month. Regarding admins did you see that (WT-de) Mistoffeles declined the administrator nomination? Would it be wise for me nominate myself? I think I could handle the tasks of go-between reports without the privileges, but if I have the magic revert button it might be nice or privileges to edit some of the MediaWiki templates if the need arises. -- (WT-en) Andrew Haggard (Sapphire) 02:09, 6 July 2006 (EDT)
 * I suggest that maybe you should wait a month or so. It would help if you've been part of the de: community for a little longer, I'd guess. --(WT-en) Evan 08:33, 6 July 2006 (EDT)


text:
Wikivoyage:Get-together

A get-together is just that. Wikivoyagers physically meeting up, to discuss the site, just for a coffee, or some "serious travel research". It can be a small group, or a large one. If you happen to be passing through a city, you can suggest a meetup to those who may be resident there.

You may want to post details on other language versions or on meta.

title: Wikivoyage:Get-together


text:
Wikivoyage:Goals and non-goals

The mission of Wikivoyage is to create a free, complete, up-to-date and reliable worldwide travel guide.

Wikivoyage articles should be useful for at least the following contexts:
 * Online use by travellers on the road – for example, travellers huddled in a late-night internet café in some dark jungle, who need up-to-date information on lodging, transportation, food, nightlife, and other necessities.
 * Offline use by travellers on the road – for example, travellers sitting in a train with a subset of Wikivoyage on their mobile device.
 * Online use by travellers still planning – for intending travellers who want to review destinations, plan itineraries, make reservations, and get excited about their trip.
 * Individual article print-outs – for people who want to print, say, a list of museums or karaoke bars and put it in their back pocket for when they need it.
 * Ad-hoc travel guides – for people who want small, fit-to-purpose travel books that match a particular itinerary.
 * Inclusion in other travel publications – for travel-guide publishers and advisers who want up-to-date information.

Non-goals

 * 1) Travel essay anthology. Wikivoyage is not a travel magazine. Articles should be directed toward practical information about travelling.
 * 2) Personal travel journals. Wikivoyagers usually have interesting stories about their personal adventures, which should instead be written somewhere other than in our articles.
 * 3) Vacation photo gallery service. Photographs and illustrations should be targeted towards illustrating destinations and sights, not toward showing Grandma how big the mai-tai was that you drank at the luau.
 * 4) Personal homepage service. Each registered user on Wikivoyage has a user page; these should be used to support the development of the travel guide, and not as an all about me or my cat website. Having one or two photographs on your user page is reasonable; more than five is pushing it.
 * 5) Travel chat board. Wikivoyage has talk pages for each article, but these should be used to develop the article itself, and not as a "comments" area. Anyone can edit a Wikivoyage article; if you have useful information about a topic, put it in the article itself.
 * 6) Advertising brochure. Wikivoyage of course has listings and information about travel-related businesses around the world. We are pleased to have representatives of these businesses keep those records up-to-date. However, blatant advertising is not welcome, and overcompetitive acts (like deleting information about rival businesses) are not tolerated.
 * 7) Yellow pages of restaurants, hotels, bars, etc. City guides should certainly include information for travel-related companies, but these should be kept to a useful number. Think of a friend from out of town asking you where they should go – you wouldn't list all 200 possibilities, but 5–10 options for a particular type, budget, or part of town would be helpful.
 * 8) Web directory. Wikivoyage articles should not have in-article links to external resources, with the exception of a link to the official website besides the name of a listing. It's not a goal to collect links about any destination. External links should support and complement the content of articles; they're not a goal per se.
 * 9) Travel guide supplement. The wiki technique we use for Wikivoyage makes it possible for us to include information that's not in other travel guides. This doesn't mean that we only include information not found in other guides. Wikivoyage aims to be a complete travel guide, not a supplement for other travel guides or a niche guide focusing exclusively on "off-the-beaten-path" attractions for those who have done everything commercial guides recommend.
 * 10) Atlas. Although travel is intimately intertwined with geography, Wikivoyage does not describe geographical features just because they're there. Nor do we create separate articles for every crossroads with a name on the map.
 * 11) Encyclopedia. Wikivoyage is not an encyclopedia. Though it aims to tell people how to travel all over the world, Wikivoyage does not document everything on the planet or how it ended up that way. If you find yourself needing references and footnotes on Wikivoyage, whatever you're writing should probably go to Wikipedia instead.
 * 12) Travel agency. Wikivoyage does not arrange visas, make bookings for airlines, car rentals, cruise lines, hotels, railways, or package tours.

There are probably lots of other near-miss goals that people might think we have; if needed, we'll list those here, too.

title: Wikivoyage:Goals and non-goals


text:
Wikivoyage:Go-between reports

This is the archive for reports from Wikivoyage sites in languages other than English prepared before August 2006.

Wikivoyage go-between reports per language

 * Project:Go-between reports/Dutch
 * Project:Go-between reports/German
 * Project:Go-between reports/Japanese
 * Project:Go-between reports/Portuguese
 * Project:Go-between reports/Spanish
 * Project:Go-between reports/Swedish

Template for go-between report

 * Project:Go-between reports/Template

title: Wikivoyage:Go-between reports


text:
Wikivoyage:Go-between reports/Dutch

Here are the go-between reports from Dutch Wikivoyage:

(It makes more sense to me to have the reports in one page.)

22 January 2006
Just some quick words. The Dutch wt is growing! Domie is very active and wants to be admin. I agree. (WT-en) Guaka 22:24, 22 Jan 2006 (EST)

29 March 2006
Slowly, but steadily growing. Some new users. 36 articles. (WT-en) Guaka 12:23, 29 March 2006 (EST)

14 June 2006
Again, slow but steady progress. 69 articles. (WT-en) Guaka 16:42, 14 June 2006 (EDT)

12 August 2006
Thanks to some new users the project now has 140 pages. (WT-en) Guaka 17:31, 13 August 2006 (EDT)

1 November
No rapid advance, 158 articles. It seems that the interface language is switching between English and Dutch. It would probably help if this were fixed. (WT-en) Guaka 03:00, 1 November 2006 (EST)

title: Wikivoyage:Go-between reports/Dutch


text:
Wikivoyage:Go-between reports/German

Here are the go-between reports from German Wikivoyage

 * Project:Go-between reports/German/German Wikivoyage Report for 23 February 2006
 * Project:Go-between reports/German/German Wikivoyage Report for 2 July 2006

title: Wikivoyage:Go-between reports/German


text:
Wikivoyage:Go-between reports/Japanese

Here are the go-between reports from Japanese Wikivoyage

 * Project:Go-between reports/Japanese/Japanese Wikivoyage Report for 7 December 2005
 * Project:Go-between reports/Japanese/Japanese Wikivoyage Report for 17 January 2006
 * Project:Go-between reports/Japanese/Japanese Wikivoyage Report for 3 March 2006
 * Project:Go-between reports/Japanese/Japanese Wikivoyage Report for 18 June 2006

title: Wikivoyage:Go-between reports/Japanese