# How should currency symbols be written? [duplicate]

I've recently posted an answer with prices in Euros, which was promptly edited to include the official euro symbol. So what is the official policy on currency signs?

1. Use the Unicode currency symbol, such as $? 2. Use the ISO 4217 code, such as USD? 3. Use the English-language name, such as dollar? 4. Use whatever symbol is most convenient to the person writing the question? • I can’t say for the other editor, but my main objective was to turn ‘5 EUR’ into something that doesn’t include figure in plain text, unit in monospace. Since that would have been a very minor thing, I figured it be a good idea to include the euro symbol, too. – Jan Jun 14 '16 at 16:37 • Use kanji for extra LOLs: 円. Jun 18 '16 at 9:35 • Please do not use "code" markup for things that aren't computer code. It looks ugly and interacts badly with screen readers, which makes posts inaccessible to the visually impaired. Jun 19 '16 at 7:51 • @DavidRicherby I've tried using the Windows on screen reader and it works fine for code formatting – JonathanReez Mod Jun 19 '16 at 9:31 • @DavidRicherby In what way specifically does the <code> tag interact badly with screen readers? And which screen readers? My understanding was that screen readers don't do anything special with inline non-link HTML tags like this one - they just keep reading? Jun 20 '16 at 11:51 • Hmm. Well, people always used to say it worked badly. Maybe it doesn't any more and I should stop using that alleged reason. But, man, it looks ugly. Jun 20 '16 at 12:00 • @DavidRicherby could you be thinking of when people use <pre> code blocks to approximate things like data tables, like meta.travel.stackexchange.com/questions/3733/… ? Those clearly might be confusing to someone on a screenreader (unfortunately there's not much better available unless real tables are allowed) Jun 20 '16 at 17:14 ## 2 Answers The problem with using the symbols is that they can be a bit hard (read annoying) to find. My standard North American keyboard comes with$ by default and I don't know where to find Euro, Yen and others without looking them up and copy-pasting: too much work.

Using simple English descriptors is vague, dollar: American ? Canadian ? Australian ? New Zealand ? Peso: Mexican ? Argentinian ? Cuban ? Chilean ?

Writing the ISO codes on the other hand is faster and more legible (in my opinion), and I think a lot of us already know a lot of them by heart from doing basic conversions (I'm guessing ?). And as you mentioned, they're easy to copy paste into search engines (or even spotlight on OSX) to get conversions.

I'm not one for strict rules or even saying we all "should" do something, this is merely my preference and just a suggestion

• I do not know any Unicode codes by heart, but I know where the "MS character map" is.. Jun 14 '16 at 16:30
• From what I found the currency symbol for most localizations is Shift+4 will give the localization based symbol. For Euro zone it would be €, UK £, and so on. Jun 19 '16 at 13:31
• I use Linux, which makes typing symbols like ¥ € £ fairly easy, with the compose key. Jun 20 '16 at 19:00
• £, $, and € are all easily available on my Irish keyboard. So is ¥, but it's not actually printed on the keyboard, so I have to know that key combination (actually, I just guessed it, and it worked). – TRiG Jun 21 '16 at 16:25 This question asks for a multi-part answer: When writing, when editing and the general typesetting. # When writing When writing a post you should use whichever format is clear enough and easy enough for you to write. That may (or may not) include the currency symbol if it is present on your keyboard or you know how to generate it. That may include three letter codes such as EUR. That may include plain text forms such as US dollars. All of these should be equally valid in my opinion. Eur is a non-standard format (as are EURO and others), and should thus not be used. Ideally, your post should look typographically ‘clean’; however, less ‘clean’ posts should not prevent people from upvoting (and vice-versa). # When editing An edit should typically include more than simply changing one variant to another variant. I admit I am guilty of suggesting a too minor edit here (which was rejected). However, the second edit was equally minor and should have been rejected, too. (Note that the second edit introduced the format symbol-value which, at least for Germany, is less common than value-symbol. Unfortunately I could not find definite sources which types are common/preferred in Germany, let alone in Austria and Slovakia.) When changing other things within the text, performing a clean-up to adhere to typographic ideals can be warranted, as it is for capitalisation (e.g. I). # From a typesetting perspective From a typesetting point of view, I would definitely prefer the corresponding currency symbols as long as it is clear which currency is meant. Using € for Euro is unambiguous. Using$ is generally ambiguous, it could be Australian, US, Canada, New Zealand, Fiji … However, if the post is clearly about getting from (say) Atlanta, Georgia to Washington DC, then it is unambiguous enough that US-dollars are meant.

Using three-letter codes can be preferable in ambiguous cases, such as when going from the US to Canada. Using the written words should be restricted to cases where the number is also written out (‘a dollar or two’).

Whichever format[1] you use for writing the unit, the same format should be used for the number. This makes things that belong together look like they belong together. Examples:

EUR 45

EUR 45

EUR 45

EUR 45

€45

€45

€45

45

It is usually preferable to use simple plain text rather than code markup, since code markup disrupts one’s flow of reading. However, that effect may be desired in given circumstances — if it is used, both number and unit should be formatted using monospace.

In English texts,[2] the three-letter code should preceed the currency value as should the currency symbol. The three-letter code should be separated by a no-break space, which can be either directly entered or entered as &nbsp;. (A normal space often does no harm but can cause line breaks between currency and value which should be avoided.) According to typical English language style guides, the currency symbol should not be separated by a space.[3] Examples:

EUR 45

€45

In most other European languages, the currency typically follows the value. For example, the following variants are preferred in German:[4]

45 EUR

45 €

From a typesetting perspective, both styles are in-line with at least one standard. As long as there is no mixing between the two styles, an edit to convert the continental one into the English one should be avoided. Again, when editing anyway, there is no harm done in harmonising to the English standard.

Notes:

[1]: Format here is taken to mean plain text, monospace, MathJax, etc. (although the latter is not active on travel.SE).

[2]: And Irish, Latvian and Maltese, among the languages of the EU. Probably in many other languages outside Europe, too.

[3]: Compare the style guide of the European Union, English version.

[4]: Compare the style guide of the European Union, German version.

• The usual format for euro in English is, in my experience, without a space: €45 Jun 15 '16 at 13:22
• You should never use code-tags to denote anything else then actual computer code. Its semantic markup it gets marked up as code, and is not for monospace text / styling! See discussions on meta.SO and Meta.SE about this. Jun 20 '16 at 8:21