1 person found this helpful
Point by point, let me try to help.
Think of each piece of your intended book as an assembly of modular parts. You can create sub-assemblies (InDesign documents) built to tight specification (templates, paragraph/document styles, Table/cell styles, libraries, etc.).
With that in mind, let's go point by point:
1) It's easy to create write once/place all elements like your document numbers. Rather than think of them as footers, per se, but as master page folio elements set up at the bottom of your pages within InDesign.
2) I'm afraid I have to respond to this question with other questions. When you're asking about "variables" causing version/issue problems, are you referring to them as text/image variables placed through some data-driven solution? Or are these variables you place manually into each document, and you're seeing versioning problems creep into your documentation? Fixes each problem are quite different than the other.
3) Yes. You can build them into a template, using master page elements, then populate them as needed for each document. If the book requires multiple InDesign documents, you can copy and paste each master between every InDesign document for the book.
4) Update your language? As in some data-driven front end? Hard tellin' not actually knowin' what you're doing right now. But as a general rule the answer probably lies in how portable data exports are, The more options you have for exporting data to InDesign, the better chance you have of finding a workable data solution for your documentation needs.If you're talking design language? It'd be as tight as your design templates.
The devil's in the details, of course. But if you can share answers to some of the questions here, and consider some of the suggestions in that light, we can help you get where you want to be. There are a lot of sharp people on here who can help.
Thanks Randy -
We are using different Master Pages for the different elements such as cover, TOC and Chapters (aka Sections). We inserted "running Header" variable in the header for the section name to appear and "custom Text" variables for the document part number, Company name and copyright info in the footer. But when we created the next document and updated the information, our original document indicated that there were updates and when it was updated the info changed to the new document info. Are we using the wrong kinds of variables? Or using the master wrong?
The standard language is created today to provide elements such as an explanation of function without the details for the specific assembly. We make thermal management systems, utilizing common components such as our controller, our fans and pumps. Specifics for the assembly are entered in tables in the text today. My expectation is that we can pull from a common .txt file for the words, using a linked COMMON file and when this text file is updated, we could go into the end document, click to update to the linked text file. The table of specific info can be edited in each separate book when it is assembled. Same for specific images where we want a placeholder for the specific image in the final book.
I thought we could create the master pages to use across-the board, add the standard text for each of the elements as chapters in a book, then combine them to make the "NEW" document for the specific assembly, adding any special elements that assembly requires. Then in the NEW document, edit the text variable and have it apply to ONLY that new document. Instead it updated all the documents. That's why I think we are using the text variable wrong.
I think I've gotcha.
You're using InDesign-generated text variables in your documents, manually entering the field value, which then populates the variable. What this does is create background, stand-alone data referenced by InDesign. Since the field reference has the same name, but the information is different, it wants to update information anywhere the field reference is applied.
Different documents referencing the same field + changing the field value = updated field references in multiple documents.
You've got two ways out here: Change the field names or eliminate the variable.
Changing the field name can be done, but eliminating the variable is much easier.
Once you're done with the previous/current issue, convert the variables to text:
- To convert a single instance, select the text variable in the document window, and then choose Type > Text Variables > Convert Variable To Text.
- To convert all instances of the text variable in the document, choose Type > Text Variables > Define, select the variable, and then click Convert To Text.
This keeps the live variable in your new document, and populates it with current variable information. And since you've killed the variable in your old document by converting it to plain ol' text, it won't change when you change the value for the next version of the document(s). Reading the link I provided above, then printing it and keeping it handy will walk you through the process of making text variables work for you.
Note: With careful version control, you can manipulate this capability to remedially correct previous information-corrupted versions. Just work from old to new, first entering values for the oldest-corrupted file, converting those variables in the InDesign document to text and then saving the old file without text variables to update. Follow these steps sequentially to correct each document, and you'll be able to fix faulty old documentation with a minimum of pain. Ask me how I know ...
Hope this helps. I think it will. If this works for you, please mark this question thread as answered. That way the moderators will archive this so it can help others who find themselves in a similar bind. This is a great place to get answers to your InDesign questions. If you have problems, there are lots of smart people around here who can help.
That sounds perfect! Convert the variable to text after we've used it to populate around the document.
Yes, we'll give that a try when we (the two of us working on implementing the use of InDesign) get together next week. If we have more trouble, I'll capture the specifics and repost.