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
Special characters (Umlaute) in path names #328
Comments
Do you see the same in the Default Skin? |
Puh - gute Frage. Ich stelle mal kurz um.
Am Di., 28. Apr. 2020 um 13:29 Uhr schrieb michaelherger <
notifications@github.com>:
… Wie sieht das im Default Skin aus?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#328 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEDUA6KAI2LNF3VWZN3VJ3TRO242BANCNFSM4MSUYU6Q>
.
|
In short: Yes. Longer: ... trifft sowohl fürs Nightly der 7.9.2 als auch fürs Nightly der 8.x Version zu. Danke für die schnelle Antwort! |
Ist das ein Netzwerk-Share? Welches Betriebsystem läuft auf dem Rechner? Über welches Protokoll ist das Laufwerk angebunden? Welches OS läuft auf dem Server/NAS? |
Ah, und noch was: ist das "nur" ein kosmetisches Problem, oder treten beim Einlesen Probleme auf? |
Das ist ein Netzwerk-Share auf einer Synology DiskStation (Linux-basiert), eingebunden auf dem LMS Server (bunsenlabs Linux, Debian-Derivat) per CIFS. Das ganze scheint nur ein kosmetisches Problem zu sein, da alles soweit funktioniert. |
Same here, on Ubuntu Studio 14.04.6, using local ext4-formatted disc and ~150,000 music files on LMS 7.9.2 - 1578996832. Purely cosmetic (logs, scan progress), otherwise these play fine and tags are shown correctly on all devices. I use very long and foreign file names (English, German, Danish, Russian, Chinese, Japanese). These are all encoded as UTF-8 (as is my system locale). Only problem here: My two "main" folders to scan are ~/Musik/Tagged
~/Musik/Schräg and the The only other (very minor) problem is when using http[s] links into my system (for Home Assistant alerts, mainly): LMS’ "direct URL" and Home Assistant’s URIs seem to use URLEncode which of course don’t map correctly to UTF-8 file names via GET or the like. |
@Moonbase59 so you're saying this issue isn't purely cosmetic, but scans actually fail if a path has an umlaut in it? |
The display issue looks to have been addressed in LMS 8.3 via PR #678, Fix scan progress reporting - 'raw' path names need to be decoded. |
Thanks! I'll consider this fixed. |
I know it may not be best practice, but: If there are Umlaute in path names, they are displayed correctly in one place and scrambled in another:
The text was updated successfully, but these errors were encountered: