Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Interesting...' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Interesting...
Authored by: robg on Nov 09, '01 02:56:31AM

I'd only been using it on my digital camera files, which are all under 32 characters. I hadn't even noticed the restriction. I'll inquire with the author and see if he's working on a fix of any kind.

I must not tend to use super long filenames very often, as I obviously hadn't even seen the bug yet!

-rob.



[ Reply to This | # ]
Interesting...
Authored by: ikari on Nov 10, '01 09:51:58AM

I was using it on mp3s that I ripped on my Windows box and couldn't be bothered re-ripping, was planning to lay them out in the iTunes style ~/Documents/iTunes/iTunes Music/artist/album/title.mp3 way, hence was planning on using ABFR to strip off the unwanted information from the mp3 filename.

Oh well, guess i'll just have to wait for an update, thanks for asking the author about it.



[ Reply to This | # ]
Response from the author
Authored by: robg on Nov 10, '01 10:27:38AM

Here's what he had to say in an email I just received:

"The long file name issue is something that we didn't catch in the first OS X release because our test cases are cross-platform (OS9 and OSX). The issue has now been largely resolved in the release which is due on Wednesday [Nov 14] (all file names are now correctly renamed) and there will be some further work on the issue in the next releases (all fields will have 255 character, etc.)."

Good news!

-rob.



[ Reply to This | # ]
Response from the author
Authored by: bhines on Nov 10, '01 07:15:11PM

So the answer was no, it won't be fixed for the next release, sounds like.



[ Reply to This | # ]