Date   

Re: Conditional Attribute Groups

Chris Papademetrious
 

Hi John,

Currently we just have product families for groups. I suppose you could create a separate group for variants, although you'd want to take care that the AND/OR filtering rules work the way you want them to.

Regarding the idea of prototyping attribute specializations, there's also subject schemes. I have yet to look at them, and I don't know how they relate to/work with/conflict with conditional attribute groups.

 - Chris


#DITA-OT - Migrating from OT-1.8 to 3.5 #DITA-OT

MarkH
 

Hi!

I have been tasked with migrating our custom webhelp plugin which was written for DITA-OT 1.8.4, to DITA-OT 3.5. From what I have read about the process, I really need to start by migrating to 2.0, then working my way up through the various versions (2.1, 2.2, 2.3, etc.). Any advice, tips, tricks, warnings, or suggestions about how best to proceed would be appreciated!

Thank you in advance!


Anyone using Oxygen XML Editor to generate WebHelp output from DITA content?

Radu Coravu
 

Hi everyone,

If you are using Oxygen XML Editor to generate Oxygen WebHelp output from DITA, and your published userguide is on a public web server would you mind sending me a link to it? You can send the link in private if you do not want to share with the list (radu_coravu@sync.ro).

I'm curious about how our WebHelp output is being styled.

Regards,

Radu

Radu Coravu
Oxygen XML Editor


Re: markdown failure with OT 3.6 #DITA-OT #markdown

Ben Colborn
 

Thank you Aliza, that certainly looks like the same error. However, I was using the dita command, not calling ant directly. This is in a Git Bash window, which is mingw. I saw the same behavior on my colleague's Windows machine (also Git Bash/mingw). However, the same failure is NOT seen on a Mac. Then I tried running dita.bat rather than dita (which is a Bourne shell script) and the md files DID parse correctly.

The conclusion is that dita.bat works in mingw, and dita works on Mac. So it seems to be a corner case with the dita shell script in mingw terminals.

Ben


Re: Conditional Attribute Groups

john.kirkilis@...
 

Thanks Chris,

Do you use other group names in the product attribute besides familyN?

I’m assuming that if you wanted to also filter by a product variant, you could also add:

product=“family1(PROD_A) variant(ONPREM CLOUD_NATIVE)”

and create DITAVAL props to filter product variants within a family, for example?

Ive seen writers use otherprops as a catch all, but if attribute groups were used, it would namespace them so orthogonal facets were obvious.


Re: Conditional Attribute Groups

Chris Papademetrious
 

Hi John,

We use them quite extensively. We have multiple product families, each with multiple products. This feature allows us to use a single attribute - the @product attribute - to write conditional content such as

<p product="family1(PROD_A)">...</p>
<p product="family1(PROD_B)">...</p>


As a convention, our product family group names are lowercase and the product name values are uppercase.

Then in our DITAVAL, we can select just an individual product out of a family without affecting other product families:

<val>
   <!-- hide all family1 products, then include only @product="family1(PROD_A)" -->
   <prop att="family1" action="exclude"/>
   <prop att="family1" val="PROD_A" action="include"/>
</val>

(And we *do* have books that involve multiple product groups, which gets interesting and fun to edit and publish!)

It initially took some time to grok that in @att can refer to both attribute names and group names used within that attribute, but it makes sense now. It's like referencing the whole tree of possible values or just a subtree of possible values.

And in the Oxygen editor, when you apply profiling conditions to content, the dialog shows an extra expandable/collapsible hierarchy for the group names, which is pretty cool:

audience
  internal
  external
product
  family1
    PROD_A
    PROD_B
  family2
    PROD_C
    PROD_D
...etc...

 - Chris


Conditional Attribute Groups

john.kirkilis@...
 

Is anyone making use of conditional attribute groups in their doc sets?

From my reading of:
that it can provide a way to structure conditional attribute values so that <props> specialization is not required. Even if a filtering specialization is needed eventually, it appears that attribute groups could be used to see if the use case is common enough to justify a specialization.

I didn't initially realize that a DITAVAL <prop> @att value can be either
  • a name of specialization of the <props> attribute (audience, product, platform, etc) OR
  • the name of an attribute group
Specializations empower rock-solid validation, content completion, subjectscheme controlled values, and easier editor features to display and apply filters. Attribute groups would rely on writer conventions and would be relatively impossible to control. It's the basic tradeoff of flexibility against "strongly-typed" conditionalization.

Will attribute groups continue to be supported in DITA 2.0?


Re: Update DITA For Print for OT 3.x? What say ye?

james.bostock@...
 

I think that an updated edition would be great!


Job opportunity at Puppet: US Remote #jobhunting

Michael McLoughlin
 

Puppet have an open position for a tech writer with DITA and OxygenXML Author experience anywhere in the US:

https://www.linkedin.com/jobs/view/2493166374/?refId=xhuqco0kmr6eD5N%2BoOIO%2FQ%3D%3D&trackingId=fxCzkB4xHvauEHyRBqCNXg%3D%3D
--
Michael McLoughlin
Senior Technical Writer
Puppet


Looking for a PDF design challenge #content-delivery

Corinna Kinchin
 

Good day all,

My colleague Joanne and I will be showcasing MiramoPDF 2.0 at a #ConVExLive test kitchen on Tuesday 27th, and I'm planning to work through developing a real-world PDF design example from scratch. Do you have any beautiful PDF designs which could be used as a basis for this? Or are there particular design features you struggle to achieve using other PDF renderers? If so please email a sample PDF to me: ckinchin@.... If you are also able to share the DITA content used to produce the PDF,  that would be great, but is not vital.

Looking forward to seeing some of you at #ConVExLive!

All the best,
... Corinna


Re: <term> element with @keyref attribute inserted within topic title, not visible in <toc> #XSLT

Nicholas Mucks
 

Hi Sharaubh,
Have you reviewed the topic title with a missing keyref in the stage1.xml file in the temp directory? It’s likely due to an empty value there. When we encounter that we’ll use the document() function on the @href to the topic and then apply-templates on the title element. We’ve also noticed that sometimes glossary references that start with that dita-ot processing instruction from preprocessing in the body of the element will do bad things, so you might want to review that as well.

Take care,
- Nick

Sent from mobile

On Apr 16, 2021, at 1:00 AM, Shaurabh via groups.io <shaurabh.prakash-ext@...> wrote:

Thanks Julio. Tried this approach, but didn't workout. Please suggest any other solution to try if possible.


Thanks,
Shaurabh


[ann][webinar] Creating Frameworks Using an Extension Script (April 21) #Oxygen

alin_belu@...
 

Hello,
 
The last live event of April is getting closer and closer, and we want you there! Join us next Wednesday (April 21) for the “Creating Frameworks Using an Extension Script” webinar. 
 
During this event, Alex Jitianu (DITA evangelist and development lead at Syncro Soft) will take an extensive look at a specific method where a framework can be created using a special XML descriptor file, either from scratch or by extending an existing built-in framework (such as DITA or DocBook) and then making modifications to it. To make this possible, Alex will be covering topics, such as: 
* The framework structure as a package that contains resources and configuration information to provide ready-to-use support for an XML vocabulary or document type. 
* What benefits this new approach brings when compared with creating a framework in GUI. 
* Exploring various use cases and implement them through the script. 
* How to extend existing built-in or custom frameworks. 
* What deployment options are available. 
 
This is a free event and you can register at http://www.oxygenxml.com/evs2021-9.html 
 
Make sure to check the full list of our upcoming events: https://www.oxygenxml.com/events_programme.html 
 
Best regards,
Alin

--
Alin Belu
Oxygen XML Editor


Re: Pdf2 plugin not working with DITA-OT 3.5.4 #DITA-OT

Melissa Kershes
 

Hi there.

 

There’s a pretty comprehensive list of migration issues listed in the DITA OT documentation.

https://www.dita-ot.org/dev/topics/migrating-to-3.5.html

 

Generally I start at the version I’m upgrading from and review all the changes in each major release until I get to my newer version. Most of the issues you may find will be solved by reviewing this content.

 

Good luck with your upgrade!

Melissa

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Shaurabh via groups.io
Sent: Friday, April 16, 2021 3:48 AM
To: main@dita-users.groups.io
Subject: [dita-users] Pdf2 plugin not working with DITA-OT 3.5.4 #DITA-OT

 

We have upgraded our application from DITA-OT 3.1.3 to 3.5.4. After upgrade, Pdf2 plugin has stopped working. Please suggest if any configuration changes is required in respective build.xml file or if any other change is required.


Re: <term> element with @keyref attribute inserted within topic title, not visible in <toc> #XSLT

Shaurabh
 

Thanks Julio. Tried this approach, but didn't workout. Please suggest any other solution to try if possible.


Thanks,
Shaurabh


Pdf2 plugin not working with DITA-OT 3.5.4 #DITA-OT

Shaurabh
 

We have upgraded our application from DITA-OT 3.1.3 to 3.5.4. After upgrade, Pdf2 plugin has stopped working. Please suggest if any configuration changes is required in respective build.xml file or if any other change is required.


Re: markdown failure with OT 3.6 #DITA-OT #markdown

Aliza Merzel
 

Hi, Ben,

 

I had the same issue

It is a known issue

 

It happens when you call the dita-ot using the ant command

When using the dita command, it should be fine

 

https://github.com/jelovirt/dita-ot-markdown/issues/59

 

Aliza

 

 

Aliza Merzel

Senior Developer and XML Specialist

Phone: +972 8-976-0323

Email: alizam@...

 

Connect with us:  twitter.png   linked-in.png  youtube.png

 

Logo-for-email-signatures - smaller

 

From: main@dita-users.groups.io [mailto:main@dita-users.groups.io] On Behalf Of Ben Colborn via groups.io
Sent: Wednesday, April 14, 2021 9:45 PM
To: main@dita-users.groups.io
Subject: [dita-users] markdown failure with OT 3.6 #DITA-OT #markdown

 

Hi dita-users. After quite some time away (since before the move to groups.io in fact), I'm dipping my toes into the lightweight DITA world and running into some issues. Right now I'm using the remotelighting.ditamap sample with just the markdown topics. Using Oxygen 23.0 (which I believe has OT 3.6) it transforms to HTML5 or PDF without any issues.

Not so with the dita command in a fresh install of OT 3.6 or 3.6.1, which I can see includes the org.lwdita plugin. The files fail to parse.

gen-list:                                                                                   
 [gen-list] Using Xerces grammar pool for DTD and schema caching.                           
 [gen-list] Processing file:/C:/Users/ben/Documents/tech-content/tech-content-tools/sample/r
emotelighting-md.ditamap                                                                    
 [gen-list] Processing file:/C:/Users/ben/Documents/tech-content/tech-content-tools/sample/m
dita/led-specs.md                                                                           
 [gen-list] [DOTJ013E][ERROR] Failed to parse the referenced file 'file:/C:/Users/ben/Docume
nts/tech-content/tech-content-tools/sample/mdita/led-specs.md'.: com.elovirta.dita.markdown.
MDitaReader                                                                                 
 [gen-list] Processing file:/C:/Users/ben/Documents/tech-content/tech-content-tools/sample/m
dita/product-specs.md                                                                       
 [gen-list] [DOTJ013E][ERROR] Failed to parse the referenced file 'file:/C:/Users/ben/Docume
nts/tech-content/tech-content-tools/sample/mdita/product-specs.md'.: com.elovirta.dita.markd
own.MDitaReader                                                                             


Output of docsrc/userguide.ditamap to html5 using the dita command works fine. Am I missing something that's needed to process the markdown topics? Thank you for any insight.

Ben


markdown failure with OT 3.6 #DITA-OT #markdown

Ben Colborn
 

Hi dita-users. After quite some time away (since before the move to groups.io in fact), I'm dipping my toes into the lightweight DITA world and running into some issues. Right now I'm using the remotelighting.ditamap sample with just the markdown topics. Using Oxygen 23.0 (which I believe has OT 3.6) it transforms to HTML5 or PDF without any issues.

Not so with the dita command in a fresh install of OT 3.6 or 3.6.1, which I can see includes the org.lwdita plugin. The files fail to parse.
gen-list:                                                                                   
 [gen-list] Using Xerces grammar pool for DTD and schema caching.                           
 [gen-list] Processing file:/C:/Users/ben/Documents/tech-content/tech-content-tools/sample/r
emotelighting-md.ditamap                                                                    
 [gen-list] Processing file:/C:/Users/ben/Documents/tech-content/tech-content-tools/sample/m
dita/led-specs.md                                                                           
 [gen-list] [DOTJ013E][ERROR] Failed to parse the referenced file 'file:/C:/Users/ben/Docume
nts/tech-content/tech-content-tools/sample/mdita/led-specs.md'.: com.elovirta.dita.markdown.
MDitaReader                                                                                 
 [gen-list] Processing file:/C:/Users/ben/Documents/tech-content/tech-content-tools/sample/m
dita/product-specs.md                                                                       
 [gen-list] [DOTJ013E][ERROR] Failed to parse the referenced file 'file:/C:/Users/ben/Docume
nts/tech-content/tech-content-tools/sample/mdita/product-specs.md'.: com.elovirta.dita.markd
own.MDitaReader                                                                             

Output of docsrc/userguide.ditamap to html5 using the dita command works fine. Am I missing something that's needed to process the markdown topics? Thank you for any insight.

Ben


Re: Update DITA For Print for OT 3.x? What say ye?

Ozana Dragomir
 

Yes, please!

Best regards,
Ozana


Re: Update DITA For Print for OT 3.x? What say ye?

stinakab
 

Yes! An update would be very much appreciated.
Best,
Christina


Re: Update DITA For Print for OT 3.x? What say ye?

Larry Kunz
 

Add me to the "yes, please" list, Leigh. DITA for Print is my Bible for PDF transforms. 

Larry Kunz

161 - 180 of 46324