This may help (caveat - found through search engine, untested): NET Web Services Fail on Unicode Control chars.
This may help (caveat - found through search engine, untested): . NET Web Services Fail on Unicode Control chars Basically it says that the XmlSerializer fails on deserializing Unicode control characters. In the comments, one of the posters links to Hexadecimal value 0x is an invalid character.0x96 isn't listed there, so I'm not sure that this is the same issue.
I was able to work around the error by changing the encoding to iso-8859-1. In my case, that code page included all the characters that my data consumed. I think theoretically it may be possible for the data to contain other characters but this is a suitable work around.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.