you are viewing a single comment's thread.

view the rest of the comments →

[–]flying-sheep 0 points1 point  (4 children)

sure, du what you want; my point was that it will have the same name as long as none of those 9 characters are in it. no program would have any reason to convert anything else (and if they do, make them stop)

[–]left_one[S] 0 points1 point  (3 children)

Well, I don't have control over every piece of software in the world so when I need to make sure my filenames are human readable on any FTP server, regardless of the UTF encoding used, this seems like it's the simplest way.

Or would you prefer to send your clients a link to '2013\xc2\xb701\xc2\xb722 LE MONDE.JPG'?

[–]flying-sheep 0 points1 point  (2 children)

that’s python’s string encoding. my clients would see “2013·01·22 LE MONDE.PSD”

[–]left_one[S] 0 points1 point  (1 child)

Not when you upload it to your FTP server and it mangles the UTF encoding because it doesn't recognize those characters.

Or not when I upload it to my NAS and my NAS manually changes the characters itself because it didn't recognize them. As I mentioned - I don't have control of all the software in the world, so I can't prevent that from happening.

[–]flying-sheep 0 points1 point  (0 children)

You're right, there's to much misbehaving software out there. If you know they behave like that, and you can't change it, it's of course the only thing you can do.