@andrew_shadura @kiilerix What is the status of this one?
I'm not entirely sure.
In some areas Mercurial makes naive guess/assumptions of what encoding is used. It might thus be necessary to run Kallithea (and thus hg) in an environment with for example HGENCODING=UTF-8 (or perhaps LANG=UTF-8 ... but that might also have other consequences). I guess it should be tested/reviewed and that code or documentation should be changed.
Thomas De Schampheleire
Some info: I encountered errors when users added unicode characters in changeset/pullrequest comments, pullrequest titles or descriptions, ...
It turned out that this was caused by the PostgreSQL database having encoding SQL_ASCII rather than the recommended UTF-8 (you can check this with 'psql -l')
This in itself was caused by having LC_CTYPE=C set when creating the database initially. Creating the database again (and migrating the existing data) but with LC_CTYPE unset so that the databases are all in UTF-8, made these issues disappear.
For reference, the LANG was always set to en_US.UTF-8 here.
The database encoding might be something that should be mentioned in the documentation?