Hi folks, Apologies for two messages in a row... We plan to upgrade our DITA-OT implementation. We have a custom PDF transform that works great in DITA-OT 1.8.5 and blows up in 2.2. Our current plugin

Howdy folks, We would like to enable using a plural form for glossary references. Conceptually, we have identified that a simple approach may be to create an outputclass for the <term> element that te

Thanks, Kris. Our team always accesses the 1.2 spec by Googling "oasis dita 1.2" and clicking on the first hit. However, Googling "oasis dita 1.3" isn't so neat and tidy. How do we update the robots t

Hi Leigh, Yeah, this seems totally fine... To cancel out any inheritance or file-specific issues, does a new keyword (xyz/zebra) in a different file properly conkeyref? If not, how about a simple conr

Thanks everyone. Using keys is probably the best approach. It keeps the file count down and allows us to single-source the material. Although that copy-to idea is also worth exploration. A writer typi

Hello. We have a topic that occurs multiple times in one document. The writer needs different related links for each instance of that topic. Is there a way to generate related links to a specific inst

Howdy! We would like the collapse the file structure in the HTML output. Right now, the output matches our input file structure. === database .........| documentation ...............| product_category

Hi Kate, We wanted to perform code reviews for a long time, and eventually decided not to do reviews because people could not find the time. Instead, we implemented Schematron Quick Fixes. They are a

Hi Kate - Scriptorium made ours, and they did a good job. We have taken over maintenance as we learn more about XSL-FO in-house. Making sure to clearly define (and understand) your requirements will h

Hi Rhonda - This conversation always invigorates the base in terms of DITA core mechanisms for content reuse. It also reminds me about how to explain using keys to the stubborn skeptics. Thanks for br

Hi Anil - You can also read about basic DITA concepts and the information types at: https://www.oxygenxml.com/dita/styleguide/webhelp-feedback/#Artefact/c_Topics_and_Information_Types.html Take care,

We have 20 writers globally and there is no way that one techie person could support everyone. However, that percentage is close to reasonable. In our team we have one "chief" architect who works 50%

Hello -- Is there a simple way to add form data to the PDF output from DITA source material? We are currently doing this manually, post-publishing. Ideally it's some sort of simple markup solution. Th

Hi, Kate -- Sorry for the business process solution, but we simply put all trademarked items in a list at the beginning of each book as a boilerplate topic. This meets legal requirements and doesn't r

Hi, Mari - We had a similar situation with reference parameters shared by the documentation and a user interface. The writer wanted to centrally manage the API information and have it feed into the as

Hi, We'd like to publish a map full of key defs to shared topics. Keydefs don't show up in output even if you remove the processing-role attribute. Besides maintaining a second map with topicrefs, is

Hello, We are developing Schematron rules for our organization. This rule identifies when a topic is missing a shortdesc: <pattern> <rule id="R_008" context="*[contains(@class, ' topic/topic ')]"> <as

#shortdesc

Hi, Erland -- That seems interesting. Is it a separate preprocessing plugin? Can you share implementation details? Thanks, - Nick

Hi, folks - Is there a way to automatically create a glossary based on the terms used in an information set? We typically maintain a glossary at the end of our PDF and HTML documents. Right now, we us

Proprietary systems vs open standards often have this dichotomy. It would be interesting to see some sort of heat map showing CMS penetration / DITA adoption in Europe.