It’s hard to tell because you’ve obfuscated a lot of the path, including text directly around the umlauts.
Perhaps it is the server. I don’t know, but alternatively it might not actually be an umlaut problem, but maybe a problem with backslashes triggering escape characters. Could you try forward slashes as a test?
Or can you anonymize your server path so you can paste the actual contents, so we can search for syntax problems, or attempt to recreate the problem?
[server-folder "testü"; file: "test"](<file:\\vm-shares-001\User\Liebel\testü\test.pdf>) => ==works not==
![[Pasted image 20221102102437.png]]
[same, but with forward-slashes](<file://vm-shares-001/User/Liebel/testü/test.pdf>)=> ==works not==
![[Pasted image 20221102102929.png]]
[same, but with Name in HTML "ü"](<file:\\vm-shares-001\User\Liebel\testü\test.pdf>) => ==works not==
![[Pasted image 20221102103300.png]]
[same, but with Unicode in HTML "ü"](<file:\\vm-shares-001\User\Liebel\testü\test.pdf>) => ==works not==
![[Pasted image 20221102103514.png]]
[server-folder "testü"; file: "testü"](<file:\\vm-shares-001\User\Liebel\testü\testü.pdf>)=> ==works not==
![[Pasted image 20221102102412.png]]
[server-folder "test"; file: "test"](<file:\\vm-shares-001\User\Liebel\test\test.pdf>)=> works
[same, but with forward-slashes](<file://vm-shares-001/User/Liebel/test/test.pdf>)=> works
[server-folder "test"; file: "testü"](<file:\\vm-shares-001\User\Liebel\test\testü.pdf>)=> ==works not==
![[Pasted image 20221102102708.png]]
Can you please explain, what your reply means according to my post?
Do you think it has something to do with how the server interprets my file-link?
If so, wouldn’t that mean, that the used file link (like \vm-shares-001\User\Liebel\testü\testü.pdf) should also not work in any other software? … - I tried that: I inserted that link in MS Word and out of that software it was possible to open that file through that link…
Could you please explain to me, what indicates to you, that I didn’t encode link correctly?