fix: use unicode error symbol � instead of failing to import data by spodlesny · Pull Request #2296 · doccano/doccano

Encoding detection is not a silver bullet, and some files can be broken inside, which ends up failing to import the whole batch of files (due to one broken file). For some tasks (sentiment detection), missing character is worth tradeoff. For other use-cases, at least the issue with encoding is presented to user in standardized way and on front-end - without looking into code, like I had to.

Replacement of null character (\x00) for � is required to successfully save data into PostgreSQL.