| Summary: | Files on the playlist with unusual characters are not recognized again after being temporarily unavailable | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Frank Schaefer <fschaefer.oss> |
| Component: | Playlist | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | tuomas |
| Priority: | NOR | ||
| Version First Reported In: | 2.9.71 | ||
| Target Milestone: | kf5 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/multimedia/amarok/-/commit/1255e9a6297a6916343a9dc94459e1e8c3a43e63 | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
|
Description
Frank Schaefer
2021-04-15 16:10:52 UTC
Are you talking about special characters in ID3 tags or actual characters in file names? You do know that these characters have never been supported in file names on computers, don't you? Is the track in the collection and is the collection set to be checked automatically? (In reply to Myriam Schweingruber from comment #1) > Are you talking about special characters in ID3 tags or actual characters in > file names? File names. I've verified that ID tags don't matter. > You do know that these characters have never been supported in > file names on computers, don't you? Almost all file systems support unicode these days and it is working fine (except this issue). Please note that the filename is recognized correctly when adding the file to the playlist and also on all further Amarok exit/restart cycles. I also tried with files on ext4 and NTFS partitions and that makes no difference. So I'm pretty sure a file system or mount parameter issue can be ruled out. > Is the track in the collection and is the collection set to be checked > automatically? That doesn't matter. Bug occurs in any of these cases. Tested on Amarok 3.0.1, Debian Bullseye (LANG=fi_FI.UTF-8): Added an album in collection with 3 tracks to playlist: Track01öä.ogg, Track02.ogg, and Track03.ogg. Visible normally. Exited Amarok Moved the directory containing the three tracks. Started Amarok. The tracks are greyed. Exited Amarok. Moved the directory back. Started Amarok. The tracks are recognized correctly. However, if I add Track01öä.ogg to playlist when it does not reside in a collection path and repeat the steps, it stays greyed out and it's path contains garbled characters. A possibly relevant merge request was started @ https://invent.kde.org/multimedia/amarok/-/merge_requests/108 Git commit 1255e9a6297a6916343a9dc94459e1e8c3a43e63 by Tuomas Nurmi. Committed on 29/06/2024 at 17:55. Pushed by nurmi into branch 'master'. Load paths from XSPF playlists as UTF-8 The saving code writes them in UTF-8 and the xml header generated states that the encoding is UTF-8, so they should be definitely also read as UTF-8. M +1 -0 ChangeLog M +1 -1 src/core-impl/playlists/types/file/xspf/XSPFPlaylist.cpp https://invent.kde.org/multimedia/amarok/-/commit/1255e9a6297a6916343a9dc94459e1e8c3a43e63 |