Thanks, Eugene.

Thanks, David. I’ll check with the powers-that-be at work about converting RGB to CMYK when exporting.

Sof ar as making high-quality PDFs, we have presets that we have to use from the printing houses. But I’ll check out the video in the next day or two (when I have time).

Thanks

David–I agree that the book publishing world is slow to change, especially the printers. But unfortunately for those in the field, RGB is a no-no, though it may be okay elsewhere in other fields.

We also supply PDFs to the printer. And one of their presets warns us if anything RGB is in there.

I’m not sure if this will help or not, but we had a problem at work last week.

When we all upgraded to the “Cloud,” a month or so back, we all got CC2014. We didn’t know that CC was still available (it is, but it’s a screwed up way to get it). Anyway–I googled it and we got CC installed on all the machines. EXCEPT for one. It refused to show the CC download option.

We called Adobe and 20 minutes later the option appeared.

You may want to call them. They even said the Extension Manager was buggy.

And don’t get me going on how buggy it is with XTags. One minute I can open a file, the next minute I’m told it’s either incompatible or out-of-date (even though it’s the latest available). I hate this

You need to resave the art in Photoshop as CMYK.

I’m the same as you, i.e., working with tagged text files. I HATE importing word files.

A few thoughts:

1) They used the actual italic font and not the fake italic (i.e., the palette)

2) If you are using document font (instead of Suitcase or some other font management program), maybe the italic font is not in the document font folder?

3) Did you try to resave as a Word file? I know from experience that RTF files are wacky as heck. In fact, I had an issue back in CS5.5. We would tag a file using XTags, import into Indesign, and then back it out as a RTF file for the designers. For some reason the RTF file would override ID’s justification and hyphenation.

I don’t trust RTF files at all. Too many issues.

I haven’t upgraded to Yoesmite, as it just came out and I usually wait a little bit.

So far as CS3, it’s not supported.

You may find this link handy. It shows what is and what is not compatible with Yosemite:

https://roaringapps.com/apps?index=a

If that does not bring you directly to it, here’s the main page:

https://roaringapps.com

EDIT: The site recommends using the latest version of Safari or Chrome. I accessed it with Firefox, but it was a bit slow.

That’s why I use a character style for my running heads. And I set it up to end at an end nested command.

I work on a lot of books where the running heads are too long. Usually when there is a colon it in, and they decide not to make it a chapter sub title. So in the instances where one is too long, I insert a end nested command before the colon.

I’ve also found using a character style much easier than paragraph style, especially if I have multiple style sheets for chapter titles (such as CT, CT2, CT3, etc.), which have different spacing below for even lines. Instead of creating three master pages for those elements, I can use one because of the running head character style.