You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DITA-OT is very good about appending suffixes to avoid file name collisions during keyscope/profiling/content-reuse uniquification.
However, rewrite rules do not provide this behavior. If rewrite rules result in identical file names:
then the output uses one of them for all references:
$ ls -1 out
commonltr.css
commonrtl.css
features.html
index.html
Possible Solution
The DITA-OT rewrite rules module could detect and resolve collisions similarly to the keyscope/profiling/content-reuse features.
Potential Alternatives
As a workaround, the user could implement a multi-pass stylesheet that applies name rules in a first pass, then resolves collisions in a second pass. However, this requires some XSLT ability that perhaps not all DITA-OT users would have.
Description
The DITA-OT is very good about appending suffixes to avoid file name collisions during keyscope/profiling/content-reuse uniquification.
However, rewrite rules do not provide this behavior. If rewrite rules result in identical file names:
then the output uses one of them for all references:
Possible Solution
The DITA-OT rewrite rules module could detect and resolve collisions similarly to the keyscope/profiling/content-reuse features.
Potential Alternatives
As a workaround, the user could implement a multi-pass stylesheet that applies name rules in a first pass, then resolves collisions in a second pass. However, this requires some XSLT ability that perhaps not all DITA-OT users would have.
Additional Context
A testcase is included: 3958.zip
To run, type
dita --project project.xml
.The text was updated successfully, but these errors were encountered: