Skip to content
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

Closed
schnillerman opened this issue Apr 28, 2020 · 10 comments
Closed

Special characters (Umlaute) in path names #328

schnillerman opened this issue Apr 28, 2020 · 10 comments

Comments

@schnillerman
Copy link

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:

@michaelherger
Copy link
Member

michaelherger commented Apr 28, 2020

Do you see the same in the Default Skin?

@schnillerman
Copy link
Author

schnillerman commented Apr 28, 2020 via email

@schnillerman
Copy link
Author

schnillerman commented Apr 28, 2020

Do you see the same in the Default Skin?

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!

@michaelherger
Copy link
Member

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?

@michaelherger
Copy link
Member

Ah, und noch was: ist das "nur" ein kosmetisches Problem, oder treten beim Einlesen Probleme auf?

@schnillerman
Copy link
Author

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.

@Moonbase59
Copy link

Moonbase59 commented May 15, 2020

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 Schräg folder seems not to be scanned anymore (not even when trying to do it manually). You can select it from the file/folder view, then Schräg immediately turns to Schräg. I cannot make out why, but it mostly doesn’t get scanned (very few times, every few months, it seems to do it).

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.

@mherger
Copy link
Contributor

mherger commented Apr 26, 2022

@Moonbase59 so you're saying this issue isn't purely cosmetic, but scans actually fail if a path has an umlaut in it?

@mw9
Copy link
Contributor

mw9 commented May 27, 2022

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.

@mherger
Copy link
Contributor

mherger commented May 29, 2022

Thanks! I'll consider this fixed.

@mherger mherger closed this as completed May 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants