Hello Damon,
Thanks for the detailed description.
Based on my understanding, now the XML gateway sends and receiveds the data
by usign GSM encoding. So the '' is '$' after the encoding. Please post
here if I have misunderstood anything.
If the GSM character set doesn't inlcude '$', I think we need to transfer
it manually. That is to say, we need to create a customized class to encode
the xml string before transferring it to GSM gateway. Then decoding work
should also be done by ourselves.
We are not sure of if there is any setting in GSM gateway side to avoid it.
You need to post in their group for more information. It is very possible
that they have existing encoding class already.
Hope that helps.
Best regards,
Yanhong Huang
Microsoft Online Partner Support
Get Secure! -
www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
!From: "Damon" <
[email protected]>
!References: <
[email protected]>
<
[email protected]>
!Subject: Re: XML seralization & hexadecimal values
!Date: Wed, 1 Oct 2003 10:46:39 +1200
!Lines: 73
!X-Priority: 3
!X-MSMail-Priority: Normal
!X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
!X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
!Message-ID: <
[email protected]>
!Newsgroups: microsoft.public.dotnet.languages.csharp
!NNTP-Posting-Host: ip-218-101-56-3.adsl.concept.net.nz 218.101.56.3
!Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
!Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.languages.csharp:188273
!X-Tomcat-NG: microsoft.public.dotnet.languages.csharp
!
!I've found out the reason why these hexadecimal values are coming up in the
!XML request. It is because the request is GSM encoded as its an XML gateway
!for sending and receiving SMS messages.
!
!This means that letters such as a-z come through fine but characters such
as
!$ which is 2 in the GSM character set throws the below error.
!
!What I'm not sure on is how to do the conversion to and from GSM. I'm
!getting the response back from the other server using a StreamReader which
!defaults to UTF8 encoding.
!
!In order to do this conversion will I need to create my own encoding object
!and then change the encoding type on the StreamReader to be something like
!GSMEncoding or is there another way?
!
!Cheers
!
!Damon
!
!!>
!> Hi Damon,
!>
!> How does your xml file serialized?
!> Is it also serialized by this 3rd part component?
!> If it is, why it can not deserialize, I think it may be the problem of
the
!> 3rd part component.
!>
!> As a workaround, may be you can use IO operation to open this xml
!> file and get all the content, then delete the '' characters store it as
a
!> new xml file.
!>
!> You can try to deserialize this new file to see if it works.
!>
!> Hope this helps,
!> Best regards,
!> Jeffrey Tan
!> Microsoft Online Partner Support
!> Get Secure! -
www.microsoft.com/security
!> This posting is provided "as is" with no warranties and confers no
rights.
!>
!> --------------------
!> | From: "Damon" <
[email protected]>
!> | Subject: XML seralization & hexadecimal values
!> | Date: Fri, 26 Sep 2003 13:13:01 +1200
!> | Lines: 9
!> | X-Priority: 3
!> | X-MSMail-Priority: Normal
!> | X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
!> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
!> | Message-ID: <
[email protected]>
!> | Newsgroups: microsoft.public.dotnet.languages.csharp
!> | NNTP-Posting-Host: pop11-port30.jetstart.maxnet.co.nz 202.89.56.30
!> | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
!> | Xref: cpmsftngxa06.phx.gbl
!microsoft.public.dotnet.languages.csharp:187448
!> | X-Tomcat-NG: microsoft.public.dotnet.languages.csharp
!> |
!> | I'm getting '', hexadecimal value 0x02, is an invalid character when
!I'm
!> | deseralizing XML from a 3rd party XML gateway. How do I get rid of
these
!> | hexadecimal values before I deserialize?
!> |
!> | Cheers
!> |
!> | Damon
!> |
!> |
!> |
!>
!
!
!
