Hi Eliot, Agreed, this feature is super convenient! And it removes another barrier to organizing keys and content nicely into submaps. We did notice a a bug in 23.x versions where submaps (but not the

#conref

Hi everyone, I created a perl script to automate @href-to-@keyref conversion for cross-references between topics: https://github.com/chrispy-snps/DITA-convert-hrefs-to-keyrefs Your map must already ha

#conref

Hi Eliot, I'm curious - how are you getting more topics in your output than exist in your map? Let's say I have bookA that references bookB as a peer map: <?xml version="1.0" encoding="UTF-8"?> <?xml-

Hi Radu, This visualization is pretty cool! I appreciate the example graph so we could easily see what is produced without running all the steps. Our books have cross-deliverable links using peer maps

Hi everyone, I updated the plugin at https://github.com/chrispy-snps/DITA-mapref-topichead as follows: The implementation is significantly simpler. Map-level @keyscope and <ditavalref> properties are

...although looking in <DITA-OT>/plugins/org.dita.html5/xsl/rel-links.xsl link creation seems to follow the same path for all @format values other than dita. - Chris

Hello fellow DITA-neers! For an external <xref> to a web URL, should @format always be set to "html"? <xref href="https://www.website.com/downloads/manual.pdf" scope="external" format="html"/> <xref h

Hi Eliot, everyone, I've made some progress on this issue. And I discovered that I can include images in groups.io posts, so let's start with some pretty pictures! Eliot, you summarized our situation

Hi everyone, To follow up on this discussion, we found the following peer map bugs in Oxygen 23: When @keyscope is defined on a peer map reference and the target map defines its own local @keyscope on

Hi everyone, I created a plugin that can automatically add navigation hierarchy for submaps: https://github.com/chrispy-snps/DITA-mapref-topichead - Chris

Hi Eliot, As always, thanks for jumping in! We use SyncroSoft's PDF Chemistry for PDF publishing. And it behaves correctly - it doesn't create navigation hierarchy from submap titles. My previous comm

Hi Dan, Thanks for the suggestion! I can't use <topichead> directly in the <bookmap> because A <bookmap> does not permit <topichead> at its top level, only <chapter>, <appendix>, and other book-like t

I'm attaching the tiny testcase I used for experimentation. - Chris

Hi fellow DITA users, We are exploring Oxygen's WebHelp Responsive transformation, so I am exploring DITA-OT chunking to understand how to control the help structure. I have multiple <bookmap> files r

If you are using Oxygen as your editor, there is a setting to always set @type in new <xref> elements: <xref href="test.dita#test_overview/fn_5fc" type="fn"/> You can find this setting in Preferences

#XSLT

Hi Shaurabh, Because <fn> elements with IDs don't generate content themselves, I keep them self-contained inside the table that references them. This way, they move along with the table if I copy/move

#XSLT

Hi Eliot, The bug with Oxygen is when option #2 is used ((1) the current book A has its own local scope A, and (2) it references a peer book B with scope B, and (3) you drag-and-drop a topic from map

Thanks Eliot! Excellent summary of the problem and the situation. Your method #2 (adding a map-level @keyscope) is what I tried, but it doesn't seem to work in Oxygen. It doesn't form the cross-book l

We have two books that share a common topic, called "Shared Topic": Book A: Topic 1 Topic 2 Shared Topic Book B: Topic 3 Topic 4 Shared Topic In "Shared Topic", we want to include a cross-reference to

@despopoulos_chriss, you make a good point about ROI. We like DITAVAL for book-wide profiling, as product conditions are group-wide and stable. But this would not be true for ad-hoc usage. If I make D