<?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: Special Symbols in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243942#M6400</link>
    <description>thats really cool. But how is it matched to the dataset and see if any of the characters are present?</description>
    <pubDate>Fri, 15 Jan 2016 21:49:21 GMT</pubDate>
    <dc:creator>SASPhile</dc:creator>
    <dc:date>2016-01-15T21:49:21Z</dc:date>
    <item>
      <title>Special Symbols</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243896#M6395</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp; How would we select all those address fields in dataset that have foriegn symbols (not the regular symbols like @,#,$) some of them like french symbols or german.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2016 19:45:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243896#M6395</guid>
      <dc:creator>SASPhile</dc:creator>
      <dc:date>2016-01-15T19:45:28Z</dc:date>
    </item>
    <item>
      <title>Re: Special Symbols</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243900#M6396</link>
      <description>&lt;P&gt;Can you be more specific, what char are ok, which are not?&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2016 20:07:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243900#M6396</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2016-01-15T20:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: Special Symbols</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243926#M6397</link>
      <description>&lt;P&gt;This is for addresses in the US:&lt;/P&gt;&lt;P&gt;charcters like .,-space&amp;amp; are allowed.&lt;/P&gt;&lt;P&gt;french accents not allowed.&lt;/P&gt;&lt;P&gt;german charcters like ö not allwoed.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2016 21:04:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243926#M6397</guid>
      <dc:creator>SASPhile</dc:creator>
      <dc:date>2016-01-15T21:04:43Z</dc:date>
    </item>
    <item>
      <title>Re: Special Symbols</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243936#M6399</link>
      <description>&lt;P&gt;The easiest way would be to build a TRANSLATE statement in a data step. The fun part is getting the correct codes as your editor font may not match the font you are used to looking at, not to mention potential UNICODE or other encoding issues.&lt;/P&gt;
&lt;P&gt;Something that might look like this:&lt;/P&gt;
&lt;P&gt;&lt;FONT face="SAS Monospace" size="2"&gt;string = translate(string,&lt;/FONT&gt;&lt;FONT color="#800080" face="SAS Monospace" size="2"&gt;'AAAAA'&lt;/FONT&gt;&lt;FONT face="SAS Monospace" size="2"&gt;,&lt;/FONT&gt;&lt;FONT color="#800080" face="SAS Monospace" size="2"&gt;'ÀÁÂÃÄ'&lt;/FONT&gt;&lt;FONT face="SAS Monospace" size="2"&gt;);&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="SAS Monospace" size="2"&gt;You really want to look at the documentation for translate as it is postional replacement and the target and source strings need to match carefully. Plus the order of parameters seems backwards to most people I've discussed this with.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the input data is straight ASCII or EBCDIC then this code will build a set with the value RANK returns for single characters and the ASCII character (defaulting to the viewer font).&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data chars;
   length character $ 1;
   do i= 127 to 255;
      character =collate(i);
      output;
   end;
run; &lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 15 Jan 2016 21:35:17 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243936#M6399</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2016-01-15T21:35:17Z</dc:date>
    </item>
    <item>
      <title>Re: Special Symbols</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243942#M6400</link>
      <description>thats really cool. But how is it matched to the dataset and see if any of the characters are present?</description>
      <pubDate>Fri, 15 Jan 2016 21:49:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243942#M6400</guid>
      <dc:creator>SASPhile</dc:creator>
      <dc:date>2016-01-15T21:49:21Z</dc:date>
    </item>
    <item>
      <title>Re: Special Symbols</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243946#M6401</link>
      <description>&lt;P&gt;The use would be in a very stubby bit of code.&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data want;
   set have;
   addressline1 = translate(addressline1,'&amp;lt;targetstring&amp;gt;','&amp;lt;searchstring&amp;gt;');
run;

&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;The joy of translate is that you already made the decision what would be done when they are encountered so you don't need a message unless you really want one. If were concerned you could start with a base variable and use a recoded value, then compare the two to generate messages about likely issues in the base data.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2016 22:15:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243946#M6401</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2016-01-15T22:15:48Z</dc:date>
    </item>
    <item>
      <title>Re: Special Symbols</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243987#M6402</link>
      <description>Normalisation of US addresses is available within the dataflux data quality product.</description>
      <pubDate>Sat, 16 Jan 2016 07:33:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Special-Symbols/m-p/243987#M6402</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2016-01-16T07:33:11Z</dc:date>
    </item>
  </channel>
</rss>

