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
Using the test documents in the dita-community project org.dita-community.indirectortopic.doctypes, the topics that are linked as resource-only topics are included in the navigation ToC and in prev/next links. They should not be.
I think the issue is with the relationship table, which is relating resource-only topics to non-resource-only topics. This is not something you would normally do, but the result should be that the resource-only topics are not included in navigation (and the links should not be instantiated).
The text was updated successfully, but these errors were encountered:
It seems to be a bit more subtle than I thought. The topicrefs in the reltable are not resource only, which is correct, but the keys they refer to are resource-only topics, so the end result should still be that the topic is not included in navigation.
Using the test documents in the dita-community project org.dita-community.indirectortopic.doctypes, the topics that are linked as resource-only topics are included in the navigation ToC and in prev/next links. They should not be.
I think the issue is with the relationship table, which is relating resource-only topics to non-resource-only topics. This is not something you would normally do, but the result should be that the resource-only topics are not included in navigation (and the links should not be instantiated).
The text was updated successfully, but these errors were encountered: