in reply to Re^5: OS X troubleshooting help needed - parse filename & open file
in thread OS X troubleshooting help needed - parse filename & open file

So, you want to distribute your program across multiple platforms but don't care whether it works there or not?

Not quite, I would like it to work everywhere for everyone. But if the user does really unreasonable things and it would take an inordinate amount of effort for me to correct what I consider to be the user's error, well, I leave them with an error message that will hopefully tell them what went wrong. There's also a readme that tells them they shouldn't have done it in the first place. It's not my fault if they didn't read it.

It depends on you whether you want to educate your users about how to properly name their files and directories or whether you want your program to just work with what they throw at it. Precisely, and in some cases, I do choose the first option. As you can see in the other thread, a bunch of monks failed to come up with a solution for the non-ascii problem in a week of brainstorming, so I called it quits. In the time it would take to sort that mess out (if I ever managed to sort it out at all, which is doubtful), I could probably introduce 5 to 10 other meaningful features instead.
As I said, I don't get paid to do this, so I can afford to ignore really egregious fringe cases.