@hhting wrote:
...
If the filename contains non-printable char (ascii < 32), we encode them using unicode. (according to this encoding doc)
...
Hi @hhting,
Since Dropbox API uses JSON encoding (RFC4627), you need to encode all codepoints < 32, as described in documentation:
...
The representation of strings is similar to conventions used in the C
family of programming languages. A string begins and ends with
quotation marks. All Unicode characters may be placed within the
quotation marks except for the characters that must be escaped:
quotation mark, reverse solidus, and the control characters (U+0000
through U+001F).
By the way, in spite supported by API, it's never good idea such chars to be used since may make Dropbox application confusion (and usually do) - as seems Dropbox application coders are newbee. If possible, try avoid them.
@hhting wrote:
...
However, this method is only valid for uploading files, downloading files will result in a malformed path error.
...
Can you give some examples of such calls that are able to upload something, but while you use the same name/path, they cannot get it back? 🤔 What's the exact name?
