Reply To: Tagged Files versus RTF (long post)

UPDATE: The over-rides for RTF files are definitely CS5, so far as I can tell. I have tried various files and jobs in CS3 and CS4 and I don't get the issue. And I was able to get rid of half the over-rides in CS5.

So I can explain better, our workflow is as follows:

1) import XTags files into ID (new document, default settings).

2) export as RTF

3) designer imports into his/her file with style sheets made and H&Js personalized

Now, normally, the designer gets the files and flows into his/her document and stylesheets come through and everything is nice and dandy. But in CS5, when the designer imports the file, there are those hypenation and justification over-rides as well as others which you can see if they export as a ID tagged file from their document.

From what I've been able to figure out and test: ID CS5 is exporting the default settings into the RTF file, and it's over-riding the designer's file. I don't have that problem with CS3 or CS4.

And, if I can match all the document settings EXACTLY in my default settings, I don't have an issue. Now, we all know that it's impossible to make my default settings match a dozen designers' settings.

For some reason CS5 insists on embedding the default settings into an RTF file.

I'm in the process of convincing the publisher in question to accept ID-tagged text files, but they are hestitant. I can say from past experience that many designers do not know how to import tagged text files. They are used to just opening the RTF file and copying and pasting [ :( ] Or they can't comprehend that there is no different between “placing” a RTF file or a tagged file.

I've been testing for the past few days (a few hours a night) and it seems to be a CS5 issue.