Closed: Case of non-graphics filenames

[Hayo Baan]

PM apparently changes the case of non-graphics files to all lower case (e.g., 20090506_19020304_D3.html becomes 20090506_19020304_d3.html). For graphics files this alteration of the case of the base name is not performed. This is problematic as this wreaks havoc on case sensitive file systems.

The case change is visible in the contact sheet, but worse, is also applied when e.g., renaming files.

Why is this done, and could this please be fixed?

[Kirk Baker]

PM apparently changes the case of non-graphics files to all lower case (e.g., 20090506_19020304_D3.html becomes 20090506_19020304_d3.html). For graphics files this alteration of the case of the base name is not performed. This is problematic as this wreaks havoc on case sensitive file systems.

The case change is visible in the contact sheet, but worse, is also applied when e.g., renaming files.

Why is this done, and could this please be fixed?

What part of the application is doing this?

-Kirk

[Hayo Baan]

Well, it seems to happen everywhere.

As I said, you can already see it happen in the contact sheet; .html files get the lower case D3.
Also when you use the batch rename dialogue, the list of files shows the resulting file with lower case base names.

Note: I have set the preference for the suffixes to lower case. Perhaps this option is spilling over?

[Kirk Baker]

Hayo,

Well, it seems to happen everywhere.

As I said, you can already see it happen in the contact sheet; .html files get the lower case D3.
Also when you use the batch rename dialogue, the list of files shows the resulting file with lower case base names.

Note: I have set the preference for the suffixes to lower case. Perhaps this option is spilling over?

I'm not seeing this when I test.  I used a filename "A_Kirk_X.TXT" and I set the filename extension case to lower.  Then I did a rename with {date}_{filenamebase} in the Rename dialog.  The previewed name was:

6-4-07_A_Kirk_X.txt

When I executed the rename I got the expected result.  How do I reproduce your issue?

-Kirk

[Hayo Baan]

Kirk, this is really weird. There can't be much difference in what the system is doing, now can there. Oh, the only thing I can think of now is that I'm on Leopard 10.5.7 and IIRC you're using Tiger 10.4.x mostly. Could that be it?

Anyway, to show you what I'm getting, I've taken some screenshots.

First of a terminal window where you can see the file names as they should be. The other captures show you part of the contact sheet as well as the rename dialogue.

Hope we get to the bottom of this one 

[attachment deleted by admin]

[Hayo Baan]

Kirk, any news on this one?

[Kirk Baker]

Hayo,

Kirk, any news on this one?

Like I said earlier, I cannot reproduce the issue.  If you can help me reproduce it, I'd be happy to fix the problem.  Perhaps sending me your files as a Zip archive will help?  Please click on my name to the left of this message, then click on the 'personal message' link.  I will respond with upload instructions.

-Kirk

[Hayo Baan]

Kirk,

I don't think there's any sense in mailing you files to help you reproduce it; for me it happens to ALL (non graphics) files, even if I simply create one on the command-line. E.g., even a file created using touch ~/Desktop/aaaTTT shows up as aaattt in the contact sheet.

I still reckon this is an issue with Tiger vs. Leopard. Have you tried to reproduce this on a Leopard 10.5.7 system already? Oh, and what file system are you running on, perhaps this has anything to do with it? Mine are all Mac OS Extended (Journaled), non case sensitive (the problem exists on FAT32 volumes as well though, I just tested this on an external disk).

Thanks

[Kirk Baker]

Hayo,

I don't think there's any sense in mailing you files to help you reproduce it; for me it happens to ALL (non graphics) files, even if I simply create one on the command-line. E.g., even a file created using touch ~/Desktop/aaaTTT shows up as aaattt in the contact sheet.

I still reckon this is an issue with Tiger vs. Leopard. Have you tried to reproduce this on a Leopard 10.5.7 system already? Oh, and what file system are you running on, perhaps this has anything to do with it? Mine are all Mac OS Extended (Journaled), non case sensitive (the problem exists on FAT32 volumes as well though, I just tested this on an external disk).

Thanks

Found it and fixed it.  Would you like to test to verify?

-Kirk

[Hayo Baan]

Found it and fixed it.  Would you like to test to verify?

Excellent! Was it a Tiger/Leopard thing or something completely different?

Oh, and sure I'm willing to test the fix 

Cheers

[Kirk Baker]

Hayo,

Found it and fixed it.  Would you like to test to verify?

Excellent! Was it a Tiger/Leopard thing or something completely different?

I never could reproduce it myself.  But one of out Q/A guys could so I identified what I believed was causing the problem, made the change, and he tried it and found that the problem was solved.

-Kirk

[Hayo Baan]

Indeed, the test version Kirk sent me fixes the problem!

Thanks