Understanding Customized Processing
ePublisher uses file and folder locations to provide a structure where you can create and store override files. These files customize how ePublisher transforms your content.
When you generate output for an output format, ePublisher uses the following process to identify the files to use to process your content and complete the task:
1. ePublisher checks the Targets folder hierarchy in your project for the files required to complete the task. ePublisher checks the folder hierarchy named for the target you are generating.
2. If the files are not found in the Targets folder hierarchy in your project, ePublisher checks the Formats folder hierarchy in your project for the files required to complete the task. ePublisher checks the folder hierarchy named for the output format of the target you are generating.
3. If the files are not found in your project folder hierarchy, ePublisher checks the installation folders.
This process allows you to override any default file in the installation folder hierarchy for one or more output formats or targets by placing a customized file with the same name at the correct location in the project folder hierarchy.
By recreating the file path in the Targets folder in your project, and storing a modified file in the correct location, you can change the processing for that specific target. This method allows you customize a specific target in a project that has multiple targets using the same output format.
By recreating the file path in the Formats folder in your project, and storing a modified file in the correct location, you can change the processing for all targets that use the same output format. This method is also helpful for projects with one target.
Note: Do not modify files in the installation folders. Store customized files only in the project folder hierarchy. You need to create the Targets and Formats folder hierarchies in your project folder, as needed for the files you want to override.
Last modified date: 11/30/2021