Okay, this one is scary. I've had 2 jobs in the last couple weeks go bad by exhibiting this behavior, but I can't recreate it on purpose. One job was a customer-supplied PDF, other was an InDesign file from which I exported the PDF using my usual settings. Applications in play are Acrobat Pro 10.1.4, Neo 10.0.2, and Photoshop CS5.1 running on Mac OS 10.6.8.

What's happening is there are some superscript characters that are dropping down to the baseline, and 2 occurrences of a space being put between an opening quote and first character ("Wouldn't.." shows up like " Wouldn't..."). This doesn't happen to all the superscripts in the file, nor all the quote marks.

My workflow on both jobs is to open in Acrobat, do a Save As to rename, run my usual preflight routine, remove the crop marks, then save and close. Open in Neo and use it to open the images in Photoshop to correct, then close and save document.

Since I can't recreate the problem on purpose, I don't know if it is occurring before or after I edit the images. I've worked here for over a year and these jobs are routine for us (one is even a monthly publication), and the problem has never happened before. None of these programs, nor the system, has been updated recently. The only change on my machine is that I did install CC last week, but didn't use it on these jobs. I think the one job happened before the CC install, but I can't be positive.

Screenshots show the superscript as supplied, and after me working on it. Got the boss breathing down my neck to explain this.

You can always go with the popular choice now.

Does it only happen to the same font?

Just wondering why you are opening them in NEO to edit the images when you could do it in Acrobat => Photoshop?

I know you said you can't recreate it on purpose but if have you tried to go back and recreate the one from Indy that you did and perform the exact same steps to the file again and check it after each step to try to narrow it down to where it is happening.

Any chance CC installed some newer version of a font with the same name? Or a similar font that is causing clashes? Even if you're not using a CC font, it could still cause some conflicts somewhere, I'm thinking. These font things can be insidious.

Quote from: Joe on October 29, 2013, 09:02:19 AMDoes it only happen to the same font?

Different fonts.

Quote from: Joe on October 29, 2013, 09:02:19 AMJust wondering why you are opening them in NEO to edit the images when you could do it in Acrobat => Photoshop?

Because half the time Acrobat won't let you edit the images. Neo always lets you.

Quote from: Joe on October 29, 2013, 09:02:19 AMI know you said you can't recreate it on purpose but if have you tried to go back and recreate the one from Indy that you did and perform the exact same steps to the file again and check it after each step to try to narrow it down to where it is happening.

Yup. Can't make it happen again.

As for the fonts, I guess CC could have installed something somewhere, but I'm dealing with PDFs with fonts embedded, so nothing should be getting replaced anywhere along the line.

It's got to be happening in 1 of 2 places - either during the initial Save As... in Acrobat, or when I save it from Neo.

I've never had Acrobat prevent me from opening a file in Photoshop. Photoshop prevents me plenty though (indexed images...NChannel images etc...) so is NEO changing images like this that then lets Photoshop open them.

I have used Acrobat X and Photoshop 5 in the past and never noticed this issue and no one ever complained so I would suspect NEO right off the bat. Do they even make/update NEO anymore? Just wondering, if it is an older version if it is understanding everything in newer PDF's?

Quote from: Joe on October 29, 2013, 10:05:21 AMI've never had Acrobat prevent me from opening a file in Photoshop. Photoshop prevents me plenty though (indexed images...NChannel images etc...) so is NEO changing images like this that then lets Photoshop open them.

Well, I don't know if it's Acrobat or Photoshop at fault when that happens - all I know is that trying to edit an image from Acrobat doesn't always work (as you said - indexed, NChannel, etc) and Neo allows it. It doesn't change the images at all.

The Neo version I have is fairly recent - it seems to handle everything fine (except for this sudden scenario, if indeed Neo is at fault.)

Since I can't recreate this, my best bet is to watch out for it carefully next time I'm editing images from Neo. I don't usually do a Save As at that point, but I will so I can see if it happens in Acrobat or Neo. Can't really not use Neo because we correct a lot of images, and if the Acrobat/Photoshop combo can't get it done I still need to get it done.

You can edit the images from Acrobat if you also have Pitstop by resampling indexed images by 1 dpi (if it is 300 dpi resample to 301 - this will remove the indexing) or convert NChannel to CMYK/grayscale before trying to open in Photoshop. Though it will be an extra step for every image so they may not be feasible but it might help for testing if you can get the problem to repeat somewhere. Photoshop is where I get the errors so it seems if you don't get the errors when opening from NEO that NEO must be changing those images. Does NEO still identify them as indexed/NChannel images?

That's a good tip about resampling - a pain, but worth remembering for future use.

I'll have to see what Neo says about indexed images next time I get one.