Creating Project Format Overrides
This section defines how to override a default file for all targets of a specific output format type in the project. Do not modify the files in the installation folder hierarchy. These files are the default files and should remain as is. These files are also overwritten when you install new ePublisher releases. Instead, store and incorporate your customized files with your Stationery so your projects based on the Stationery get those customizations.
Note: Changes to .xsl and Format Trait Info .fti files are considered advanced customizations and are not supported through the Quadralay Product Support department. If you are familiar with the XSL language, you may find this to be a powerful way to achieve very specific results in your generated output or output deployments. However, you need to understand that the override files that you create must be maintained by you and not the Quadralay Product Support department.
File names used in ePublisher are case sensitive. Make sure the file and folder names you create exactly match the default file and folder names in the installation folder hierarchy. Do not copy any files into the project folder hierarchy that you are not overriding.
The following task assumes that ePublisher is installed in the default location and your ePublisher projects are stored in the My Documents folder. If you installed ePublisher to a non-default location, or if you store your projects in a folder other than the My Documents folder, adjust the paths in the following task.
To override a project format
In Windows, open your project folder.
Create a new folder named Formats in your project folder.
In this new Formats folder, duplicate the folder hierarchy of the file you want to override. For example, if you want to override the Page.asp file for HTML Help output, create the Microsoft HTML Help 1.x\Pages folders in the Formats folder.
Copy the file you want to override from the default installation folder location into the new location in your project folder hierarchy. For example, if you want to override the Page.asp file for HTML Help output, copy the Program Files\WebWorks\ePublisher Pro\Formats\Microsoft HTML Help 1.x\Pages\Page.asp file to the My Documents\component Projects\project\Formats\Microsoft HTML Help 1.x\Pages folder, where component is the name of the ePublisher component you are using to create the project, such as ePublisher Pro or ePublisher Express, and project is the name of your project.
Modify the copied file in the project folder hierarchy as needed, and save the file.
The next time you generate your project, the modified file automatically overrides the default file and the changes you made are incorporated into the output for all targets that produce that output format.
Note: When you save the ePublisher project as Stationery, the project format overrides you have created are saved with your Stationery. This Stationery can then be used to create future projects in ePublisher Express and ePublisher AutoMap.