Hi Kris, In my computer's desktop there is a folder containing the full 1.3 specification, another one with the errata text plus a folder with errata grammars, a folder with dita-lwdita-master and a

You are really missing the boat here. Please see my comments inline. Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal

Hi Dan, You need to explicitly set the "print='yes'" attribute on the glossref: https://github.com/dita-ot/dita-ot/issues/3328 Regards, Radu Radu Coravu <oXygen/> XML

Thanks. I am just a longtime user and use Eclipse (Spring Tool Suite) as my authoring environment. I use standalone DITA-OT as well as the Maven plug-ins to publish my

I wanted to take some of the content from a recent post and turn it in a more positive direction. Question: Where do you go for high-quality information about DITA? My personal

Hi Ron, The first link you mentioned cannot be "fixed" per se. At least, that page can never be changed. It is a specification, not "documentation". FWIW, there is a newer version of the DITA

Is there any way to fix http://docs.oasis-open.org/dita/v1.2/os/spec/DITA1.2-spec.html ? The descriptions are very cryptic and often seem almost self-referential. The examples are often edge cases

I am using DITA to document the plans for condominiums in a condo association. Many units have the same plan. The relatble links the plan to the condos bult with the plan and links each condo unit to

It may be that DITA is I/O bound rather than CPU bound. Adding more processors thrashing the same disk may not help. I had very good results by creating a RAM drive and using that for document

Thanks, I’ll take a look at when I’m back at work

Dan: I sent you a sample project that should get you started. I put it together for last year’s DITA North America presentation. -Wayne

I've been following the instructions for using the glossary elements https://www.oxygenxml.com/doc/versions/21.1/ug-editor/topics/dita-creating-glossary.html This all works perfectly for HTML output.

I'd expect that since you are using windows, git, when run from oxygen, has no knowledge of your cygwin environment and thus cannot launch your script with bash. I'd guess that you'd need to give the

Hi Radu, So originally my intent was to mirror the numbering outcome we achieved using FrameMaker. There we achieved numbering for all topics as well as the DITA <section>, so a topic might show like

Hello; I'm trying to create a workflow that starts with multiple DITA files inside oXygen that end up as a single md file in GitHub. I have installed the GitHub plugin (built on on the JGit library)

Yes, I am building a custom DITA-OT plug-in. I'm not modifying the master files. I'm just pointing out where to find it.

Have you built a DITA-OT plug-in that you are using to override the DITA-OT defaults? Or are you modifying the DITA-OT files directly. The latter is a bad practice ... Best,

Found a solution finally. Edit the front-matter-attr.xsl file to: <xsl:attribute-set name="back-cover"> <xsl:attribute name="force-page-count">auto</xsl:attribute>

Hi Matt, I stumbled on this thread, as the thread is long it was an easy stumble :) So our DITA to PDF using CSS documentation mentions: but I think the "section" wording there was originally

I hope someone at Oxygen stumbles on this thread - regardless I think the definition for <section> from the Oasis website clears things up and affirms we may have been using it wrong: 3.1.1.2.31