My friend it's possible to translate to English, just turn on "subtitles/cc" and "automatically translate" to the specified language.
Yes, I am aware of that but are you aware how terrible auto-translate works (or actually not works
) ?
But it is also a bit besides the point.
I had a look at the framework and I understand the concepts that are used as well as the implementation.
The part were things seem to go wrong is when the framework is applied in practice. Ergo, the end-user who made use of the framework made a mistake somewhere along the line which resulted in that JSON string.
I am unable to replicate that because I am not the person who created the code and I will not be able to make that exact same mistake because I understand how JSON works (famous last words
).
That is why I posted an example using fpjson (which the Horse Framework can use as well) that is able to produce such 'faulty' JSON strings. I did that in the hopes that you perhaps are able to recognize the (faulty) pattern so that you are able to figure out where things go wrong for you.
It is also (still) unclear for me if you are creating the 'faulty' JSON string yourself and if so whether or not that was done locally or if the faulty JSON string is produced by a server (and in case the latter if you coded the server yourself or if you retrieved that faulty JSON string from an external server that is written by someone else)
So, I actually have more questions than I have answers, I am afraid...