Search found 22 matches
Search found 22 matches
• Page 1 of 1
- by Marvin
- Thu Jan 17, 2019 11:44 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Elements are only converted in FO/PDF output, not HTML
- Replies: 22
- Views: 6336
Re: Elements are only converted in FO/PDF output, not HTML
Thank you, Radu. Like I said, I went without the template at first and simply renamed our <definitionlist> elements to match the DITA standard - but then some elements simply would not be rendered. I have now created a custom template and it looks like all elements are rendered. Not quite the way we...
- by Marvin
- Wed Jan 16, 2019 4:35 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Elements are only converted in FO/PDF output, not HTML
- Replies: 22
- Views: 6336
Re: Elements are only converted in FO/PDF output, not HTML
Unfortunately I didn't make it to the conference, but now the issue from the beginning is back: In a preprocessing step, all our <definitionlist> elements are renamed to <dl>, including the child elements (dlentry/dt/dd). This works fine, the HTML5 plugin usually renders some output. However, some o...
- by Marvin
- Thu Oct 25, 2018 5:27 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Elements are only converted in FO/PDF output, not HTML
- Replies: 22
- Views: 6336
Re: Elements are only converted in FO/PDF output, not HTML
Hi Radu, Yes, I did find that article, but it doesn't mention that you can use this to add element templates. It also doesn't mention where "gen-user-header" comes from (I assume that is a pre-defined extension point, but I didn't find it in any of those lists). In fact, I didn't find a si...
- by Marvin
- Thu Oct 25, 2018 2:49 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Elements are only converted in FO/PDF output, not HTML
- Replies: 22
- Views: 6336
Re: Elements are only converted in FO/PDF output, not HTML
Thank you much! That is exactly what we needed.
It would be so great if more documentation on stuff like this was available somewhere...
It would be so great if more documentation on stuff like this was available somewhere...
- by Marvin
- Mon Oct 22, 2018 2:20 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Elements are only converted in FO/PDF output, not HTML
- Replies: 22
- Views: 6336
Re: Elements are only converted in FO/PDF output, not HTML
I am having the same issue with some more elements: <!ATTLIST emailaddress %global-atts; class CDATA "+ topic/data xnal-d/emailaddress "> <!ATTLIST url %global-atts; class CDATA "+ topic/data xnal-d/url "> <!ATTLIST section %global-atts; class CDATA "- topic/section " >...
- by Marvin
- Mon Oct 15, 2018 1:42 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Named destination to an object in the PDF output
- Replies: 24
- Views: 7297
Re: Named destination to an object in the PDF output
After looking at the PDFs using the Aspose PDF library, I don't think they contain information about the original ID's, unless named destinations are specified in the .fo file. Internal links within the same PDF document namely do not seem to point to any sort of ID, but instead they simply say &quo...
- by Marvin
- Thu Oct 11, 2018 12:07 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Named destination to an object in the PDF output
- Replies: 24
- Views: 7297
Re: Named destination to an object in the PDF output
Hi Radu,
I am a software developer myself, so implementing this wouldn't be a problem.
The challenge here is identifying the links and their destinations. Do you happen to know where I could find the ID's in the PDF's using one of the many PDF libraries?
Thanks,
Marvin
I am a software developer myself, so implementing this wouldn't be a problem.
The challenge here is identifying the links and their destinations. Do you happen to know where I could find the ID's in the PDF's using one of the many PDF libraries?
Thanks,
Marvin
- by Marvin
- Thu Oct 11, 2018 11:18 am
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Named destination to an object in the PDF output
- Replies: 24
- Views: 7297
Re: Named destination to an object in the PDF output
That would be fine. Our issue is this: In the PDF we currently only have internal links, but no links to other documents. There are <xref> tags in the source, but links to other documents are disabled by prepending a '#' to the destination. I would like to add named destinations as well as links bet...
- by Marvin
- Wed Oct 10, 2018 8:00 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Elements are only converted in FO/PDF output, not HTML
- Replies: 22
- Views: 6336
Re: Elements are only converted in FO/PDF output, not HTML
Yes, I noticed that, too. But I suspect it might have been done like this on purpose.
After all, it's working well in the PDF generator, so I think there must have been a reason for doing it like this.
After all, it's working well in the PDF generator, so I think there must have been a reason for doing it like this.
- by Marvin
- Wed Oct 10, 2018 3:28 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Named destination to an object in the PDF output
- Replies: 24
- Views: 7297
Re: Named destination to an object in the PDF output
By the way, is there a way to identify objects from the FO file in the (default) PDF export, based on their ID or so?
Or is all that information removed if you don't explicitly insert it using named destinations or such?
Or is all that information removed if you don't explicitly insert it using named destinations or such?
- by Marvin
- Tue Oct 09, 2018 5:38 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Elements are only converted in FO/PDF output, not HTML
- Replies: 22
- Views: 6336
Re: Elements are only converted in FO/PDF output, not HTML
Thank you, that helped. You meant topic/dl, not topic/dlentry, right? I think I now found the relevant code in the PDF generator: <!--Definition list--> <xsl:template match="*[contains(@class, ' topic/dl ')]"> <fo:table xsl:use-attribute-sets="dl"> <xsl:call-template name="c...
- by Marvin
- Tue Oct 09, 2018 12:54 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Elements are only converted in FO/PDF output, not HTML
- Replies: 22
- Views: 6336
Re: Elements are only converted in FO/PDF output, not HTML
Thank you, that makes a little more sense to me now. What would be the best way to verify that the DTD is in fact loaded correctly, with all its class mappings? The class mappings are actually defined in a separate .mod file which is loaded like this: <!ENTITY % ourcompany-section-typemod PUBLIC &qu...
- by Marvin
- Tue Oct 09, 2018 12:38 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Named destination to an object in the PDF output
- Replies: 24
- Views: 7297
Re: Named destination to an object in the PDF output
Thank you! Unfortunately our ID's are just GUID's, so the oid's wouldn't help. But then I'll just use an <fo:wrapper>. Thanks!
- by Marvin
- Tue Oct 09, 2018 11:07 am
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Named destination to an object in the PDF output
- Replies: 24
- Views: 7297
Re: Named destination to an object in the PDF output
Ah, ok. Thank you for checking! What would you recommend for getting "pretty" named destinations? Apparently it's not possible to create a named destination that points to a different ID. Would you just outright change the ID of the original block elements then or instead add a new element...
- by Marvin
- Tue Oct 09, 2018 11:04 am
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Elements are only converted in FO/PDF output, not HTML
- Replies: 22
- Views: 6336
Re: Elements are only converted in FO/PDF output, not HTML
Thank you. So alternatively, I could just add that class to the <definitionlist> element? I think I tried that and it didn't work, but maybe I didn't have enough whitespace around the class. Why are all classes specified with so much whitespace around (" topic/dl ") and what does the leadi...
- by Marvin
- Tue Oct 09, 2018 12:41 am
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Elements are only converted in FO/PDF output, not HTML
- Replies: 22
- Views: 6336
Re: Elements are only converted in FO/PDF output, not HTML
Ok, somehow it did work now by renaming the elements in the source document: <dl id="definitionlist_A4F5FF1D27AF4A3B8E14311EF5F9DD6D"> <dlentry id="listentry_3189354FC62A4D31AFEB885DD57756FE"> <dt id="dterm_F33742B299E942A5BE0F2322077EDC70">f<sub id="sub_5400D2E170...
- by Marvin
- Tue Oct 09, 2018 12:15 am
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Elements are only converted in FO/PDF output, not HTML
- Replies: 22
- Views: 6336
Re: Elements are only converted in FO/PDF output, not HTML
Hi Radu, The problem is the person who originally wrote most of this specialization does not work for the organisation anymore, and the other one who has worked a lot on this is currently on sick leave. But I have been able to find some things related to <definitionlist> elements in the PDF generato...
- by Marvin
- Mon Oct 08, 2018 3:18 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Named destination to an object in the PDF output
- Replies: 24
- Views: 7297
Re: Named destination to an object in the PDF output
Yes, I also want to have custom named destinations ("chapter3" sounds better than a long GUID) and I'm not sure if we can just modify the existing GUID's or if they are used elsewhere. But I was still surprised to learn that apparently all ID's are now automatically converted to named dest...
- by Marvin
- Mon Oct 08, 2018 12:22 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Named destination to an object in the PDF output
- Replies: 24
- Views: 7297
Re: Named destination to an object in the PDF output
Do you know when that became the standard behavior? Granted, we are currently still using DITA-OT 1.8 and Apache-FOP 1.1, but still: Almost all our elements have ID's: <fo:block id="unique_3_Connect_42_p_DF7A55AB5C754EA9B3B7FD11D2839E2A" space-after="3pt" space-before="1pt&q...
- by Marvin
- Mon Oct 08, 2018 11:35 am
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Elements are only converted in FO/PDF output, not HTML
- Replies: 22
- Views: 6336
Re: Elements are only converted in FO/PDF output, not HTML
Thank you so much for the swift reply. That's what I already suspected, how can we catch things like this? There is absolutely nothing in the log file, even with -d and -v specified. With other elements/attributes, there is at least a warning in the log, like this: [gen-list] [DOTJ030I][INFO] No 'cl...
- by Marvin
- Fri Oct 05, 2018 3:47 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Elements are only converted in FO/PDF output, not HTML
- Replies: 22
- Views: 6336
Elements are only converted in FO/PDF output, not HTML
We have DITA files which are converted to PDF via FO as an intermediary format using DITA OT (v. 1.8 - hasn't been updated in a while). As a new feature, we also want to create HTML output, for which we decided the latest version of DITA OT (v. 3.1) and the HTML 5 plugin. Unfortunately, some element...
- by Marvin
- Fri Oct 05, 2018 3:37 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Named destination to an object in the PDF output
- Replies: 24
- Views: 7297
Re: Named destination to an object in the PDF output
When did DITA OT start generating named destinations for IDs? We generate PDF documents using DITA OT, converting first to FO and then on to PDF. But we don't get any named destinations in the PDFs at all, though all elements have IDs, like this: <subsec1 id="subsec1_BE8049C4430E45639C1B7E99657...
Search found 22 matches
• Page 1 of 1
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