You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
docs contain invalid chars
using JS sdk method paperDocsDownload({ doc_id, export_format: 'html' }) and certain character (m-dash, curly quotes) come thru as â. The test document is here: https://paper.dropbox.com/doc/test...
Thanks!
I was able to reproduce the issue. It looks like it is a matter of encoding it properly. You can do so like this:
new Buffer(doc.fileBinary, 'binary').toString()
I'll ask the team to look into whether or not the SDK should/can do that for you though.
Greg-DB
Dropbox Staff
Dropbox StaffThe 'paper2json' GitHub link you shared is a 404 for me. (Perhaps it's not publicly accessible?)
In any case, can you share just the code snippet(s) needed to reproduce the 'â' issue?
When I download the data to an html file using `URL.createObjectURL(response.fileBlob)` the resulting html file shows the correct characters.
In any case, can you share just the code snippet(s) needed to reproduce the 'â' issue?
When I download the data to an html file using `URL.createObjectURL(response.fileBlob)` the resulting html file shows the correct characters.
Greg-DBDropbox Staff
Dropbox StaffThe repo is available now, and it looks like you're running in node and not browser JavaScript like I was testing with. I'll try your code in node. Thanks!
interestingly, I dont see the malformed html when I use the http api via:
curl -X POST https://api.dropboxapi.com/2/paper/docs/download \ --header "Authorization: Bearer xxyyzzzzzz" \ --header "Dropbox-API-Arg: {\"doc_id\": \"S7sSIlM2E0g6p3OXhhts4\",\"export_format\": \"html\"}"- Greg-DB
Thanks!
I was able to reproduce the issue. It looks like it is a matter of encoding it properly. You can do so like this:
new Buffer(doc.fileBinary, 'binary').toString()
I'll ask the team to look into whether or not the SDK should/can do that for you though.
Doh! You're right.
Proper way to do this in Node 6+ is like this:
Buffer.from(doc.fileBinary, 'binary').toString()
But yea, I can't think of a reason why an SDK user would want different behavior from the HTTP API.
Thanks!
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
