Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resource only topicrefs considered duplicates by key processing #2304

Closed
jelovirt opened this issue Apr 15, 2016 · 2 comments
Closed

Resource only topicrefs considered duplicates by key processing #2304

jelovirt opened this issue Apr 15, 2016 · 2 comments
Labels
bug preprocess/keyref priority/medium Medium (or unknown) priority issue
Milestone

Comments

@jelovirt
Copy link
Member

For map

<topicref href="foo.dita" processing-role="resource-only"/>
<topicref href="foo.dita" />

The latter topicref is considered a duplicate by key processing and is renamed to foo-1.dita. Resource only topicrefs should not be counted when considering duplicates.

DITA-OT 2.2

@eerohele
Copy link

This happens to fix #2134 because the test files in that issue use <keydef>, which has implicit @processing-role="resource-only", but IIRC #2134 still occurs if the key-defining topicref has a normal processing role.

@eerohele
Copy link

No, I remembered wrong, I reread what I wrote in #2134 and ran some tests and it seems this resolves #2134 as well. If something additional surfaces, we can open a new issue.

(This doesn't resolve #2242, though.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug preprocess/keyref priority/medium Medium (or unknown) priority issue
Projects
None yet
Development

No branches or pull requests

2 participants