Paulo, What encoding is your file stored in? My suggestion applies only if it's already in UTF-8 encoding (-d would mangle that but --data-binary or -T would not). I think it's clear that the file is not stored in UTF-8 encoding (I'm guessing iso-8859-1 btw) so you'll need to convert it as dch shows.
B. On 27 April 2012 07:33, Paulo Carvalho <[email protected]> wrote: > Hello > > Thanks for the answers. > > As suggested, I executed the following command: > curl -X PUT -T xpto2.json http://127.0.0.1:5984/mybd/doc_id > > But the result was the same: > {"error":"bad_request","reason":"invalid_json"} > > And in couchDB log: > <<"{\"docs\":[{\"comm\":\"Taille éoyenne pour les structures -- > Échantillons : 116-121\"}]}">>} > > If you have another suggestion, it is very welcome. > > Thank you > > Regards > > > On Thu, Apr 26, 2012 at 8:40 PM, Dave Cottlehuber <[email protected]> wrote: > >> > On Thu, Apr 26, 2012 at 4:37 PM, Paulo Carvalho <[email protected] >> >wrote: >> > >> >> Hello, >> >> >> >> I have a json file, which I think is valid, with the following content: >> >> >> >> {"docs":[{"comm":"Taille éoyenne pour les structures -- Échantillons : >> >> 116-121"}]} >> >> Prior to transferring to couch, can one validate this? >> >> - as utf-8 >> - as json >> >> Given a file utf8wtf.json, how about: >> >> iconv -f UTF-8 utf8wtf.json >> >> or with perl installed I can use this and check json as well: >> >> json_xs -t null -v < utf8wtf.json >> >> Any other ideas that might be more cross platform? >> >> A+ >> Dave >> > > > > -- > Paulo Carvalho > 1 rue du Chateau > 57710 Aumetz > France > http://forum-informatico.forumeiros.com/index.htm > http://ummundoecologico.blogspot.com
