search

gobbledegook / creevey

Phoenix Slides
174 stars 25 forks source link

Bug - Can't open images in subfolders with ä ö ü in folder name since macOS 11 #20

Closed bambi24x closed 8 months ago

bambi24x commented 1 year ago

First of all thank you very much for the best image viewer on Mac!

Since the upgrade from macOS 10 to 11 and to a newer version of Phoenix Slides, the app doesn't open images in subfolders with ä ö ü in the folder name if the directory reaches a certain length. e.g. /Users/mac/files/further ideas/businesscards/products türen/01.jpg

Phoenix Slides is able to open images if there are less subfolders. e.g. /Users/mac/files/fotos/motorräder/cafe racer/01.jpg

Would be great if the app would support directories with more than 300 characters.

Thanks!

gobbledegook commented 8 months ago

Hi, I'm not able to reproduce this. I'm able to navigate to a directory like this with no problem on macOS 14:

/Users/myname/Desktop/files/further ideas/businesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusinesscardsbusi/products türen/01.jpg

yes, that directory in the middle has a name with 251 characters!

Is this issue still happening for you?

gkertai commented 8 months ago

A possible explanation…

There was a bug in the Big Sur 11.7.5 security update (not sure if / when it was fixed), which caused file names with NFC normalization refuse to open. This affected many of my files with accented characters on multiple different volumes.

According to this post HFS+ file names (and presumably APFS too) must be in decomposed form, but apparently macOS was previously more lenient about it.

This was causing me problems across many different applications. I ended up using convmv to fix the file names (available via Homebrew).

gobbledegook commented 8 months ago

That is so delightfully obscure! I feel bad for those affected by this bug, but practically speaking I don't see how I can fix/workaround this without a way to reproduce the issue...

gobbledegook commented 8 months ago

Closing since this has presumably been fixed in a later version of macOS. If people are still running into this problem I will need detailed instructions on how to reproduce this, or somehow get my hands on a configuration that has this issue.