<abbreviated-form> not shown in pdf
Post here questions and problems related to editing and publishing DITA content.
-
- Posts: 19
- Joined: Fri Feb 10, 2017 6:10 pm
<abbreviated-form> not shown in pdf
Post by grethelgomez »
Hi,
My team uses custom DITA plugins in Oxygen 18.
When generating a pdf, the glossary terms that are not shown are the ones referenced with <abbreviated-form @keyref> that have <keyword @conkeyref> inside the <glossentry>.
This is similar to the issue presented in post51208.html?hilit=abbreviated%20form#p50909.
Example:
Output of the pdf: "Testing this problem with Gloss Term One and "
Source files:
Topic.dita has inside one of its elements the following paragraph:
The two glossentries are similar except that GlossTermTwo has a <keyword @conkeyref>:
I also have Oxygen 21.1 because we'll be moving to this newer version later this year. I tested the custom pdf plugin, built for OT 2.x, and it seems to work fine in Oxygen 21.1. All the <abbreviated-form> show in the pdf. However, we cannot move to Oxygen 21.1 right now because the other plugins don't work.
How could we apply the fixes for <abbreviated-form> done in Oxygen 21 to Oxygen 18?
This would help us to continue working with our custom plugins in Oxygen 18 until we are ready to move to 21.
Thanks in advance!
Grethel Gomez.
My team uses custom DITA plugins in Oxygen 18.
When generating a pdf, the glossary terms that are not shown are the ones referenced with <abbreviated-form @keyref> that have <keyword @conkeyref> inside the <glossentry>.
This is similar to the issue presented in post51208.html?hilit=abbreviated%20form#p50909.
Example:
Output of the pdf: "Testing this problem with Gloss Term One and "
Source files:
Topic.dita has inside one of its elements the following paragraph:
Code: Select all
<p>Testing this problem with <abbreviated-form keyref="GlossTermOne_glosskey"/> and <abbreviated-form keyref="GlossTermTwo_glosskey"/></p>
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glossentry PUBLIC "-//OASIS//DTD DITA Glossary//EN" "glossary.dtd">
<glossentry id="GlossTermTwo" xml:lang="en-US">
<glossterm>Gloss Term Two</glossterm>
<glossdef><ph>Definition of Gloss Term Two that references the product <keyword conkeyref="OneOfMyProducts" />
using a keyword .</ph></glossdef>
<prolog>
<!--<meta info here>-->
</prolog>
<glossBody>
<glossSurfaceForm>Gloss Term Two</glossSurfaceForm>
<glossAlt>
<glossAcronym>GTT</glossAcronym>
</glossAlt>
</glossBody>
</glossentry>
I also have Oxygen 21.1 because we'll be moving to this newer version later this year. I tested the custom pdf plugin, built for OT 2.x, and it seems to work fine in Oxygen 21.1. All the <abbreviated-form> show in the pdf. However, we cannot move to Oxygen 21.1 right now because the other plugins don't work.
How could we apply the fixes for <abbreviated-form> done in Oxygen 21 to Oxygen 18?
This would help us to continue working with our custom plugins in Oxygen 18 until we are ready to move to 21.
Thanks in advance!
Grethel Gomez.
-
- Posts: 9436
- Joined: Fri Jul 09, 2004 5:18 pm
Re: <abbreviated-form> not shown in pdf
Dear Grethel,
The similar post you found is for producing PDF from DITA using CSS for styling the output. It's a new transformation type we developed over the last years and it's not really related to the classic PDF output you are obtaining from DITA right now.
Oxygen 21.1 comes bundled with DITA OT 3.x which indeed might have fixed various problems that you are experiencing in the DITA OT 2.x you are using right now. But it's hard to know exactly when the problem was fixed and what the problem implied (maybe the problem was fixed in a Java library so it's not an XSLT fix, the entire Java library from the DITA OT 2.x distribution would need to be updated with a fix).
So sorry but I don't think we can provide a backward fix for this. As a workaround you could try to avoid using that construct which seems to cause the problem in the glossdef (maybe use conref instead of conkeyref if it works better).
Regards,
Radu
The similar post you found is for producing PDF from DITA using CSS for styling the output. It's a new transformation type we developed over the last years and it's not really related to the classic PDF output you are obtaining from DITA right now.
Oxygen 21.1 comes bundled with DITA OT 3.x which indeed might have fixed various problems that you are experiencing in the DITA OT 2.x you are using right now. But it's hard to know exactly when the problem was fixed and what the problem implied (maybe the problem was fixed in a Java library so it's not an XSLT fix, the entire Java library from the DITA OT 2.x distribution would need to be updated with a fix).
So sorry but I don't think we can provide a backward fix for this. As a workaround you could try to avoid using that construct which seems to cause the problem in the glossdef (maybe use conref instead of conkeyref if it works better).
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
-
- Posts: 19
- Joined: Fri Feb 10, 2017 6:10 pm
Re: <abbreviated-form> not shown in pdf
Post by grethelgomez »
Hi Radu,
Thank you for your quick reply. I will check if using conref is an option in our case.
We will have to move to Oxygen 21.1 as soon as possible anyways.
Thanks again!
Grethel.
Thank you for your quick reply. I will check if using conref is an option in our case.
We will have to move to Oxygen 21.1 as soon as possible anyways.
Thanks again!
Grethel.
Return to “DITA (Editing and Publishing DITA Content)”
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service