<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Pound sign as Â£ in Everything else</title>
    <link>https://community.plus.net/t5/Everything-else/Pound-sign-as-%C3%82/m-p/1430412#M17414</link>
    <description>&lt;P&gt;I have seen this happen to a number of websites I have worked on in the past and this generally occurs on pages where text has been copied directly from an MS Word document. Characters that are affected can be dashes, apostrophes, ampersands and currency (amongst many many others). Changing the meta to UTF-8 fixes them in most cases but not always. I personally character encode all special characters with the proper HTML references as working on ISO entity sets was the norm until about 7 years ago. This wikipedia article is probably the most visited of my bookmarks:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references" target="_blank"&gt;https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 10 Apr 2017 14:57:39 GMT</pubDate>
    <dc:creator>jaread83</dc:creator>
    <dc:date>2017-04-10T14:57:39Z</dc:date>
    <item>
      <title>Pound sign as Â£</title>
      <link>https://community.plus.net/t5/Everything-else/Pound-sign-as-%C3%82/m-p/1430409#M17413</link>
      <description>&lt;P&gt;In case anyone else experiences the same problem…&lt;/P&gt;
&lt;P&gt;I have an HTML file on Hostopia that is displayed in an &amp;lt;iframe&amp;gt; on a ‘home pages’ server page.&lt;/P&gt;
&lt;P&gt;From last week (3&lt;SUP&gt;rd&lt;/SUP&gt; Apr onwards) sometime, the £ currency sign has been displaying as Â£. All other special characters seem OK&lt;/P&gt;
&lt;P&gt;I assume this is a change (the PHP version change?) within Hostopia.&lt;/P&gt;
&lt;P&gt;The problem is fixable by prefixing the HTML by &amp;lt;meta charset="UTF-8"&amp;gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2017 14:44:30 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Pound-sign-as-%C3%82/m-p/1430409#M17413</guid>
      <dc:creator>decomplexity</dc:creator>
      <dc:date>2017-04-10T14:44:30Z</dc:date>
    </item>
    <item>
      <title>Re: Pound sign as Â£</title>
      <link>https://community.plus.net/t5/Everything-else/Pound-sign-as-%C3%82/m-p/1430412#M17414</link>
      <description>&lt;P&gt;I have seen this happen to a number of websites I have worked on in the past and this generally occurs on pages where text has been copied directly from an MS Word document. Characters that are affected can be dashes, apostrophes, ampersands and currency (amongst many many others). Changing the meta to UTF-8 fixes them in most cases but not always. I personally character encode all special characters with the proper HTML references as working on ISO entity sets was the norm until about 7 years ago. This wikipedia article is probably the most visited of my bookmarks:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references" target="_blank"&gt;https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2017 14:57:39 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Pound-sign-as-%C3%82/m-p/1430412#M17414</guid>
      <dc:creator>jaread83</dc:creator>
      <dc:date>2017-04-10T14:57:39Z</dc:date>
    </item>
    <item>
      <title>Re: Pound sign as Â£</title>
      <link>https://community.plus.net/t5/Everything-else/Pound-sign-as-%C3%82/m-p/1430489#M17415</link>
      <description>&lt;P&gt;Have you escaped the character. The html should read &lt;EM&gt;&lt;STRONG&gt;&amp;amp;pound;&lt;/STRONG&gt;&lt;/EM&gt; rather than just have a pound sign character in the document. That way the browser will sort it out for you.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2017 18:43:49 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Pound-sign-as-%C3%82/m-p/1430489#M17415</guid>
      <dc:creator>mikelahey</dc:creator>
      <dc:date>2017-04-10T18:43:49Z</dc:date>
    </item>
    <item>
      <title>Re: Pound sign as Â£</title>
      <link>https://community.plus.net/t5/Everything-else/Pound-sign-as-%C3%82/m-p/1430492#M17416</link>
      <description>&lt;P&gt;If the HTML page were&amp;nbsp;inline code then I would certainly have used &lt;STRONG&gt;&lt;EM&gt;&amp;amp;pound;&amp;nbsp;&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;But the page content is generated by the end-user, with PHP inserting some &amp;lt;div&amp;gt;s and appending an HTML prefix and suffix around whatever the user types in. In days gone by, PHP then FTPd this page to 'home pages' where it was displayed &amp;nbsp;within a container page via SSI. The move to Hostopia put paid to progammatic outbound FTPs, hence the use of an &amp;lt;iframe&amp;gt;.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And to&amp;nbsp;&lt;SPAN class="login-bold"&gt;&lt;A id="link_12" class="lia-link-navigation lia-page-link lia-user-name-link" href="https://community.plus.net/t5/user/viewprofilepage/user-id/4" target="_self"&gt;jaread83&lt;/A&gt;&amp;nbsp;reply, I have always found that charset list particularly memorable because amid the arcane mathematical symbols and Greek characters &amp;nbsp;there is a hearts, spades, diamonds and clubs!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2017 19:02:15 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Pound-sign-as-%C3%82/m-p/1430492#M17416</guid>
      <dc:creator>decomplexity</dc:creator>
      <dc:date>2017-04-10T19:02:15Z</dc:date>
    </item>
    <item>
      <title>Re: Pound sign as Â£</title>
      <link>https://community.plus.net/t5/Everything-else/Pound-sign-as-%C3%82/m-p/1430807#M17427</link>
      <description>Have you tried passing the user input string through the htmlentites() function in PHP. This will replace the characters in the string with the escaped equivalent. So &amp;amp; becomes &amp;amp;amp; &lt;BR /&gt;&lt;BR /&gt;See: &lt;A href="http://php.net/manual/en/function.htmlentities.php" target="_blank"&gt;http://php.net/manual/en/function.htmlentities.php&lt;/A&gt;</description>
      <pubDate>Tue, 11 Apr 2017 16:40:19 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Pound-sign-as-%C3%82/m-p/1430807#M17427</guid>
      <dc:creator>mikelahey</dc:creator>
      <dc:date>2017-04-11T16:40:19Z</dc:date>
    </item>
    <item>
      <title>Re: Pound sign as Â£</title>
      <link>https://community.plus.net/t5/Everything-else/Pound-sign-as-%C3%82/m-p/1433061#M17479</link>
      <description>&lt;P&gt;Yes Mike - thanks.&lt;/P&gt;
&lt;P&gt;Later-developed pages do indeed use&amp;nbsp;&lt;SPAN&gt;htmlentities() &amp;nbsp;- and its inverse html_entitity_decode() when displaying the text for updating.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;And lest anyone else has encountered the issue with PHP upgrade, it is not confined to &amp;lt;iframes&amp;gt;, but my workaround (in the original post) won't work for SSI-included text, because prefixing the SSI text by &amp;lt;meta charset="UTF-8"&amp;gt; is ignored, presumably because &amp;lt;meta&amp;gt; tags must be in &amp;lt;head&amp;gt; ... &amp;lt;/head&amp;gt; and the SSI includes are in &amp;lt;body&amp;gt;...&amp;lt;/body&amp;gt;. I just changed the charset of the SSI-including page to UTF-8 instead!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Apr 2017 14:29:44 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Pound-sign-as-%C3%82/m-p/1433061#M17479</guid>
      <dc:creator>decomplexity</dc:creator>
      <dc:date>2017-04-19T14:29:44Z</dc:date>
    </item>
  </channel>
</rss>

