Adobe Creative Suite

Mysterious application failures caused by delocalization

OS X supports a large number of world languages, but if you only understand one language, you’re hauling around many megabytes of files you don’t need. Many Mac users try to free up some disk space by using a utility that removes versions of files for languages they don’t want. This has given rise to a class of utilities that hunt down and delete all the files for specified languages. Some of these utilities are:
Delocalizer [Note: This software appears to be discontinued. (June 2011) ]
Macaroni
Monolingual
Youpi Optimizer  [Note: This link is now dead. (June 2011) ]

Nearly all of my applications run fine after delocalization, but there are a few that don’t like to have their localized resources deleted, and they refuse to run without them. These applications might not display a specific error message for this, so all you see is a general error message that leaves you guessing.

The applications that I know about that don’t like to be delocalized are:
Adobe Illustrator CS2 (the 12.0.1 updater fails to install the update)
Adobe Acrobat 7 (Macaroni users update to Macaroni 2.0.6 or later)
Adobe Acrobat 8 (application will not launch, says “A required component was not found.”)

(NOTE: Macaroni 2.0.8 is now available, and according to its release notes, it will no longer delocalize any Adobe applications. This should prevent future Macaroni delocalization problems with Adobe apps.)

If you run a delocalizer and those applications or their updaters stop working, you must reinstall the application. Then you have a choice: Either see if your delocalizer utility has a way to exclude specific applications (a whitelist), or don’t delocalize again. Read on for why that second option might be realistic.

Nobody likes to have something not work, especially if it’s just one pesky app that breaks after delocalization when all the other apps are fine. And delocalization can benefit users with small hard disks. But you may not need to delocalize if you have an up-to-date computer. Today’s hard drives, now typically 250GB and up even on notebooks, are so large that a hundred or so megabytes of localized files are unlikely to be the major cause of a full hard drive. If your Mac hard drive is filling up, you’ll probably get a lot further by moving unneeded movies, photos, and music to another drive. One hour of miniDV format video from is around 13GB, many times larger than all your localized files. Also, the digital audio and graphics samples that come with multimedia applications such as GarageBand, Apple Soundtrack, and Apple LiveType take up several gigabytes on their own, so you might want to clean house there unless you need those samples.

Why would an application fail after delocalization? In many cases an application will use a checksum to verify its integrity. It knows what its file size was when originally installed, and if it notices that there’s a discrepancy the next time it launches (because you removed stuff), it won’t run. It does this because a size discrepancy can indicate that the application code has become corrupted or that malware has infected and modified the application for its own nefarious purposes. Those are some of the reasons why an application may be built to be extremely suspicious when its size changes, to the point of shutting itself down. The developer wants to make sure that the application won’t do any damage to your files.

Bridge CS2: Renaming files with the keyboard, whether you meant to or not…

To rename a selected file or folder in Adobe Bridge CS2 without using the mouse, press the spacebar, type the name, and then press Return or Enter. (For Bridge CS3 and later, see the note at the end of this post.)

If you pressed the spacebar without intending to change the filename of the selected file, your next keystroke will accidentally change the filename, and it will become permanent as soon as you click anywhere else. Once a new filename is committed, you can’t undo it. This can be a disaster if you never realize you renamed a file that was selected, and you go looking for it later without knowing that it’s under a new name. If you suddenly realize you’ve entered filename editing mode by accident, immediately press the Esc key to escape that mode without changing the original filename.

Pressing the spacebar to rename may not be intuitive if you’re used to pressing Return on Mac OS X to rename a file, but in Bridge, the Return key is already taken: it opens the file in the default editor for its file type. That use of the Return/Enter key is consistent with Windows.

Why would anyone have a reason to press the spacebar in a file browser other than to rename a file? Sometimes it’s because of the habits people pick up in other programs. Some people press the spacebar to get to the top of an alphabetical list, and others are used to pressing the spacebar in other Adobe applications to get a hand tool to pan a document in a window.

Note: In Bridge CS3, accidental renaming is much less likely because the renaming shortcut was changed to the F2 key. You can still click the filename after the file is selected; just don’t double-click the file or you’ll open it.

Back up important preferences files

When an application isn’t quite working right, sometimes the cause is a preferences file that’s gotten corrupted, so a common troubleshooting step is to delete an application’s preferences file. That’s easy to do, but with many of today’s more complex software programs, preferences are key to your workflow, and when you lose your preferences, the program may no longer do what you expect it to because it’s reverted to the factory defaults. If you’re trying to get jobs out fast, reset preferences can slow you down until you get all of them back to the way they were.

Let’s take Photoshop, for example. The preferences control everything from how keyboard shortcuts work to which disks are used for scratch files. If you’ve changed 24 preference settings and then one day you have to delete the preferences file to solve a problem, it’s hard to remember all of the options you changed. Keyboard shortcuts, units of measure, tool defaults, printer profile choices, and scratch disk locations can all be changed to settings you aren’t used to.

Here’s an easy way to restore your preferences easily in case you have to delete your preferences. After you get preferences set up the way you want, and before a problem happens, just create a .zip archive of your preferences. Whether you use Mac OS X or Windows this is easy and just takes a second.

First, find the preferences file you want to preserve.
Then, on Mac OS X, select the file and choose File > Create Archive Of (the filename).
On Windows, right-click the file and choose Send to > Compressed (Zipped) Folder.

You can just leave the zip archive next to the original preferences file because the program that uses that file will ignore it if it has the .zip filename extension instead of its normal one. Because the zip archive is created in the same location with a nearly identical filename, you don’t have to fish it out of a backup somewhere; it’s already in the right place.

When you have a problem that requires deleting preferences, delete the actual preferences file and then simply extract the backup preferences from the zip archive by double-clicking it. On Mac OS X, the file appears in the same place you zipped it, which should already be the right place if you zipped it in its proper folder location. On Windows, you may have to go through the extra step of dragging it out of the containing folder that the Extraction Wizard creates and then deleting that extraction folder. On either OS, the zip archive remains in place so you can easily extract the backup again in case you have another problem in the future.

Some applications have entire folders of preferences, or additional folders in the Application Support folder on Mac OS X or the Common Files folder in Windows. If those folders contain presets or other files that can’t be reinstalled from the original disks because they’re unique to you, it can be a good idea to back those up in place too.

Dr. Brown’s Place-O-Matic: Camera Raw color space not used?

If you use the Dr. Brown’s Place-O-Matic plug-in for Photoshop and the Space in the Adobe Camera Raw dialog box doesn’t seem to be applied to the Photoshop document containing the Smart Objects generated by the plug-in, change your Color Settings in Photoshop (Edit > Color Settings) before using Dr. Brown’s Place-O-Matic. Dr. Brown’s Place-O-Matic sets up the Photoshop document using the current Color Settings.

I came across this when I selected ProPhoto RGB and 16 Bits/Channel in the Camera Raw dialog box, and noticed that the resulting Photoshop document was in sRGB. When I changed my Color Settings to use ProPhoto RGB, the Photoshop document created by Dr. Brown’s Place-O-Matic was created with ProPhoto RGB.

Dr. Brown’s Place-O-Matic is a free Photoshop plug-in available from the Tips and Techniques page on Russell Brown’s web site. It helps you create one image from two different conversions of the same camera raw format image, such as when you want to combine the very light and very dark parts of the same image. Because the plug-in imports two versions of a camera raw image as smart objects, you can alter the conversion settings at any time, which gives you a lot of flexibility.

“Folder not found” error when batch processing in Photoshop

If you try to run a batch process in Adobe Photoshop (either from Photoshop or from Adobe Bridge) and you get an error message that says a folder wasn’t found, here are some things to check:

  • In the Batch Processing dialog box, look at the Errors section at the bottom of the dialog box. If you have the Errors pop-up menu set to Log Errors to File, click Save As and reset the error log file location. Pointing the log file to a disk or disk name that isn’t mounted or no longer exists can cause the error message. For example, maybe you renamed or deleted the folder that the error log was pointed to before.
  • Check the action you’re running, and if there any folder paths in any action step, make sure those paths are still valid. Folder paths can exist in can Open step, a Save step, or a Load or Save step. For example, you might have a step that loads a saved curve from disk into the Curves dialog box.
  • If you action calls other actions, check the folder paths in those sub-actions.