I've just started using this - somewhat cautiously. It seems to do several things quite nicely - thinning fat binaries and compressing tiffs. It leaves extra languages intact, though, even when I check the option asking it to remove them and when the application contains relevant files. Just wondered if anybody else was seeing this or if it is a peculiarity of my set-up.
It's possible that this happens because my first choice of language is not US English (or, indeed, English) - perhaps it finds no files for my language and, rather than keeping language files for my second choice of language or deleting all of the language files (which would not be good), it keeps all of the languages. (Just a theory.) I would be interested to know what others are finding - both users with English as their first choice of language and those with something else.
Trimmit!
eliminating bloatware: delete junk files, clear resource forks, strip universal binaries...
Version: 0.95
Partial success?
Feedback Type: Commentary
Contributed by: cfrees Saturday, April 05 2008 @ 05:10 PM PDT
Product Platform: MacOSX
Used Product For: Less than a month
Recommend Product: YES
Comments
Languages - cfrees
I figured out how to persuade it to keep all the languages I list in System Preferences, if they are available, and to keep my second/third choices if not. So now it will keep English/English-GB no matter what and Welsh if it is available.I'm guessing other users might like this sort of flexibility but wouldn't have a clue how easy (or otherwise) it might be to implement in the general case.
Thanks!
cfr
Thursday, May 01 2008 @ 08:41 AM PDT
Languages - ankur1
That's correct - if the application is not localized in your first language, it leaves the language files alone rather than deleting all of them.Reply to This
Thursday, April 24 2008 @ 08:48 PM PDT