[GH-ISSUE #646] Russian encoding in songs metadata #460

Closed
opened 2026-02-26 02:33:17 +03:00 by kerem · 3 comments
Owner

Originally created by @T-REX-XP on GitHub (Aug 29, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/646

I have problem with russian language in music metadata. Using latest version but in docker container https://github.com/binhex/arch-koel. Insted song name a get ???? symbols ((

Originally created by @T-REX-XP on GitHub (Aug 29, 2017). Original GitHub issue: https://github.com/koel/koel/issues/646 I have problem with russian language in music metadata. Using latest version but in docker container [https://github.com/binhex/arch-koel](https://github.com/binhex/arch-koel). Insted song name a get ???? symbols ((
kerem closed this issue 2026-02-26 02:33:17 +03:00
Author
Owner

@gamerlv commented on GitHub (Aug 29, 2017):

I tried to replicate your issues using the indicated docker container. I tested using the one from dockerhub, russian symbols got imported as one would expect. Both filenames as metadata appeared in russian symbols.
It does appears that the container on docker hub is over 4 months old and thus is missing some recent changes.

In order to help you better could you provide some additional information?

Did you run the container from docker hub or build it yourself from the github repo?
I'm wonder if your database is correctly UTF-8. The following command shows what character set your DB is using;

docker exec <container name> mysql koel -e "SELECT default_character_set_name FROM information_schema.SCHEMATA WHERE schema_name = 'koel'"

Lastly a sample of filenames / metadata which fail to import/display would be useful.

<!-- gh-comment-id:325711474 --> @gamerlv commented on GitHub (Aug 29, 2017): I tried to replicate your issues using the indicated docker container. I tested using the one from dockerhub, russian symbols got imported as one would expect. Both filenames as metadata appeared in russian symbols. It does appears that the container on docker hub is over 4 months old and thus is missing some recent changes. In order to help you better could you provide some additional information? Did you run the container from docker hub or build it yourself from the github repo? I'm wonder if your database is correctly UTF-8. The following command shows what character set your DB is using; ```bash docker exec <container name> mysql koel -e "SELECT default_character_set_name FROM information_schema.SCHEMATA WHERE schema_name = 'koel'" ``` Lastly a sample of filenames / metadata which fail to import/display would be useful.
Author
Owner

@T-REX-XP commented on GitHub (Aug 29, 2017):

this is my output

sudo docker exec koel mysql koel -e "SELECT default_character_set_name FROM information_schema.SCHEMATA WHERE schema_name = 'koel'"

default_character_set_name
utf8

koel image
2017-08-29 23 58 06

<!-- gh-comment-id:325805587 --> @T-REX-XP commented on GitHub (Aug 29, 2017): this is my output > sudo docker exec koel mysql koel -e "SELECT default_character_set_name FROM information_schema.SCHEMATA WHERE schema_name = 'koel'" ``` default_character_set_name utf8 ``` koel image <img width="671" alt="2017-08-29 23 58 06" src="https://user-images.githubusercontent.com/4560084/29844138-f472ce1a-8d16-11e7-9e6c-c7d8f71251ca.png">
Author
Owner

@ghost commented on GitHub (Jan 11, 2018):

I can tell you with 99% probability your id3 tags are encoded in CP1251, convert them into UTF-8

<!-- gh-comment-id:356815868 --> @ghost commented on GitHub (Jan 11, 2018): I can tell you with 99% probability your id3 tags are encoded in CP1251, convert them into UTF-8
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#460
No description provided.