Replies: 3 comments 3 replies
-
|
I can see the issue but I'm not entirely sure how to solve it because caesura is technically correct. The file path is retrieved from the tracker API and that includes the mark. It's actually encoded as html entities so it's much clearer: {
"filePath": "The Byrds- Sweetheart Of The Rodeo (1968) Jpn Sony Records Int'l ‎– MHCP 71 {2003} [FLAC]"
}caesura decodes it here: The issue arises because many torrent clients filter out certain invisible marks (see). They do this because they can be used maliciously to disguise file extensions (see). I'm going to convert this to an idea discussion because while it's an issue I suspect it's a fairly rare occurrence and I don't have the bandwidth to address it at present but I would welcome anyone else contributing a solution |
Beta Was this translation helpful? Give feedback.
-
|
Hi, |
Beta Was this translation helpful? Give feedback.
-
|
Fixed in #169 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Caesura expects directory:
the directory in my content folder:
It seems even GitHub doesn't notice these characters:
Never seen this before and wondering if it's more common than I think. Ever encountered this? What's the recommended way to go about fixing? It feels kinda weird to rename the directory to add this random unicode character:
https://unicode-explorer.com/c/200E
Thanks for this amazing software btw.
Beta Was this translation helpful? Give feedback.
All reactions