|
|
|
|
|
Project Overrides
When generating output, the ePublisher engine has three places to look for the files it requires to complete the transform. The user may modify two of these locations in order to create unique content.
By default, the ePublisher engine will look first for a Targets directory inside the project folder for the files it requires. Next, the engine looks for a Formats directory inside the project folder for the files it needs. Finally, the engine will look inside the installation directory for the required files.
By recreating the file path of the installation directory inside the Targets folder and storing a modified file in the correct location, the user can make changes to a specific target. This is useful when there are multiple targets for a project and the user wishes to customize only one of them.
By recreating the file path inside the Formats directory and storing a modified file in the correct location, the user can make changes to an entire project. This is useful when there is only one target, or if all targets should be modified in the same way.
Modifying files in the installation directories is not recommended. Files should be modified on the target or project level or in user-created formats only.
|
|
Both the Targets and Formats directories, as well as the folder hierarchy necessary to override a given file, must be created by the user. |
Figure 39 illustrates the same file hierarchy in the Targets and Formats directories.
Figure 39 Identical File Hierarchies in Formats and Targets Directories
