More > JRiver Media Center 30 for Mac

Remaining Problems

<< < (7/11) > >>

bob:

--- Quote from: HaWi on October 14, 2022, 10:09:54 am ---Yes, I am

--- End quote ---
I wouldn't be surprised if that's part of your issue.
I think we are seeing 2 different issues.

Also, on your Samba/NAS filesystem (which is it?)
And what is the filesystem type?

HaWi:

--- Quote from: bob on October 14, 2022, 10:07:37 am ---I think I see what's going on here.

The issue is that apps in MacOS use pre-composed utf-8, basically the kind we'd normally expect.
The limitations of the MacOS hfs+ filesystem requires de-composed utf-8. That convention has been kept for apfs.
The decomposed utf-8 for the ä in Vänskä is 0xc3a4
The pre-composed utf-8 for the same character is 0x61cc88

The only reason you are seeing the lack of umlaut and space added is because you are copy/pasting from the finder which is why the Brian and I haven't been able to reproduce your issue.

Here's some more info (ignore the programming language details)
https://numa.hypotheses.org/66

--- End quote ---
Thanks Bob, that explains a lot. Is there a possible solution to this or anything we can do that would allow us to use diacriticals in MC?
many thanks,
Hans

bob:

--- Quote from: HaWi on October 14, 2022, 10:29:17 am ---Thanks Bob, that explains a lot. Is there a possible solution to this or anything we can do that would allow us to use diacriticals in MC?
many thanks,
Hans

--- End quote ---
I'm looking at the first issue now, handling the decomposed text from the paste of a filename from finder.
App to App diacriticals work fine right now as far as Brian and I've been able to show.

Not sure about non-MacOS filesystems yet.

HaWi:
Thank you so much, Bob for looking into this.

bob:
Got the paste from the clipboard working. It will be in the next build.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version