Thanks Anash. I'm not going to Excel. I'm going download to text file, then SSIS for ETL into SQL db. This still looks like it could potentially be an XML issue (because I get the characters correctly in XML, but not in TSV or CSV).
At this point, there is a decent amount of work required if I were to switch formats. I'd most likely download XML, output textfile, and thus leave the ETL alone, but that seems so roundabout. I'd rather fix the TSV download, if possible. On Monday, September 17, 2012 7:59:26 AM UTC-4, Anash P. Oommen wrote: > > Hi Crosby, > > Pretty much what Zweitze mentioned. AdWords API CSVs are encoded in UTF-8 > without BOM, but excel likes only ascii (if it is csv), or UCS-2 > little-endian (a.k.a. unicode) encoding (if the file is tab separated txt). > The AdWords API .NET client library downloads the data in whatever format > the server gives, but then to make it work with your end client, you > usually have to do some re-encoding. XML is a pretty decent alternative, > but there's the parsing overhead. Plus, XML 1.0 doesn't support ascii > characters 1 to 12, (http://www.w3.org/TR/REC-xml/#charsets), so if > someone puts a non-printable control char in the campaign name, your parser > could potentially choke on that character (System.Xml does, if I remember > correctly). > > Cheers, > Anash P. Oommen, > AdWords API Advisor. > > On Monday, 17 September 2012 13:12:51 UTC+5:30, Zweitze wrote: >> >> The problem with CSV is, that it's a standard that doesn't specify the >> character set. So everybody chooses its own character set. >> (Actually that isn't really the case, the character set just isn't ANSI, >> ASCII, Unicode, UTF-8, UTF-16 or anything of those 'new' sets. It's EBCDIC. >> It's a shame everybody diverges from that standard.) >> >> My suggestion: for any project, avoid CSV. It's not worth the trouble. >> >> >> On Sunday, September 16, 2012 3:14:16 AM UTC+2, Crosby >> (StoneTempleConsulting) wrote: >> >>> bump. Anybody using .NET and CSV or TSV having trouble with unicode >>> handling? >>> (seems to work OK with XML, so I am thinking this is a library issue.) >>> >>> Maybe someone from the .NET team could weigh in? >>> >>> >>> On Sunday, August 19, 2012 8:49:01 AM UTC-4, Crosby >>> (StoneTempleConsulting) wrote: >>>> >>>> following up a bit... >>>> when I download with DownloadFormat as CSV or TSV, i get the same issue. >>>> But when I download as .XML, the characters seem to come down encoded >>>> correctly. >>>> >>>> ... this is looking more like a .net library issue? >>>> FWIW, I'm on v13.3.0 of the .net client library. >>>> >>>> Does anybody know if this issue has been resolved in a more recent >>>> version? >>>> I'd like to upgrade, but haven't work through the migration yet - i've >>>> got a fork where I'm working on it (different issue). >>>> >>>> thanks! >>>> >>>> -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
