@tfmorris the escape worked like a charm, THANK YOU!
curl didn’t like the [ and made me face a learning curve that I chose not to follow just yet. wget did give me proper json as a file when I escaped the semicolon.
Your line with curly quotes replaced by straight ones worked straight away. It gave me clean json. Parsing that was no problem.
I looked up the documentation for escape and I have to admit I’d never thought of this being a solution. Learning all the time…
I think it’s a nice use case too, as the built-in reconciliation features don’t let you select partial results by language. That was the reason for trying this.