Re: char[] indexs jumping..
c00jz3r0@gmail.com wrote:
I'm not assuming that... I know the server is returning me XML...
In which encoding? XML is just a text file. The fact that the content is
XML doesn't say anything about the encoding of the text.
The server is responding me with XML. I'll then have to process that
XML... I'll have to find some API to handle this XML but I dough that
it will be in UNICODE format...
XML does not mandate any particular encoding for the text. The encoding
might be specified in Content-Type: header the server sends with HTTP
response, or it may be specified at the beginning of XML file, as in
<?xml encoding="utf-8" >
Most often, XML files use UTF-8 encoding. Read about it.
I also have a SIP/SDP stack that needs data that is coming in the
server answer...
I have no idea what SIP/SDP means, sorry.
Also... I can't debug any information that is on UNICODE because that
information appears with strange characters on the debugger...
This is most likely due to the fact that you take a non-Unicode data and
place it into wchar_t[] buffer, thus (mis)interpreting it as if it were
Unicode. The debugger assumes that every two bytes form a single Unicode
character, but they don't really, so you end up with garbage.
What can I do? Do you have a suggestion?
I suggest using data types appropriate for data stored in them.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925