text:
Wikivoyage talk:Fellow traveller Expedition

Moved from Project:travellers' pub by (WT-en) Evan'

Hi,

I have one question: Is there already a page which links to similar projects like Wikipedia (sharing the software & general idea) and to other community-driven traveller's web sites? To name an example, there is http://openguides.org, which is a software (and some websites) for constructing city guides ... but as I understand, these people are not licence-aware.

--(WT-en) Zenogantner 06:25, 10 Nov 2003 (PST)

 * No, there's not a current page for that. What would be the point? -- (WT-en) Evan 07:53, 10 Nov 2003 (PST)

 * Actually, on re-reading this, I can say that it makes sense to have this kind of stuff on Project:Cooperation. I'm starting a list of similar projects there right now. -- (WT-en) Evan 11:53, 19 Nov 2003 (PST)

 * Project:Cooperation (now) redirects here.
 * See also/instead Project:List of related projects.
 * ~ 125.24.1.84 07:52, 5 August 2006 (EDT)

An Open Invitation for Extlinks
According to this page, any travel guide on the Internet would appear to be eligible to be a "Fellow Traveller" and therefore by eligible to be added to Project:List of related projects. I'm pretty sure that's not what we want.

What do we want though? What is a "related project" exactly?

How about dead projects? WikiOutdoors is, rather sadly, moribund. There are others like this.

Seems to me this is a leftover idea from the founding of wikivoyage that just doesn't match who we are today. -- (WT-en) Colin 23:56, 1 June 2009 (EDT)

 * Agree.... we could quite easily lose this article.... – (WT-en) cacahuate  talk 00:30, 2 June 2009 (EDT)

 * I'd be fine with deleting it. Alternatively we could severely limit the scope: only list open content wiki projects that are related to travel? I count about six that actually meet that criteria. Then merge the list here. Just a suggestion, though—I don't think this is needed. --(WT-en) Peter Talk 02:32, 2 June 2009 (EDT)

 * Not a bad idea.... reinvision it as a tight list of projects that are compatible with our copyleft that we can (and would consider) giving and taking from, like openstreetmap? Still not super necessary, but at least a bit closer – (WT-en) cacahuate  talk 03:12, 2 June 2009 (EDT)

 * This policy is the basis for all the "Cooperating with XXX" pages. It makes sense to me to have such pages for any kind of website we can share content with (Open Street Map), or that a user might mistakenly think we could share content with (Wikipedia).  We just need to tighten the language here to better restrict the set of listed sites to ones that make sense.  -- (WT-en) Colin 04:45, 2 June 2009 (EDT)

 * I'm in favour of deleting it. Peter's idea of limiting it to open content wiki guides related to travel sounds good, but I don't think they are necessarily the sites we work and interlink with, which is what I think Fellow Traveller means.  Unless there is some special relationship there, this is just a list that has to be maintained.  This doesn't mean we can't list these sites in the appropriate places.  OSM should be mentioned within the mapping expedition, for example.
 * This page demonstrates its own failure - it hasn't been updated, and even long term users of the site don't quite know what it is for. --(WT-en) inas 19:22, 6 August 2009 (EDT)

 * Bump. Is someone prepared to really take this on as a task?  --(WT-en) inas 23:26, 24 August 2009 (EDT)

 * Yep, done. --(WT-en) Peter Talk 11:26, 3 May 2010 (EDT)

Link to TravelBlog?
I discovered TravelBlog a few weeks ago and I think it's a great resource for those less-visited countries. We have links to Wikipedia, Open Directory, & World66, what are your thoughts about adding TravelBlog? It might not be very helpful to view the thousands of blogs in the US, but I have found it very interesting to view travelers' experiences in off-the-beaten path countries like Mauritania, Sudan, Afghanistan, Turkmenistan, Yemen, and many, many more. (WT-en) AHeneen 17:39, 9 April 2009 (EDT)

Link to Wikioverland, the encyclopedia of overland travel

I'd like to continue a discussion about linking to WikiOverland, the encyclopedia of overland travel - it contains extremely detailed information for people traveling with vehciles. (see a better description here WikiOverland discussion)

Thanks. -(WT-en) Dangrec 12:14, 30 November 2011 (EST)

Adding index from travel book
Would it be legal to create an index of places based off a travel book such as Weird New York? Also, why are there no citation templates on this wiki?Smallman12q (talk) 01:46, 22 February 2013 (UTC)

 * We don't use citations. Travel guides (unlike encyclopaedias) generally don't, as they can contain original research.  I don't think we'd use an extract like that of place names derived from a non-free source.  --Inas (talk) 02:12, 22 February 2013 (UTC)


text:
Wikivoyage talk:Field research checklist

Just noticed this! Great idea... (WT-en) Majnoona 16:55, 12 May 2006 (EDT)

 * Whoa, now I just noticed this. Cool little article to which we should try and give a bit more visibility, methinks. --(WT-en) Peter Talk 16:47, 29 September 2011 (EDT)

 * It would be an odd thing to do, but maybe it would make sense to list this under travel topics? --(WT-en) Peter Talk 16:49, 29 September 2011 (EDT)

research checklists
Sweeping in from the pub:

When traveling offline, I make lots of notes about the places I visit, but when I come home I still find that many aspects of restaurants/hotels/attractions/airports etc are not covered.

This led me to idea to create researcher checklists for the objects we most frequently describe. Here's a first draft: User:(WT-en) DenisYurkin/Wikivoyage:Research Checklists. Right now it contains a random (and small) subset of what we write in respective listings or sections--but I think it illustrates the idea.

Anyone willing to join in improving checklists like those? Can it be helpful for many contributors? Can I move it from User: to Wikivoyage: namespace in its current immaturity? --(WT-en) DenisYurkin 17:51, 1 February 2008 (EST)

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


text:
Wikivoyage talk:Fields of Pursuit

I have little personal investment in this particular line of plunging forward, but it started because of a link on the talk page of Soccer in Europe. From there I went to Project:Other ways of seeing travel where I noticed that the Fields of Pursuit block was being left alone. Then I flipped flopped a bit and decided I'd go ahead and build the structure.

If you build it they will come? -- (WT-en) Ilkirk 22:16, 25 July 2006 (EDT)

 * I do wonder (to myself for now) - how will we tell the difference between a Field of Pursuit and an Itinerary? Scuba diving?  The lone survivor of a VFD: Talk:Birdwatching in Peru?  A mock suggestion from that talk page: Bungee jumping in the United States? -- (WT-en) Ilkirk 22:23, 25 July 2006 (EDT)

 * An itinerary is (or at least can be) a particular kind of FoP article: one that follows the Itinerary template. I'm more concerned about how to identify a FoP as compared to travel topics in general, and whether Project:List of Fields of Pursuit is going to be just a partial duplicate of Travel topics . - (WT-en) Todd VerBeek 22:34, 25 July 2006 (EDT)

 * I believe that a FoP is essentially a travel topic which you can do. Looking at the list of Travel topics, FoP will pretty much encompass Travel topics, plus a few additions, such as Travel_topics. However, a Travel activities page does already exist, which seems to me to be what we're thinking of making here... (WT-en) Tim 05:06, 16 August 2006 (EDT)

 * The distinction between Fields of Pursuit and Travel Topics is slight. Maybe meaningless.  I think the important thing is to make sure that there are adequate links between them, and to keep both options available to users.(WT-en) Brhumphreys 23:16, 24 February 2008 (EST)

Merge into Travel topics?
Whoah, didn't even know this existed, it seems totally obsolete. Time to officially merge this into Travel topics? Or Travel activities? (WT-en) Jpatokal 10:47, 23 May 2009 (EDT)

 * By all means...I had no idea it existed either. (WT-en) Gorilla Jones 11:52, 23 May 2009 (EDT)

 * What a strange and musty corner of WT. Since this is obvious overlap, I've gone ahead and merged anything worth merging, and redirected all to travel topics. --(WT-en) Peter Talk 12:15, 23 May 2009 (EDT)

title: Wikivoyage talk:Fields of Pursuit


text:
Wikivoyage talk:Finnish Wikivoyage Expedition

So, while I'm willing to be the go-between and give this an initial push, we're going to need somebody else to volunteer to be the 'main' admin before this thing can/should be launched. (WT-en) Jpatokal 05:28, 16 August 2006 (EDT)

Locked and loaded
So, the Finnish Wikivoyage version is ready to go (see http://fi.wikivoyage.org/wiki/ ). Right now, we just need someone to take on the go-between job, and we're ready to go. I can unlock it when someone who's the new go-between says so. I had some serious problems working with the Finnish language file, so I think we'll use the MediaWiki namespace to customize the interface and clear out any remaining "Wikipedia" or "GFDL" strings.

I wouldn't bother with a big voting cycle for being go-between. It's not a glamorous job and it's hard enough to find someone to do it, let alone go through some open-ended election process. I suggest that if anyone wants to do this job, they just list their name, and we get going. --(WT-en) Evan 07:31, 9 September 2006 (EDT)


text:
Wikivoyage talk:Fixed bugs

So, I moved this page because it's just an easier name to write and remember. There's no reason that this and Project:Bug reports 1.3.5 need to have a sub-page relationship. --(WT-en) Evan 12:58, 25 Oct 2004 (EDT)

title: Wikivoyage talk:Fixed bugs


text:
Wikivoyage talk:Florida Expedition

Welcome
Maryland will crush you! --(WT-en) Peter Talk 22:13, 25 August 2008 (EDT)

 * I used to live there, so I will contribute what I can. --(WT-en) Matt Talk 12:31, 26 August 2008 (EDT)

Outline Articles
Easiest way to get started: Choose an article that is still in Outline status and work to bring it up to Usable status. (WT-en) gamweb 13:37, 26 August 2008 (EDT)

Photos
Easiest way to start here: Go through the image collection at Wikimedia Commons, and find images that are Public Domain or a license that is compatible here. Upload them to Wikivoyage Shared. (WT-en) gamweb 13:41, 26 August 2008 (EDT)
 * [Current Florida images available at WikiTravel]
 * [Florida images at Wikimedia Commons]

Florida region page Improvement Map
Some thoughts for ways to improve the Florida Region page (other user opinions welcome here):

Cities
Add a small line describing the most important fact about each linked city.

By Plane
Make a hierarchy of these numerous airports, it seems a bit overwhelming for someone just looking to get into Florida. Rank them in importance and relevance, and add which sub-region of the state they are located in.

Get Around
Add train info.

See
List 7 to 9 best things to see in Florida, with links to sight's city. The exhaustive list of Lighthouses seems too encyclopedic for the casual traveler. Maybe we can list Florida Lighthouses as a linked Travel Topic. Same for the national parks list.

Learn
This too seems very encyclopedic, I'm not sure a traveler interested in visiting Florida would be interested in this information. Also, Learn is not a part of Wikivoyage's recommended Region template. Perhaps this heading should be deleted and the individual listing put in the city pages. (WT-en) Jtesla16 22:38, 4 September 2008 (EDT)
 * I see your point. Do you think a list of all of them belongs on the main Florida page though? I think they are important and should be individually listed as "Go see Blank" Under the Do Section of each Florida region. Will that work?(WT-en) Jtesla16 17:18, 6 September 2008 (EDT)

Article Status
There are some city pages in Florida I think should be raised from Outline to Usable status. Can I make that status change or is there some review system?(WT-en) Jtesla16 17:33, 6 September 2008 (EDT)

Saying Hey
Heya guys, I grew up in Pensacola, and after being invited, I figured I'd help you guys out a bit with the expedition for Florida. Right now, I really want to get the Pensacola article up to star status, and get Milton, Pensacola Beach, Perdido Key, Escambia County, and Santa Rosa County up to guide. However, since you guys need the Florida Panhandle worked on for your expedition, I'll work on that next, once I finish Pensacola. Also, I should be able to do some work on the Gulf Islands National Seashore article; I love that place! --(WT-en) Tally 15:32, 11 September 2008 (EDT)
 * Sounds good, glad to have you. (WT-en) Jtesla16 16:09, 11 September 2008 (EDT)

Gulf Islands National Seashore
Does anyone have any idea on how I should format this article? It's a bit of a mess right now, and the Gulf Islands National Seashore is a challenge to discuss. It's located in two (noncontiguous!) states, Florida and Mississippi. It is subdivided into twelve smaller parks, each of which is very different from the others; some are beaches, some are islands, some are forests. Each has a different way to 'Get In' and 'Get Around,' and most are unconnected with each other. I'm thinking about giving each area a separate writeup, but how? Should I give each subpark it's own "See" and "Do" section? Or (overkill) separate articles for each? --(WT-en) Tally talk 18:47, 28 October 2008 (EDT)

New Hierarchy
I've proposed a new hierarchy for the state. Head on over to the Florida talk page to see what I'm proposing. (WT-en) AHeneen 19:52, 17 March 2009 (EDT)

Archived
This expedition has been archived because it has not had any activity since 2012. If anyone wishes to reactivate it then please give notice in the Travellers' pub --Andrewssi2 (talk) 22:45, 22 September 2014 (UTC)

title: Wikivoyage talk:Florida Expedition


text:
Wikivoyage talk:Foreign-language names

Diacritics → Project:Article naming conventions/Accented characters

Establishment names
Hiya all. I'm new to wikivoyage and while contributing to the entry on Utrecht I ran into a question about this whole language thing. Now, I understand the principle, I'm just not entirely clear on how far to take it. Specifically, should it be applied to the names of establishments like bars, theatres etc., or should these be left in the original language.

In keeping with the the traveller comes first idea, I'd say they should stay in the original language. After all, if I went to Utrecht, I'd be looking for a restaurant with a sign that says Stadskasteel Oudaen and not Citycastle Oudaen. Now, in this case the Oudaen is a giveaway, but if it wasn't part of the name, then the confusion would be complete.

Anyways, I was wondering what the consensus is on this issue. (WT-en) Gorath99 11:33, 7 Jul 2004 (EDT)

 * Yeah, that's a tough question. We haven't been particularly consistent about it, but this'd be my opinion: I'd probably say "the most common English name" is probably applicable here, too. I think it's extremely rare that businesses -- restaurants, stores, bars, hotels -- have different names in English and the local language. It's still rare, but occasionally there are notable local attractions that have different names in English than in the local language. An example that springs to mind is "The Eiffel Tower" (La Tour Eiffel). I'd think the former would be a more useful name than the latter (although we should probably list the local name, too, for reference). --(WT-en) Evan 21:52, 7 Jul 2004 (EDT)

 * I think in this case, just a restaurant not some international landmark, I'd go with the name on the door and not some off-hand translation. I used to inisit on calling Demilune bar in Geneva Half moon just to be silly, and this seems to fall into that category, not the Tour/Tower category. We should always give the translation as well: "The Eiffel Tower (La Tour Eiffel) / "Stadskasteel Oudaen" (City castle Oudaen)-- how's that sound?. (WT-en) Majnoona 21:58, 7 Jul 2004 (EDT)

 * Sounds good to me. Seems like you get the best of both worlds this way. (WT-en) Gorath99 13:19, 2004 Jul 8 (EDT)

 * Even if the traveler can't be expected to read the name on the door, I think it should be provided so you can match up the funny squiggles with those on your printed Wikivoyage and say "Yep, this must be it" : Osaka -- (WT-en) Paul Richter 03:57, 8 Jul 2004 (EDT)

Romanization
I'd don't want to reopen this particular can of worms. But I would like to see one thing added to the policy. It would be nice if Asian place names could be written in full native-language Unicode format in a limited set of circumstances: -- (WT-en) Colin 20:52, 2 Oct 2004 (EDT)
 * 1) If the place name is something like a subway station, where it is helpful to have a printed version of the characters so one can compare it to station names to figure out when to get off the train, we should permit non-English characters.
 * 2) If the place name is something that might be useful to show to someone who doesn't speak English, it is useful to permit non-English characters in the guide.  For example, if you need to take a Taxi to your hotel, maybe having the street name in local format would be useful so you could point at it.

Prefixing the language
I think prefixing the language is A-OK in case where there is any potential for confusion, but I think it's pretty redundant for (eg.) obscure Japanese podunk towns where it should be darn obvious that the name in question is in Japanese. Any ideas for how to codify this? (WT-en) Jpatokal 03:46, 25 Jan 2005 (EST)

 * I think that the first time a foreign language name is used in an article the language should be indicated as English language name (language:foreign language name). As an optional extra, the language could link to the phrasebook. All other foreign language translations should then be italicised the first time they are used, as either:
 * foreign language word (English translation)
 * English place name or word (foreign language translation)

 * If there is any confusion, such as multiple languages being used, then languages should be indicated for each word. (However, this should be avoided if possible.)

 * If an English translation of a foreign place name is given because this gives greater understanding then one could use Foreign Place Name in its English Form (literally:English literal translation) or (translation:English translation)

 * For example:
 * Grossglockner Hochalpenstrasse (German:Großglockner Hochalpenstraße) (literally:Big Bell High Alpine Street/Road) or (translation:Grossglockner High Alpine Road)

 * If there can be no confusion as to the language being used, such as ideographs, say Chinese characters, then (Ideographs) is probably sufficient.

 * -- (WT-en) Huttite 05:20, 25 Jan 2005 (EST)

 * Me like. However, I think that glosses should be in quotes, like so: (WT-en) Jpatokal 06:43, 25 Jan 2005 (EST)

 * Grossglockner Hochalpenstrasse (German:Großglockner Hochalpenstraße, "Big Bell High Alpine Street/Road")

 * "Quotes" work for me too, I hadn't considered that. Though it could get confusing if the place was named after a saying, as happens with a lot of Maori placenames in New Zealand, but we can cross that bridge when we come to it. -- (WT-en) Huttite 06:54, 25 Jan 2005 (EST)

 * I'm not sure I'm quite clear on the utility of prefixing the language except in the odd case of Freiboug where there are two local languages. Otherwise shouldn't the local language just be assumed? -- (WT-en) Mark

 * I think one reminder per article is probably pretty OK. --(WT-en) Evan 11:21, 25 Jan 2005 (EST)

title: Wikivoyage talk:Foreign-language names


text:
Wikivoyage talk:Foreign words

This page is about common nouns (kung fu, tuk tuk). Project:foreign-language names is about proper nouns (Geneva, Eiffel Tower, Mao Tse Tung). This page was abbreviated into that other page, I believe erroneously. I've reverted the change, and added See also sections instead. --(WT-en) Evan 11:17, 25 Jan 2005 (EST)

 * What, pray tell, is the point of maintaining such a hair-splitting distinction, and on two separate pages to boot? The layout being proposed is effectively identical.  (WT-en) Jpatokal 11:45, 25 Jan 2005 (EST)

 * No, it's not. The first section is about whether or not to use italics for foreign-language words in regular prose. However, I moved the contents of Project:foreign-language names to Project:foreign words, on the principle that a name is a kind of word, so it makes sense to have the names stuff be part of the words page. --(WT-en) Evan 18:45, 25 Jan 2005 (EST)

Throughout the Wikis, Asian Characters are not italic-ed (technically possible, but Chinese cannot be written italic). Should be said somehow.
 * Somewhat on this note, words using non-latin alphabets really should not ever be italicized. Italicizing "foreign" alphabets can really impede intelligibility (e.g., italicized Russian letters are in some cases totally different from their non-italicized counterparts. This issue has been beaten into the ground on Wikipedia, and they ultimately decided to completely avoid italics in non-latin alphabets. --(WT-en) Peterfitzgerald Talk 00:54, 6 April 2007 (EDT)

Local place names
Which order is preferred with regards to local place names: local name first and English translation after that, e.g. "Kauppatori (Market Square) is a favorite of tourists", or vice versa? Also, sticking to that order, should the translation/local name be mentioned after each instance of the word in different sections of the article? I'm trying to streamline and unify the article about Helsinki and I'm not sure which way to go. (WT-en) Jopo 12:47, 17 August 2006 (EDT)
 * I think the consensus was either way is fine but it should be consistent within an article. That said, I think I prefer "Local word (Translation), since the local word is what travellers will be using/looking for... (WT-en) Maj 13:46, 17 August 2006 (EDT)

Pronunciation Help
I want to verify that edits like this are counterproductive, correct? I've noticed User:Fabimaru has recently been adding them to various Japan articles, changing place names to add the diacritics for pronunciation purposes. In most cases it seems inappropriate, but I'd like to double check before reverting. ChubbyWimbus (talk) 16:48, 30 August 2014 (UTC)
 * Note that I did not change the name of any existing page, I only changed the display name. The only drawback I see is that it makes it harder to search a name on the page using the browser (not everyone can easily type such characters). But the reason why I did is that it allows to know the right way to pronounce it. For me it's like not having accents on French names, it leads to ambiguity. It may contribute to be understood when in Japan. From my experience, if you have both the wrong pronunciation and a strong foreigner accent it does not help. Also, Wikipedia (English and French) use the diacritics (excepted for the major cities like Tokyo or Osaka I think), so there would be some consistency between the two projects. But if my view is not shared, no problem, I can stop such modifications and rollback the previous ones. Maybe it should be clarified in the help pages (to be honest I did not check). - Fabimaru (talk) 18:35, 30 August 2014 (UTC)

 * Interesting question. For example, under North Korean romanisation rules, the capital city is P'yŏngyang (with diacritics) whereas is it typically spelt just as Pyongyang by everyone else, including Wikipedia . --Andrewssi2 (talk) 01:22, 31 August 2014 (UTC)
 * I agree with Fabimaru that it is important to convey pronunciation for places that don't have a standard common print form in English. That either needs to be with lines over long vowel (more common) or doubling vowels (less common), preferably the first. Tokyo, Osaka, and Kyoto have a standard way, but most other places don't so the diacritic should be used, else ambiguity is introduced. This is how we've done it for other countries like Vietnam, Portugal, etc... Texugo (talk) 01:43, 31 August 2014 (UTC)

 * Kyotanabe, Kyotango, etc. all have established English names, and I don't see why we would allow diacritics in city links when the cities themselves don't use them. The 'ambiguity' is here is all self-created with our own inconsistencies. I live in Japan, so I can see the names that are used and these cities are never written in diacritics on anything official, travel brochures, (anyplace). Ignorant Wikipedians who are unfamiliar with the area probably created those pages (neither wiki article contains much info), but they don't need them. Incidentally, I've read diacritic arguments on WP and conversations I've read have a strong pro-diacritic brigade that tend to bully those with differing opinions. I tend not to use WP as a reference on this for that reason. When I do an English search, Wikipedia is the ONLY source that uses the diacritics which suggests that a name has been established and Wikipedia is actually the outlier. ChubbyWimbus (talk) 15:50, 31 August 2014 (UTC)
 * Hmmmm.. I dunno, I lived in Japan for many years as well, and I think the long vowel symbol is pretty common on train stations signs and the like since as you know there is a difference in pronunciation between きょう and きょ or おお and お. I'm not familiar with either of the places you mentioned, which is exactly why I'd like to know if there are long vowels. And regardless of how the local folks there might write it in English, I don't think they are well-known enough or widely written about enough outside the local area to have the same "established spelling" that Tokyo or Hanoi or what have you. Texugo (talk) 16:17, 31 August 2014 (UTC)
 * In my experience we've used diacritics when the original name is written in Latin characters (e.g. Västerås) and just in 99% of those cases (e.g. Zurich is written without the trema). When it's a romanized name like Pyongyang we haven't used them. ϒpsilon (talk) 16:28, 31 August 2014 (UTC)
 * That's a valid point, and admittedly, we generally haven't used the diacritic for Japanese locations so far. I just think maybe we should, because unlike the tonal languages like Thai or Mandarin, the full pronunciation info for Japanese can be conveyed if we just allow this one fairly intuitive symbol that most of us know from grammar school. Texugo (talk) 17:14, 31 August 2014 (UTC)
 * I approve of any kind of standard diacritics and the like, whenever there is no well-known and accepted standard English name for a place. Ikan Kekek (talk) 19:32, 31 August 2014 (UTC)
 * or for these well-known English name, just once in its main article (just like there is the kanji name) - Fabimaru (talk) 21:06, 31 August 2014 (UTC)
 * I can see the names that are used and these cities are never written in diacritics on anything official, travel brochures: I just checked (Google image search), the names on the JR platforms use the diacritics at least for Tokyo and Shin-Osaka (edit: so, not never, maybe often). - Fabimaru (talk) 21:06, 31 August 2014 (UTC)

 * The pronunciation help is good, but it should be separate from the place name, unless the real place name does include the diacritics. Västerås is Västerås, no one in Sweden would write it in any other way and I suppose there is no common English spelling differing from the Swedish one. In cases where diacritics are not part of the name, but a pronunciation aid for non-locals, we should be very clear about what the real name is. I also think it is problematic when links to a destination are written in a way that cannot be cut and pasted and used in the web address (as in the above cited case: Kyōtanabe is a redlink; genitives etc. are a different matter as they are obvious). --LPfi (talk) 09:44, 1 September 2014 (UTC)

 * Totally agreed, and the crucial point is your first sentence: The diacritics have to be in the official name. Ikan Kekek (talk) 09:47, 1 September 2014 (UTC)

 * In addition to the above reasons, the diacritic-included pronunciation is actually in the article beside the Japanese-language name. Take a look: Kyotanabe. So there is in fact, already no confusion in pronunciation to anyone who actually wants to know. Why don't we just establish this as a rule? Then we don't have to have diacritic discussions of this nature anymore. The pronunciation will be there while the actual city name can remain normal. Links from other articles don't need the diacritics in this case either, because if someone really cares, they should click the article. ChubbyWimbus (talk) 12:27, 1 September 2014 (UTC)

 * My opinion is that (1) using the diacritic is the most correct way to represent the name (2) people should care, and if we only put it in the main page then people will read (and then pronounce later) the name incorrectly. Also, I think that the diacritics should be used also for the points of interest (ex: temples…; with the same argument: avoid confusion when talking with locals, either in English or in a few words of the local language). Then in this case there would be a inconsistency between the norm used for the pages and the PoI. - Fabimaru (talk) 17:23, 1 September 2014 (UTC)
 * I'm not sure that I agree with your claim that "using the diacritic is the most correct way to represent the name". My inclination is to assume that the most correct way to represent the name is however the official publications (like the city's website, if it has an English-language section) do it.  WhatamIdoing (talk) 20:53, 1 September 2014 (UTC)

 * Well, it is true that the macron is not the only way to accurately convey long vowel pronunciation information — there are other systems which convey the same information by doubling letters, etc. The macron is part of the Hepburn system, the most common system and one widely considered to be the best and most intuitive for English speakers, which figures into the JR railway standard and various official government ministry publications, etc. The second and third main systems do basically the same thing but with a circumflex instead of a macron. Some other systems use "oh" for a long O, etc. I think the point is that in terms of "correctness", as measured by the degree of certainty someone can have of pronouncing the place correctly without additional explanation, the current non-standard romanization at use in our Japanese article titles comes way down the list behind all those other systems, making no distinction between short and long vowels at all, meaning that common placename components like big (大, long o) and small (小, short o) get oddly represented as identical, and potentially introducing ambiguity. I personally don't think adopting an occasional single diacritic is such a huge sacrifice to gain the advantage of having names fully pronounceable. I think the very easiest and clearest way would be to follow the Hepburn system, for which we can easily use the WP titles as a model. I don't know or care who the diacritic enthusiasts of WP are, but in the case of Japanese placenames, the result is that they are spelled consistently and clearly, and I don't know why we'd prefer not to have such consistent and clear spelling.
 * At the very very least, we should be consistent. The only thing I can thank of that would be worse than our current unstandardized quasi-Anglicized system is the notion that we should attempt to follow whatever the local town governments have put on their websites. Those do not necessarily represent some consciously chosen spelling system proclaimed to be the correct one for their little town. A more likely scenario is that an underpaid city employee who speaks little English wrote some copy, sent it to a translation agency or the local gaijin English teacher, and then submitted it to their boss who also speaks little English, and it just gets assumed that whatever transliteration system the translator chose to use "must be correct because it came from a native English speaker after all". Or maybe they are simply written by someone unaware of the rules of existing romanization systems, or they don't know how to type the macron, or they opt not to type it just because the macron can't be used in the URL of their site and they want it to match, or any number of other reasons which don't necessarily imply that some "official" spelling has been declared. Trying to follow whatever they come up with for dozens and dozens of small town websites will just leave us with a completely heterogenous mix of systems, where we have random variation such as using "O" for the 大 in Oita and Ogawa but inexplicably changing to "Oh" for the exact same 大 in Oda and Otawara.
 * We should at least choose one romanization system and stick to it. I'd still say there isn't any good reason for us not to choose the same system adopted on both Wikipedia and JR railroad signs. Texugo (talk) 22:46, 1 September 2014 (UTC)

(Indent) I think the usefulness of the diacritics here is quite exaggerated. To be frank, the diacritics don't/won't help most foreigners. Most of them elongate the "o" sound naturally, so it's not a problem and they can't even hear the difference when they are told. And saying Kyotanabe vs Kyōtanabe is going to cause confusion is laughable. The foreign accent and non-Japanese appearance of the speaker are going to be what make you "hard to understand", not a lack of vowel extension. I tend to be against diacritics unless there really is no viable option, which is not the case here. Our article titles should not be thought of as pronunciation guides. We should just be giving the names, not "representing" the names. ChubbyWimbus (talk) 13:43, 2 September 2014 (UTC)

 * For sure if you reduce all the cases to Kyotanabe out of any context, yes it is laughable. What I am talking about is the pronunciation inside a conversation. It happened to me many times that I had to ask my interlocutor to repeat the names of French cities they were talkin about (French is my native language), and we both had decent skill in English. It also happened to me in Italian (even if French and Italian are supposed to be similar; I did not used the long vowels as it's supposed to be done in Italian). Or maybe it's just me who is bad :-) - Fabimaru (talk) 20:09, 2 September 2014 (UTC)

 * I'm not denying that it happens. Of course it happens a lot. English speakers don't even pronounce Paris correctly by French standards, but we didn't name the article Pah-ree or paʁi. We just call it Paris and leave it at that. If we want the proper pronunciation, I think it should go at the article lead but not replace the city's name. ChubbyWimbus (talk) 11:18, 3 September 2014 (UTC)

 * I would be glad if we could go forward with a consensus, because I don't want to submit any other name modification if I know that it may be reverted (you know, it takes time). What should we do? Wait for more feedback? Vote? I searched a bit more (it is as funny as reading the terms&conditions of an service :-, and in the recommmandation page concerning the Japanese names, it is asked not to use macrons in the page title. It has been added by Jpatokal in this WikiTravel modification in 2006. What puzzles me is that it is not exactly in line with the Wikipedia policy, which recommends using the name commonly used in English (if any exists, and it is not obvious to determine which one) and add redirections when macrons are used. My proposal is to use the same names (for page titles and other names such as those of temples, gardens and people) than in Wikipedia. I cannot see how the two projects could reach different conclusion for a name with the same rules. - Fabimaru (talk) 08:06, 6 September 2014 (UTC)
 * Different projects, different contributors, different goals. Wikipedia has a lot of editors who value accuracy above all else, including accessibility.  Wikivoyage places more emphasis on the latter than Wikipedia does.  Powers (talk) 13:38, 6 September 2014 (UTC)
 * Yes, we can be different if we choose, but that doesn't mean we shouldn't weigh the advantages and disadvantages. And in this case, I strongly agree with Fabimaru. Given that, as we do for other languages, we can use redirects to ensure people don't have to type the macron to reach the very small number of destination articles that the diacritic would affect, I am completely failing to see an accessibility issue or any other consideration that could possibly outweigh the various advantages of:
 * showing placenames the way the traveller is most likely to see them on highway signs and at train stations;
 * having a consistent naming system across all Japan articles, which avoids introducing arbitrary transcription differences like those I mentioned above;
 * removing ambiguity in pronunciation; and
 * never having to discuss case by case what the best spelling would be for a given destination.
 * Where are the comparable advantages of the current way? How does insisting on an inconsistent, arbitrary non-system we made up serve the traveller better than the most widely-used and recognized form of transcription that we ourselves use on the phrasebook page? Texugo (talk) 14:49, 6 September 2014 (UTC)

 * Actually, the version you are supporting is much more arbitrary and inconsistent than simply NOT using the diacritics, AND your way would in fact welcome discussions on any city that someone feels shouldn't use them, so your only argument is pronunciation aid, which I already addressed above. If we say "no diacritics", then we just write the names as they are (correctly). If we say "Okay" to diacritics, then we open every city to the "fame" discussion just like other places. We have to ask ourselves, "Is the non-diacritic name more famous and widely used?" and if someone says "no", it can always be questioned.

 * I already addressed the pronunciation argument, but I'll say it again; we don't and should not be using our article names as pronunciation guides. They're city names. If the name is difficult to pronounce for English-speakers or is pronounced in a way that is not obvious to English-speakers, let's put it in the article rather than messing around with the city names. It's a much simpler solution and can be applied to every city across the world. If we start doing it in all of our articles, users will also start to notice and be able to reference it.

 * I beg to differ that diacritics are "the most widely-used and recognized form of transcription" of the city names. That's not at all true. Kyotanabe doesn't . Osaka doesn't . I never understand why people think Japan is such a "special" case when it's not. I notice the Wikipedia articles don't use pinyin for Chinese names. We don't either, because we don't name our articles to be pronunciation guides; we just write the names. ChubbyWimbus (talk) 16:22, 7 September 2014 (UTC)

 * That is just purely wrong. Hepburn romanization wouldn't exist as the most popular transcription system if it were arbitrary and inconsistent. It simply isn't. It is beyond ridiculous to insist that Hepburn, the number one way to write anything in Japanese in the western alphabet, is inferior with regard to pronunciation or in any other sense to our idiosyncratic, made-up non-system of maybe-Hepburn-but-disregarding-the-macron-except-sometimes-when-we-feel-like-putting-an-'h'-or-a-'u'-in-there-instead, depending on whether the website creator happened to subscribe to a third-rate non-standard transcription system. And if our decision is to follow WP spelling, as Fabimaru and I have advocated, there would be no reason for us to have any separate argument about spelling anyway, but even if we didn't follow WP — to the extent that it affects travel, with the exceptions of Tokyo, Osaka, Kyoto, and Hokkaido, there are no destinations that both contain the long O sound and are famous enough to have any standardized spelling the layman who hasn't been to Japan would be used to seeing in print. As the spelling system used officially by both the highway system and the rail system, Hepburn is very easily the "most widely-used and recognized for of transcription", and easily the system the traveler will be most likely to encounter on the ground in transit. Anyway, for you to say "we should just be giving the names, not 'representing' the names" makes very little sense. Any time you write a Japanese place name, you are choosing a way to represent it. And while we are choosing a way to represent Japanese placenames, there is absolutely no convincing reason why choosing to vaguely approximate but not actually follow any actual system would be better than choosing the most popular established system used by all the major forms of transport that the traveller is most likely to use. Texugo (talk) 20:46, 7 September 2014 (UTC)
 * It's also pretty hard to claim Kyotanabe doesn't use it. Texugo (talk) 22:34, 7 September 2014 (UTC)
 * To be fair, highway signs seems to always dismiss any mention of long vowels. But it was not my argument for using the macron (allows knowing the pronunciation without changing page, and having consistent usage of macrons for all the place names including points of interest) - Fabimaru (talk) 18:42, 8 September 2014 (UTC)

I don't need an irrelevant link to something that was already stated (or even linked?) above. Yours is of the JR station. My link was of the actual city and what the city calls itself (aka: relevent). Nice try though.

Your arguments about the Hepburn system are moot. The Hepburn system was designed for translating WORDS. We're talking about cities that already have English names. We don't have to translate anything. Also, you are using the modified version, not the original Hepburn system, which never used diacritics for elongated vowel sounds. And the Hepburn system is once again no more "special" than pinyin, which once again, we don't use. Of course based on how pro-diacritic people seem to be, it may just be a matter of time before China is targeted...

In response to your comments about Oda vs Ohda, Google produces many more results for Oda than Ohda (with Shimane), so I think it's safe to continue using it without being hypocrites. Whether you like it or not, these cities HAVE English names, so changing them to a phonetic representation is not better. I don't see how using their English names is NOT a convincing argument? I LIVED around Kyotanabe, and nothing in the city about the city in English uses diacritics. That's enough for me to say let's leave it alone. Adding diacritics would be the arbitrary thing to do. The diacritics REALLY aren't important for a traveler. Even those train station names are better known without them because Hyperdia doesn't use diacrtics.

Do you have a response for what's so wrong about just writing the pronunciation beside the name in the article lead? It seems like a win-win to me. The city name doesn't have to be changed and the pronunciation is there for people who are really concerned about being exact. ChubbyWimbus (talk) 13:10, 8 September 2014 (UTC)
 * The city name doesn't have to be changed: I can take care changing the names. So I (or any other person) do it, what is wrong with my approach? It's a win-win, those who are not concerned by the diacritics are still able to read it, and the other have the pronunciation information anywhere. - Fabimaru (talk) 18:42, 8 September 2014 (UTC)

I would appreciate if we have more opinions from other people, because the discussion is going round in circles. - Fabimaru (talk) 18:42, 8 September 2014 (UTC)
 * I would too but, I must say that I have just heard two claims that I feel are blatantly untrue and wholly unsupportable: the notion that Hepburn is only "for words and not for names" is completely ridiculous and I have no idea where you pulled that out of. Hepburn was designed to transcribe anything in Japanese, and placenames are constructed out of hiragana and katakana and kanji just like anything else in Japanese. Similarly, any claim that "Japanese towns all have an established name in English" is completely and utterly and laughably unfounded. I've already explained why above. Just because somebody, very likely not even a Japanese person from the given town, translated a website either using or not using a diacritic cannot in any way be interpreted as a statement on the part of the city that "this is our official name we consider to the the correct way to write our city name in English".
 * You have tried (unsuccessfully I think) to deconstruct the advantages that Fabimaru and I have given for adopting the most popular common transcription system, and you have tried to downplay the disadvantages we've pointed out in the current idiosyncratic approach, of insufficient pronunciation, introduction of ambiguity, inconsistency, and divergent transcriptions of things that are identical in Japanese. But what advantage are you offering?? What are you defending, and why? A system where instead of following a standard, we go case-by-case following whatever arbitrary decision was made by the person who did the translation of the website, regardless of which transcription system they happen to subscribe to, if any at all, and/or the evidence of Google searches made unreliable by the fact that Google searches ignore the macron, all because we want to... what? Where is the comparative advantage of the current bias against the macron? You are denying a system with more consistency, fuller pronunciation, and less ambiguity in favor of what, exactly? Even if I was inclined to concede all the points you just tried to make and pretend the current system has none of the disadvantages already pointed out, I would still see absolutely no convincing reason not to go ahead and use Hepburn. Texugo (talk) 22:13, 8 September 2014 (UTC)

 * Your claim that Wikivoyage discovered all these Japanese cities and therefore needs to name them is ridiculous. I've already shown that these places do in fact already have names. Kyotanabe has a name, and it doesn't include diacritics. You can whine about it all you want but that doesn't change the facts (nor does stating that what has already been supported is "wholly unsupportable"). This isn't about the Hepburn system; we didn't discover these places and I guess neither did Hepburn. They don't need special Wikinames. I'm not sure how you can even propose that looking at how a place name is written is not a viable way to see how it is written. If the city hall and all references to and promotions of the city that don't copy and paste from Wikipedia write it the same way, you say NONE of it can be trusted, simply because it's not written your way.
 * Please don't put words in my mouth. Nowhere above did I deny that the diacritics could not be useful for pronunciation. In fact, the suggestion I've made a few times, which you continue to ignore in favor of irrelevant Hepburn rants, is that we should give the cities their names and put the pronunciation in the lead beside the name. I'm not downplaying the advantages of the macron. The advantages are truly minute here. You're talking about adding a symbol to tell people to elongate an "o" that most foreigners already elongate, so who cares? The example above of when the diacritics are useful wasn't even a Japanese case.
 * The problem is, you are talking about the "advantages" of renaming cities, and while you have ("unsuccessfully I think" to quote you) tried to twist and refute my argument, my argument is that these places have been named. Since they've been named, we need not debate; we can just write the names. You talk about all these "difficult situations" that exist, yet no one has ever refuted any of the Japanese city name spellings. Why? Because they're established, and we all know it.
 * The anti-diacritic and pro-English stance of naming destinations is a Wikivoyage rule of naming, so the fact that you think it's stupid doesn't matter.
 * To recap the points that I'm making: We don't need to name named places (As I've said, I know Kyotanabe extremely well and the names we use have never been controversial, because everyone knows them), diacritics are to be avoided whenever there are English names (which there are), AND I'll reiterate my idea to write the names as they've been named but put the pronunciation with the name in the lede, which would be a win-win and could be applied across all non-English city names. ChubbyWimbus (talk) 12:03, 9 September 2014 (UTC)
 * Youour argument hinges on the claim that there is already a single official way to write every town name in English. Your chosen example was Kyotanabe, and I have already shown that even in that case there are at least two different orthographies the tourist will likely encounter. That means that no, in fact, there is no single English name for it. There are only competing transcription systems, at least three of them, and trying to determine in each case which to follow is silly because it presents no advantage. It would be prudent to choose one and be consistent. Texugo (talk) 13:05, 9 September 2014 (UTC)

 * My argument doesn't hinge on that at all. If it did, you could have just pointed to Wikipedia's arbitrary names as "proof". Also, your "proof" is a JR Station, which is named by JR West and has no connection to the city itself or how it writes its own name, so you have no proof. Do you want to name every city based on its station name? Above you said that station names were inconsistent and not credible, so have you changed your mind, or are they only credible when they say what you want them to say?
 * There need not be a "single" way to write a name in order for it to have an established name. We've dealt with many cities where there are slight variances in spite of having one established and common one, and I think you know that. Why do keep saying we will have to "try and figure out which case to follow" when the names are already clear? You keep talking about consistency, but we're already quite consistent; we've named the cities according to... their names. And saying "no diacritics" does in fact create consistency.

In doing a search in Japanese (in hopes of being fair) I could only find non-diacritic namings: Kyotanabe is Kyotanabe　   [] Soja is Soja I tried to find them written with macrons, and they didn't exist. The only inconsistency that I could find on an official page was that Kyotanabe's Chamber of Commerce website forgot the "e" at the end of the name, but we all know it should have the "e" so there is no controversy. Using the diacritics would be just as I said, a special Wikiname that does not reflect reality. That's why I will once again suggest naming the cities without the diacritics and then writing a pronunciation aid beside the city name at the beginning of the article. ChubbyWimbus (talk) 13:46, 10 September 2014 (UTC)

 * I cannot fathom how it is so easy for you to dismiss the evidence to the contrary. Again, the reality in the ground is the the diacritic is, quite indisputably, used as well. Even if we limit discussion to only your example, the very first thing the very vast majority of visitors will see is a sign using the diacritics. I already posted that pic above and you somehow tried to dismiss it. And that being the case, it's simply not possible to claim that I'm advocating some "made-up wiki name". There are, as I stated, multiple transcriptions in use, on the ground, in reality. It would be far easier to pick one than to go case by case relying on difficult google searches to trying to determine which transcription to use and end up with a collection a Japanese articles which are not titled consistently according to any single established system. If there is any "made-up wiki system" here, it might be the current one that eschews existing standardized spelling systems in favor of a "go with whatever flow you can discern from google but avoid macrons at all costs" approach. Texugo (talk) 16:53, 10 September 2014 (UTC)

 * The reason you cannot fathom it seems to be that you aren't reading what I wrote, because I've addressed your ONE example above. Do you even remember your own example? It's the JR station to refresh your memory. Please reread my last comment. It has been addressed. I've addressed all of your comments while you continue to state that I am "ignoring" them. It's getting old.
 * My examples are "on the ground", relevant to travelers, and plentiful, while you are clinging to ONE station name that not only I addressed but YOU yourself called unreliable. Your ONLY source in unreliable by your own admission and, to repeat myself again, a single example does not show that it's an established name. Mine are all reliable sources. That is fact. Your assertion that your way of writing is all over cannot be taken seriously since you have no proof aside from a station name that we've both refuted. How does my proof hold less weight than your word? You don't even know the city. I've both provided evidence AND know that area yet you pretend you know what it's like "on the ground level". Clearly you don't.
 * And once again, you talk about all these Google searches, "difficulties", and pandemonium without an "established system". Sorry, but there aren't any difficulties and the naming system is well-established and really simple; use the city's name. No one is confused about the naming conventions except you apparently. You are the only one who seems to require Google. The rest of Wikivoyage has been naming these cities without controversy for a long time. Where are the confused masses you pretend exist? At this point, your argument seems to have boiled down to unproven blanket statements, false claims that I've not addressed what you've said, and claims about naming confusions that have never and still don't exist. You've ceased responding to the information I've given you and continue to reiterate things that I've addressed multiple times. I've even proposed a solution that includes the pronunciation guide 5 times. ChubbyWimbus (talk) 18:00, 10 September 2014 (UTC)
 * I am really sorry. I hope we can reduce the level of emotion we seem to be investing in this. Maybe you didn't mean certain claims the way I took them, and I certainly didn't mean some things the way you seem to have taken them.
 * We are just looking at this from different perspectives and talking past each other.
 * What I see is 京田辺. I see 大田. I see 安城. And lots of other placename with various sounds. And for each, regardless of who writes it or where, there is one way to write it in Japanese, and multiple ways to write it using the alphabet which are being used on the ground. You are surely aware that the long O sound can be written with a macron, with an oh, with an ou, or with o with nothing signifying its length. The づ sound can be written as du or dzu or zu. The しゅう sound can be written as shu or shuu or syu or syuu or shū or syū. If you gave any placename containing any of these sounds to 20 Japanese people and told them to write them down in English, you'd definitely get a range of spellings. So, if you are claiming that all Japanese places already "have a name in English" that we should use, what I do not understand is: how do we know which of the possible spellings that supposedly established name is? Where do we find this "established name" you speak of? What is our source? The only possible answers I have seen implied are
 * a) we look at the town's website - If this is our answer, I wonder what you suggest when a place doesn't have a website, or has no English on its website, or uses machine translation on its website, or contains internal inconsistency on its website. Do we assume the website reflects some "official sanctioned" spelling even if the name is written nowhere except in the url or the copyright notice? Do we take the official town website spelling even if local tourism infrastructure tends to use a different spelling? If a town website does use a diacritic, do we use it too?
 * or
 * b) we look at Google results - In this case, it is rather difficult to get a clear answer on the most common placename orthography because place names coincide with business names and personal names, because Google ignores diacritics in searches, etc.
 * Ok so then, if that question is satisfactorily answered, the next thing I don't understand is: why is that better than following a standard orthography that always writes the same sounds in the same way? Given that we know people will see the placenames spelled different ways in different places no matter which spelling we choose, how is matching city hall websites or whatever case by case more advantageous than spelling things consistently and unambiguously using a recognized common system? Since most Japanese placenames are pretty unknown to westerners, and since there are multiple spellings of many of them to be found out there anyway, when I weigh the existing system against the advantages of following an established orthography system (still very minimal diacritics - just one, improved pronunciation information conveyance, using the same spellings to write the same sounds/kanji, simple check of WP instead of digging up city hall site/google search, etc), then I still wonder: Why are you so vigorously defending the current system versus those advantages? It must have some bigger advantages that outweigh them, right? That is what I do not see. Texugo (talk) 23:14, 10 September 2014 (UTC)

 * The way I look at is that 99.99% of the cases, we would not need to consult sources. The names simply are. Do we really need sources for Kyoto? Kochi? Oita? I don't think so. Perhaps some of my views of the "obvious" are because I'm talking about places I've been and often visit, so I have seen more than even an internet search will allow. If however, someone DOES questions a name, such as Kyotanabe, then we can of course do a search and provide proof of our assertion. In Kyotanabe's case there are not only official websites from the city and tourism bureau, but also the university, which is known throughout the nation, spelling it with no diacritics, no "oo", and no "oh", so there is plenty to show as proof of its established name. I did the same with Soja above.

 * Modern naming conventions have almost completely dropped the "oo" and "oh" from usage, so they will generally not be an issue.

 * The only major case of the "oh" still being used in English that I am aware of is that of Minoh (Minō). Even Wikipedia uses Minoh instead of Minō without anybody questioning it (and we probably should, too. Our way, Mino, with or without the diacritic is less common than Minoh or Minoo, but Minoh is really the dominant name). You pointed out the city hall website of Oda city using Ohda. Most sources in English use Oda, though. If however, you or someone else were to say that Ohda is the name, it could be discussed and considered. If we need sources, we should never use just one to determine the name anyway, regardless of what country the city is in. Google actually corrects the name if you type "Ohda Shimane" which is another indicator that just Oda should be used. But cases that may lead to discussions are very rare.

 * I would much prefer to review controversial names than to choose a single naming convention for an entire country without regard for how the name has actually been transcribed. It would seem to be against our goals to establish such a system and it would not be to the benefit of the traveler. In the Minoh example, to say that Minoh and Minoo have both been cited and therefore we will use Minō follows no sense of logic and is no help to the traveler. If the discrepancy is between "oh" and "oo", then we should discuss it and the result should be one of those, not something completely different. Pronunciation guides are useful, though, and do have a place, but it should not supersede all other naming rules. That's why I still think it best to write the names as they are written in English (with discussion if "the way it is written" is truly unclear). I think requiring a pronunciation guide in the article lead would be a great improvement to Wikivoyage for all cities with non-English name origins, but I'd keep them out of the article names themselves for the reasons I've stated above. ChubbyWimbus (talk) 09:22, 11 September 2014 (UTC)

Well, I don't have anything else to add really, and maybe you don't either. Summing up, I still see a plurality of orthographies that anyone writing about a given place has to choose between, and the fact that a city hall has had to pick one for their own writings does not to my mind imply that their choice therefore constitutes an "established" name in English. And since I think there is at least reasonable doubt in my mind as to whether there are universally "established" names in English, it is very hard for me to see what advantage an unstandardized selection of dubitably "established" spellings has over a clear and consistent and fully pronounceable orthography system recognized as the most widely-used romanization and adopted by various government agencies including the national rail system that is by far the most common choice of travellers. I have tried my best to explain and support my position above, as have you, and neither of us has managed to convince the other. Now I'm pretty tired of this conversation. Maybe we should hear from some other users who are less familiar with Japan and Japanese. Texugo (talk) 23:41, 11 September 2014 (UTC)

 * I suppose we have both stated our arguments. I just don't see why we would/should establish a naming convention for one country that supersedes our established naming convention rules makes sense or is necessary, particularly when it is a country where names have been transcribed already in a variety of English materials. To me, it seems we should always at least try to take into consideration how a city's name has already been written in English (as I tried to show with Mino, our current name and the proposed naming conventions completely ignore that the name is most commonly written as "Minoh").
 * On the note of attracting other user comments, I think we may have confused or scared others away (lol). ChubbyWimbus (talk) 13:57, 13 September 2014 (UTC)

I'm a bit late here, but this discussion really belongs on Wikivoyage talk:Romanization. Nonetheless, I'll summarize my view, which is essentially unchanged since 2006: for non-Latin scripts in general and Japanese in particular, use of diacritics is essential in pronunciation guides, but adds little to negative value in article titles due to the broken link problem. I don't care deeply either way about using macrons in link titles, but it seems a bit pointless.

Also, Hepburn is *the* standard for romanizing Japanese and any alternative spellings should be nuked from orbit. Wikipedia's "use the most common name" policy is a snakepit of endless, pointless festering disputes (I think you'll agree that the discussion above proves this point rather handily); we have the luxury of being able to dictate our own polocy, and "use Hepburn, no macrons" has worked pretty darn well for Japanese place names to date. Jpatokal (talk) 11:58, 28 September 2014 (UTC)
 * That page says "Indicate long vowels with macrons, except in article titles" which is not quite the same as "use Hepburn, no macrons". WhatamIdoing (talk) 15:56, 4 October 2014 (UTC)

I edited this policy
See here for what I added. I hope this is okay. If not, please discuss. Hobbitschuster (talk) 16:27, 17 August 2016 (UTC)

Templates for foreign words
One thing that's always surprised me is that WV has no markup or templates for foreign words. Per wv:Foreign words words in Roman letters (or romanizations) should be written in italics, but that's it. No HTML markup, no templates.

Compare this to WP, which has templates for everything. In particular, w:Template:Nihongo and the reversed w:Template:Nihongo3 are widely used, and closely match what how foreign words are presented on WV.

Why is this important? Well, aside from enforcing consistency in the order of words and formatting them in italics, the templates wrap text with HTML tags to indicate the language (English, foreign, romanized, etc.). In Chinese and Japanese text, the language tags can actually be necessary and not just a luxury, because there's no other way to distinguish which form of a hanzi/kanji character to use (traditional, Chinese-simplified, or Japanese-simplified). It can similarly be helpful in right-to-left languages like Arabic and Hebrew text when there's Roman lettering mixed in. It also helps screenreaders so they can use different pronunciation rules, and can help any bot that scrapes and interprets content.

See also https://www.w3.org/International/questions/qa-lang-why.

Is anyone in favor of creating and beginning to use such templates on WV? Would it be worthwhile and feasible to create a bot to try to automatically convert text in existing articles to use such templates, or is that a fool's errand? --Bigpeteb (talk) 18:16, 6 March 2019 (UTC)
 * Count me as 100% in favor of providing structure to non-English content. This could be very useful for (e.g.) apps that translate on the fly or finding search terms or providing preferred fonts (particularly for non-Latin languages), etc. I see several benefits and no downsides other than some work but no one is mandating that everyone change every instance of "pommes frites" to " pommes frites " immediately. Like a lot of changes, we can can course in policy, slowly change our habits, and maybe have some bots or semi-automated tools help. —Justin ( koavf ) ❤T☮C☺M☯ 18:25, 6 March 2019 (UTC)
 * Seems user-unfriendly for editors. And it won't enforce consistency because a lot of people won't use the new templates, just as they don't follow conventions on capitalization, not touting, not listing ordinary tours, etc., etc. It seems like it'll just create a lot more work for someone, with very little difference in what the reader sees. And I think a greater explanation is needed for why templates are needed for Chinese, Japanese, Hebrew, etc., when we seemingly haven't needed them for all these years. Ikan Kekek (talk) 21:15, 6 March 2019 (UTC)
 * It is more difficult for editors, especially new and pass-by editors (which are more important for us than for Wikipedia). But as tools get better, the advantage of good markup increases. The examples Bigpeteb mentions were probably irrelevant ten years ago, as the software would't choose appropriate fonts or adapt pronunciation. I suppose the advantage still affects only a minority of readers, so I'd support keeping our present "keep it simple" policy, except where the value is clear – but choosing appropriate hanzi/kanji seems to me to be such a clear advantage. Perhaps language templates could be used in these limited cases. --LPfi (talk) 21:28, 6 March 2019 (UTC)
 * I think the "alt" field in listings shows exactly why we have needed language templates like this for a very long time. The "alt" field awkwardly tries to serve as both "romanized name" and "name in native script(s)" and "alternative/former/other name". That's why it has hacks like "if the first character of 'alt' is a non-roman character, don't italicize the field", in which case editors must manually italicize if the field contains both foreign script and a romanization, and then there's no place to separately add an actual alternate name, and... it's a mess. I think the correct solution from the beginning should have been to have language templates, and use them in the "name" field and anywhere else that's appropriate. For example, such a listing might look like . Styles would take nesting into account, making sure that only one part of the primary name gets bolded, and romanizations are always italicized. Dynamic maps would have multiple names available, and could display all of them, or perhaps have a user setting to choose whether to show English, foreign, or romanized names. Editors would have easy but useful abilities like easily being able to reverse the name without losing any of the formatting or the markup that's helpful for bots (example:   would generate "* Nihon-bashi ( 日本橋, "Japan Bridge"). Free.").
 * Is this more complex than formatting things manually? Perhaps so, but I wouldn't say it's any more complex than Mediawiki markup in general. (I can't tell you how many times I've miscount the number of quote in something like, so   to me is easier to get right even if it's a little more typing.) Is it user-unfriendly, something that a lot of people will ignore? Well, users will ignore whatever rules they want to, and in fact on WV we encourage them to edit even if it's not perfect, since someone else can come along later and fix it up. I would think/hope it's easier than, say, looking up correct coordinates for a listing. But the fact that something is slightly more difficult or that new users might not use it has not stopped us from making other changes; let's not use that as an argument for or against this, either. --Bigpeteb (talk) 18:35, 13 March 2019 (UTC)
 * Perhaps you can designate yourself the editor who inserts all those codes all the time. I do a hell of a lot of patrolling and don't look forward to doing these kinds of edits, so I may choose to ignore them. I hope that doesn't sound unfriendly; we all choose what to do with the time we choose to volunteer on this site. Ikan Kekek (talk) 01:33, 14 March 2019 (UTC)
 * VisualEditor will add the HTML markup for you (from the character formatting menu, ), and I prefer that to trying to remember which template name is used on which wiki.  WhatamIdoing (talk) 02:57, 7 March 2019 (UTC)
 * That is odd. I understand using a menu is easier than remembering what to write, but HTML is not easier for editors than mediawiki templates. If we do not want that code, using VE to insert it is not better than inserting it by hand. And why dir="ltr" (left-to-right)? Isn't that implied by the page being in English and the phrase in Spanish? --LPfi (talk) 20:13, 7 March 2019 (UTC)
 * I think that the direction is supposed to be specified for everything, even if it "should" be obvious. There are a few wikis where I find that I have to specify three components to get English displayed properly:     (This is probably not required for span tags, as they don't affect whole paragraphs.)  WhatamIdoing (talk) 21:34, 7 March 2019 (UTC)
 * Boilerplate like that is precisely the problem that templates solve. I don't know whether the ltr tags are required or not, but by putting it in a template, we can consistently apply and change formatting everywhere (for example, if we at first decide the ltr tag isn't needed but then find some browser that requires it). --Bigpeteb (talk) 17:46, 13 March 2019 (UTC)
 * I think you're making some good points here. I added some localized text by hand recently, and it was a pain. There's definitely some benefit to be had from language templates. However, I think they may also be a bit premature for this community. While we do have some text in other languages, we have many more instances of foreign currencies and measures with units, and we have had templates for them for a long time now (see, e.g. EUR and km); still, nearly all mentions of a unit or currency are regular untemplated prose, and this is despite concrete benefits, for all readers, coming from those templates (i.e. automatic currency conversion tooltips and non-breaking spaces). I would much rather see those templates made ubiquitous, something I've been working towards when I can (and hope others join me), than the addition of some more. When that's done, I'd see a much stronger case for language templates. ARR8 (User talk:ARR8 | Special:Contributions/ARR8) 03:27, 14 March 2019 (UTC)

Historic names?
Should we add a section/text about when (not) to add historic names? Places all over the world have had different names throughout history - but only some are relevant to the traveller. This doesn't always depend on the age a name was used in... Uruk, Ctesiphon or Gaugamela will be more relevant to a traveller - at least one interested in ancient history - than maybe Chemnitz having been called Karl-Marx-Stadt or Zchinwalis old name of Staliniri. ObersterGenosse (talk) 21:05, 26 March 2023 (UTC)
 * I don't know; is that needed? My feeling is that historic names should be mentioned whenever they're interesting. Ikan Kekek (talk) 18:06, 27 March 2023 (UTC)
 * By the way, I'm unfamiliar with Zchinwali, but I would say that mentioning Chemnitz's former name of Karl-Marx-Stadt is very relevant to travelers because of the huge statue of Karl Marx in the city. Ikan Kekek (talk) 18:12, 27 March 2023 (UTC)

title: Wikivoyage talk:Foreign words


text:
Wikivoyage talk:French Wikivoyage Expedition

So, what's happening here? Even though the structure of the French Wikivoyage Expedition is good, it still hasn't been moving forward for weeks. Perhaps it would be necessary to speak with the large French Wikipedia community - perhaps place a notice on the front page mentioning this expedition so we can get more users to finally form the French Wikivoyage. That's what happened with the Romanian Wikivoyage - it was and still is "advertised" on the Wikipedia main page and it gathered users. So, good luck and hopefully we can get some progress with this expedition! (WT-en) Ronline 01:51, 18 Jan 2004 (EST)

 * I just announced it on the Bistro. I'm not frequent enough on the French Wikipedia to put something on the main page, but hopefully that'll catch some eyes. -(WT-en) phma 09:22, 18 Jan 2004 (EST)

 * Actually, I am strongly against aggressive recruiting from Wikipedias. We have a fairly tenuous good relationship with Wikipedia as a whole, and I'd rather not have it damaged by looking like we're abusing their site to advertise this one. So, please be respectful if you decide you want to do this.

 * I probably also need to remind folks that Wikivoyage is not a Wikimedia project. We're not like Wikibooks or Wiktionary. We're something different. So, we're not part of the "family" at Wikimedia web sites; we're guests. --(WT-en) Evan 11:20, 18 Jan 2004 (EST)

 * Another reason why I put it on the Bistro. Putting a note on people's talk pages would be aggressive; putting it on the main page would be too bold; putting it on the Bistro isn't, I think. I first learned of Wikivoyage because someone said that an article on Wikipedia belongs on Wikivoyage. -(WT-en) phma 15:48, 18 Jan 2004 (EST)

 * Well, it's up to you what you want to do, but the Bistro listing seems to be working, as there are 3 users already! Hopefully, we can get 5 as soon as possible. Considering Wikipedia, I know we're not a Wikimedia project, but they really are related projects and many people here (me for example ;-) have come from Wikipedia and are still active at Wikipedia, so we have a good relationship with the main contributors of our language version of Wikipedia and can "recommend" Wikivoyage to them. On Romanian Wikipedia anyway (I don't know if on others) important things and news can be put on the front page and people were actually very happy about Wikivoyage in Romanian (well, in a way it was the second language version - national pride always attracts people ;-)

 * But anyway, it's really, really good to see the French Wikivoyage Expedition starting up. By the way, out of curiosity, where is the Bistro? Is it a place on French Wikipedia? (WT-en) Ronline 17:55, 18 Jan 2004 (EST)

 * Yes, I just looked at French Wikipedia - Bistro is like the Travellers' Pub. By the way, I am intent on starting an Estonian Wikivoyage Expedition and will talk to the Estonian Wikipedia via similar means. Bonne chance avec le Wikivoyage français, (WT-en) Ronline 18:00, 18 Jan 2004 (EST)

 * The announcement has been taken off Bistro, which is very busy. Would someone like to announce it on Accueil? -(WT-en) phma 11:01, 26 Jan 2004 (EST)

Getting started
So, I'd love to get this language version started. I don't think it'd be really responsible of me to join the Expedition, though, as I should probably stay focused on the whole shebang.

I'd like to start the interface translation process, though, so we could maybe get a quick start when Mystery Guest #5 finally signs up. Any objections?

By the way, I'd support waiving the 5-member rule if the 4 people who've signed up already expect that they can get the necessary work done -- help text, MoS, About, etc. -- in the first month or so, without a fifth helper. --(WT-en) Evan 16:43, 4 Feb 2004 (EST)

 * So, what to do now? (WT-en) Yann 09:19, 7 Feb 2004 (EST)

 * Pick a go-between for the French and English Wikivoyages. You 5 need to figure out how to do that. The Romanian group did it by voting. At the very least, the go-between should be bilingual, have time to do a report once a month, and be familiar with English Wikivoyage. They should probably also have the unleadership skills :-) necessary to get a new Wiki off the ground.

 * After that -- actually, I'll be doing it at the same time -- I'll set up the French wiki, and then we're off to the races. --(WT-en) Evan 18:07, 7 Feb 2004 (EST)

Interface files to translate
So, as mentioned before, we need to translate the interface file into French in order to set it up. I've put up the English Wikivoyage interface file, as well as a starter French version, based on the file distributed with MediaWiki.

Probably the best way to attack this is just to go through the French Wikipedia version, and compare each entry to the one in the English Wikivoyage version. If they're different, translate the the English Wikivoyage version into French. Some good thing to look out for: license info, site name, etc.

Thanks for everyone helping out on this. --(WT-en) Evan 13:52, 5 Feb 2004 (EST)

 * Hi, I remplaced all occurences of Wikipedia by Wikivoyage, and GFDL by licence Creative Commons Share-Alike. It seems ok to me now. (WT-en) Yann 15:23, 5 Feb 2004 (EST)
 * Ok for me --(WT-en) Pontauxchats 05:27, 9 Feb 2004 (EST)

"Francophone" not "French"
So, one complaint I've heard on the wikipedia-l mailing list is that the French Wikipedia has a lot of problems between contributors from France and contributors from the rest of "francophonie". Some people seem to consider the "French" in "French Wikipedia" to mean "by and for citizens of France" rather than "in the French language". So some discussions about language by Quebecois, Swiss, Belgian, African, or other francophone contributors are dismissed.

Given that there's something like 30 countries world-wide with significant francophone populations, I think it'd be a shame to lose contributors from these countries based on a national versus linguistic definition of "French Wikivoyage".

I'm wondering what the best way to specify that this is the French language Wikivoyage and not French national Wikivoyage. I'd thought about calling it "Wikivoyage francophone", but I'm now wondering if it's not just a wee bit patronizing to spell things out entirely for French-speaking contributors. I mean, nobody seems to confuse "English Wikivoyage" to mean "Wikivoyage for citizens of England", to the exclusion of Scots, Canadians, Americans, New Zealanders, Jamaicans, Australians, etc.

Would there be another clear way to say that "Wikivoyage français" means "Wikivoyage francophone"? --(WT-en) Evan 16:07, 8 Feb 2004 (EST)

 * Of course, I agree with you. In French, "français" means from/about France and "francophone" means French speaking, but I am not sure if the meaning is the same in English. (WT-en) Yann 16:37, 8 Feb 2004 (EST)

 * Yes, the meaning is different in English. --(WT-en) Dawnview 22:58, 8 Feb 2004 (EST)

"Wikivoyage francophone" sounds funny to me. Wikivoyage doesn't have a voice, except for the Romanian sound samples, so I have trouble picturing a Wikivoyage with a French sound. "Wikivoyage français" sounds fine to me, though ambiguous, but since at least three of us are not in France, that makes it clear. Now if the Cypriots someday start writing Greek and Turkish in the Welsh Wikivoyage, then we'll have a problem. -(WT-en) phma 18:02, 8 Feb 2004 (EST)

 * Interestingly, my welcome message to the French Wikipedia calls it "Wikipedia francophone"! That aside, I think we can probably put some information somewhere in the FAQ or About that specifically points out the French language rather than French national nature of the project.

 * I think it might be worthwhile to start considering what language rules will be used on the site, though. --(WT-en) Evan 18:31, 8 Feb 2004 (EST)

 * I agree with Wikivoyage francophone rather than Wikivoyage française (french WT). I don't want to see the same behaviour than on fr:WP, where many people forget the rest of the globe... --(WT-en) Pontauxchats 05:27, 9 Feb 2004 (EST)

Voting twice/thrice
I notice Pontauxchats has been voting for three different users! Is this OK, because I think it does open up the possibility of there being a tie between three potential go-betweens. I think the easiest, most democratic and fairest way would be for each user to only vote for 'one' go-between. Anyway, it's great to see the French Wikivoyage going ahead - keep it up! (WT-en) Ronline 07:35, 9 Feb 2004 (EST)

 * I think it should be limited to one for and one against. Of course it is possible for A to vote for B, B for C, C for D, D for E, and E for A and there be no winner. -(WT-en) phma 10:43, 9 Feb 2004 (EST)

 * Sorry, I didn't read enough... So I'll choose one (and only one) of them. Just note that I voted for two (and not 3) users. :o) --(WT-en) Pontauxchats 10:49, 9 Feb 2004 (EST)

 * Sorry - I now realise you only voted for two people and one against. Yes, so one for and one against is OK. I think it looks like there is one definite winner in the go-betweens! (WT-en) Ronline 03:27, 10 Feb 2004 (EST)

 * We can't declare a winner until Nikolai votes. The result could be a tie. -(WT-en) phma 07:23, 10 Feb 2004 (EST)

 * Yes, or wait for an other volunteer, cause it seems nikolaï is a mort-né... :o( Moreover, Mark didn't vote for anybody. --(WT-en) Pontauxchats 07:55, 10 Feb 2004 (EST)

Evan said that another use might not be necessary. And I am sure than once started, other contributors will come. However I am a bit surprised to be the one with more votes. $o) I am a bit new to Wikivoyage and I would have expected Pierre Abbat to be the go-between. Anyway it is OK for me. (WT-en) Yann 09:30, 10 Feb 2004 (EST)

So now :
 * Pierre : 2
 * Yann : 2
 * Mark : -1
 * Pontauxchats : -1
 * Nikolai : -2
 * NB : I don't like a system where you can't vote for yourself. (Note : I'm sure Chirac voted for himself...:o) ) We're waiting for Mark's vote... --(WT-en) Pontauxchats 10:21, 10 Feb 2004 (EST)

 * I'm on the edge of my seat! This is just like Star Académie! --(WT-en) Evan 12:24, 10 Feb 2004 (EST)

 * OK. It sounds like Yann feels too new to Wikivoyage.. so I guess I'll vote for Pierre Abbat, assuming he's up for the extra workload.  -- (WT-en) Mark 11:23, 11 Feb 2004 (EST)

Prêtons à rumbler
Uh, so, it looks like we got a team, a go-between, and a language interface file. And now we have a wiki. I'd really appreciate it if folks in the Expedition could concentrate on getting the help documentation, policies, and descriptive pages set up, so that when new users come in, they'll have some idea what to get done. That should really be priority #1.

You guys might also want to try to split up the work to make it easier. Good luck! --(WT-en) Evan 17:12, 11 Feb 2004 (EST)

 * I copied Main Page, translated a few words, copied Project:Goals and non-goals, and translated a few more words before I got a phone call and I have to work on a website. If you want to plunge forward, please do! BTW, where do I put reports? -(WT-en) phma 20:45, 11 Feb 2004 (EST)


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

I protected this page because it's not really open to editing by anyone. The license needs to remain verbatim. -- (WT-en) Evan 07:44, 14 Aug 2003 (PDT)
 * Should anyone wonder what those weird edits by me were about - I meant to edit a different wiki and somehow ended up editing Wikivoyage's page. -- (WT-en) Andrew H. (Sapphire) 14:11, 24 October 2006 (EDT)
 * That's weird. --(WT-en) Evan 14:29, 24 October 2006 (EDT)
 * I know. I was perplexed, but I was using this page as a basis for the other work so I think I got the two tabs mixed up. -- (WT-en) Andrew H. (Sapphire)

Should this page be moved to Shared? ~ 203.189.134.3 10:15, 10 October 2007 (EDT)


text:
Wikivoyage talk:Gender issues in Wikitravel participation

Women Wikivoyagers
So, I was just reading a thread on the Debian mailing lists about women involved with that project (It's got something like a 900-to-1 ratio of men to women). And it got me thinking: female travelers seem underrepresented on Wikivoyage, too. Why is that? And what can we do about getting more? --(WT-en) Evan 03:00, 16 Mar 2004 (EST)
 * First, I belive that you can't really know how many women surf wikivoyage. Second, I think that mostly men (or at least more men) become addicted to the net or some site (so there are fewer of us around to begin with). 61.247.241.181 08:01, 16 Mar 2004 (EST)

 * Been extremely busy with school (studying) and school (teaching) lately, so I haven't been around much lately. On the teaching side, I may get the ratio to swing a bit the other direction as I start using Wikivoyage with students at one or two women's universities here. (WT-en) Ted 05:29, 17 Apr 2004 (EDT)

 * FWIW, I found Wikivoyage through a link from that massive Linux conference in Portland (Oregon). If everyone's finding wikivoyage through existing Open Knowledge communities, then wikivoyage will inherit exisitng gender balances (how does wikipedia do on that front?). The typical reasons given for women not participating in Open Knowledge communities are: many women use their 'leisure' time for household and relationship maintainence rather than online projects (although given how many women blog, I think this is wearing thin); women prefer an environment with social interaction rather than technical interaction; women aren't as comfortable in environments where criticism rather than praise is the normal social lubricant. I can't actually figure out how much of that applies to wikivoyage. (WT-en) Hypatia 21:07, 16 Dec 2004 (EST)