ltlevine wrote:Sure - but all of that is in service of having experienced software not doing a good job of managing the characters. My view is that just because you can work around a bug (by putting the onus on the user to avoid some set of characters) that doesn't make it any less of a bug.
Anyway - this thread has devolved from me making a simple (and I thought clear) bug report to a bunch of wanna be 'engineers' waxing about why it's all the users fault for not sticking with some arbitrarily defined character set. I'm not putting you in that group, you're just explaining what you tell clients to get avoid having issues like what I ran into happen in the first place.
However it's sliced, good software should manage these things gracefully. Adobe, Microsoft, Apple, and many others do so just fine. Resolve should do a better job rather than just dropping whole directories and files from processing, without a word back to the user.
I do appreciate your comment though, because it clearly illustrates that the failings of software to reliably interpret some characters forces users to work around these failings to have a stable work environment. As long as the OSs (Win/Lin/Mac) let users use these characters freely, the users will do so.
Couldn’t get the last line out of my head, so I break my own promise. I’ll start on the most universal part of computing text, naturally included in unicode, universally usable in any modern text editor, but certainly not recommended for use as filenames. It may still not prevent you from trying, but… look…:
1. Why start on “weird and silly”, when you could do the following, to “see the light”, or start fighting Microsoft and Apple, when using the characters “:” and ”\” etc. in filenames. Characters that have been valid in even primitive editors and text use since the world only had the ASCII character set?
2. Try using a filename with the completely - ahem - "innocent" text:
- Text inside file. Try using it as a filename.
- Skærmbillede 2024-05-22 kl. 14.40.46.png (8.67 KiB) Viewed 1076 times
(the characters “:”+”\”+”&”+ “/“ + “.” + “:” + “x”. I have to enter them as single, quoted characters here, otherwise some end up as emojis in this thread, which are not usable either) also using it in the filename and save it on an ExFAT SD Card from a Mac. :
- Save As on Sonoma 14.4.1 - saving to ExFAT formatted SD Card (Audio, Camera use etc).
- MacOS 14.4.1 Save As.png (23.72 KiB) Viewed 1076 times
3. Obviously the silly demand is ignored. Completely. User getting the same filename as shown above in the "filename field" on the SD Card (try for yourself - time to meet reality - ehhh...).
4. This is what you get in Windows 10 (version 22H2) still officially supported (Windows screendump via Remote Desktop):
- Same filename, as it shows up on Windows 10.
- Windowss 10 SD ExFAT.png (33.44 KiB) Viewed 1076 times
5. Do you demand, that Apple should prevent you from using legal macOS filenames, on the odd chance, that you will end up using Windows?
6. Haven’t even attempted general use to Linux, Windows command prompt or Mac terminal use. Tools - sometimes - required to repair the effects of typical user-FUBAR-actions. Especially difficult, if the user sends one the name of a file, that any supporter anywhere on earth certainly won’t find anywhere in their standard system.
7. Now, I ask you, why camera manufacturers, tools manufacturers all over the word, in EU, China, Emirates, India, Japan, Korea etc. should invest millions if not - combined - billions in preventing users from behaving downright silly? Manufacturers of Swiss Army knifes have done their best to prevent users from cutting themselves. No success. Even in the most gun crazed parts of 'merica some decide to collect a Darwin Award in the most silly way dreamed of by accidentally shooting themselves, when cleaning a loaded gun pointed to themselves. Sigh... how is that preventable (ah, no guns, but...).
Still requiring every character to be supported everywhere in all use cases and all environments?
There is a simple, practical and hugely cost saving reason behind - for example - not supporting the use of “hieroglyphs” everywhere. It makes litle sense for almost all use cases in real life. I'm convinced, that almost all use cases involving “faraonic Egypt” in the Egyptian Museum in Cairo will not lead to demanding absolute and universal usability of hieroglyphs across all used platforms (or warnings of not possible in a German camera in the Chinese politics department in Buenos Aires).
Feel free to ignore, what I wrote. Your problem.
Why not accept, that when professional, knowledgable, hugely experienced and seasoned video-editors/camera user/producers of actual material (earlier in the thread) - that have seen users do any (un)imaginable stupid thing - give you and their customers free advice, on how best to fashion filenames to avoid any confusion or complications anywhere in a - maybe very long - chain of production elements, hardware, operating systems and whatnot?
Regards