In a Typefi workflow, the production designer creates a Typefi-ready template in Adobe InDesign. The template may include Typefi Elements, which are objects or groups of objects distinguished from the core text in a publication. Depending on the complexity of an Element (controlled by the production designer), you might be prompted to provide specific content—such as text, image data, or Field data—as you insert the Element into Word.
Insert a Typefi Element
- Place the cursor at the end of a paragraph, before the paragraph return character.
Always insert Elements at the end of a paragraph. Inserting Elements mid-paragraph results in the paragraph 'breaking' at that point. In cases where an Element must be placed as close as possible to related topic content in the text, add an Element Reference in that location after inserting the Element. This reference may appear anywhere within paragraph text but is best at the end of a paragraph.
- In the Typefi tab within the Insert group, click Element.
- In the Select Element dialogue, choose the Element you want to insert and click OK.
If you are inserting a Floating Element with named variants, you can specify which variant to use. Floating Elements with unnamed variants will not display an option to choose a variant. The default variant is Automatic for named variants, which means that Typefi will decide which variant to place during the automated page composition process. This also applies to Elements with unnamed variants. To choose a variant, click Change and choose the variant.
The Element is inserted into the Word document.
You can edit the Element at any time.
- If your workflow uses InDesign Server 2020 or 2021, you cannot insert a video Element in a Typefi Writer document and publish it. If you try to publish a document with a video Element, you get this error message: Error: Request failed because the underlying functionality is no longer available in the current version of the application. This error occurs because Adobe now blocks Flash content from running. There is no workaround at this time.