Baggage File(s) in Specific Output Directory without Duplication
Summary and Description
Currently, it is possible to add baggage files to the Files folder of a project. These baggage files are then deployed to each sub-directory in the build output. This is great for commonly-used files such as a legal notice or company logo.
In addition, it would be useful to add baggage files to selective output directories. For example, let's say I have an externally-generated PDF that I would like to link to in my help system. I can add this to the Files directory, but then it is duplicated for every sub-directory in the build output, which unnecessarily increases the size of the help system. I can also create pre- or post- processing scripts to add externally-generated PDFs to the output directory, but this is less desirable and I already have to manage a number of pre- and post-processing scripts.
It would be great if there was a higher level baggage files directory so that the files are not duplicated for each sub-directory. Perhaps the high level baggage files could be deployed to the \output\wwhelp\ directory.
| Stephanie Bodoff | Currently the tpl folder is added to each PDF output directory. Since PDF files are self contained, this tpl folder serves no purpose and must be manually deleted after deployment. If fact when ePublisher first released, it did not have this behavior. |
2011-09-13 16:36:07 | ||
 |
LoriBresnahan | I have a similar issue with the Files directory. If you want to embed flash videos into specific topics in a merged help system, you have to put the flash videos in the Files directory. But then when you build help, all of those videos get propagated to every group's directory. For example, if I create 10 embedded flash videos, and I have 15 groups in my merged help system, I will end up with 10 x 15 = 150 copies copies of the flash videos. This will massively inflate the size of the help system, and makes embedding vidoes un-usable for us (unless we want to manually go though each directory and delete the ones that don't apply). A given flash video should only be propagated to the groups that actually use it. |
2013-11-07 12:12:36 | |