![]() ![]() I have total control over the editor workstations and we've had a customized "normal.dot" for years. I think we're probably going to have to make the running of the "cleanup" script part of the workflow. That still counts as an override, of course. a Korean font would be named Gulim on one computer and 굴림 on the other computer. Zero of my contributors are working in English, so I've always had the create-charstyles-and-clear-the-rest-of-the-overrides step in my workflow, because even in the days of "seamless" CS3 import there would still be a lot of divergence induced by the fact that e.g. When I have some spare time I will do some test imports to see if I can find something worth a bug report, but to be honest, CS3 Word placing was never as seamless for me as it was for you. I am uncertain, but I suspect that both the Word file format and the Word import filter in ID's Place tool are moving targets for developers on both sides. If your editors are inside your organization, or otherwise willing to submit to delousing of their Word templates, then it might reduce the frequency of spurious overrides being applied in InDesign upon placing your Word files, because you could ensure that the styles that were being altered by simply opening docs in Word and working on them actually had the same definitions in the Word document template as they did in InDesign. Clearning 'em out has helped a great deal in a a number of cases. You made that completely clear in your original post, I just had a momentary lapse of reading comprehension.Īnother possiblity for resolving your difficulties: To what extent do you have control over the workstations used by the editors? I've smoothed out some Word-file-import issues in the past by examining the normal.dot of some contributors and found that they've acquired years' worth of cruft, which in some cases (trial installs of translation memory tools, for example) has induced all kinds of style-override nonsense. Sorry, Allison, I should have sworn off posting on the Internet on a day when I've not had any caffiene at all. Importing the Word styles, using auto-renaming so that InDesign explicitly does NOT match styles. This Word-file-import issue might be new to CS5 for English-language-only users, but I've been clearing all overrides (or, as above all remaining overrides) on Word documents in a wide variety of languages for some years now. If you are confident that the overrides induced by Word import should not be included in the InDesign styles, then why not simply return to the style-mapping-import workflow? Include a new step: "Clear all overrides after placing Word document." Or, alternately, I might run a script like PrepText first, then clear all remaining overrides. I've tried saving the Word files as doc or rtf instead of docx but this doesn't make a difference in this problem.Īny help or advice would be much appreciated.Īfter importing text, all the styles in InDesign have local overrides assigned to them that don't make sense (hyphenation exceptions, tab settings). This is frustrating because it used to be smooth and seamless and while some new features of CS5 are great, it's annoying that it's broken this fundamental function! (see screenshot)Īre we left with our original work-around? Importing styles then manually deleting and replacing them? ![]() All the Word styles are Times New Roman so all superscripts in InDesign are coming in as superscript + TNR. The problem is those local overrides in Word-InDesign not only respects the italic or superscript, it also respects the font attribute. With Word 2011 docx files, the import works almost like it did in CS3, the styles almost come in cleanly: If the style in Word has NO local overrides, such as italics or superscripts, the InDesign style is correctly applied. This has gone on for several months and we've now upgraded to Office 2011 but that hasn't solved the problem. Then delete the Word styles one by one from the paragraph style panel, replacing with the desired ID style. So I'm left with importing the Word styles, using auto-renaming so that InDesign explicitly does NOT match styles. Automatic mapping on import no longer seems to work: After importing text, all the styles in InDesign have local overrides assigned to them that don't make sense (hyphenation exceptions, tab settings). ![]() would be respected as local overrides in InDesign. This worked fine in Word 2004 and InDesign CS3: Word "text" style would map on import to the InDesign "text" style, even though they had totally different attributes. ![]() Designers use import options to match the Word styles to the ID styles. Does anyone have any experience with importing styled Word docs into InDesign?Įditors style their Word documents with some basic styles (Text, References, Headline, etc.) using a Word template that I created. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |