Web Connection 5.0
Re: JSON Special Characters?
Messages
Reply to this message
Nov. 14, 2012
01:50 pm
3N70TNK75![Show this entire thread in new window]()
01:50 pm
3N70TNK75
| From: | Rick Strahl |
| To: | Todd Landrum |
| WWIPSTUFF.ZIP |
Ok... the issues is that JSON.NET doesn't deserialize characters in the 127-255, which apparently is per spec. Only high characters are to be encoded.
I've fixed this by changing the JSON string encoding routine to NOT encode upper ASCII characters - they're just embedded into the string now.
I've attached the updated wwIpStuff.dll in the attached ZIP file.
+++ Rick ---
Thanks for the speedy work.
I've tested against several different tables and it seems to be pretty solid. I did have some data with chr codes beyond 127. The deserializer turns those into question marks. Will this not support those characters?
(example: Change the name field in your example to chr(150) + chr(146), the n-dash I think and single apostrophe. The returned values for name becomes "??".)
Also, a blank memo field with just a return in it (chr(13) + chr(10)) gets turned into a empty string.
Rick Strahl
West Wind Technologies
Making waves on the Web
West Wind Technologies
from Maui, Hawaii
Making waves on the Web