Choosing ePublisher Express and either Adobe FrameMaker and/or Microsoft Word to produce technical documents and online content is the first step in building a powerful single sourcing environment. Incorporating and WebWorks AutoMap into your conversion process gives you the ability to schedule your conversions of multiple source files.
Using your source files, ePublisher AutoMap allows you to produce all of your information—print, HTML, XHTML, XML, eBooks, WebWorks Help, WinHelp, HTML Help, JavaHelp 1 and 2, Oracle Help, and PDF—from a single publishing engine. You create content using any XML editor, Adobe FrameMaker, and/or Microsoft Word and then use ePublisher AutoMap to convert your documents to any of the output formats that you require.
This section gives you important information to get you started with ePublisher AutoMap. It includes the following sections:
This section describes the purpose and benefits of using ePublisher AutoMap and includes the following sections:
ePublisher AutoMap allows you to automatically create and convert ePublisher projects without manually opening either ePublisher Express or your source file applications. Source file applications currently include Adobe FrameMaker, Microsoft Word and all DITA content. After you create your job, ePublisher AutoMap either of the following:
ePublisher AutoMap automates the process of converting your DITA, Adobe FrameMaker, and/or Microsoft Word content files into online output formats. It lets you create and convert content at the times you schedule and works seamless with several content management and revision control systems.
The following are just a few of the features of ePublisher AutoMap that will save you time and effort:
ePublisher AutoMap allows you to specify scripts for retreiving files from revision control and content management systems such as:
In addition, ePublisher AutoMap can work with any revision control or content management systems that are scriptable from the command line.
The following are the minimum and recommended system and product requirements for ePublisher AutoMap. These are the same requirements as those for ePublisher Pro and Express.
ePublisher AutoMap has been tested and compatibility verified on Microsoft Windows Server 2003 Standard Edition and Microsoft Windows Server 2003 Enterprise Edition. There are no additional requirements when running ePublisher AutoMap on Microsoft Windows Server.
ePublisher AutoMap will not convert WebWorks AutoMap 2003 jobs. Since ePublisher AutoMap is based on the new ePublisher technology, new jobs must be created using ePublisher based projects or stationery.
The Norton AntiVirus Office plug-in has been known to cause problems when using parts of the Microsoft Office Suite. You may encounter problems when attempting to create and generate online content using Microsoft Word and ePublisher AutoMap, if you have installed any of Symantec’s Norton AntiVirus software.
If you encounter any error messages indicating compatibility issues while working with ePublisher AutoMap, refer to the following Microsoft Knowledge Base article:
http://support.microsoft.com/kb/329820
ePublisher AutoMap is capable of converting source documents from Adobe FrameMaker and Microsoft Word with no special modifications necessary. By default, ePublisher AutoMap will use the paragraph formatting as defined in the source document(s). In addition, ePublisher AutoMap will convert any DITA compliant content.
ePublisher AutoMap works with different files and structures to perform its tasks along with accomplishing integration with ePublisher Express. Understanding these interactions requires learning some terminology and the differences between each of these structures and file types. Some of these files have common capabilities but are used in different situations to meet a specific need. Others only serve a single purpose for a particular product.
This section explains the terminology and helps define when to use each including:
Formats refer to the base outputs included with ePublisher AutoMap, ePublisher Express, and ePublisher Pro. They are the starting point for all ePublisher AutoMap, ePublisher Express, and ePublisher Pro projects. Each format produces a specific type of output.
The formats are provided and maintained by Quadralay. Although formats can be customized and new formats may be created by end users, the format terminology refers to those formats as delivered by Quadralay in ePublisher AutoMap, ePublisher Express, and ePublisher Pro.
The following is a list of formats currently provided in WebWorks products:
Formats initially reside in a ‘Formats’ folder at the root of an ePublisher Pro installation. Once a stationery is created using ePublisher Pro, then a “snapshot” of one or more of the formats that were configured are packaged in entirety with your stationery.
User formats are either formats that have been modified by end users or brand new formats created by end users. In this sense, modifying a format does not refer to changes made in a ePublisher AutoMap job or ePublisher Express project. Rather it refers to customizations to the underlying XSL or other structure in the format folder. Customizing a format is an advanced concept and requires an understanding of the ePublisher Pro design process. Any change made within the product itself does not constitute a customization to the format.
Further, it is possible for users to create brand new formats not based on those provided by Quadralay. This allows targeting a new or custom output while still utilizing all of the advantages provided by the ePublisher product workflow.
User formats may be installed anywhere other than the formats folder. ePublisher AutoMap provides an application preference for specifying the User Formats Folder.
Stationery contains all ePublisher Pro project configurations except for document overrides and source documents themselves. Stationery includes style configurations, variables, conditions, targets, etc. By saving a project as stationery, configurations for a format can be repeatedly reused by ePublisher AutoMap and ePublisher Express for converting any source documents.
Stationery can be installed anywhere accessible to the project or job including a network or shared volume. Stationery files include a .wxsp (WebWorks Stationery Project) extension and are saved in their own folders.
Formats are base outputs as provided by Quadralay. They contain no user specified configurations or settings. Stationery may be associated with one or many formats and include all user adjusted settings and configurations.
Formats can be viewed as the starting point for identifying a base output type. Stationery are configurations of a format meeting specific user needs which are reused as often as necessary. This removes the requirement of re-specifying every configuration each time a new project or job is created.
Jobs are entries that ePublisher AutoMap schedules using a stationary or project for conversion.
By default, job files are created in:
\Documents and Settings\username\My Documents\WebWorks ePublisher AutoMap\Jobs
username represents the login name of the current user and not the actual value as written. The default path can be changed in the ePublisher AutoMap application preferences. Job files have a .waj (WebWorks ePublisher AutoMap Job) extension. Job files depend on other files located in the job folder and should not be moved or copied independently.
- Related Topics
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
