<?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: Why does SAS Import Procedure reveal hidden characters? in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/Why-does-SAS-Import-Procedure-reveal-hidden-characters/m-p/202890#M50638</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Export into .csv from Excel and use a hex-capable editor to inspect the data. This might give you a clue what's happening.&lt;/P&gt;&lt;P&gt;Most probably you have a difficulty with UTF vs single-byte representation.&lt;/P&gt;&lt;P&gt;A common single quote (which I would expect to be there) will always translate properly, so I guess someone used an extended character where it is not necessary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Programmer's heaven is a place where English is the only language, and only 96 characters/symbols are needed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Jun 2015 05:35:36 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2015-06-11T05:35:36Z</dc:date>
    <item>
      <title>Why does SAS Import Procedure reveal hidden characters?</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Why-does-SAS-Import-Procedure-reveal-hidden-characters/m-p/202889#M50637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are currently importing Excel 2007 files to SAS using SAS proc import code. We found that SAS detects hidden characters and translates these to a question mark after import. May we know how can we make SAS not detect these hidden characters and import the data as is?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, this field has this value in Excel:&lt;/P&gt;&lt;P&gt;Its not going to happen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When it was converted to SAS, it became:&lt;/P&gt;&lt;P&gt;It?s not going to happen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can we get rid of the question mark? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jun 2015 02:18:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Why-does-SAS-Import-Procedure-reveal-hidden-characters/m-p/202889#M50637</guid>
      <dc:creator>angeliquec</dc:creator>
      <dc:date>2015-06-11T02:18:06Z</dc:date>
    </item>
    <item>
      <title>Re: Why does SAS Import Procedure reveal hidden characters?</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Why-does-SAS-Import-Procedure-reveal-hidden-characters/m-p/202890#M50638</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Export into .csv from Excel and use a hex-capable editor to inspect the data. This might give you a clue what's happening.&lt;/P&gt;&lt;P&gt;Most probably you have a difficulty with UTF vs single-byte representation.&lt;/P&gt;&lt;P&gt;A common single quote (which I would expect to be there) will always translate properly, so I guess someone used an extended character where it is not necessary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Programmer's heaven is a place where English is the only language, and only 96 characters/symbols are needed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jun 2015 05:35:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Why-does-SAS-Import-Procedure-reveal-hidden-characters/m-p/202890#M50638</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2015-06-11T05:35:36Z</dc:date>
    </item>
  </channel>
</rss>

