Search the Community

Showing results for tags 'utf-8'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 3 results

  1. Hi! Localized strings are returned with wrong escaping in JSON, e.g.: { "message": "Der ausgew\u00c3\u00a4hlte Ordner wurde bereits zu BitTorrent Sync hinzugef\u00c3\u00bcgt.", "result": 200 } These are escaped UTF-8 bytes, which is wrong. Either don't escape at all, as UTF-8 is default for JSON anyways and if you must escape then see 2.5 in RFC 4627. You should also send a charset=utf-8 along with Content-Type. Regards
  2. Hi, maybe I'm using an exotic constellation btsync is running in ubuntu vm, this vm is using files from an old xp vm (on same laptop), filesystem NTFS btsync should sync this data to other ubuntu systems and an raspberry pi Now I noticed that all files using german letters (äöü...) are not synced If I rename one of this file not using german letters file is synced immediately. I read this hint on support page: Ubuntu can use this files and filenames without any problem, why btsync agent can use this file for syncing, running on same ubuntu system? Files with german letters and hosted by an ubuntu system on EXT filesystem, can synced without any problems How can I sync files with german letters from NTFS from my old xp vm? Should I ran btsync agent on xp for this files? Will this help for german letters? If this help, how can I reuse read+write-key on xp system from my ubuntu vm? I can't use xp as another peer, because ubuntu and xp using same directory !!! I don't want to create a new key and delete old peer connections, which will have to resync again all other peers any help is welcome Frank
  3. I am trying to use the API to write a simple CLI. Unfortunately the API escapes unicode characters in a strange way. Example: [ { "dir": "\/home\/scus\/Universit\u00c3\u00a4t", "error": 0, "files": 10813, "indexing": 0, "secret": "--------------------------------", "size": 2211998011, "type": "read_write" } ]I think the solution might be to not escape those characters (complies RFC 4627) and to send an "charset=utf-8" header with the response. Side note, the content-type header should say "application/json". If it is necessary to escape non-ascii characters, the character ä for example should be escaped by "\uc3a4". Regards, scus This bug is mentioned already here: But since this is the "Bug-Forum"...