Open equivalentideas opened 9 years ago
An underlying reason for the confusion is the difference in the way that encoding is handled in the console output versus the data in the database. It might be worth revisiting that.
The console just forces the encoding to be utf8, I think, and hopes for the best.
Reading data from the database I think is handled slightly differently. I think it tries to convert it to utf8 and then removes anything it can't leading to different behaviour.
I might be slightly wrong on the details (I haven't checked the code) but the main point is there are differences and that can make it confusing for the user.
See discussion at https://help.morph.io/t/nepali-text-not-being-saved/82/2 and the scraper https://morph.io/tmtmtmtm/nepal-ca-members .
When the SQLite DB is downloaded, the characters are there, but in the table display on the scraper page, and in the csv and json formats, they are not rendered.
Data table on morph.io
SQLite DB downloaded