-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solving 10 years of unicode problem? #4563
Comments
I propose using Otherwise, we must conform to the "unicode sandwich" ideology. |
I support There is a backport available here: https://pypi.org/project/pathlib2/ |
Since the default python version for Ubuntu 18.04 is |
How should this be scheduled with PY3 upgrade we believe? |
I believe PY3 upgrade will go smoother if we first move to pathlib. |
@ichorid I have a working Python 3 branch (https://github.com/egbertbouman/tribler/commits/py3tests, ~1400 line changes). We can merge this into devel once v7.3 is out. |
As Egbert has PY3 GUI+core operational, please build Unicode on top of that work once it is merged. |
Investigate possible libraries for universal support of unicode in Tribler. The library should work on all platforms we support (Windows, MacOS and Linux).
Note that there are issues in windows with availability of codecs and encoding. We already remap the codecs to support
'mbcs
andcp65001
. So this should be tested with various encodings to avoid future issues.I suggest creating a utility to encode and decode the python strings (and paths) and using it across Tribler. This utility could depend on some other library but Tribler should not directly depend on the library itself so we can switch the underlying library later if necessary.
Note that UTF-8 character set should be
utf8mb4
where a character is represented by one to four bytes instead ofutf8mb3
which misses some supplementary characters.The text was updated successfully, but these errors were encountered: