Sorry, the em dash is 915-199-244, not 915-244-71.

a unicode em dash is unicode 2015 .. I'm not sure how these numbers relate
though....


On Tue, Mar 26, 2013 at 4:08 PM, Rick Root <rick.r...@gmail.com> wrote:

>
> Hi all,
>
> I am getting some data feeds from our SAP system (god help me).  Some of
> the data contains unicode characters apparently like em dashes and such.
>  For example, take the following string:
>
> AMEX – ADR Box
>
> The em dash seems to come through in my text file is 3 characters when I
> view it in notepad++
>
> IF I open the document in Word, it asks me for a character encoding and I
> say UTF 8, and it appears to show the em dash as a single character:
>
> AMEX – ADR (copy paste from word)
>
> However, when the data is loaded into SQL Server, it goes in as three
> characters.  unicode 915-199-71
>
> In fact, it looks like pretty much all of these special characters start
> with unicode 915-199 and then some other character.
>
> SQL Server 2005 does not support UTF-8 apparently.
>
> Has anyone run across this problem and implemented some kind of solution?
>
> My data files are fairly large (1.3GB of data in 26 files), and they are
> loaded every night (full replace)
>
> Rick
>
>
> --
> The beatings will continue until morale improves.
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:355154
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm

Reply via email to