Gson supports consuming of field names without quotes or with single
quotes. We also allow the same input to mix it up with some field
names with double quotes, some with single quotes, or some with no
quotes at all.
However, we always produce valid JSON with double quotes around field
names. there is currently no option to change that behavior.
Can you file a bug on the other library to start accepting valid JSON
too, or is that not an option?
In your first example, I note that you are missing "," to separate out
the array entries. Could that be the cause of problem?
Inder
> This would not be valid json according to the spechttp://
json.org/.