-
Notifications
You must be signed in to change notification settings - Fork 29
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
Problem with encoding and other charsets #140
Comments
Hi Bennet,
|
Sorry I ment to type Windows. The screenshot is from the default file explorer. |
I also ran into the same issue with special chars. I tried opening the tracks on MusicBrainz Picard and the names appeared written correctly in there. After adding a space in front of the name and saving it in Picard it fixed the issue of the names appearing mangled on the files. |
This could be caused by pytaglib using UTF-8 encoding for all tags, while other taggers / viewers might use different settings. Could you try the following: save tags with picard, trying different text encodings (see here for how to set it). Can you reproduce the problem (and/or the correct behavior) with any of those? Alternatively (or in addition), can you figure out the encoding and ID3 version of both the broken and correct files? I am not sure if the first is possible, but e.g. picard shows the ID3 version if you right-click a file and select "Info..". You can also send me one of the files and I'll try to find the time to debug it myself. |
Thanks for the response. The only file type where the problem happens is wav. I tried saving in Picard with all encoding types and both ID3 versions and couldn't reproduce the issue. It always comes out correct. I'm using it here, for reference: |
If I use pytaglib to add a new tag that contains for example an Ä, Ö or Ü it is not saved correct and looks like this:

If I read the tag again with pytaglib the output is correct but Window wont display it porpperly. If I use another program to add the tag I dont have the problem.
The text was updated successfully, but these errors were encountered: