To provide the best experiences, we and our partners use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us and our partners to process personal data such as browsing behavior or unique IDs on this site and show (non-) personalized ads. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Click below to consent to the above or make granular choices. Your choices will be applied to this site only. You can change your settings at any time, including withdrawing your consent, by using the toggles on the Cookie Policy, or by clicking on the manage consent button at the bottom of the screen.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.
The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
It was not Adobe’s fault, but Rosetta’s…
Sorry, I jumped the gun, but apparently the situation is only “improved” and not fixed. Many non-integer numbers will display as intended, but other will still display out to 15- or 16-digits. It’s still a worthwhile update, but it doesn’t technically “fix” the cosmetic measurement problem with InDesign CS2.
It also doesn’t fix the apparent Rosetta problem where if you click on a colour in your swatch palette, it gives the proper colour mix in CMYK, but if you click on the colour in the colour picker, it’s incorrect. This happens in InDesign CS2 and Illustrator CS2. Doesn’t seem to happen on PPC machines.
Unfortunately, the update seems to have introduced another serious -perhaps more serious- problem. When using any of the Pathfinder functions, be it from the pallet or as an effect, on a circular path, Illustrator crashes like there’s no tomorrow…
yes, a couple of newly installed Illustrators on new Mac Pros are experienceing this exact problem, a fix is in order
please contact me with any new info, [email protected]
thanks
i can’t even get ill to boot up without it crashing. it started yesterday when i installed the 10.4.8 update. I’m on a preIntel Mac (last one before the switch). Any thoughts? CC my email adderess if so. Thanks.
I get the crash with using the pathfinder and also using the knife tool, everytime.
The Illustrator bug is a known issue. The fix is to close the Appearance palette and then quit Illustrator. When you restart the program the bug is gone (you have to ensure the Appearance Palette is always closed when quitting).