-
-
Notifications
You must be signed in to change notification settings - Fork 958
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
Failure while executing task: UnicodeEncodeError: 'utf-8' codec can't encode characters in position 0-1: surrogates not allowed #5041
Comments
Normalizing the properties files so that it doesn't use surrogates should help. But still this should be handled more gracefully. Can you try it with debug enabled in Weblate, so that the log contains traceback as well? |
Hi! I didn't plan to use surrogates in properties, I think this is an a mistake or some conversion error. Weblate setupWEBLATE_DEBUG=1 How I can set logging to be more verbose? |
That should be good enough .... and it's in the log, sorry for not seeing it there:
Not sure if Weblate should try to normalize these or fail on parsing, but it should fail on parsing the file, not when saving it to the database. See also psycopg/psycopg2#586 |
As a note: previously, in Weblate version 2.17 this file was imported without any errors. |
This has been changed in Python 3, see above referenced psycopg issue... |
Look at actual class instead of querying the class attributes. Issue WeblateOrg#5041
This will be needed for future fixups. Issue WeblateOrg#5041
Look at actual class instead of querying the class attributes. Issue #5041
This will be needed for future fixups. Issue #5041
Thank you for your report, the issue you have reported has just been fixed.
|
Hello!
When I trying to add new component to my project, I got an error:
(complete log attached to the issue - creationError.log)
I tried changing file_format atttribute to 'properties-utf8' or just 'properties' but it didn't help a bit. Source language is russian, format - java properties.
Weblate version is 4.3.2.
How I can workaround this error?
Thanks!
The text was updated successfully, but these errors were encountered: