I just learned that NTFS/Windows doesn't allow the ":" character in filenames, what the fuck? Then how do you tag time on files? what happens if you download pic related?
>>80347988>Then how do you tag time on filesYou can use periods or single quotes.>From video at 3'05.png>From video at 3.05.png
>>80347988>what happens if you download pic related?turns into underscore
>>80348067That's wrong and looks like a date or a millisecond time
>>80348085thank you>>80348067Using quotes sounds retarded, I want to develop for windows so I want to know about it. God what a backwards system, even the slash in the directories is backwards>>80348107true, both are bad, I think I'll go with underscore
windoze will never be able to handle this filename
>>80348115>Using quotes sounds retardedPlenty of professionals used quotes to write timecodes on tapes. A single stroke can be placed faster than a colon.
>>80348238now try actually looking at it in your file explorer
>>80347988>what the fuck?This has been the case since 1985 and you learn about it today?
I don't think this is an NTFS problem. Windows carries some bullshit bugs since the days of CP/M (MS-DOS was based on this system and so is Windows).
>>80348271>Plenty of professionals used quotes to write timecodes on tapes. A single stroke can be placed faster than a colon.Not for filenames in an operating system retard
you can't create a folder named CON too
>>80347988Use any other format, literally. I've seen phones save photos with timestamps such as DDMMYYYY_HHMMSS so you get something like 23022021_191525.
Windows can't handle ?, " and * either. Very annoying when using multiple operating systems. I managed a fairly large catalog of music on linux with funky song names as filenames, some of which contained various illegal symbols. I could change the names only with a linux machine. Windows simply cannot do anything with files that have those characters in the filename.Also the path character limit of 260 has been very painful occasionally.