Using DITA 1.3 with DITA-OT 2.x
92 views
Skip to first unread message
Frank Ralf
Aug 28, 2015, 11:25:11 AM8/28/15
to DITA-OT Users
Hi,
I cannot see a plugin for DITA 1.3 at https://github.com/dita-ot/dita-ot/tree/develop/src/main/plugins. Do I have to integrate the DITA 1.3 doc types manually to get full/better DITA 1.3 support?
Kind regards,
Frank
I cannot see a plugin for DITA 1.3 at https://github.com/dita-ot/dita-ot/tree/develop/src/main/plugins. Do I have to integrate the DITA 1.3 doc types manually to get full/better DITA 1.3 support?
Kind regards,
Frank
Kristen James Eberlein
Aug 30, 2015, 8:26:42 PM8/30/15
to dita-o...@googlegroups.com
If I set <property name="args.chapter.layout" value="BASIC"/>,
then the <shortdesc> in the topic that is referenced by a
<chapter> or <appendix> element is NOT rendered.
Is this is a known bug, or should I report it?
Is this is a known bug, or should I report it?
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
Radu Coravu
Aug 31, 2015, 1:25:56 AM8/31/15
to Frank Ralf, DITA-OT Users
Hi Frank,
For now you would have to manually install DITA 1.3 plugins in the DITA OT 2.1.
Oasis recommends that instead of the schemas used in Eliot's project you use the ones available on its web site:
https://www.oasis-open.org/committees/document.php?document_id=56284&wg_abbrev=dita
https://www.oasis-open.org/committees/document.php?document_id=56284&wg_abbrev=dita
If you are interested I can make available to you an Oxygen 17.1 beta kit which contains the latest DITA OT 2.1 + DITA 1.3 plugins already integrated.
--
You received this message because you are subscribed to the Google Groups "DITA-OT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dita-ot-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Radu Coravu
Aug 31, 2015, 2:12:36 AM8/31/15
to Kristen James Eberlein, DITA-OT Users
Hi Kris,
I cannot reproduce this on my side but maybe I'm not understanding the entire situation.
I cannot reproduce this on my side but maybe I'm not understanding the entire situation.
Maybe you should try to come up with a small sample DITA Book Map + 1,2 topics to reproduce the issue.
If you want I can also test it on my side before adding an issue.
--
Frank Ralf
Aug 31, 2015, 3:45:53 AM8/31/15
to DITA-OT Users, frank...@gmx.de
Hi Radu,
Thanks for this information. I find it sometimes difficult to find the correct page on the OASIS website.
And yes, I'd like to have a look at oXygen 17.1 (if I find the time).
Best regards,
Frank
Thanks for this information. I find it sometimes difficult to find the correct page on the OASIS website.
And yes, I'd like to have a look at oXygen 17.1 (if I find the time).
Best regards,
Frank
Kristen James Eberlein
Aug 31, 2015, 4:57:02 AM8/31/15
to dita-o...@googlegroups.com
Sure, Radu -- thanks. I noticed this while building a
new PDF customization to generate OASIS Committee Notes in PDF
format, but reproduced it with the sample content that ships
with the Toolkit. FWIW, this problems does not occur if you use
the MINITOC layout.
Test scenario
Build a PDF using samples/taskbook.ditamap AND <property name="args.chapter.layout" value="BASIC"/>.
Chapter one of the bookmap references installing.dita, which contains the following content (<shortdesc> and its content highlighted in red):
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "../../dtd/topic.dtd">
<topic id="installing" xml:lang="en-us">
<title>Installing</title>
<shortdesc>You install components to make them available for your
solution.</shortdesc>
<body>
<p>Usually, you can install the components once and then forget about the
details of this task. Before installing the components, you should make a plan for what you need to
accomplish and the components that will support these goals. After installing
the components, you will probably want to perform some preliminary configuration. </p>
</body>
</topic>
Result from DITA-OT 2.1
Test scenario
Build a PDF using samples/taskbook.ditamap AND <property name="args.chapter.layout" value="BASIC"/>.
Chapter one of the bookmap references installing.dita, which contains the following content (<shortdesc> and its content highlighted in red):
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "../../dtd/topic.dtd">
<topic id="installing" xml:lang="en-us">
<title>Installing</title>
<shortdesc>You install components to make them available for your
solution.</shortdesc>
<body>
<p>Usually, you can install the components once and then forget about the
details of this task. Before installing the components, you should make a plan for what you need to
accomplish and the components that will support these goals. After installing
the components, you will probably want to perform some preliminary configuration. </p>
</body>
</topic>
Result from DITA-OT 2.1
Note that the content of the
<shortdesc> element -- "You install components to make them
available for your solution." -- is not rendered. It's also
not in topic.fo.
Result from DITA-OT 1.8.5
Result from DITA-OT 1.8.5
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
Kristen James Eberlein
Aug 31, 2015, 5:08:53 AM8/31/15
to dita-o...@googlegroups.com
I've opened a GitHub issue for this:
https://github.com/dita-ot/dita-ot/issues/2023
https://github.com/dita-ot/dita-ot/issues/2023
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
Frank Ralf
Sep 3, 2015, 9:21:49 AM9/3/15
to DITA-OT Users, frank...@gmx.de
Hi Radu,
Besides installing the DITA 1.3 plugin, should I keep or remove the existing DITA 1.2 plugin (org.oasis-open.dita.v1_2)?
Kind regards,
Besides installing the DITA 1.3 plugin, should I keep or remove the existing DITA 1.2 plugin (org.oasis-open.dita.v1_2)?
Kind regards,
Frank
On Monday, August 31, 2015 at 7:25:56 AM UTC+2, Radu Coravu wrote:
Radu Coravu
Sep 3, 2015, 9:32:01 AM9/3/15
to Frank Ralf, DITA-OT Users
Hi Frank,
if you do not remove the DITA 1.2 DTDs plugin there is a possibility that the "catalog-dita.xml" will prefer to resolve the standard DITA public IDs with the DITA 1.2 DTDs instead of the DITA 1.3 DTDs.
The Relax NG based maps and topics will always work with the DITA 1.3 schemas (because there were no DITA 1.2 schemas for them).
Frank Ralf
Sep 3, 2015, 9:47:49 AM9/3/15
to DITA-OT Users, frank...@gmx.de
Hi Radu,
The official files still contain a typo Toshihiko Makita has reported at https://lists.oasis-open.org/archives/dita-comment/201507/msg00001.html:
dita-v1.3-csprd01\part3-all-inclusive\dita-v1.3-csprd01-part3-all-inclusive-grammars\rng\technicalContent\catalog.xml line 98 to 101:
<system systemId="urn:oasis:names:tc:dita:rng:taksMod.rng:1.3" uri="rng/taskMod.rng"/>
<system systemId="urn:oasis:names:tc:dita:rng:taksMod.rng" uri="rng/taskMod.rng"/>
This should be following:
<system systemId="urn:oasis:names:tc:dita:rng:taskMod.rng:1.3" uri="rng/taskMod.rng"/>
<system systemId="urn:oasis:names:tc:dita:rng:taskMod.rng" uri="rng/taskMod.rng"/>
The official files still contain a typo Toshihiko Makita has reported at https://lists.oasis-open.org/archives/dita-comment/201507/msg00001.html:
dita-v1.3-csprd01\part3-all-inclusive\dita-v1.3-csprd01-part3-all-inclusive-grammars\rng\technicalContent\catalog.xml line 98 to 101:
<system systemId="urn:oasis:names:tc:dita:rng:taksMod.rng:1.3" uri="rng/taskMod.rng"/>
<system systemId="urn:oasis:names:tc:dita:rng:taksMod.rng" uri="rng/taskMod.rng"/>
This should be following:
<system systemId="urn:oasis:names:tc:dita:rng:taskMod.rng:1.3" uri="rng/taskMod.rng"/>
<system systemId="urn:oasis:names:tc:dita:rng:taskMod.rng" uri="rng/taskMod.rng"/>
On Monday, August 31, 2015 at 7:25:56 AM UTC+2, Radu Coravu wrote:
Kendall Shaw
Sep 3, 2015, 5:22:20 PM9/3/15
to DITA-OT Users
That typo is not there when I look at the files from:
Kendall
Kristen James Eberlein
Sep 3, 2015, 6:36:31 PM9/3/15
to dita-o...@googlegroups.com
Note the highlighted part of the URL:
dita-v1.3-csprd01\part3-all-inclusive\dita-v1.3-csprd01-part3-all-inclusive-grammars\rng\technicalContent\catalog.xml
csprd stands for committee specification public review draft;
this is the version of the DITA 1.2 specification that Toshihiko
Makita commented on.
A more recent version of the DITA 1.3 spec can be found at the following URL.
http://docs.oasis-open.org/dita/dita/v1.3/cs01/part3-all-inclusive/dita-v1.3-cs01-part3-all-inclusive.html
A more recent version of the DITA 1.3 spec can be found at the following URL.
http://docs.oasis-open.org/dita/dita/v1.3/cs01/part3-all-inclusive/dita-v1.3-cs01-part3-all-inclusive.html
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
Kendall Shaw
Sep 3, 2015, 6:52:59 PM9/3/15
to dita-o...@googlegroups.com
Thanks. For people trying to not fall behind too much on developments is there a reason to stick with the public review draft instead of cs01?
Kendall
Kristen James Eberlein
Sep 3, 2015, 6:56:42 PM9/3/15
to dita-o...@googlegroups.com
No. Committee specification 01 (cs01) includes fixes made in
response to the public review; it is the most recent and best.
It is very unlikely that we will make any future changes.
It is very unlikely that we will make any future changes.
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
Frank Ralf
Sep 7, 2015, 4:05:25 AM9/7/15
to DITA-OT Users
Hi Kris,
That's the version I'm talking about: http://docs.oasis-open.org/dita/dita/v1.3/cs01/part3-all-inclusive/dita-v1.3-cs01-part3-all-inclusive-grammars.zip
Line 72 of taskMod.rng contains the typo:
<rngMod>urn:oasis:names:tc:dita:rng:taksMod.rng<var presep=":" name="ditaver"/></rngMod>
Sorry for not being more precise in my original post. Is there a place where to post a patch or a pull request for this kind of error?
Best regards,
Frank
That's the version I'm talking about: http://docs.oasis-open.org/dita/dita/v1.3/cs01/part3-all-inclusive/dita-v1.3-cs01-part3-all-inclusive-grammars.zip
Line 72 of taskMod.rng contains the typo:
<rngMod>urn:oasis:names:tc:dita:rng:taksMod.rng<var presep=":" name="ditaver"/></rngMod>
Sorry for not being more precise in my original post. Is there a place where to post a patch or a pull request for this kind of error?
Best regards,
Frank
Frank Ralf
Sep 7, 2015, 4:08:56 AM9/7/15
to DITA-OT Users, frank...@gmx.de
Hi Radu,
Thanks for this information. I will keep an eye open whether this issue affects our customization.
Kind regards,
Frank
Thanks for this information. I will keep an eye open whether this issue affects our customization.
Kind regards,
Frank
On Thursday, September 3, 2015 at 3:32:01 PM UTC+2, Radu Coravu wrote:
Hi Frank,
if you do not remove the DITA 1.2 DTDs plugin there is a possibility that the "catalog-dita.xml" will prefer to resolve the standard DITA public IDs with the DITA 1.2 DTDs instead of the DITA 1.3 DTDs.
Kendall Shaw
Sep 8, 2015, 2:04:45 PM9/8/15
to DITA-OT Users
I hope this doesn't distract from the question:
First, I see that typo also.
Practically, I think that particular typo, unlike the one that was in catalog in the csprd grammars, only has a practical consequence for software that uses the metadata for conversion, like Eliot's dtd-rng converter.
In other words, it would not prevent the grammars from being used in DITA-OT. For example, I had no problem using the cs01 RNG schemas with the tasks in the demo files that were in dita-ng on googlecode.
Kendall
Reply all
Reply to author
Forward
0 new messages