CreativePro Forum

Return to Member Forum

• Author
  Posts
• • January 4, 2011 at 5:33 pm #58287
    Dwayne Harris

    Member

    We do a lot of jobs where we supply keystrokes and the designer flows in the type. As we deal with Quark and InDesign, we use Xtags for importing files. It's easier for markup and importing. The issue is that many designers want us to provide them with RTF files that they can flow it. We export from InDesign, but there is paragraph style over-rides. I don't know it's an issue with InDesign, Word, or XTags. When I export their problem file I see these codes (NOTE: They are not in the file I sent, but when they import into their file which has style sheets written). Our file we import into is blank and no styles as it's keystrokes.:

    <pHyphenationLadderLimit:><pHyphenationZone:><pKinsokuTable:>

    <ParaStyle:TX><pHyphenationLadderLimit:0>

    <pHyphenationZone:0.000000><pKinsokuTable:Soft>

    I broke up the code so I would not stretch the screen.

    Has anyone come across this?

    Also–We are deciding to export the files as tagged ID files instead, but there are issues with that, but I don't think it's a big deal. Occasionaly, when the file is imported, the import dialogue box appears as plain text, and not tagged text. They have to open the tagged file in Word and re-save as a text file. To me it's not big deal, but they expect 100% no issues. And, for some reason, ID CS5 sometimes sees a tagged file as text only, instead of a tagged text file. One Mac will see it correctly, and one won't. No rhyme or reason, but I figure something that just happens. Thoughts?

    And lastly (whew–I told you this would be long): If I import a tagged ID file into CS5 (without style sheets written as I just want to be sure it flows in okay with no errors), it defaults to Minion Pro. My default font is Times. It comes in as Times in CS3, CS4, but in CS5 it insists on Minion. Thoughts?

    Sorry for the length, gang, and I apologize. I've gotta read through these threads as I've been gone for a while. I hope all of you are doing well.

    doc

  • January 4, 2011 at 6:25 pm #58290
    David Blatner

    Keymaster

    I have seen the kinsoku stuff come in from Word files, but I have no idea why it's there. It almost always just requires doing a remove overrides in InDesign. Frustrating.

    CS4 and earlier had a “default font” of Times. CS5 switched to Minion Pro for a variety of reasons. If you need Times, you'll have to build that in to your paragraph style.

  • January 4, 2011 at 6:36 pm #58291
    Dwayne Harris

    Member

    Thanks Dave. I figured it was a CS5 thing. Damn it, it seems like CS5 changed so much stuff and made some things worse.

    We're gonna have to go with tagged ID text files, I guess. That was always my preference, but years back designers had brain farts when importing tagged files. They were used to copying and pasting word files, and didn't know how to import. We got them used to RTF files, and now we need to go tagged text files.

    I figured the Minion thing was CS5 only, as I had no problems with other versions.

    Appreciate the help.

    doc

  • January 12, 2011 at 6:35 pm #58360
    Dwayne Harris

    Member

    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.

• Author
  Posts