Gradients rasterize when saving down a version..

hello, can anyone help me find a work-around? i'm working in CS4 and when i save the file down, all of my gradients rasterize and all that's left is the nofill outline of the vector object. I'd like the gradients to remain the way they are in spot colors. How can i save this file properly so it works when another user working in an earlier version will be opening it? thank you!

that's not the problem though. the problem is that the gradients all convert
to clear boxes, which, upon deletion, reveal a full gradient square. the
gradient is no longer held within the boundaries of the vector object; it
covers it and totally distorts the image. i can't take my cs4 version to the
printer's computer; you're telling me there's no simpler way than having the
designer go in, individually select each piece with a gradient, delete the
clear box, then the gradient box, then click around until they find the
vector object which is invisible because it has no fill or stroke, and then
they have to repeat it for every gradient on the design? i'm sorry, there
has to be some sort of fix for that! i've had clients send me work saved
down with gradients in illustrator and i've opened them in older versions
with no problems, there has to be an option i've missed somewhere.
there just has to be.

Similar Messages

LV2011 bug - Error wired to boolen function breaks when saving for previous version

I just downloaded LabVIEW 2011 this morning. I created this VI and saved it for LV2010 to see how it would deal with it. I opened the VI in LabVIEW 2010SP1 and the error wire is broken. There were no warnings about problems saving this VI as an earlier version.
=====================
LabVIEW 2012
Solved!
Go to Solution.

I would not consider this to be a "bug".
I would call it rather an "incomplete feature" were the extra-mile (backwards compatibility) is not fully implemented. So filing a suggestion is really the best thing to do (i will not file one since it is your idea, but i will kudo it!).
Saving VIs to previous versions does not change the BD itself. The requested functionality would require BD analysis and inserting (per scripting) an unbundle into the error wire. This is a complete new functionality, at least i am not aware that this is happening anywhere else....
As a "part time solution" i would like to see a BD analyzer which warns you about possible issues during downconvert. So in your case an "errorlist entry" like:
Warning: Connecting the error cluster to boolean functions is a new feature to LV 2011. Saving for previous version will lead to a broken VI.
just my 5 cents,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Problems with gradient feather when saving as pdf

I have an InDesign CS4 file which has a high-quality grayscale jpg with a CMYK jpg on top of it. The later has a gradient feather effect applied to it. When I export to pdf, some people (I believe with an older version of Reader or Preview) cannot view the gradient. From a computer like this, it prints the most transparent part of the gradient as the entire gradient, so I think it's still there but very hard to see.
I haven't been able to test it in Reader because I can't find an older version, but I know it doesn't work in an older version of Preview (3.0.9 is what I tried). However, everything I've tried hasn't worked—I've tried changing the Transparency Blend Space to RGB, Exporting as Acrobat 4.0 (which works but looks horrible); I've exported as Press Quality and High Quality Print, and played with profile settings. I've also made sure that all my graphics and profiles match as CMYK, because originally they didn't. The only thing that works is if I open it in my version of Mac Preview (5.0.2) and then Save As a pdf from it. But I'm afraid the colors and perhaps quality are affected in so doing. I've also googled this to no avail.
Has anyone else had this problem? Can someone help?
This is what is should look like.
This is what it does. Notice the color is still in the "contact us" (and all the colors on p.2 are fine).

What version campatibility for Acrobat do you have selected in your export settings? Changing to Acrobat 4 will make it compatible with 4 and later, but you'll wind up falttening the the transparency and heve nasty looking white stitching lines all over the place that will show on screen and print on most desktop devices, not to mention a loss of interactivity, I think.
Reader is free... Tell these people to download an upgrade to the most recent version that will run on their systems rather than trying to dumb down your file.

When saving down an Illustrator CC file to Illustrator 3 I am getting a meta data error. Any ideas how to fix this??

Unfortunately, I have a printer who is working on Illustrator 3 (Don't ask). Any work arounds that you know of that can fix this issue? I can save all of the way down to CS without issue, but anything prior is giving me the following message:
Cant Open the Illustration. The illustration contains an illegal operand.
Offending operator: {ps_metadata_stream}
Context:
I am at a loss right now. I've removed metadata using Bridge and Acobat to no avail.

Are you trying to open the AI3 file or is the printer? Who is getting the error message?

Illustrator CS6 Rasterizes Drop Shadows When Saving Back to CS

I am working with Illustrator CS6 and when I save a file to an earlier version - CS3 or CS - that has a drop shadow effect, the effect gets rasterized. Drop shadows are not new to this latest version of Illustrator so shouldn't they still be editable when saving to a version above CS?
Thank you.

Actually Gaussian Blur was indeed updated in CS6 to be much faster. All drop shadows use Gaussian Blur, as do outer glows and inner glows. If you need live drop shadows and glows in CS5, then apply them in CS5.

CS2 freezes when saving files

I'm running Windows 7 Ultimate 64 Bit and suddenly my files freeze when saving. Runing version 9.0.2. Can anyone help?

Photoshop CS2. When I work on a file and click "save" it freezes. If I click save as, using the same name it freezes. If I save it and number or change the file name it save correctly without freezing. i.e. Save 1.jpg' save 2.jpg etc.

Crystal 10 Shuts down when saving to enterprise Server

When I do a save in Crystal 10 it simply Shuts down with no error message or anything ONLY when saving to enterprise Server any thoughts on what it could be
newbie here

What version of Enterprise are you saving to and if they are the same major version are they the same patch level?
Check with the CE administrator to make sure you have rights to save to Enterprise.
Thanks
Don

While using a drop-down menu i.e. File, edit, image, or even when saving as and choosing the file type; the list appears and I am able to highlight what i want but cannot click on anything.

While using a drop-down menu i.e. File, edit, image, or even when saving as and choosing the file type; the list appears and I am able to highlight what i want but cannot click on anything. This is becoming incredibly frustrating. It happens at random time and a restart of the computer is all that helps, then with out any notice it starts to do this again. Mac Book Pro i7 2.2 16 GB 1333 Ram, (2) 450GB SSD both internal to machine. At this point I am losing file because I am unable to save in the file type I need. Does anyone out there know how to solve this issue?
Thanks
phil

I haven't been unify photoshop much in the past month, but I did try your suggestion and it seemed to work for a while. Today when i went to save a document the same thing happened: click on file>save at this point I can not click on save even though it is highlighted. Tryed to use command s that brings up the save dialogue box, but when I try to change file type I again cannot select it from the drop down menu.

Good day! When saving a file in Illustrator, I can not keep the older version. How You can save the file in an older version?

Good day! When saving a file in Illustrator, I can not keep the older version. How You can save the file in an older version?

When you save a file that's what options offers application
05 мая 2014 г., в 13:40, Jacob Bugge <[email protected]> написал(а):
sage go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
To unsubscribe from this thread, please visit the message page at . In the Actions box on the right, click theStop Email Notifications link.

Why does saving down from Illustrator 6 to older version sometimes not work?

We have some users with CS6 and some with CS3 and 4, when a user tries to open an illustrator file from CS3 and 4 saved down from CS6 it will not open. some files will open but most won't.

Try running Firefox in [[Safe Mode]]. If it functions properly in that configuration, then one of your add-ons is the culprit.

InDesign Shuts Down When Saving

InDesign CS3 5.0.2
InDesign shuts down when saving a file. The ONLY time it seems to act up is when we try to save using any option except for "save a copy." There are no numbers, messages, etc. outside of the standard: "InDesign has encountered a problem and must shut down. We apologize for any inconvenience..."
When it does shut down, whatever file was open at the time is lost. Totally. I have yet to be able to locate the previous file using any means.
Has anyone else had this problem. Any fix?

Normally I would recommend replacing your preferences as a first step. I'm not sure quite how to test, though, without putting something at risk.
Maybe replace the prefs, open a new file that won't matter, save a copy, then try a save as and see what happens. You might also try turning off video hardware acceleration, but that seems tenuous, as does a bad font.
Is there a network involved, or are you working locally? If yes, what kind of network? Have you tried working locally?
If none of this has any effect you may need to reinstall, but I hate to put anyone through that pain without a better idea of what the problem is.
Peter

Incompatibility issues when saving BW workbook in early excel versions

When saving a BW workbooks to my desktop for example so that I can then send it to a user to view the report I get incompatibility issues when saving workbook to earlier excel versions. I am currently using 2007 and when I save the workbook to Excel 97 - 2003 then I get incompatibility messages. If I ignore these and just save then no one is able to open the workbook. This means that I cannot also save workbooks on the reporting system as those users not using 2007 cannot view them. The message that I get is that 'the features of this workbook are not supported by the earlier features of Excel.'

Hi,
Please refer to this note,
Note 1152092 - Error opening MS Excel 2007 workbook in MS Excel 2003
Usually when you do any formatting feature available in Excel 2007 to the workbook it would throw you the error, not sure if you are formatting the workbook.
Regards,
Mani

Hi i recently created a document on iwork pages via my icloud account however when i click on the document now it doesnt seem like it saved the latest version? can anyone help with this?

Hi i recently created a document on iwork pages via my icloud account however when i click on the document now it doesnt seem like it saved the latest version? can anyone help with this?

Welcome to the Apple Community.
Are you also trying to re-open it on the same device as you edited it.

Page shows different data when saved after few minutes

Hi,
I have a peculiar problem to describe.
I have a page which contains af:table inside af:panelCollection layout. I use a af:commandLink to drilldown to another page using setCurrentRowWithKey method.
I am able to drill down to the correct data in another page which contains data that is editable. Once after editing the page when i click save button, i am able to save the data. This is working fine.
But the problem is, once i drilled down to this edit page and edit some fields and save it after few minutes, say 5 minutes later, it is not saved. Also, the page is refreshed to bring some random record.
Can anyone let me know why is this happening and how to resolve it?
Thanks

Hi Timo,
Which jdev version?I am using jdev 11.1.1.3.0.
Is it possible that the data has changed (e.g. by an other user) after you drilled to the one record you want to change?There is a possibility that the data can be changed by other user as well. But, for the time being we have implemented for the single user environment.
When you click save after some time, do you get any error (on the screen or in the logs)?Yes. On the screen, it is displayed as "oracle.jbo.JboException: Document type mismatch (source INVOICE, type Sales)". It is a validation exception thrown at viewRowImpl level by me. But it validates the data perfectly when saved immediately after editing
Which session timeout do you have configured in your web.xml?Session-timeout is given as 240
Have you tried your use case with the HR schema?Yes. when i reproduce the situation in HR schema, it is getting saved perfectly
Regards

Items missing from CC document reappear when saved as CS4

Had a two hour chat with Adobe this afternoon and uploaded a suspect file, but am now unable to get in contact, so I'll give this a go.
We've recently upgraded from CS3 to CC and have thousands of legacy files. The docs look fine when opened in CC and output correctly to PDF for commercial printing purposes. Today, however, has thrown a major spanner in the works. Three days ago we opened a CS3 document into CC, made amends, output a PDF proof for the client, and saved it as CC (.indd). The client has sent back the marked up PDF to make further amends. On opening the CC doc, it is immediately apparent that things aren't as they should be. Several items from different pages and different layers - images and text boxes, are missing. We scratched our heads for a while to try and work out how we could possibly have accidentally deleted various items, with no convincing answer. A confusing anomaly was that one of the items missing was a full page full colour placed image which just happened to be on the back cover also. We copied this image and tried to place it on the front but it wouldn't allow us, saying something about boundaries not being big enough - the first sign that something may be damaged.
I then looked on the web to see if anybody else had had similar problems. It appeared that nobody had but one of the results was an Adobe page for repairing corrupted files. I decided to try one of their recommendations, which was to save as a CS4 file then reopen in CC. We did this and hey presto, it worked! All the missing items returned.
Our initial joy was quickly replaced by dread as we realised that we had opened what appeared to be a corrupted file, with absolutely no external indication that it was damaged. If it hadn't opened at all, or if there'd been a warning to say the file was damaged, we'd have been pre-warned; but the fact that it opened with no problem whatsoever, meant we didn't know it was damaged. On this occasion, the absence of the front page image made us aware of a problem, but what if it was a 200 page catalogue that we'd just been given the go-ahead to print? Before today we certainly wouldn't have been thinking that we need to go through every page to make sure every item is still there!
We very often open old docs and create PDFs for print without looking at the files, but even if we did, how are we possibly going to remember every item that appears on every page just to make sure they're still there when we print 3 days, 3 weeks or 3 months later.
I've been doing this job for twenty five years and never come across this, and from a business point of view, this is VERY scary.
Anybody any idea what's happening?

... this kind of problem is common enough that I never recommend opening a legacy .indd file in a newer version. Instead export the file to .inx from the original version (or .idml for CS5 or newer files) and open that for conversion.
Peter,
I've never seen or heard of such a thing. I have had guides get totally screwed up when files are saved down to IDML and then re-opened. That's why I don't really trust the IDML saving except for damaged files.
But opening legacy files is not supposed to have these types of problems.
It is very possible that this is a one-time aberration of only one file.
But what you're recommending is too onerous for most companies to do.
It is not feasible for companies to keep a copy of legacy software (in this case CS3) running. So they would have to anticipate needing to re-open the file as INX. They would have to keep a copy of CS3 available to export as INX. But it is doubtful that CS3 would run on today's machines running the latest OS. So what you're recommending is they have to export as IDML before they archive a file. And I don't even know if the INX from CS3 can be opened by CC. That could have just as many problems
I'm happy for the client that saving the IDML and then re-opening in CC fixed their problem. Obviously the CS3 file was damaged.
And there really is no excuse for not checking a document before it goes to press.
But if people can't trust opening legacy files, Adobe has a huge problem on their hands.

Gradients rasterize when saving down a version..

Similar Messages

Maybe you are looking for