Date   

Diagram XML markup/definition language within DITA?

Daud Vyd
 

Hello,

I'd like to create tree diagrams and flowcharts for insertion in my DITA documents. I'm familiar with tools like GraphViz but see that Oxygen-XML has support for creating similar diagrams for XML Schema visualization. Are people using Oxygen-XML or another tool to create diagrams in a format that is particularly suitable for DITA documents?

thank you,
-d. vyd


[ann] Oxygen Terminology Checker add-on has been released! #Oxygen

alin_belu@...
 

Hello, 


We want to let you know that the 
Oxygen Terminology Checker add-on has been released! 

With this add-on, you can create mappings between matched terms (words or sequences of words) and their suggested replacements. The incorrect terms that you will configure will be highlighted in the Author visual editing mode. 

You can right-click the highlights to access various actions allowing you to replace each individual highlight with suggestions or to apply the same suggestion in multiple places in the opened document. 

The add-on is free to use and it is available starting with version 21.1 of Oxygen XML Editor.

For a complete guide on how to install and use the new Oxygen Terminology Checker add-onread the following article: 


Best regards,
 
Alin 

--
Alin Belu
Oxygen XML Editor


Re: Text in SVG images not searchable in DITA-OT 3.x HTML5 output

Dan Vint
 

I found a similar problem with external links in an svg. Standalone the svg worked in the browser but referenced from the html generated the links didn't  work. In my case using a svgref element corrected the problem. I wanted to keep 2 separate files.



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Radu Coravu <radu_coravu@...>
Date: 6/16/20 2:52 AM (GMT-08:00)
To: main@dita-users.groups.io, dita-users@groups.io
Subject: Re: [dita-users] Text in SVG images not searchable in DITA-OT 3.x HTML5 output

Hi Yves,

You can try pasting the SVG content directly inside the DITA topic
inside an svg-container element, this should generate an HTML file
containing the embedded SVG, I think the browser will be able to allow
searching inside it if you do so.
If you are referring to the SVG using the DITA <image> tag it probably
needs to be published embedded inside the HTML instead of referenced
using <img src>.
A while back I created a plugin for this:

https://github.com/oxygenxml/dita-embed-html-mathml-svg

Regards,
Radu

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

On 6/16/2020 12:43 PM, Yves Barbion wrote:
> Hi group
>
> I've got SVG images which contain text. If I just open the SVG in one of
> my browsers (Chrome, Firefox, Edge), the text is searchable. If I put
> the images in a DITA topic and generate HTML5 output with the DITA-OT
> 3.x, the text is no longer searchable.
>
> Any idea why this happens and how it can be fixed?
>
> Thanks
>
> Yves
>






Re: Text in SVG images not searchable in DITA-OT 3.x HTML5 output

Yves Barbion
 

Hi Radu

Your plugin works (of course! ;-) ). Thank you very much.

Kind regards

Yves

On Tue, 16 Jun 2020 at 11:52, Radu Coravu <radu_coravu@...> wrote:
Hi Yves,

You can try pasting the SVG content directly inside the DITA topic
inside an svg-container element, this should generate an HTML file
containing the embedded SVG, I think the browser will be able to allow
searching inside it if you do so.
If you are referring to the SVG using the DITA <image> tag it probably
needs to be published embedded inside the HTML instead of referenced
using <img src>.
A while back I created a plugin for this:

https://github.com/oxygenxml/dita-embed-html-mathml-svg

Regards,
Radu

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

On 6/16/2020 12:43 PM, Yves Barbion wrote:
> Hi group
>
> I've got SVG images which contain text. If I just open the SVG in one of
> my browsers (Chrome, Firefox, Edge), the text is searchable. If I put
> the images in a DITA topic and generate HTML5 output with the DITA-OT
> 3.x, the text is no longer searchable.
>
> Any idea why this happens and how it can be fixed?
>
> Thanks
>
> Yves
>






Re: Text in SVG images not searchable in DITA-OT 3.x HTML5 output

Radu Coravu
 

Hi Yves,

You can try pasting the SVG content directly inside the DITA topic inside an svg-container element, this should generate an HTML file containing the embedded SVG, I think the browser will be able to allow searching inside it if you do so.
If you are referring to the SVG using the DITA <image> tag it probably needs to be published embedded inside the HTML instead of referenced using <img src>.
A while back I created a plugin for this:

https://github.com/oxygenxml/dita-embed-html-mathml-svg

Regards,
Radu

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

On 6/16/2020 12:43 PM, Yves Barbion wrote:
Hi group
I've got SVG images which contain text. If I just open the SVG in one of my browsers (Chrome, Firefox, Edge), the text is searchable. If I put the images in a DITA topic and generate HTML5 output with the DITA-OT 3.x, the text is no longer searchable.
Any idea why this happens and how it can be fixed?
Thanks
Yves


Re: Text in SVG images not searchable in DITA-OT 3.x HTML5 output

David Hollis
 

Hi Yves,

Is it possible that something in the pipeline creates a raster image preview, or even converts SVG to a raster image?

What's the current browser support for SVG images? Do they all support it?

HTH,
David


Hi group

I've got SVG images which contain text. If I just open the SVG in one of my browsers (Chrome, Firefox, Edge), the text is searchable. If I put the images in a DITA topic and generate HTML5 output with the DITA-OT 3.x, the text is no longer searchable.

Any idea why this happens and how it can be fixed?

Thanks

Yves


Text in SVG images not searchable in DITA-OT 3.x HTML5 output

Yves Barbion
 

Hi group

I've got SVG images which contain text. If I just open the SVG in one of my browsers (Chrome, Firefox, Edge), the text is searchable. If I put the images in a DITA topic and generate HTML5 output with the DITA-OT 3.x, the text is no longer searchable.

Any idea why this happens and how it can be fixed?

Thanks

Yves


[ann][webinar] Oxygen Markdown Support #Oxygen

alin_belu@...
 

Hello everyone,

Our weekly series of live events continues on June 17 with the “Oxygen Markdown Support” webinar.
 

During this live event, Alex Jitianu, lead developer at Syncro Soft, will focus on showing you how Oxygen XML Editor supports SMEs (developers, or engineers) working with Markdown documents by offering features such as: 

  • Editing support 
  • Conversion to other formats, like HTML or DITA 
  • Using Schematron rules to validate and check for completeness in a Markdown file 
  • MDITA, the authoring format of LwDITA that uses Markdown to structure information 

 

You can register for free at http://www.oxygenxml.com/evs2020-4.html 

 

Check the full list of the upcoming webinars and follow the links to see more details and register for free: 

17 June  – Oxygen Markdown Support 

 

Best regards, 
Alin

--
Alin Belu
Oxygen XML Editor


Re: Official docker image missing tools.jar?

Radu Coravu
 

Hi Nick,

This is a warning:

Unable to locate tools.jar. Expected to find it in /opt/java/openjdk/lib/tools.jar
which the ANT processor gives when a Java Virtual Machine without an SDK (used to compile Java code) is used to run it. As your publishing does not need a Java compiler, you can safely ignore it.

The error is this one:

Unable to locate tools.jar. Expected to find it in /opt/java/openjdk/lib/tools.jar
java.lang.IllegalArgumentException: -c
The command line seems to pass an argument named "-c" to the "bin\dita" executable and the executable complains that it does not know what it is and exits.

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 6/12/20 3:40 AM, Nicholas Mucks via groups.io wrote:
hello~

We're migrating to the official DITA-OT 3.5 docker image but it looks like it's missing tools.jar:

Unable to locate tools.jar. Expected to find it in /opt/java/openjdk/lib/tools.jar
java.lang.IllegalArgumentException: -c
	at org.dita.dost.invoker.ConversionArguments.parse(ConversionArguments.java:159)
	at org.dita.dost.invoker.ArgumentParser.processArgs(ArgumentParser.java:123)
	at org.dita.dost.invoker.Main.processArgs(Main.java:267)
	at org.dita.dost.invoker.Main.startAnt(Main.java:160)
	at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
	at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
ERROR: Job failed: exit code 1


This happens whenever we try to publish output using exec mode. It works OK if we use the the shell mode, which is what is described in the documentation, but that won't fit into the existing process as well. 

Has anyone encountered this and maybe found a workaround?  It's this image: docker.pkg.github.com/dita-ot/dita-ot/dita-ot:3.5

Thanks!
Nick


  


Official docker image missing tools.jar?

Nicholas Mucks
 

hello~

We're migrating to the official DITA-OT 3.5 docker image but it looks like it's missing tools.jar:

Unable to locate tools.jar. Expected to find it in /opt/java/openjdk/lib/tools.jar
java.lang.IllegalArgumentException: -c
at org.dita.dost.invoker.ConversionArguments.parse(ConversionArguments.java:159)
at org.dita.dost.invoker.ArgumentParser.processArgs(ArgumentParser.java:123)
at org.dita.dost.invoker.Main.processArgs(Main.java:267)
at org.dita.dost.invoker.Main.startAnt(Main.java:160)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
ERROR: Job failed: exit code 1


This happens whenever we try to publish output using exec mode. It works OK if we use the the shell mode, which is what is described in the documentation, but that won't fit into the existing process as well. 

Has anyone encountered this and maybe found a workaround?  It's this image: docker.pkg.github.com/dita-ot/dita-ot/dita-ot:3.5

Thanks!
Nick


Re: DTD syntax checking

Larry Kollar
 

Hi Radu,
I'll check to see if the employer is OK with sending those. I think I solved the problem, but I'll give as much detail as possible in hopes of better troubleshooting techniques in the future.


Re: DTD syntax checking

George Cristian Bina
 

Hi,

From this message:
***
Could not resolve PublicID: [null] SystemID: [file:/.../com.dtd.test/dtd/technicalContent/dtd/ourReference.dtd]
***

It looks like your document specifies a DTD using a SYSTEM identified and without a PUBLIC identifier.
This means that the catalog resolution is done on the SYSTEM identifier. If that SYSTEM identifier is a relative location (not an absolute URI) then that is very sensible to both finding the DTD location and mapping it thought the catalog, because it is made absolute before going to the catalog to be resolved.
As Bill also mentioned, if the file is not saved then the base URL for resolving relative references will be considered the oXygen working directory, and that may also create issues.

To get to the point, please check if you are using relative references and if that is the case then this is probably the reason for the issue. There are a few solutions:

- resolve the references using resoveSuffix entries in the catalog, thus you basically ignore the variable part of the absolute URL that will be used for catalog resolution
- use absolute URLs instead, you resolve them anyway through the catalog
- use also PUBLIC identifiers and prefer them for catalog resolution

Hope this helps!

Best Regards,
George
--
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 6/11/20 5:11 PM, Bill Burns wrote:
Hi, Larry.
I seem to recall seeing this happen if I'm not using a project ion Oxygen and on initial creation of topics with a custom DTD. The error would go away once the topic is saved.
--
*Bill Burns*
bb@simplea.com <mailto:bb@simplea.com>
512-646-2100 ext. 365
--
*We are [A] *
simplea.com <http://simplea.com>;
On Wed, Jun 10, 2020 at 10:07 PM Radu Coravu <radu_coravu@sync.ro <mailto:radu_coravu@sync.ro>> wrote:
Hi Larry,
If you can provide us (support@oxygenxml.com
<mailto:support@oxygenxml.com>) with a sample XML document, DTD
specialization plugin and steps to reproduce the problem I can try
to look more into this.
Because right now I do not know how the DTD is mapped through the
XML catalog, I do not know how the XML document refers to the DTD
and what precise error you get when you attempt to validate the
newly created XML document before saving it.
Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 6/11/20 12:10 AM, Larry Kollar wrote:
We've recently been alerted to an issue in our (mostly
constrained) DTDs. If I set the catalog in Oxygen 20.1 to use the
directory where I'm storing a working set, it will trip errors
when I attempt to create certain topics (path scrubbed):

Could not resolve PublicID: [null] SystemID:
[file:/.../com.dtd.test/dtd/technicalContent/dtd/ourReference.dtd]

I've been all through the catalogs and ent/mod files. I corrected
a couple of issues, and that reduced but didn't eliminate the
errors. Is there anything in Oxygen that can provide a more
specific pointer to the problem? The "ourReference.dtd" is defined
in the catalog, for example, so I don't know why it can't resolve
the public ID.

Interestingly enough, the error occurs when creating a topic from
templates we stored in Oxygen. BUT, if I save the created topic
file and re-open it, no errors.


Re: DTD syntax checking

Bill Burns
 

Hi, Larry.

I seem to recall seeing this happen if I'm not using a project ion Oxygen and on initial creation of topics with a custom DTD. The error would go away once the topic is saved.

--
Bill Burns
512-646-2100 ext. 365
--
We are [A] 


On Wed, Jun 10, 2020 at 10:07 PM Radu Coravu <radu_coravu@...> wrote:

Hi Larry,

If you can provide us (support@...) with a sample XML document, DTD specialization plugin and steps to reproduce the problem I can try to look more into this.

Because right now I do not know how the DTD is mapped through the XML catalog, I do not know how the XML document refers to the DTD and what precise error you get when you attempt to validate the newly created XML document before saving it.

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 6/11/20 12:10 AM, Larry Kollar wrote:
We've recently been alerted to an issue in our (mostly constrained) DTDs. If I set the catalog in Oxygen 20.1 to use the directory where I'm storing a working set, it will trip errors when I attempt to create certain topics (path scrubbed):

Could not resolve PublicID: [null] SystemID: [file:/.../com.dtd.test/dtd/technicalContent/dtd/ourReference.dtd]

I've been all through the catalogs and ent/mod files. I corrected a couple of issues, and that reduced but didn't eliminate the errors. Is there anything in Oxygen that can provide a more specific pointer to the problem? The "ourReference.dtd" is defined in the catalog, for example, so I don't know why it can't resolve the public ID.

Interestingly enough, the error occurs when creating a topic from templates we stored in Oxygen. BUT, if I save the created topic file and re-open it, no errors.


  



Re: DTD syntax checking

Radu Coravu
 

Hi Larry,

If you can provide us (support@...) with a sample XML document, DTD specialization plugin and steps to reproduce the problem I can try to look more into this.

Because right now I do not know how the DTD is mapped through the XML catalog, I do not know how the XML document refers to the DTD and what precise error you get when you attempt to validate the newly created XML document before saving it.

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 6/11/20 12:10 AM, Larry Kollar wrote:

We've recently been alerted to an issue in our (mostly constrained) DTDs. If I set the catalog in Oxygen 20.1 to use the directory where I'm storing a working set, it will trip errors when I attempt to create certain topics (path scrubbed):

Could not resolve PublicID: [null] SystemID: [file:/.../com.dtd.test/dtd/technicalContent/dtd/ourReference.dtd]

I've been all through the catalogs and ent/mod files. I corrected a couple of issues, and that reduced but didn't eliminate the errors. Is there anything in Oxygen that can provide a more specific pointer to the problem? The "ourReference.dtd" is defined in the catalog, for example, so I don't know why it can't resolve the public ID.

Interestingly enough, the error occurs when creating a topic from templates we stored in Oxygen. BUT, if I save the created topic file and re-open it, no errors.


  


DTD syntax checking

Larry Kollar
 

We've recently been alerted to an issue in our (mostly constrained) DTDs. If I set the catalog in Oxygen 20.1 to use the directory where I'm storing a working set, it will trip errors when I attempt to create certain topics (path scrubbed):

Could not resolve PublicID: [null] SystemID: [file:/.../com.dtd.test/dtd/technicalContent/dtd/ourReference.dtd]

I've been all through the catalogs and ent/mod files. I corrected a couple of issues, and that reduced but didn't eliminate the errors. Is there anything in Oxygen that can provide a more specific pointer to the problem? The "ourReference.dtd" is defined in the catalog, for example, so I don't know why it can't resolve the public ID.

Interestingly enough, the error occurs when creating a topic from templates we stored in Oxygen. BUT, if I save the created topic file and re-open it, no errors.


Re: Compatibility question

Bill Burns
 

Thanks, Radu.


On Tue, Jun 9, 2020 at 1:37 AM Radu Coravu <radu_coravu@...> wrote:

Hi Bill,

The Oxygen Web Author has a server side component and a client side component (which uses HTML and Javascript).

The server side component does not work on Chromebook due to the restrictive nature of the OS, but nobody would install a server on Chromebook anyway.

But the client side component (which is actually used by end users to edit content) should work also on Chromebooks.

You can use our online demo web author to try it on your side:

https://www.oxygenxml.com/oxygen-xml-web-author/app/oxygen.html

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 6/8/20 10:02 PM, Bill Burns wrote:
Greetings,

Is anyone using or supporting Oxygen XML Web Author on Chromebook? 

-- 
Bill Burns
512-646-2100
--
We are [A] 


  



--
Bill Burns
512-646-2100
--
We are [A] 


Re: Compatibility question

Radu Coravu
 

Hi Bill,

The Oxygen Web Author has a server side component and a client side component (which uses HTML and Javascript).

The server side component does not work on Chromebook due to the restrictive nature of the OS, but nobody would install a server on Chromebook anyway.

But the client side component (which is actually used by end users to edit content) should work also on Chromebooks.

You can use our online demo web author to try it on your side:

https://www.oxygenxml.com/oxygen-xml-web-author/app/oxygen.html

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 6/8/20 10:02 PM, Bill Burns wrote:

Greetings,

Is anyone using or supporting Oxygen XML Web Author on Chromebook? 

-- 
Bill Burns
512-646-2100
--
We are [A] 


  


Compatibility question

Bill Burns
 

Greetings,

Is anyone using or supporting Oxygen XML Web Author on Chromebook? 

-- 
Bill Burns
512-646-2100
--
We are [A] 


Re: Project files in OT 3.5

Nicholas Mucks
 

that did it. thanks, Radu!

On Thursday, June 4, 2020, 08:10:19 PM PDT, Radu Coravu <radu_coravu@...> wrote:


Hi Nick,

I found the same problem about 2 days ago:

https://github.com/dita-ot/dita-ot/issues/3526

You should specify in the command line also a base output folder like:

--output=.

This should remove the NPE.

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 6/5/20 12:58 AM, Nicholas Mucks via groups.io wrote:
Hi,
We're exploring project files. They seem to work fine in DITA-OT 3.4 but throw this error in DITA-OT 3.5:

java.lang.NullPointerException

at org.dita.dost.invoker.Main.lambda$handleProject$3(Main.java:397)

at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)

at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)

at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1654)

at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)

at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)

at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)

at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)

at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)

at org.dita.dost.invoker.Main.handleProject(Main.java:443)

at org.dita.dost.invoker.Main.processArgs(Main.java:342)

at org.dita.dost.invoker.Main.startAnt(Main.java:160)

at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)

at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)


We're testing with the project files that come with OT itself. It looks something like this:

dita-ot/3.4/dev/bin/dita --project=/dita-ot/3.4/dev/docsrc/samples/project-files/pdf.xml > succeeds
dita-ot/3.5/dev/bin/dita --project=/dita-ot/3.5/dev/docsrc/samples/project-files/pdf.xml > fails

Any thoughts?

Thanks,
Nick




  


Re: Project files in OT 3.5

Radu Coravu
 

Hi Nick,

I found the same problem about 2 days ago:

https://github.com/dita-ot/dita-ot/issues/3526

You should specify in the command line also a base output folder like:

--output=.

This should remove the NPE.

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 6/5/20 12:58 AM, Nicholas Mucks via groups.io wrote:

Hi,
We're exploring project files. They seem to work fine in DITA-OT 3.4 but throw this error in DITA-OT 3.5:

java.lang.NullPointerException

at org.dita.dost.invoker.Main.lambda$handleProject$3(Main.java:397)

at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)

at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)

at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1654)

at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)

at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)

at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)

at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)

at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)

at org.dita.dost.invoker.Main.handleProject(Main.java:443)

at org.dita.dost.invoker.Main.processArgs(Main.java:342)

at org.dita.dost.invoker.Main.startAnt(Main.java:160)

at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)

at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)


We're testing with the project files that come with OT itself. It looks something like this:

dita-ot/3.4/dev/bin/dita --project=/dita-ot/3.4/dev/docsrc/samples/project-files/pdf.xml > succeeds
dita-ot/3.5/dev/bin/dita --project=/dita-ot/3.5/dev/docsrc/samples/project-files/pdf.xml > fails

Any thoughts?

Thanks,
Nick




  

441 - 460 of 45963