Make sure you set your page size right, and do so right away, at the start. The VERY first thing to do is understand your page size. But to really understand the page size, get a sheet of paper the size of the page you are creating. Physically seeing what you are about to work with makes a big difference. May as well get that pesky configuration out of the way early. However, every good template has a lot of setup that a user hardly ever sees.
FrameMaker includes a bunch of default reference pages. You can control the appearance of quotation marks, spacing single or multiple, and if a space can start a paragraph , what characters allow line breaks, and even the appearance of Superscript, Subscript, and Small Caps in your text. Metadata is additional information about a FrameMaker source file or book that is transferred to the PDF document when converted using the Adobe Distiller. It also provides background on the file that is currently open, so you may as well put some information in there by default and remind users of the template to update it.
FrameMaker has a lot of stuff you see and some that is hidden that you need to set in the template. The best way to set this information up work with a bit of sample content a few paragraphs in unstructured FrameMaker, or a couple of elements and content in structured FrameMaker , so you can clearly see the impact your changes make. In structured FrameMaker, when new elements are inserted, a dialog may appear that prompts you in regards to attributes.
And, if you are like me, then you likely want to disable that. One last template trick to leave you with. When you insert a table, you see a bunch of default options. The number of rows, columns, and even the types of paragraph tags that appear in a table. Now you can! Or contact me at Publishing Smarter to learn more about training in FM and other services. Email Address. Terms of Service Privacy Policy. Page Size Sounds easy, right? Click Custom. Set up the dialog with all your dimensions, columns, pagination, and other settings.
Finally, you need to copy the application files into the directory where the structured application definition expects them. Copy the proposal. Obtain a copy of the standard files, and modify the provided DTD or schema file to match your requirements. Once you have your structure definitions, you need to set up the structured application. Open the structapps. The Structured Application Designer allows you to create a structured application using a graphical wizard. The Structured Application Designer is displayed as follows:.
Select a base Application on which the new application is based. To load a new set of base applications, click Load Applications and select the relevant structured application file. The list of applications is automatically populated from the selected structured application file. By default, the application is saved in the structapps.
To change the filename, click Save As and select or enter a new filename. Optionally, to set advanced settings, click Advanced Settings and make your desired selections.
All elements are loaded in the EDD interface. Click Save to save your changes or Reset to roll back to the last saved state. To generate a new template, select the corresponding EDD file and click New from the Template section. Add any other required configuration settings, such as handling of conditional text and external cross-references, in the structured application definition. This helps simplify rule generation, since you have all the settings at one place, and do not have to remember any rule syntax.
The Rule File Maker dialog is displayed as follows:. Import-Export Settings : These settings are applicable for the reading and writing operation. Export-Only Settings : These settings are not covered in the Import-Export Settings and are only applicable for the writing operation.
The Import-Export Settings section is divided into four sections:. FrameMaker, then displays a list of elements. Entities : Displays the list of all entities that are present in the DTD. The Export Only Settings section is divided into three sections:. In addition, each FM Object category lists the markups mapped as that object. When saving the rules, FrameMaker saves only the elements and the rules that have been modified modified elements have their values marked in bold, on the right pane.
Default behaviors are not saved. If prompted, select the Proposal application. In an XML or a text editor, modify the file you just exported. Save the new XML file. Verify that the XML file imports correctly and that formatting is applied automatically. Every structured application has a configuration file that defines the behavior of the structured application.
Learn how to use the Configuration File editor in FrameMaker. Every structured application may include an XML configuration file. The configuration file is optional and contains attributes and their suggested and default values. When opening a structured application, FrameMaker reads the corresponding configuration file if it exists and populates the attribute values automatically.
The attribute editor allows you to change these values, when using the structured application. The Configuration File Settings dialog is displayed as follows:. To load an existing configuration file, click Load Configuration File and select the file. Set the configuration values as desired. Click the value column of the choice or default to be changed and enter the new value. To insert a new choice, right click the row above which the choice is to be placed, and select Insert Above.
To delete a choice, right click the choice and select Delete. To save the configuration as a new configuration file, click Save As and enter the new filename. FrameMaker checks whether the current document is an EDD. If so, the Open dialog box appears and you can specify the CSS file.
If the EDD contains formatting rules, the CSS properties are appended to the existing rules if the properties are unique. Multiple CSS files can be imported sequentially for multi-level formatting. When importing element styles, FrameMaker retains the context information element property or selector from the CSS and imports it into the appropriate EDD contexts.
The Import CSS dialog box appears. Select the application that was used to create the EDD file. Click Continue. Cascading Style Sheets let authors attach styles, such as fonts and spacing, to structured XML files. CSS2 format is a W3C standard. When you choose the Generate CSS2 command, styles from well-formed structured documents are generated, based on the formatting information available in the EDD associated with the source document. FrameMaker exports style information only at the element level.
For example, if you apply a style to only one particular word in the Text element, that one instance of style is not exported. FrameMaker validates the document structure against the associated schema upon both import and export to XML, but does not retain all schema information upon export.
You can import an XML document that references a schema file, and you can specify a schema file in your structure application, to use for validating a document upon export to XML.
For a specific XML document, you can include the path of the schema file in the XML using the attributes noNamespaceSchemaLocation or schemaLocation depending on whether your schema includes a target namespace or not. To specify a schema file for use in exporting XML, modify the structapps.
Save the XML using a structured application. In this workflow, a DTD is generated automatically as an intermediary file from the schema given in the XML document, and you do not modify it. Each command opens a File Choose dialog box that allows you to specify the schema file, then a Save dialog box in which you specify where to save the resulting DTD file.
This will make sure that FrameMaker works correctly with your template. Validation of input and output XML is still performed against the schema. The scope of a namespace extends beyond its containing document. Because a single XML document can contain elements and attributes that can be used by multiple software applications, you can use namespaces to differentiate which elements and attributes are to be used by which applications.
Software applications that process XML use namespaces to recognize which tags and attributes they are designed to process. Names from XML namespaces may appear as qualified names, which contain a single colon, separating the name into a namespace prefix and a local part. The combination of the universally managed URI namespace and the document's own namespace produces identifiers that are universally unique. FrameMaker supports namespace usage for all elements in an XML document.
When you import an XML document containing namespaces, all namespace information is preserved. You can also use this command to view the definition of the prefix on an element tag and select the element that defines the prefix.
By default, namespaces in FrameMaker are handled as namespaces, appearing in the Namespaces dialog box. However, you can disable namespaces in the application and have them handled as attributes instead, appearing in the Structure View. In the Namespaces dialog box, click Select Defining Element to view the namespace for the selected element in the Structure View. To close without saving your changes, close the dialog box without clicking an option.
Legal Notices Online Privacy Policy. Learn how to get started with structured applications, the significance of formatting in the structured application In unstructured FrameMaker, setting up an authoring environment requires only a template file.
You can link elements in the EDD to formatting in three ways: Formatting template You can assign formatting based on the various tags paragraph tags, character tags, and so on in a template. Format change lists You can create named formatting definitions in the EDD. Embedded formatting You can specify formatting by writing the formatting into each element definition. Structured application The structured application lists all of the component files in your structure implementation and provides configuration information.
Structured templates All FrameMaker structured applications require a structured template. Content analysis The term content analysis describes a process in which you review existing documents to understand how they are designed and what implicit structure they contain.
Note: A similar problem occurs when creating unstructured FrameMaker templates. You want to minimize the number of tags that must be maintained while providing all of the tags that are needed to create your content.
Use a standard Build your own You are required to deliver content that follows the standard. The structure needs to match the content precisely. A longer implementation period is an acceptable cost to ensure you can build exactly what you need You do not have the technical expertise or resources available to build your own structure. Elements The basic building blocks of structured documents are elements. A complex element can have attributes and can: be empty. Elements can have values within a specified range of valid values.
Attributes Attributes supply additional information about an element. Element rules Following seven rules control how the elements are used in terms of their sequence, number of occurrences, and group.
All Indicates that child elements can appear in any sequence but must appear at least once. Choice Indicates one or the other child element can occur. Sequence Indicates the order in which the child elements appear. Element Groups Elements can be grouped under a group declaration. Attribute Groups Attributes can be grouped under an attributeGroup declaration.
XML schemas define the following: List of elements that can appear in a document Attributes that can appear in a document for an element Hierarchy of elements—which elements can appear as child elements Sequence of child elements Number of child elements The data types for elements as well as attributes Default and fixed values for elements and attributes XML namespace XML namespaces allow the same document to contain XML elements and attributes taken from different vocabularies, without naming collisions.
Opening or importing a schema You can import an XML document that references a schema file, and you can specify a schema file in your structure application to use for validating a document upon export to XML. Following are the basic steps to get started with structured authoring in FrameMaker.
Analyze requirements Before building the proposal template, analyze existing proposals to identify their components. The proposal example results in the following sequence: Title Executive summary: Title, One paragraph Project description: Title, One or more paragraphs Cost: Title, One or more paragraphs Schedule: Title, One or more paragraphs Note: You could probably build the EDD for this simple example without formal content analysis.
For larger projects, though, content analysis is critical. You use the same guided editing environment to create the EDD that you use to edit other structured documents.
Define child elements Position your cursor at the bottom of the structure. Note: Like the paragraph tags, the information you enter is case-sensitive and space-sensitive. Test the results Save the EDD.
Until you save a document, it is not available in this list. Open the EDD. The DTD is now ready to be used. Build a structured application Learn how you can build a structured application in FrameMaker. You also need a structured template that contains formatting and EDD information. Delete all content from the file. A structured template must be empty. Now, you are ready to configure the structured application. If you set up the applications definitions correctly, Proposal appears in the drop-down list object.
In the xml folder, create a proposal folder. Build structure files Decide whether to use an existing standard or create your own structure. Create structure files without using an existing standard In FrameMaker, create an EDD that matches your structure requirements. Test the EDD to verify that the structure definitions are correct. Use an existing standard Obtain a copy of the standard files, and modify the provided DTD or schema file to match your requirements.
Note: FrameMaker includes several variations of DocBook as sample structured applications. If you plan to create DocBook-based structure, consider modifying one of the provided applications. Set up the structured application Open the structapps. Using the Structured Application Designer The Structured Application Designer allows you to create a structured application using a graphical wizard.
0コメント