Date   

Re: [Ann] Oxygen XML Suite Version 22.0 Release #Oxygen

cristi_talau@...
 

Hello,

For 1, we added this fragment element for extensibility. We may need to add other child elements for "prefix-replacement" in the future.

For 2, that's a use-case that we plan to implement in a future release. I added your vote to this feature request and will let you know when it is available.

3 - You are right. This is a bug with the current implementation - we are going to fix it. 

4 - We encountered the same situation for XHTML - lists are forbidden in paragraphs. We will probably add an XML attribute in the configuration file to specify that the parent should be replaced. However, there are several cases to consider, e.g. if the paragraph already had some profiling attributes, they may disappear when the paragraph is replaced.

Best,
Cristian


Re: Shout-out to Oxygen's technical support #Oxygen

Jochem de Vos
 

(Happily created a groups.io account to reply this thread)

I don't work much anymore with Oxygen (unfortunately), but definitely a great product with a great team supporting it.


Re: Recommendations for content delivery platform #content-delivery

etudsbery
 

Hi Jana,

 

easyDITA do now have a CDP. They’ve realized this was a missing piece in their offering so they have created one.

 

Our business case runs to about 20 pages but it is basically about joining up different content silos within the company, improving customer self-service (very low in our company), support, and customer satisfaction as measured by NPS scores. We already have Salesforce community and lightning so we need something that can be integrated with these solutions.

 

Regards,

 

Ed

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Don Bridges via Groups.Io
Sent: 18 February 2020 14:04
To: main@dita-users.groups.io
Subject: Re: [dita-users] Recommendations for content delivery platform

 

Ed,

 

FluidTopics and Zoomin are CDPs, Bluestream is a CCMS and CDP, and easyDITA is a CCMS.  All are viable tools and each may be a good fit depending on your situation and use cases.  There are other options in both the CDP and CCMS arenas.

 

Maybe you can share your Business Case for this investment?

 

Don Bridges

JANA



On Feb 18, 2020, at 3:44 AM, etudsbery <etudsbery@...> wrote:



Hi there,

 

Our company is currently looking at content delivery platforms (CDP) based on DITA  that we can integrate with Salesforce.

 

We have seen demos from Fluidtopics, Zoomin, Bluestream and easyDITA. Has anyone had any experience with these products either as CCMS or content delivery platform? Or perhaps you know of another CDP based on DITA?

 

Thanks for any information.

 

Regards,

 

 

 

Ed Tudsbery
Team Leader

 

E etudsbery@...

P +33 (0)1 41 29 36 51

Immeuble Ampère, 8, rue Eugène et Armand Peugeot, 92 500 – Rueil Malmaison, France

 

 


If you wish to view the CPA Global group email disclaimer, please click here



Re: Recommendations for content delivery platform #content-delivery

nmcdonagh
 

Don

I have looked at all of these systems and actually settled on Zoomin when we had the need for a content delivery platform. We found them to be flexible and easy to use and implement and since our implementation their integration with Salesforce brings many more benefits. If you need specifics, feel free to reach out direct.


Re: Recommendations for content delivery platform #content-delivery

Don Bridges
 

Ed,

FluidTopics and Zoomin are CDPs, Bluestream is a CCMS and CDP, and easyDITA is a CCMS.  All are viable tools and each may be a good fit depending on your situation and use cases.  There are other options in both the CDP and CCMS arenas.

Maybe you can share your Business Case for this investment?

Don Bridges
JANA

On Feb 18, 2020, at 3:44 AM, etudsbery <etudsbery@...> wrote:



Hi there,

 

Our company is currently looking at content delivery platforms (CDP) based on DITA  that we can integrate with Salesforce.

 

We have seen demos from Fluidtopics, Zoomin, Bluestream and easyDITA. Has anyone had any experience with these products either as CCMS or content delivery platform? Or perhaps you know of another CDP based on DITA?

 

Thanks for any information.

 

Regards,

 

 

 

Ed Tudsbery
Team Leader

 

E etudsbery@...

P +33 (0)1 41 29 36 51

Immeuble Ampère, 8, rue Eugène et Armand Peugeot, 92 500 – Rueil Malmaison, France

 

 


If you wish to view the CPA Global group email disclaimer, please click here



Re: Branch filtering on reused content #conditional-processing

Pieterjan Vandenweghe
 

Hi Radu,

Defining keyscopes and keys for each topic did the trick.
Thank you for the tip.  

Kind regards,

Pieterjan


Re: Shout-out to Oxygen's technical support #Oxygen

Kristen James Eberlein
 

And just another accolade for the Oxygen Technical Support team and their overnight support. I've never experienced this level of support with any other software vendor!

Wonderful product and wonderful team.

Happily entering my second decade of using Oxygen XML Editor on a daily basis ...

Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
OASIS Distinguished Contributor
Principal consultant, Eberlein Consulting LLC
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)

On 2/15/2020 3:51 AM, Radu Coravu wrote:
Hi,

Thanks to everybody who contributed to the thread for the kind words.
We are happy and proud to be working for you, your questions and improvement ideas help us improve Oxygen further.

Regards,
Radu


Re: [Ann] Oxygen XML Suite Version 22.0 Release #Oxygen

Chris Papademetrious
 

Adding another question about the text-to-markup automatic conversion feature:

4. In a new Oxygen DITA project, the list completion shortcuts create the list inside a <p> element:

    <p>
      <ol>
        <li/>
      </ol>
    </p>

But in our custom DITA grammar, we disallow lists (and figures and such) inside <p> elements; they can only be peer block elements with <p>. Is there a way to somehow insert the new content just before the current <p> where the shortcut was typed, or to replace the current <p> (if it contained *only* the shortcut) with the content?

 - Chris


Recommendations for content delivery platform #content-delivery

etudsbery
 

Hi there,

 

Our company is currently looking at content delivery platforms (CDP) based on DITA  that we can integrate with Salesforce.

 

We have seen demos from Fluidtopics, Zoomin, Bluestream and easyDITA. Has anyone had any experience with these products either as CCMS or content delivery platform? Or perhaps you know of another CDP based on DITA?

 

Thanks for any information.

 

Regards,

 

 

 

Ed Tudsbery
Team Leader

 

E etudsbery@...

P +33 (0)1 41 29 36 51

Immeuble Ampère, 8, rue Eugène et Armand Peugeot, 92 500 – Rueil Malmaison, France

 

 


If you wish to view the CPA Global group email disclaimer, please click here



Re: [Ann] Oxygen XML Suite Version 22.0 Release #Oxygen

Chris Papademetrious
 

Hi Radu,

The text-to-markup automatic conversion feature is great for configuring the DITA authoring experience!

1. In the included file at

<OXYGEN_HOME>/frameworks/dita/resources/structureAutocorrect.xml

I see an additional <fragment> element that is used:

  <!-- Ordered lists -->
  <prefix-replacement prefix="1.">
    <fragment>
      <ol><li></li></ol>
    </fragment>
  </prefix-replacement>

What purpose does it serve?

2. Is there a flag to make a particular entry work when used beyond the beginning of a line? I was thinking it would be nice to change $tool to <ph keyref="Tool"/> in running body text. This would be a great keyboard-only way to insert keyref-based variables, unless there is already way to do this in the editor (in which case, please let me know if there is!).

3. Is it possible to specify more complex structures, and to specify where the cursor should go? For example, I'd like to insert this when "prompt>" is typed:

<ph keyref="Prompt"/>&gt; <user-input>CARET</user-input>

When I tried this, it only inserted the <user-input/> element.

By the way, I appreciate that this feature is incremental for extended frameworks, unlike the cc_config.xml file that must be copied and modified and placed first in the class path.

Thanks very much for such an impressive release!

 - Chris


[Ann] Oxygen XML Suite Version 22.0 Release #Oxygen

Radu Coravu
 

Hi everyone,

We released Oxygen XML Author/Editor version 22.0 a few days ago.

The entire list of new improvements can be found here:
https://www.oxygenxml.com/xml_editor/whats_new.html

Listing below some new features which may be useful for our DITA users.

Editing:

* DITA authoring enhancements include a new DITA Perspective that provides an optimal UI environment for working with DITA projects.

* Media resources (images, videos) are now presented in the DITA Reusable Components View.

* Support was added for the DITA-OT project file, used to define all the contexts and deliverables for a DITA publication project. Some of its benefits include simplified publishing using a single configuration file, the possibility to share and reuse project configurations, project-level validation support, and enhanced authoring.

* Text-to-Markup Automatic Conversions.
Some built-in frameworks have shortcut patterns that can be used to automatically insert a certain XML structure. The XML structure (fragment) automatically replaces a specific prefix pattern. For example, if you enter a hyphen (-) followed by a space at the beginning of a paragraph in a DITA document, the prefix pattern is replaced with an unordered list element (ul) with a child list item element (li). Similarly, "Note:" will be converted to a <note> element in DITA, and triple backticks to a codeblock element.

* The built-in Markdown editor is more powerful than ever. You can now apply business rule checks using real-time Schematron validation, and the editor now has synchronized scrolling between the source pane and preview pane, which offers the possibility of previewing the Markdown content as HTML, DITA, or Lightweight DITA, with the latter two facilitating the use of Markdown in the DITA ecosystem.

Add-ons:

* DITA Outgoing References View Add-on. The new DITA Outgoing References View add-on contributes a side view that shows all outgoing references for the current DITA topic. This side-view includes contextual menu actions for opening an outgoing reference or showing the definition location.

https://github.com/oxygenxml/oxygen-dita-outgoing-references-view

* Oxygen Emmet Add-on. The new Oxygen Emmet add-on provides the means for high-speed coding and editing in Text mode or Author mode via a content assistance mechanism. . For details, see: Oxygen Emmet Plugin:

https://www.oxygenxml.com/doc/versions/22.0/ug-editor/topics/emmet-addon.html

* Improvements to the Git Add-on. The Oxygen Git Support add-on has a new History side-view, a Show Blame action was added for presenting more details about a revision, and a Pull (rebase) action was added to the toolbar.

* More Types of Conversions Added to the Batch Converter Add-on. The batch converter add-on can now batch convert Microsoft Office files directly to DITA.

Publishing:

* The bundled DITA Open Toolkit was updated to version 3.4.

* DITA publishing to PDF using CSS was updated with various new parameters and styling features, and it is now possible to transform a single DITA topic to CSS-based PDF output.

* Introducing Oxygen Feedback - The New Comment Management Platform.
Version 22 marks the release of a new product called Oxygen Feedback. It is a modern comment management platform that provides a simple and efficient way for your community to interact and offer feedback. It can be embedded into WebHelp Responsive output or added to any HTML-based website. An add-on is also available that contributes a side view where you can see all the comments from your output directly in Oxygen. For more information, go to: https://www.oxygenxml.com/oxygen_feedback.html.

We hope you will enjoy Oxygen 22.0 and as always any feedback on it is welcomed.

Regards,
Radu

Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com


Re: Branch filtering on reused content #conditional-processing

Radu Coravu
 

Hi Pieterjan,

It probably depends on the order in which the DITA OT engine does the branch filtering and the conref resolution.
From what I looked it seems to first do the filtering and then the conref resolution.
In my opinion maybe something like this would work:

<topicref href="ta_ditavalref.dita" navtitle="Ditavalref">
<ditavalref href="branchfiltering.ditaval" format="ditaval"/>
<topicref href="to_reuse.dita" processing-role="resource-only"/>
</topicref>
 

otherwise you may need to define a key scope, define a key for the topic and use conkeyref in the topic.

Regards,
Radu


Re: Shout-out to Oxygen's technical support #Oxygen

Radu Coravu
 

Hi,

Thanks to everybody who contributed to the thread for the kind words.
We are happy and proud to be working for you, your questions and improvement ideas help us improve Oxygen further.

Regards,
Radu


Re: Lwdita plugin extension points #LwDITA

Radu Coravu
 

Hi Nick,

Not sure why this does not work for you.

If you look on your side in the XSLT:

plugins/org.lwdita/resources/dita2markdown_template.xsl

does it contain a line like:

<dita:extension id="dita.xsl.markdown" behavior="org.dita.dost.platform.ImportXSLAction" xmlns:dita="http://dita-ot.sourceforge.net"/>
?

Also the "org.lwdita/plugin.xml" should contain the line:

<template file="xsl/dita2markdown_template.xsl"/>
If not you may use some older lwdita plugin.

Regards,

Radu

Radu Coravu
Oxygen XML Editor
On 2/14/20 6:38 PM, Nicholas Mucks via Groups.Io wrote:
Hi Mark, Radu,

It’s unsuccessful. Adding this to the custom markdown plugin.xml file throws an integration error about dita.xsl.markdown being an undefined extension point...

<feature extension=“dita.xsl.markdown” file=“xsl/custom.xsl”/>

Is there some registry that shows all supported extension points in an implementation? It seems like the same declaration as other extension points that work, but perhaps it’s not registering properly? Maybe I’m not using it correctly.

Take care,
- Nick

Sent from mobile

On Feb 13, 2020, at 7:16 PM, Mark Giffin <mark@...> wrote:

 Hi Nick,

Can I request that you post here what happens with this? It would be useful to know.

Thanks,
Mark Giffin
Mark Giffin Consulting, Inc.
http://markgiffin.com/

On 2/13/2020 6:59 PM, Nicholas Mucks via Groups.Io wrote:
Thanks, Radu. I’ll give this markdown extension point shot.

Take care,
- Nick

Sent from mobile

On Feb 13, 2020, at 5:40 AM, Radu Coravu <radu_coravu@...> wrote:



Hi Nicholas,

There seems to be an XSLT extension point named "dita.xsl.markdown" which can be declared from your plugin and gets expanded in the DITA to MD XSLTs:

https://github.com/jelovirt/org.lwdita/blob/master/src/main/resources/dita2markdown_template.xsl

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 2/13/20 5:32 AM, Nicholas Mucks via Groups.Io wrote:
Hello!
We’d like to customize the structure of some output elements and also add the original file path and a few other details to the bottom of every page in the vanilla Markdown output. I’m not finding extension points that allow you to insert your own xslt to do this. Has anyone done this? Maybe I’m just blind.


Take care,
- Nick

Sent from mobile






Re: Lwdita plugin extension points #LwDITA

Nicholas Mucks
 

Hi Mark, Radu,

It’s unsuccessful. Adding this to the custom markdown plugin.xml file throws an integration error about dita.xsl.markdown being an undefined extension point...

<feature extension=“dita.xsl.markdown” file=“xsl/custom.xsl”/>

Is there some registry that shows all supported extension points in an implementation? It seems like the same declaration as other extension points that work, but perhaps it’s not registering properly? Maybe I’m not using it correctly.

Take care,
- Nick

Sent from mobile

On Feb 13, 2020, at 7:16 PM, Mark Giffin <mark@...> wrote:

 Hi Nick,

Can I request that you post here what happens with this? It would be useful to know.

Thanks,
Mark Giffin
Mark Giffin Consulting, Inc.
http://markgiffin.com/

On 2/13/2020 6:59 PM, Nicholas Mucks via Groups.Io wrote:
Thanks, Radu. I’ll give this markdown extension point shot.

Take care,
- Nick

Sent from mobile

On Feb 13, 2020, at 5:40 AM, Radu Coravu <radu_coravu@...> wrote:



Hi Nicholas,

There seems to be an XSLT extension point named "dita.xsl.markdown" which can be declared from your plugin and gets expanded in the DITA to MD XSLTs:

https://github.com/jelovirt/org.lwdita/blob/master/src/main/resources/dita2markdown_template.xsl

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 2/13/20 5:32 AM, Nicholas Mucks via Groups.Io wrote:
Hello!
We’d like to customize the structure of some output elements and also add the original file path and a few other details to the bottom of every page in the vanilla Markdown output. I’m not finding extension points that allow you to insert your own xslt to do this. Has anyone done this? Maybe I’m just blind.


Take care,
- Nick

Sent from mobile






Re: Lwdita plugin extension points #LwDITA

Mark Giffin
 

Hi Nick,

Can I request that you post here what happens with this? It would be useful to know.

Thanks,
Mark Giffin
Mark Giffin Consulting, Inc.
http://markgiffin.com/

On 2/13/2020 6:59 PM, Nicholas Mucks via Groups.Io wrote:
Thanks, Radu. I’ll give this markdown extension point shot.

Take care,
- Nick

Sent from mobile

On Feb 13, 2020, at 5:40 AM, Radu Coravu <radu_coravu@...> wrote:



Hi Nicholas,

There seems to be an XSLT extension point named "dita.xsl.markdown" which can be declared from your plugin and gets expanded in the DITA to MD XSLTs:

https://github.com/jelovirt/org.lwdita/blob/master/src/main/resources/dita2markdown_template.xsl

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 2/13/20 5:32 AM, Nicholas Mucks via Groups.Io wrote:
Hello!
We’d like to customize the structure of some output elements and also add the original file path and a few other details to the bottom of every page in the vanilla Markdown output. I’m not finding extension points that allow you to insert your own xslt to do this. Has anyone done this? Maybe I’m just blind.


Take care,
- Nick

Sent from mobile






Re: Lwdita plugin extension points #LwDITA

Nicholas Mucks
 

Thanks, Radu. I’ll give this markdown extension point shot.

Take care,
- Nick

Sent from mobile

On Feb 13, 2020, at 5:40 AM, Radu Coravu <radu_coravu@...> wrote:



Hi Nicholas,

There seems to be an XSLT extension point named "dita.xsl.markdown" which can be declared from your plugin and gets expanded in the DITA to MD XSLTs:

https://github.com/jelovirt/org.lwdita/blob/master/src/main/resources/dita2markdown_template.xsl

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 2/13/20 5:32 AM, Nicholas Mucks via Groups.Io wrote:
Hello!
We’d like to customize the structure of some output elements and also add the original file path and a few other details to the bottom of every page in the vanilla Markdown output. I’m not finding extension points that allow you to insert your own xslt to do this. Has anyone done this? Maybe I’m just blind.


Take care,
- Nick

Sent from mobile











Branch filtering on reused content #conditional-processing

Pieterjan Vandenweghe
 

Hi,

I am currently trying to figure out the branch filtering mechanism, but I am lost when it comes to branch filtering and reused content.
Is it possible to do branch filtering on reused content?

I will try to explain my problem with an example.

I created the following sample ditamap:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
<map>
<title>Ditaval test</title>
<topicref href="ta_ditavalref.dita" navtitle="Ditavalref">
<ditavalref href="branchfiltering.ditaval" format="ditaval"/>
</topicref>
<topicref href="to_reuse.dita" processing-role="resource-only"/>
</map>

In the topic ta_ditavalref.dita I have the following sample text (see also: attached branch_filtering.png).
In the conreffed items I added extra filtering attributes.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task PUBLIC "-//FLOW BV//DTD Agilent DITA specialization task//EN" "task.dtd">
<task id="ta_ditavalref" xml:lang="en-US">
<title>Branch filtering</title>
<taskbody>
<context>
<p conref="to_reuse.dita#untitled1/p_u4r_jwz_rkb" id="p_wn1_twz_rkb"/>
</context>
<steps>
<step audience="expert">
<cmd>This is for experts</cmd>
</step>
<step audience="novice">
<cmd>This is for novices.</cmd>
</step>
</steps>
</taskbody>
</task>

This is the reuse.dita file

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic id="untitled1">
<title>Warehouse</title>
<prolog/>
<body>
<p id="p_u4r_jwz_rkb">This information depends on the audience: <ph audience="expert">Expert</ph>
<ph audience="novice">Novice</ph></p>
</body>
</topic>
 


When I process these files to PDF/HTML and exclude audience="novice" via branch-filtering, the branch-filtering works fine on the filtering attributes which are present in the topic itself, ie. the two steps.
However the branch filtering doesn't work on the 'conreffed' item in my reuse.dita file. Both <ph> elements are published (see branch_filtering_pdf.png).

Is it possible to get this working on the conreffed items too? How should I change my structure to get this done?
Please find attached my sample DITAMAP for reference.

In my current project I need to add a similar DITAMAP twice in one publication, once with info for the experts and once with for the novices.
If possible I would like to use branch filtering.

Thanks a lot for your help in advance.

Kind regards,
Pieterjan





Re: Lwdita plugin extension points #LwDITA

Radu Coravu
 

Hi Nicholas,

There seems to be an XSLT extension point named "dita.xsl.markdown" which can be declared from your plugin and gets expanded in the DITA to MD XSLTs:

https://github.com/jelovirt/org.lwdita/blob/master/src/main/resources/dita2markdown_template.xsl

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 2/13/20 5:32 AM, Nicholas Mucks via Groups.Io wrote:

Hello!
We’d like to customize the structure of some output elements and also add the original file path and a few other details to the bottom of every page in the vanilla Markdown output. I’m not finding extension points that allow you to insert your own xslt to do this. Has anyone done this? Maybe I’m just blind.


Take care,
- Nick

Sent from mobile





  


Lwdita plugin extension points #LwDITA

Nicholas Mucks
 

Hello!
We’d like to customize the structure of some output elements and also add the original file path and a few other details to the bottom of every page in the vanilla Markdown output. I’m not finding extension points that allow you to insert your own xslt to do this. Has anyone done this? Maybe I’m just blind.


Take care,
- Nick

Sent from mobile

1061 - 1080 of 46276