Hello Dyutiman,
Well, there's definitely an XML parser in the picture here, since
something is converting the XML into a in-memory structure that is
being written to the database. But if you're not sure what the
underlying parser is or how to swap it out for a version that doesn't
exhibit those symptoms, that's okay.
How about just taking a look at the first line of text in the XML
report you download and if it's something that you think your program
can't handle, change the text on your end to something that is known
to work?
Cheers,
-Jeff Posnick, AdWords API Team
On May 30, 8:50 am, "Dyutiman Chaudhuri"
<
dyutiman.chaudh...@gmail.com> wrote:
> ok, its not exactly an XML parser, I am running a tool which takes the XML
> file as input, transform its data and put it into database. For those files
> which has written 'encoding="UTF-8"' are working perfectly, other fails.
> May that tool has a problem in parsing XML but we cant change its source
> code. So if I can get all the XML files with 'encoding="UTF-8"' written then
> my problem would be solved.
>
> On Wed, May 28, 2008 at 8:51 PM, AdWords API Advisor <
>