I'm noticing that sometimes people use the html markup code "€" and sometimes the character itself "€". Is there advantage to using one or the other? Dollar signs and pound signs are always by character for example, and when I edit I'd rather see and use the € symbol than the "€" markup as the latter is messier. any opinions?? psychofish 15:22, 10 July 2007 (EDT)
The character is better for the reasons you state, it's just not available on all keyboards (like mine). Feel free to change any amp-euros you see. Jpatokal 22:03, 10 July 2007 (EDT)
The € character is not on my keyboard either, but can easily be accessed by hitting Ctrl-Alt-4. Does this advice qualify me as a computer geek? Jnich99 13:14, 16 May 2009 (EDT)
The first section says that "Wrong: $100". Is that a typo, cause I see nothing wrong there?
For long numbers, I'm sympathetic to eliminating commas since that is not a universal scheme, and commas can be confused with decimal points. But spaces are used when wrapping text, and it looks bad to wrap in the middle of a number:
Disneyland is filled with long lines and admission will cost $1
000.99 for a group of ten people.
Thanks for writing this up! -- Colin 15:59, 24 February 2006 (EST)
It says "all other currencies use the currency code assigned to it" -- does that mean the ISCO country code and not the currency code? I noitced changes being made to the currency on Bombay (Rs to INR?) and Montreal (CDN? -> CAN), is this correct? Majnoona 17:57, 24 February 2006 (EST)
Ordinary travelers tend not to see ISO 4217 codes frequently, but "customary" symbols and abbreviations tend to meet travelers more often. ISO cannot make its own standards mandatory.Jusjih 01:00, 24 February 2011 (EST)
First, I thank the anonymous hard-working person who started this page. Good idea!
Second, I've changed a couple of things. First, I said to use the local symbols, which is what travellers will encounter. All our prices are supposed to be in the local currency (see e.g. Wikitravel:accommodation listings), so the local symbols make the most sense. We've been doing this for most destinations so far, and it's been a recommendation on talk pages and in the pub.
I changed the section about billions to be more succinct.
Lastly, I changed the number format to use commas. --Evan 18:00, 24 February 2006 (EST)
I agree with using the local symbols! Thanks for the clarification... Majnoona 18:02, 24 February 2006 (EST)
Me too. The contributor who started this went and changed all "Rs." in the Bombay page to "INR", which is weird - only currency traders use INR. A normal traveller will see Rs. 100 and the like. --Ravikiran 18:40, 24 February 2006 (EST)
There's the ticket -- the traveller comes first. Whatever the traveller is going to encounter, use that whether it's a standard or not. -- Colin 18:42, 24 February 2006 (EST)
What is the best way to list prices for Hong Kong?
Some parts of the articles use HK $, other just $ (HK being implied).
Or should we be using HKD, HK$ or other variant?
Hkpatv 03:24, 7 Oct 2005 (EDT)
Typically I think just go for "HK is implied". This is what seems to have happened in Australia with the dollar symbol. It will only not make sense in places where you can make transactions in two types of dollar (probably USD and local). This certainly isn't the case in Australia and sounds like it isn't in HK either.
Thanks for the input, that makes sense to me. I will update the curent prices in the HK section if I see any, unless someone tells me not to.Hkpatv 06:06, 24 Oct 2005 (EDT)
That makes the most sense to me. --Evan 09:51, 24 Oct 2005 (EDT)
Suggestion: Make a page for each currency (eg: USD) discussing where people from a country that uses that currency can travel to take advantage of good exchange rates (and where the rates aren't so favorable). For example, i'm American and when i travelled to Budapest and Prague i was amazed at how cheap everything was, leveraging the relative strength of the dollar at the time.
184.108.40.206 13:43, 29 Jan 2006 (EST)
In addition to being very complex (we'd need about 175 pages to cover every currency), this information can be rather volatile. If the Freedonian Libertino were officially devalued to half its previous exchange rate, that'd mean a lot of pages to update with the "Freedonia's a bargain" info... and then to periodically re-edit to correct this as inflation gradually raised prices to their former international value. If a country is chronically inexpensive for foreigners to visit, that's worth noting in the article for that country. But it usually has less to do with the currency exchange rate per se than it does with other factors (e.g. local standard of living, economic development). TVerBeek 19:34, 29 Jan 2006 (EST)
And the US dollar is not exactly strong. When the currency of a country fall, prices do not immediately go up. So for a while it will be cheaper to go to that country for everyone outside the country. So major shifts in exchange rates should be travel news. --elgaard 20:11, 29 Jan 2006 (EST)
Well, for example, the main page right now talks about how Kuala Lumpur has some of the cheapest 5-star accomodations in the world. It makes me wonder what other countries are like that. I guess i could go read every article on this site, but it would be easier if there were a list. 220.127.116.11 01:42, 30 Jan 2006 (EST)
Any objections to this being explicitly mentioned in the guidelines? ~ 18.104.22.168 03:18, 4 January 2007 (EST)
Hmm. I was about to object, but I can't think of any currency where the prefix or abbreviation cannot be placed in front ($1, S$1, €1, ¥1, Rs.1, Rp 1, B1...). But then we should also specify that, if the currency name is used in full, it goes after (1 dollar, 1 euro, 1 yen, 1 baht, 1 rupee, 1 rupiah). Jpatokal 04:04, 4 January 2007 (EST)
Consistency is the hobgoblin of stable currencies
The current guideline says that the local currency should always be used: however, in basketcase countries like Cambodia and Indonesia, any larger transactions (like a hotel room) are invariably priced in dollars. I've thus added an exception to say so. Jpatokal 02:53, 26 March 2007 (EDT)
ViMy brought up on the Copenhagen talk page that the use of DKK was not consistent with wikitravel policies - problem is there is not established national standard abbreviation, but up to 6 different abbreviations used basically everywhere. Online (even on Danish websites written in Danish) DKK, which also happens to be currency code, seems to be the most widely used; The National tourist board uses DKK, so does big attractions like Tivoli and Legoland - even on the Danish version of their websites.
I also checked out some of the other major Scandinavian cities, and in Oslo, Trondheim and Tromsø people have used NOK. In Stockholm, Gothenburg and Malmö they have used SEK. In Reykjavik they have used ISK, and in Tallinn EEK are used. I think that is pretty overwhelming empirical evidence, that this is the form people find most natural when writing. (For those who don't know, all those countries currency are called kroner/kronor). --Stefan (sertmann)Talk 18:34, 15 May 2009 (EDT)
But do prices on the street really use "DKK"? Surely they say "100 kr", no?
Also, people tend to ape existing entries, so if one says "DKK", people will copy it. China was stuck on "RMB" for a long time, but after a Long March of Re-education Through Labor, it's been corrected to ¥ now. Jpatokal 23:48, 15 May 2009 (EDT)
On pricetag in Norway you will see kr used. On websites, aimed at visitor, NOK is often used. ViMy 11:44, 16 May 2009 (EDT)
I'd definitely recommend kr — it's more in line with policy, shorter, and less obtrusive. Similarities with other Scandinavian currencies shouldn't be a concern, since travellers should be able to assume that symbols used for multiple currencies (like $ or £) apply to the local currency. --PeterTalk 20:13, 16 May 2009 (EDT)
As Swedish, Norwegian, Danish and Icelandic kronor are often confused, many visitors even believing they are the same currency, Wikitravel should use the currency codes for these. /Blist 11:31, 23 July 2012 (EDT)
I'd like to raise this question again. Presently, kr vs. NOK seems to vary between every article regarding Norway, at least. Whether to put it before or after the number might even vary within the articles. The most common way of displaying prices in Norway is by far simply "100,-" without any currency sign at all (obviously not a practical solution on Wikitravel). I would consider kr to be at least as commonly seen as NOK, if not more. I propose the format "kr 100" with the currency sign placed before the number to conform with the policy regarding dollars, euros etc. Separated from the number by a space, and no period. Distinguishing the different Scandinavian currencies should be no more complicated than distinguishing the plethora of dollar-denominated currencies (and other currencies that use the $-sign). The currency codes should be used only when a price is quoted in another kroner/kronor-currency than that of the country in question - most relevant for cross border travel. Asitor (talk) 17:25, 8 May 2013 (EDT)
It seems like official policy is to use "baht", but why not ฿? We use € for euros, so I don't see why Thailand should be an exception. ฿ is used everywhere. --globe-trotter 12:55, 9 January 2010 (EST)
It seems reasonable to me. That symbol is listed below, and if they use it in Thailand, it makes sense to use it here.ChubbyWimbus 13:09, 9 January 2010 (EST)
Yes, the symbol is even in the currency list down below. --globe-trotter 15:57, 25 January 2010 (EST)
Actually, ฿ is not very commonly seen in Thailand, the locals use บาท or บ. "Baht" is short, snappy and (unlike "euro") monosyllabic. Jpatokal 00:48, 26 January 2010 (EST)
I think it is very commonly seen, especially in Bangkok and other popular tourist areas. ฿ is the official sign, and it is also a standard character on any Thai keyboard. Obviously in rural areas they use the Thai alphabet more, but most tourists would go to Bangkok and the islands. --globe-trotter
Was there any agreement to this? I see on the project page it still recommends "100 baht in Bangkok" rather than to use "฿100" (or should it be 100฿, with a trailing ฿?) I'm editing the Chiang Mai page now and find that writing baht all the time results in some awkward prose at times. I'd prefer to use ฿. - Cardboardbird 09:31, 7 December 2010 (EST)
I've changed it to ฿. --singaporeAlice 03:04, 15 November 2012 (EST)
Absolutely NOT the case that ฿ is frequently used in Bangkok or Thailand. But if we were to base this decision on usage, we would use "bath", as this misspelling of "baht" is much more frequently seen than "฿". Why not use the universally accepted ISO currency standard for all currencies?seligne 22:18, 18 November 2012 (EST)Seligne
A clear and logical precedent was established with Bali for this and was discussed here. To quote Jani from that discussion "...my rule of thumb is simple: use the prices that the traveller will encounter". The Currency guideline was never changed though, and the matter has come up again with the star nomination of Nusa Lembongan. To me it is very clear. If a booking is made in US$ (for example) and the traveler is charged in US$, then that is the price we should show. I think this reality is much more important than the need for the neat and a tidy state of only one currency used per article. This is a bit different to the exception already given in the article for large amounts in unstable currencies (US$25 is not a large amount, nor is the Rupiah a particularly unstable currency). Any objections to changing the guideline to reflect this exception, which in reality is going to be quite rare? Alternatively, we can just record the exception on this talk page, so that users can be pointed to it when objections are raised to double currency use, as happened with Nusa Lembongan. --Burmesedays 23:15, 12 February 2010 (EST)
India now has a symbol for the Indian rupee along the lines of $, and its usage seems to be increasing at quite a pace. All newspapers use it. Should we start replacing Rs ? Upamanyuwikitravel • ( Talk ) • ( Travel ) • 07:46, 7 December 2010 (EST)
It's been just about 2 and a half years since the post above, and the new symbol has really taken off in India. Most businesses are using it now. The India article can make reference that both symbols are used, but I think it's definitely time we began using ₹. The symbol (₹) has also been available in unicode for years. I'm proposing we modify the quick access template below the editing window with all the currencies, and also actively change mentions of the old "Rs". Wikipedia has done so rather successfully. JamesA>talk 05:39, 29 May 2012 (EDT)
I have already written about it in India's Buy page and have been using it all over the place. Do you know what the special page for the quick access template is? I can change it there. — Ravikiran 00:53, 30 May 2012 (EDT)
Thanks Ravikiran. The page is here. You can go ahead and change the "Rs" over if you think it is necessary. Also, if you do change it, change the Wikitravel:Currency page as it currently mentions "Rs" should be used for Indian rupees. JamesA>talk 04:12, 30 May 2012 (EDT)
I think this is done. Thanks for bringing this up! Ravikiran 22:13, 30 May 2012 (EDT)
It would be great to have a box in the "buy" section of country articles (and regions, ie. Hong Kong, when appropriate) which could have exchange rates that are automatically updated (weekly). I frequently come across old exchange rates on articles and there are many country articles without an exchange rate listed. This would make it very helpful when looking at prices...is 5000 francs in French Polynesia expensive? For a meal yes...for a hotel room its dirt cheap by local standards! But I have to take a minute to calculate it, and I know where to go and how to do it, which many WT readers likely don't. The box could be simple with just the name of the currency & code listed at top and 3-5 exchange rates listed. Since this is the English WT, there should at least be US dollars (USD), Euros (EUR), & GB pounds (GBP) and possibly Canadian, Australian, & NZ dollars as well. The bot could be written based on the 3-letter currency code, so that the currencies listed could be changed to reduce redundancy (ie. 1 USD=1 USD on the US page) or reflect regional currencies which travelers may have or be familiar with (ie. South African rand in southern African, Russian rubles in Central Asia). Examples (would need a better format):
Actually, the big issue is programming and running the bot. =) We've had bots before on which we relied, but they stopped working. I think a single template would be best, as it would avoid having constant updates to every country page on the site. MediaWiki's parser functions should be able to handle the basic math, though we might have to work a bit on rounding (or borrow from Wikipedia). LtPowers 08:49, 16 November 2011 (EST)
Why don't we pull exchange rates we have out into a template anyway. At least then there is only one place to update them. I think we'll encounter other issues when doing this, not least of people wanting their own currency listed, and ending up with hundreds. --Inas 17:20, 16 November 2011 (EST)
We can always (and probably should) establish a list of 7+-2 major currencies that we allow to be listed against the local currency in question. Nobody from Suriname or Laos or Tajikstan should be surprised if we have an establish policy that doesn't include their currency. If they are the type to travel internationally, they are probably already quite familiar with the exchange rate of their currency versus at least one or two of the currencies we do allow...texugo 08:44, 17 November 2011 (EST)
We probably should think this through before we go any further. Picking 9 currencies for each destination? I'd say we limit ourselves to USD and EUR for now, and hope that one day we can pick out the users local currency. --Inas 17:58, 17 November 2011 (EST)
I don't think listing 7 +/- 2 currencies would be a good idea either. The idea I had was to have one template, which would include the US dollar, Euro, & pound, and have a couple additional lines ("currency 4=", "currency 5=") where 1-2 additional currencies could be added when appropriate because they are widely accepted or common in the region and which traveler would have or need to exchange. Examples would be the South African rand, which is commonly used in southern African countries, the Russian ruble in Central Asia, the Australian dollar in the South Pacific, the Swiss Franc in Western Europe, etc. This isn't simply to help travelers from those countries, but even for an American visiting southern Africa, you'll likely become familiar with using the rand and while shopping in Botswana, where many merchants will accept rand, it would be helpful to know the exchange rate between the two when a price is listed as 100 pula, but the shopkeeper says he'll accept 150 rand (the exchange rate is only 1.09 rand=1 pula)...much simpler than trying to convert each to dollars. Hopefully that example is clear. I don't have any programming knowledge, but basically the text of the template that the user would copy onto the page would look like this:
| Currency= Name of country's currency (AAA) (where AAA is the 3-letter currency symbol)
| Currency1=USD (use 3-letter currency symbol, USD should always be listed first except in countries using the US dollar)
| Currency1flag=Image:flag (small flag of country issuing currency 1)
| Currency2=EUR (use 3-letter currency symbol, USD should always be listed after the US dollar, and not listed in countries using the Euro)
| Currency2flag=Image:flag (small flag of country issuing currency 2)
| Currency3=GBP (use 3-letter currency symbol, GBP should always be listed after the Euro, and not listed in countries using the Pound)
| Currency3flag=Image:flag (small flag of country issuing currency 3)
| Currency4= (use 3-letter currency symbol, only list additional currency widely accepted in this country or major regional currency)
| Currency4flag=Image:flag (small flag of country issuing currency 4)
| Currency5= (use 3-letter currency symbol, only list additional currency widely accepted in this country or major regional currency)
| Currency5flag=Image:flag (small flag of country issuing currency 5)
If this were a bot, then it would simply take the currency from the first line (the one for the country of the page it is on) and the other currencies and display the current exchange rate and the date it was last updated. If it was simply a template, then additional lines for each currency would be needed to list exchange rates & url to current rate (like in Tenge example above). Or a better idea might be to just keep things simple and just have the url to the current exchange rate, which users simply click on and go straight to the up-to-the-minute rate. While simple, it wouldn't be useful to travelers who download to use WT offline and might cause problems with mobile versions/apps of WT. The text for a template which includes the rates would look like:
| Currency= Tenge (KZT)
| Currency1=USD (use 3-letter currency symbol, USD should always be listed first except in countries using the US dollar)
If the consensus is for a template and not a bot, then I like the example with just the links, even with its issues. AHeneen 21:20, 17 November 2011 (EST)
Can't see the point in adding multiple links to an exchange rate engine. Just clutter. It is pretty much the exact kind of extlink we've always discouraged, no information, useless offline or printed, etc. --Inas 22:18, 17 November 2011 (EST)
For anyone that is interested, WikiOverland, the encyclopedia of overland travel does real-time currency conversion for prices and units of measure using a custom plugin and rates data from the Open Source Exchange Rates. You can see a great example at Argentina - WikiOverland - just choose your preferred currency and unit of measure and watch it change. It also stores your choice in a cookie so you don't have to choose it again on subsequent pages. Let me know if you have any questions. -Dangrec 01:29, 1 December 2011 (EST)
That's just what I was hoping for! I was worried that all the available exchange rate sites on the internet were commercial and not compatible with WT guidelines. I don't know about using this in-text, as it would be a HUGE task getting this into every price in every page, but I think it would be great to have in a table (like I suggested above) on country pages and top-level pages of territories, dependencies, etc. which use a particular currency (ie. on Saint Helena page, since they use St.Helena pound, Hong Kong, New Caledonia, etc.). I don't know anything about programming, but it would be great if someone could work this into a currency box (as outlined above) which could also be printed (current to time page is printed) or saved for off-line use. AHeneen 10:59, 2 December 2011 (EST)
Is it really what you were looking for? Do you want all prices on a page to be displayed by default in the local currency, and you can change them all to another currency on request? In any event, if you really want that functionality, then we need the mediawiki plugin to do it, so it is a tech request. If we just want the template with a bot update behind it, we can do this without it. --Inas 22:47, 20 December 2011 (EST)
To be clear, the custom plugin used on WikiOverland, the encyclopedia of overland travel uses a cookie to store your currency (and unit of measure) preference. That means when you visit a page, all prices on that page will be displayed in your preferred currency, and you have the option to view them in any other currency if you wish.
Hey W. Frank, thanks for the kind words. I'm currently spearheading a discussion around Wikitravel:Cooperating with Wikioverland so wikitravellers can benifit from the information there. If you'd like to include a comment in the discussion for that page, that would be very helpful.
On a side note, if you know a thing or two about driving across the Sahara, please add it to WikiOverland. African Overland routes are of particular interest to us right now. Thanks! -Dangrec 14:50, 15 November 2012 (EST).
My idea is that we do not need a bot nor we need scraping of any sites. A traveler who reads an article which mentions local currency should have an option such as "show also prices in US dollars/Euros/Pounds/Cambodian reals". When he or she clicks on this option, something like "currency exchange rate is set by bibigonda to 7000 kip to 1 USD at Jan 7, 2015 7:10pm", and any user should be able to change the currency exchange rate; those changes should be global. What can I do to help having it done?--Bibigonda (talk) 22:11, 7 January 2015 (EST)
It seems silly to have to keep updating every price for a country with high inflation, when the equivalent in USD or some other stable currency remains the same. I'm in Sierra Leone, which has by no means runaway inflation, and the prices on Wikitravel are absurdly wrong. Even my 2-yr-old guide book has prices at about $1=3,000 leones, but it's now $1=4,300 leones, so I have to convert everything I read in the guide twice. Might it make more sense to make an decision on the country talk page to use USD when inflation will render our pricing guides wrong within a year? --PeterTalk 14:08, 19 December 2011 (EST)
Bump. FWIW, I've gone ahead and done this where it seemed to make sense. But should we add a note about this in this article? --PeterTalk 18:23, 6 July 2012 (EDT)
I'm having second thoughts about changing baht to ฿ as our standard.
1) Colleagues tell me that ฿ is not very often seen in Thailand - บาท or บ is used instead
2) If it is used, Thai usage is to put ฿ after the amount - not before, as our guidelines dictate
What do folks think, please? --singaporeAlice 00:35, 17 November 2012 (EST)
Here is my two cents: going to the ฿ symbol is easily done, but why? It is not a standard and is little used, even in Thailand. My vote is very simple: use the well-established ISO currency standards for ALL currencies. E.g., THB, GBP, JPY, USD, CAD, etc. Digressio: I think we should use existing ISO standards in all applicable cases: time, distance, volume, etc. In fact most WT guideline do adhere to ISO with some exceptions such as currency. 22.214.171.124 22:13, 18 November 2012 (EST)Seligne
Using three letter symbols was discussed (at length) on this page and the consensus was what is now distilled in the article. It is clear that, if you are limited to a choice of Baht or ฿, you would choose Baht. Should the "b" (for bravo) be capitalised or lower case? --singaporeAlice 00:29, 19 November 2012 (EST)
I went to the websites of the Royal Mint of Thailand; the Bank of Thailand; the Thai Ministry of Finance; McDonalds Thailand; and Honda Thailand, and could not find a single occurrence of the symbol "฿". They use either the ISO formulation, or a hyphen following the price, or "Baht" or "baht" (English) with the former probably predominating, or "บาท". I dislike currency symbols as they can be 1) ambiguous, 2) sometimes do not render properly in print or on screen, 3) little used, and thus of no use to the visitor. If I cannot vote for ISO, I vote for "baht". seligne 01:03, 19 November 2012 (EST)Seligne
After one week with no opposing viewpoints I have made the necessary changes in the article from ฿ back to baht. --singaporeAlice 20:50, 25 November 2012 (EST)
I think that is certainly for the best. I changed "baht" to the proposed "฿" on a page or two and stunned by how much more work it is dealing with special characters. (Admittedly, maybe there is a shortcut I don't know about.)seligne 21:07, 25 November 2012 (EST)
There are many countries around the world that use the name "dollar" and the symbol "$" for their currency. Our usual policy is that Prices should be listed with the currency symbol that travellers will encounter, specifically the local formatting. The currency symbol should always be prefixed. Travellers should be able to assume that symbols used for multiple currencies (like $ or £) apply to the local currency. Do not use currency codes like "USD", "EUR", or "GBP" if the symbol is established.
$100 in Detroit, not US$100, 100 USD or 100 dollars
$100 in Vancouver, not CAD$100, 100 CAD or 100 dollars
$100 in Wellington, not NZD$100, 100 NZD or 100 dollars
$100 in Canberra, not AUD$100, 100 AUD or 100 dollars
and I propose no change in respect of this.
However, the currency of Colombia poses special dangers of inconsistency and confusion as exemplified in our Cartagena (Colombia) article.
Colombia is unusual in having an officially recognised currency symbol of "$" that (unlike Singapore, etc) is not actually used on their banknotes - where, instead, "pesos" is printed. Since prices in the tourist industry in Colombia are also often quoted in US$, I propose that we use "pesos" instead of either the $ symbol or COP for Colombia currency.
This is somewhat analogous to the "Baht or ฿" situation adjudicated above but differs in that I propose using the plural "pesos" rather than "peso" since
the peso is so minute as to be almost never encountered in the singular
Does anyone disagree with my proposal? --singaporeAlice 15:13, 26 November 2012 (EST)
Nobody has raised any objections so I will now make the necessary policy change. --singaporeAlice 18:45, 30 November 2012 (EST)
I think there is a better way to handle the more than 100 different countries that don't have a commonly recognised symbol or abbreviation, Alice. Please see the sub-section immediately below. --W. Franke-mailtalk 19:41, 9 July 2013 (EDT)
There are more than 100 different countries that don't have a commonly recognised symbol or abbreviation and I don't think we should list them all on this page. Instead,my proposal is that the following paragraph is added after the current sentence in the lede of "There are many different currencies in the world. In order to ensure consistency, certain style conventions should be used on Wikitravel.":
"Except for the countries specifically listed below, suffix currency amounts with the three letter ISO 4217 code for the currency in capitals and separate it from the amount by a non-breaking space ( ), to avoid a line wrapping accidentally at the wrong point.
100 AZN in Azerbaijan, not ман 100, AZN100 nor 100 Azerbaijan New Manat"
Good idea, but if you stick the codes immediately AFTER the amount new editors won't be confused by that pesky non-breaking spaceHTML. Waddya think? --126.96.36.199 11:34, 25 July 2013 (EDT)
That's true, but what about putting them BEFORE the amount (but still with no "pesky non-breaking spaceHTML") in a similar way to the way we use the $, € and £ symbols, wouldn't that be even better? --W. Franke-mailtalk 19:53, 11 October 2013 (EDT)