Associate ditaval file with a project instead of with a ditamap
Summary
Allow specification of a ditaval file in the Target Settings.
Detailed Description
The requirement that ditaval files have the same name as the ditamap is too restrictive. The whole purpose of ditaval files is to be able to filter content based on the setting of the attributes in the ditaval file. If I can only use one file then if I want different settings for the attributes I have to change the content of the ditaval file. What I would like to have is multiple ditaval files with the desired settings and choose the file I want to use for an ePublisher project in the same way that I can set conditional variables settings in a project.
Use Cases
Publish different versions of a map based on different attribute values in the ditaval files.
| BenAllums | This is already possible by creating target specific "default.ditaval" files. |
2011-11-08 08:04:53 | ||
| StephanieBodoff | I would like to explicitly specify the ditaval file for a map that does not have the same name as the ditamap, overriding the default which requires the ditaval file to have the same name as the map. |
2011-11-10 16:17:50 | ||
| CatherineVolodko | +1 It seems that ePublisher does not support one of the main DITA reuse concepts - using one map with different ditaval files. I think that this is a ePublisher concept issue. Please address it the sooner the better. It is very inconvenient to generate one map with different ditavals that are stored in the source control system. |
2012-05-03 08:51:16 | ||