You guys realize its possible the Company office has not problems handling the characters but still does not want them used because they share data with others. Others who might make dumb decisions like "I can trust the data because its coming from a state agency."
This is the reality of inter-operating with other's systems for those of you have not figured it out yet. Even if your system does everything right, you still get black eye and get blamed as often as not. Maybe your web service returns a nice JSON blob with everything correctly escaped for JSON, maybe you explicitly stated in the documentation, that content is not neutralized for HTML. Guess what when some bank blindly sets the CompanyName string you send to the.innerHTML property of some DOM object they will still call you and complain if something bad happens.
Did not read the TFA (Score:5, Insightful)
You guys realize its possible the Company office has not problems handling the characters but still does not want them used because they share data with others. Others who might make dumb decisions like "I can trust the data because its coming from a state agency."
This is the reality of inter-operating with other's systems for those of you have not figured it out yet. Even if your system does everything right, you still get black eye and get blamed as often as not. Maybe your web service returns a nice JSON blob with everything correctly escaped for JSON, maybe you explicitly stated in the documentation, that content is not neutralized for HTML. Guess what when some bank blindly sets the CompanyName string you send to the .innerHTML property of some DOM object they will still call you and complain if something bad happens.