{"id":6666,"date":"2014-04-20T21:49:32","date_gmt":"2014-04-20T21:49:32","guid":{"rendered":"https:\/\/unknownerror.org\/index.php\/2014\/04\/20\/0128-html-entity-for-euro-currency-symbol-not-visible-in-gmail-collection-of-common-programming-errors\/"},"modified":"2014-04-20T21:49:32","modified_gmt":"2014-04-20T21:49:32","slug":"0128-html-entity-for-euro-currency-symbol-not-visible-in-gmail-collection-of-common-programming-errors","status":"publish","type":"post","link":"https:\/\/unknownerror.org\/index.php\/2014\/04\/20\/0128-html-entity-for-euro-currency-symbol-not-visible-in-gmail-collection-of-common-programming-errors\/","title":{"rendered":"&amp;#0128; HTML entity for Euro currency symbol not visible in GMail-Collection of common programming errors"},"content":{"rendered":"<ul>\n<li><img decoding=\"async\" src=\"http:\/\/www.gravatar.com\/avatar\/4e6875fca5b169e666882616e30bc652?s=32&amp;d=identicon&amp;r=PG\" \/><br \/>\ncrmpicco<\/p>\n<p>I am having an issue with the Euro currency sign HTML entity when viewing in GMail.<\/p>\n<p>I am using <code>\u20ac<\/code> instead of <code>\u20ac<\/code> and this shows as a square box\/bad character in GMail when using Firefox, whereas when I switch it to <code>\u20ac<\/code> it works.<\/p>\n<p>It doesn&#8217;t seem to affect Yahoo! email accounts, only GMail from what I have seen so far.<\/p>\n<p>Some research leads me to believe that <code>\u20ac<\/code> is less widely supported than <code>\u20ac<\/code> and I should switch, however i&#8217;d ike to know which should be used for conformity and support?<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/www.gravatar.com\/avatar\/248875947a0c1d55596daafe060e83ff?s=32&amp;d=identicon&amp;r=PG\" \/><br \/>\ntdammers<\/p>\n<p>It&#8217;s probably a character encoding issue. <code>\u20ac<\/code> simply means character number 128 from the ISO 10646 codepage, which is technically undefined. For historical reasons, most browsers map these characters according to windows-1252, but this is anything but standardized behavior. <code>\u20ac<\/code>, however, unambiguously maps to the euro currency sign, regardless of character encoding. There is a third option: use the unicode code point for the euro sign (<code>\u20ac<\/code>). This, too, should work in any browser. And finally, you can put a literal euro sign into the HTML, but if you do, you need to make sure you set the correct encoding in your content-type headers, so that the receiving user agent can make sense of it.<\/p>\n<\/li>\n<li><img decoding=\"async\" src=\"http:\/\/www.gravatar.com\/avatar\/9870a37447a4ae811096e8e7d10ed3f9?s=32&amp;d=identicon&amp;r=PG\" \/><br \/>\nJoni<\/p>\n<p>The code <code>\u20ac<\/code> corresponds to the ISO-10646 character <code>\\u0080<\/code>, which is a non-printable control character. Despite this fact some browsers may interpret it as the euro character because in one of the text encodings used by Microsoft the byte <code>80h<\/code> is used for euro, but it is not standard.<\/p>\n<p>If you want a portable way to encode the euro sign use <code>\u20ac<\/code>, <code>\u20ac<\/code>, or <code>\u20ac<\/code>.<\/p>\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>crmpicco I am having an issue with the Euro currency sign HTML entity when viewing in GMail. I am using \u20ac instead of \u20ac and this shows as a square box\/bad character in GMail when using Firefox, whereas when I switch it to \u20ac it works. It doesn&#8217;t seem to affect Yahoo! email accounts, only [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-6666","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts\/6666","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/comments?post=6666"}],"version-history":[{"count":0,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts\/6666\/revisions"}],"wp:attachment":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/media?parent=6666"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/categories?post=6666"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/tags?post=6666"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}