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
