Skip to content

Conversation

@xcentaurix
Copy link
Contributor

the old python2 umlaut style produced incorrect encoding when processed by the updateallpo.sh script. the new python3 style works fine.

@Huevos
Copy link
Contributor

Huevos commented Feb 5, 2026

You have non-ascii characters in python and no encoding is declared.

@xcentaurix
Copy link
Contributor Author

which non-ascii chars are you referring to?
i thought in python3 utf-8 is default and doesnt need to be declared.

@Huevos
Copy link
Contributor

Huevos commented Feb 5, 2026

Did it compile?

If you use non-ascii chars you should force the encoding.
# -*- coding: utf-8 -*-

@xcentaurix
Copy link
Contributor Author

i tested it with a test script and it works:
(venv) (chroot) root@dm900:/git$ cat test.py
t = "Tragödie"
print(t)
(venv) (chroot) root@dm900:
/git$ python test.py
Tragödie
(venv) (chroot) root@dm900:~/git$

in python3 you dont need any

-- coding: utf-8 --

btw. german umlauts are ascii-chars as well.

@Huevos
Copy link
Contributor

Huevos commented Feb 6, 2026

No, they are not ascii. Ascii only covers the first 127 chars.

@xcentaurix
Copy link
Contributor Author

anyway, the enigma2 build in the pr checks was fine.

@Huevos Huevos merged commit 9f7ea91 into OpenViX:Developer Feb 6, 2026
1 check passed
@xcentaurix xcentaurix deleted the utf8 branch February 6, 2026 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants