CS3 to CS2 Format Problem

I save my CS3 file as a CS2 file to give to my client. They open the CS2 file and all of the layers are grouped together in one layer. Does anyone know why this happens and how I can fix it?

Any time you save a file down to an earlier version you're asking for trouble. It doesn't matter if it's Illustrator, inDesign, Quark, whatever.
After you down-save, when you open it again in CS3 to check are the layers still intact?

Similar Messages

Flash CS3 / Illustrator CS2 Heritage Problem

Does anyone know if there are any heritage problems that
occour when you open an CS2 Illustrator file in Flash CS3?
Someone told me certain effects dont appear (i.e. gradients)
or that that image wont move as it's supposed to.
I have CS2 Illustrator & I want to purchase CS3 flash,
but I'm not sure if there would be a problem while importing my CS2
.AI files.

I have encounterd the same problems. ( illustrator,flash, indesign not working)
I did almost every thing I could think of: clear Caches, Prefs, and run CS3 clean script before reinstallation.
I also had the latest Version CUE updates 3.0.1 (downloaded the FixVCUIFramework).
But nothing above helped :( , apps still crashed right after launch.
*Then, I remembered having installed this thing called "Application Enhancer" right before the apps starting to crash. SO I REMOVED IT, and haunted down all the remaining files, trashing them all.
Next I went into the SAFE MODE (so the system clears up some caches)
After that I also DISABLED the USER FONTS when I login to the normal mode.
And my CS3 apps WORKS AGAIN !!! :)
I'm not sure which one of the above steps really solved the problem...
All I knew was that none of them could work out the problem alone.
Hope this helps a little...
GOOD LUCK!!
Ps. the Fonts thing are really troublesome!! Caused a lot crash for the system!

Importing INX from CS3 to CS2 problem

Greetings,
I'm working on a 16-page newsletter file saved from ID CS3 to INX that then won't import into CS2. When I try, a list of missing plugins come up that its saying are needed. The thing is, I've done this before and it wasn't a problem. Also, I've tried a blank test INX from CS3 into CS2 and it opens.
I'm assuming there's something in this particular CS3 newsletter file that's causing the snag, but have no idea what I'm looking for or how to fix it. A corrupt font, maybe? or corrupt image file?
I had a similar newsletter file last month that I did the CS3 --> INX --> CS2 thing with, and it worked fine as well. I just repeated that process with those old files and it still works, so the problem is with this new file. I'm not using any new plug ins or doing anything really different this month compared to last.
Any ideas? I'd really rather not have to recreate it from scratch, especially if it may not solve the problem -- it'd take a long time and we're in a bit of a hurry.
Thanks for any help.

I saw the hyperlink in there just by luck -- it was a long document and I was just scanning through, seeing what I could see. I went back to the InDesign CS3 file to remove it via the "Hyperlinks" panel, and resaved as INX, which opened in my CS2.
Unfortunately it didn't open in my colleague's CS2 after all though, which is why we were doing the INX deal in the first place... so we gave up and we're editing it over the phone. Real high-tech.
There really needs to be a plug-in or something next time around, Adobe, or preferably, built-in backward-compatibility like most other apps have. This whole "save as INX" thing is extremely annoying.

Mac OS10.5.6 CS2 printing problems

I cannot get my documnet to print correctly( alignment on the page) using CS2 on a Mac 10.5.6. I read several posts that this is a compatibility issue between InDesign CS and Leopard. And that there is not a fix? Is this true? And why in the world would the biggest design application company not be compatible with the latest Apple OS? It's not like Leopard came out last month? Any insight?

OK, let me try this again.
In terms of MacOS X 10.5 and all the 10.5.# double dot releases, I am sure that the compatibility problems are frustrating to you. They are just as frustrating to us. Don't you think that many of our internal +users are on Macintoshes? But even Apple admits (at least to us if not publicly), that operating system bugs were the cause of these myriads of problems that plagued not only the CS2 applications, but the CS3 applications as well. There were also issues with printer drivers and their interactions with both the application programs and the operating system. Thus, the problems had nothing to do with Apple "updating and improving" as much as Apple attempting to update and improve without quite enough concern for the ability of existing applications to continue to run unimpeded. (Years ago, I actually ran an operating system development group for a major computer company. The most important criteria ranking above that of new features was the cardinal rule that we not do any harm to existing applications or system programs. The application program vendor should not need to modify the applications to run on the new OS release. And likewise, a user should not need to buy a new application version simply to take advantage of a dot release or even a major release of an operating system.)
Quite frankly, I am actually glad that no one at Adobe promised you anything with regards to a combination of a particular printer, its driver, MacOS X 10.5.6, CS4, and particular printing settings. The combinations and permutations are mind boggling and believe it or not, we as well as our network of beta testers can only test a small subset of said combinations and permutations. If you find a problem with a current release of an Adobe application and you report it, we will attempt to track down the problem with the combination of OS vendor (Apple in this case) and printer vendor if necessary to find the cause, a temporary workaround, and hopefully a more permanent fix. Unfortunately, Adobe does not have engineers doing compatibility fixes for software that is no longer being licensed. Thus, we have some engineers working on patches and workarounds for CS4 at this time (and as necessary, collaborating with the OS vendor and printer vendors), but not CS3 or CS2. The majority of our engineers are working on the next major release of our software.Can that be that complex a fix? In terms of the misaligned page and your question "can that be that complex a fix," the answer is "yes, it could require an OS fix, a driver fix, and/or some application workaround which in total is indeed complex" requiring coordination between two or three companies and multiple development, support, and test organizations. Oh, by the way, exactly what printer were you having problems with. I checked this thread and I haven't seen you reveal that interesting little piece of information!
Going back to the Lightroom question, no, Adobe doesn't expect "everyone to fall in line with" the DNG format. But if Canon and Nikon, to mention only two of the camera manufacturers, make unannounced and/or undocumented changes to their proprietary RAW formats as part of their release of new camera models, it is very unreasonable to expect that Adobe or any other software vendor will magically have a means of decoding such formats the day such cameras are released. We deliver updates as best we can with or without the assistance of the camera companies. And if you must be the very first on your block to take delivery of a Nikon D3x or a Canon EOS 5D Mark II, you'd better expect that it may be a month or two or more before either Adobe or other vendors providing RAW format support will be able to support the new cameras. If the vendors were willing to publicly define and stick to a common RAW format, this class of problems would effectively go away. (Note that Adobe has been posting beta/pre-release versions of both Lightroom and Camera RAW Photoshop plug-ins on the AdobeLabs site to help minimize the pain to such early camera adopters using our current software versions!)
- Dov

Photoshop CS3 (nor CS2) won't launch since CS3 install

Since installing Adobe Creative Suite 3 Production Premium I can no longer open Photoshop. It repeatedly crashes on the launch window. For the sceptical, my CS3 Production Premium collection was all legitimately authorised and registered.
Of the other CS3 apps that installed (can't install Encore, Premiere or Soundbooth on PowerPC) they all open and run perfectly fine.
I uninstalled all CS3 and re-installed CS2. Now Photoshop CS2 won't open either (but everything else is still fine). Exactly the same problem, Photoshop crashes during the launch window.
What has CS3 changed to my system that prevents Photoshop opening and can I correct the issue? From searches on this subject Someone suggested repairing permissions before and after installing CS3. This had no effect.
Thank you for any help.
//-- edit- the crash seems to happen when 'Building TWAIN menu items' --//
Message was edited by: Frwthr

You can try trashing and regenerating Photoshop preferences when you launch.
Hold down command/option/shift while launching Photoshop. You will be asked if you want to get rid of Photoshop settings. Choose yes.
See if this works; you may have to reset some of your Photoshop preferences afterward. I'm not sure why you can't install the other applications.
Also, it may have something to do with activation; did you activate your copy of CS3? You should be able to have CS3 and CS2 both running as far as activation is concerned, but are they on the same drive? This might be a problem if one version is trying to read the other's settings during launch.

InDesign CS2 Printing Problems

I teach in a Mac computer Lab (mac OS X) and InDesign CS2 is a huge headache for me; my students can't print their work half the time. I read online a lot of member posts about InDesign CS2 printing problems. Would a CS3 upgrade help?

CS3 upgrades are no longer available now that CS4 is out!
Perhaps if you described your particular problems, members of this forum could assist you. Note however, that CS2 was not supported on MacOS X 10.5 (Leopard).
- Dov

Snippets: CS3 vs CS2

We're just moving up to CS3 from CS2.
In CS2, when I placed a snippet it was automatically placed in the position where it was when created. In CS3, I get a loaded cursor that wants me to click. In looking at InDesign help, I found there is a new preference under "file handling" that I THOUGHT would help, but it does not. I changed the preference setting to "position at original location", but I still have to click for the snippet to place.
I know it seems like it's not a big deal, but we have a script that places a snippet (among doing other things) and I really don't want it to stop for the user to click. They're used to things just showing up where they're supposed to be.
Is there another preference setting I'm missing?
Lisa

> Has anyone noticed a difference in Dreamweaver CS2 vs
CS3 regarding
> stylesheets
> and publication?
Only that DWCS3 renders CSS-based pages better than DW8 did
(I assume that's
what you mean by CS2).
> Could it be something else?
Definitely. Can you post a link to a page?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"catsr#1" <[email protected]> wrote in
message
news:flbkod$f2p$[email protected]..
> Has anyone noticed a difference in Dreamweaver CS2 vs
CS3 regarding
> stylesheets
> and publication? What I mean is, DW-CS2 shows my page in
layout form with
> the
> attached stylesheet and the pages look fine and publish
fine. When I close
> DW-CS2 and open DW-CS3 and open up the same files they
look as though the
> stylesheet is not attached to the file and when you
publish the file it is
> showing messed up without noticing the stylesheet is
attached. (<link
> rel="stylesheet" type="text/css" media="all"
href="includes/xxx.css" />).
> I've
> tried various ways of attaching the stylesheets but they
continue to not
> work
> or publish correctly in DW-CS3 and I have to close down
and open up CS2 to
> view
> the files correctly and republish them to make them look
the way they did.
> Basically, currenlty I can not use DW-CS3 for stylesheet
related designs.
> Does
> anyone know of this being a bug? Is there a fix? Could
it be something
> else?
> Have you had this problem? Thanks!
>

CS3 and CS2

I was searching forum and read that it may be an issue with installing CS3 and CS2 on the same computer. Can someone confirm this for me as true.
Thanks,
Tim

Never had any problem at all, although (disclaimingly yours) YMMV.
I should mention that my experiences are based on chronologically installing CS, CS2, and CS3,
i in that order.
(It might be important -- perhaps someone with lots of free time can experiment with different install orders.)
As the file extension for all three versions is the same (".indd"), Windows cannot link files made with different versions to their original creators, and using the Explorer, the latest installed version will lways open. However, each separate program can be started manually, and can open its own documents and older ones w/o any problem at all.

Every single box is outlined after conversion from CS3 to CS2!!!! Plz HELP!!!

Hi there guys,
I'm quite new to the forum, but I have come through an issue that is weird to me...
See: One of my clients I'm a freelance designer– is an ad agency whose only graphic designer is on marriage vacation.
This guy converted some files from Indesign CS3 to CS2 so I can go on whit the projects while he is out happily just married in Thailand...
The problem is, however, whit every single box, doesn't matter if they are text or image boxes or even empty boxes. Neither if they already had outline or not. They all have somehow come up whit a black outline. And I'm starting to lose my nerves on fixing that...
Moreover, there are some text boxes –footnotes and the like– that contain a web address or an e-mail direction. This "www.xxxxxxxxx.com" and the "[email protected]" stuff is outlined within the text box with the same black line that will disappear only if I type back the thing...
Is this maybe a known issue? Has anyone ever heard or experienced that?
Any workarounds or known fixes or whatever?
Thanks a lot for taking the trouble to read and answer!!!

The outlines around hyperlinks are just visual indicators for you so you'll know they are there (not all hyperlinks show up as URLs) and won't print. You should be able to turn them off in the hyperlinks palette if you want to. If you just re-type the hyperlink text it will no longer be a real hyperlink, if that'st required.
As far as the strokes on everything, I'm not sure. Is it possible there's an object style applied to all of these items and the stroke is now defined in the style. (Does CS2 support object styles? I've forgotten and don't have it on this machine to check). It could also be some sort of translation glitch in the move from CS3 to CS2.

Apostrophe glyph does not transfer from CS3 to CS2 by inx

Can someone please confirm this: The Apostrophe glyph does not transfer by inx from CS3 5.0.2(640) to CS2 4.0.5(688).
It does transfer by inx from CS2 4.05(688) to CS1 3.0.1(838).
It also does roundtrip in CS3, CS2, and CS.
This is not a problem for me now that I know about it. I just wanted to report it for the benefit of others, as this is a commonly used character.
I tested this with Times (T1) in a very simple file containing just the apostrophe glyph followed by the lower case "x". These tests were conducted in Tiger 10.4.11.
It seems like it may be related to the similar problem with bullet glyphs that has been mentioned by Sandee and others in this forum.
Al

I can reproduce the report by Klaus of being able to put in the "missing" apostrophe with a text editor. But using TextWrangler I was unable to find the "missing" apostrophe in the CS3 inx by searching for "'" or "0027" (the Unicode value for the apostrophe). Now, since IDCS3 is able to open its own inx including the apostrophe glyph, it must be encoding it in the inx in some special way. Exploring the IDCS2 inx for a test file with the string "CHICKEN 'N WAFFLES" shows that it is saved as "c_CHICKEN"+"&apos"+";N WAFFLES". Then searching from the top for the string "&apos", finds 5 instances of it. While a simillar search for "&apos" in the CS3 inx finds only one instance of it. Clearly IDCS3 and IDCS2 write their inx files differently. No surprise there. Searching the CS3 inx for *parts* of "CHICKEN 'N WAFFLES" locates: <txsr prst="o_u65" crst="o_u62" paln="e_cent" ptfs="c_Medium" ptsz="U_18" font="c_Helvetica"> <pcnt>c_CHICKEN </pcnt> </txsr> <txsr prst="o_u65" crst="o_u62" paln="e_cent" ptfs="c_Medium" ptsz="U_18" ligt="b_f" font="c_Helvetica" OTca="b_f"> <pcnt>e_SSSq</pcnt> </txsr> <txsr prst="o_u65" crst="o_u62" paln="e_cent" ptfs="c_Medium" ptsz="U_18" font="c_Helvetica"> <pcnt>c_N WAFFLES</pcnt> </txsr> Now if I paste in a copy of the lines : <txsr prst="o_u65" crst="o_u62" paln="e_cent" ptfs="c_Medium" ptsz="U_18" font="c_Helvetica"> <pcnt>c_N WAFFLES</pcnt> </txsr> after the first occurrence and save the file from TextWrangler, it will then reopen in IDCS3 with the text string "CHICKEN ''N WAFFLES" (note the two apostrophes). But in the case of the string " 'x" as the only contents of the text frame where the apostrophe *does* transfer from CS3 to CS2 it is encoded this way: <txsr prst="o_u6b" crst="o_u68" ptfs="c_Regular" ptsz="U_18" ligt="b_f" font="c_Times (TT)" OTca="b_f"> <pcnt>c_ '</pcnt> </txsr> <txsr prst="o_u6b" crst="o_u68" ptsz="U_18" font="c_Times (TT)"> <pcnt>c_x</pcnt> </txsr> Note the "&apos" in that code, which is what CS2 is able to import. Conclusion: IDCS3 does indeed save the apostrophe in the inx in a completely different way than IDCS2, and in different ways under different circumstances. So the bug is that Abobe forgot to take into account how the new way of writing the apostrophe would affect IDCS2's ability to import it. Al

Adobe Photoshop CS3 had encountered a problem V10.0.0.0

Photoshop V10.0.0 will not open. It crashes as its loading the Twain drivers at start up. I am running Windows XP.
I've tried deleting the preferences file, reloading Photoshop and, as a desperate measure, deleting and reloading CS3. Nothing has worked. I tried upgrading photoshop but still no luck. Set my default printer to PDF, still nothing. Disabled my firewall, still nothing.....
The worst bit is its been working quite happily since June 07 and then in late Nov early Dec it decided not to work. I also had a printer problem during this time and reinstalled the printer software, but photoshop wasn't working before I did that.
The error I get is:
Adobe Photoshop CS3 has encountered a problem and needs to close
Error signature App Name: photoshop.exe
AppVer 10.0.0.0
ModName: unknown
ModVer: 0.0.0.0 Offset 0.0.0.0.0.0.0.4
Any assistance would be great - I am getting desperate!
Regards
Sally

When I uninstalled my Dell 944 printer Photoshop worked. When I reloaded my printer it crashed again. It seems to crash everytime it loads the TWAIN part of the photoshop opening screen.
I've tried downloading and installing the latest driver from Dell for the printer but its 2005 and the same as the one I have so no luck there.
I still need my printer to work (its my scanner as well) but I am desperate to get Photoshop back! Any clues??

Exception in XML Parser (format problem?)

Hi Experts,
I am working on IDOC -> AS2 Configuration and the AS2 Configuration has the below structure
<RecordSet>
 <Row1>
 <row1 - field1>
 <row1 - field2>
 <row1 - field3>
 </Row1>
 <Row2>
 <row2 - field1>
 <row2 - field2>
 <row2 - field3>
 </Row2>
 <Records>
 <Record1>
 <Record1-Field1>
 <Record1-Field1>
 <Record1-Field1>
 </Record1>
 <Record2>
 <Record2-Field1>
 <Record2-Field1>
 <Record2-Field1>
 </Record2>
 </Records>
</RecordSet>
We are getting the expected Structure when we AS2 Receiver has the xml format. But while doing module development with the strctxml2Plain, we are getting the below error in RWB CC Monitoring.
Message processing failed. Cause: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException''; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException'
Any ideas, why this error we are getting.....
Thanks in advance,
Regards,
Vasu

Hi Vasu,
Not in the Mapping of IR.
In BIC Mapping Designer you have to test with the standard Mappings by providing the sample file whether the Conversion is happening correctly or not.
You have to take the same input file that what ever you are having now.
So that it will say clearly what is the problem in converting the XMLto the required EDI Format...
Check whether you have any Date Format Values are comming from the input file.
Regards
Seshagiri

Dreamweaver CS3 has encountered a problem...

I have searched the interent for hours trying to resolve this issue.
Everytime I open up DW, i get the error message:
"Adobe DW CS3 has encountered a problem and needs to close."
When i click "send error report" or "Dont send," DW closes.
If I just leave that alone, i can work in DW.
The problem is its also doing it for Adobe Acrobat 8.0.
I am operating on XP.
I have tried to go in and unistall the entire Adobe Creative Suite. I click on "remove" and nothing happens.
I am really frustrated with this. Any help is appreciated.

Does CuteFTP work on it's own when DW is closed?
I too, use CuteFTP in conjunction with DW and have for many years and have never had such a problem.
Are you doing anything specific in Cute FTP when DW crashes?

Attempt to process file failed with Exception in XML Parser-format problem

Hi all,
Iam getting an unusual error in the J2EE stack in XI.
And the message is:
006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)' 2006-11-30 17:31:07 Error Exception caught by adapter framework: null 2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
My scenerio iam posting IDOC to a flat file with content conversion in the receiver side,the mapping got executed successfully and in the audit log i found that the error was after the 'Start converting XML document content to plain text'.
This means that error occured during content conversion of XML to the prescribed file format.
Can anyone suggest any better approach using which we may trace the junk data in IDoc. Manual adhoc approach could take time and is error prone.
Thanks in advance...
karun

Hi Bhavesh,
Thanks for the early reply. I checked the mapping and everything is fine and the output is also in valid XML format.
The audit log shows that the mapping got executed successfully and the error is after the step 'Start converting XML document content to plain text '. Is there any constraint in the file adapter regarding the message size for parsing.
2006-11-30 17:30:50 Success Transfer: "BIN" mode, size 2912595 bytes, character encoding -
2006-11-30 17:30:50 Success Start converting XML document content to plain text
2006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)'
2006-11-30 17:31:07 Error Exception caught by adapter framework: null
2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2006-11-30 17:31:07 Success The asynchronous message was successfully scheduled to be delivered at Thu Nov 30 17:36:07 GMT 2006.
2006-11-30 17:31:07 Success The message status set to WAIT.
2006-11-30 17:31:08 Success Acknowledgement creation triggered for type: SystemErrorAck
2006-11-30 17:31:08 Success Acknowledgement sent successfully for type: SystemErrorAck
2006-11-30 17:36:08 Success Retrying to deliver message to the application. Retry: 1

I am exporting a pages doc to ePub and I keep getting formatting problems any idea thx in advance

I am exporting a pages doc to ePub and I keep getting formatting problems any idea thx in advance

Since you don't say what the "formatting problems" are, all we can say is:
"There, there. Hope they get better."
Peter

CS3 to CS2 Format Problem

Similar Messages

Maybe you are looking for