Date   

Looking for a PDF design challenge #content-delivery

Corinna Kinchin
 

Good day all,

My colleague Joanne and I will be showcasing MiramoPDF 2.0 at a #ConVExLive test kitchen on Tuesday 27th, and I'm planning to work through developing a real-world PDF design example from scratch. Do you have any beautiful PDF designs which could be used as a basis for this? Or are there particular design features you struggle to achieve using other PDF renderers? If so please email a sample PDF to me: ckinchin@.... If you are also able to share the DITA content used to produce the PDF,  that would be great, but is not vital.

Looking forward to seeing some of you at #ConVExLive!

All the best,
... Corinna


Re: <term> element with @keyref attribute inserted within topic title, not visible in <toc> #XSLT

Nicholas Mucks
 

Hi Sharaubh,
Have you reviewed the topic title with a missing keyref in the stage1.xml file in the temp directory? It’s likely due to an empty value there. When we encounter that we’ll use the document() function on the @href to the topic and then apply-templates on the title element. We’ve also noticed that sometimes glossary references that start with that dita-ot processing instruction from preprocessing in the body of the element will do bad things, so you might want to review that as well.

Take care,
- Nick

Sent from mobile

On Apr 16, 2021, at 1:00 AM, Shaurabh via groups.io <shaurabh.prakash-ext@...> wrote:

Thanks Julio. Tried this approach, but didn't workout. Please suggest any other solution to try if possible.


Thanks,
Shaurabh


[ann][webinar] Creating Frameworks Using an Extension Script (April 21) #Oxygen

alin_belu@...
 

Hello,
 
The last live event of April is getting closer and closer, and we want you there! Join us next Wednesday (April 21) for the “Creating Frameworks Using an Extension Script” webinar. 
 
During this event, Alex Jitianu (DITA evangelist and development lead at Syncro Soft) will take an extensive look at a specific method where a framework can be created using a special XML descriptor file, either from scratch or by extending an existing built-in framework (such as DITA or DocBook) and then making modifications to it. To make this possible, Alex will be covering topics, such as: 
* The framework structure as a package that contains resources and configuration information to provide ready-to-use support for an XML vocabulary or document type. 
* What benefits this new approach brings when compared with creating a framework in GUI. 
* Exploring various use cases and implement them through the script. 
* How to extend existing built-in or custom frameworks. 
* What deployment options are available. 
 
This is a free event and you can register at http://www.oxygenxml.com/evs2021-9.html 
 
Make sure to check the full list of our upcoming events: https://www.oxygenxml.com/events_programme.html 
 
Best regards,
Alin

--
Alin Belu
Oxygen XML Editor


Re: Pdf2 plugin not working with DITA-OT 3.5.4 #DITA-OT

Melissa Kershes
 

Hi there.

 

There’s a pretty comprehensive list of migration issues listed in the DITA OT documentation.

https://www.dita-ot.org/dev/topics/migrating-to-3.5.html

 

Generally I start at the version I’m upgrading from and review all the changes in each major release until I get to my newer version. Most of the issues you may find will be solved by reviewing this content.

 

Good luck with your upgrade!

Melissa

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Shaurabh via groups.io
Sent: Friday, April 16, 2021 3:48 AM
To: main@dita-users.groups.io
Subject: [dita-users] Pdf2 plugin not working with DITA-OT 3.5.4 #DITA-OT

 

We have upgraded our application from DITA-OT 3.1.3 to 3.5.4. After upgrade, Pdf2 plugin has stopped working. Please suggest if any configuration changes is required in respective build.xml file or if any other change is required.


Re: <term> element with @keyref attribute inserted within topic title, not visible in <toc> #XSLT

Shaurabh
 

Thanks Julio. Tried this approach, but didn't workout. Please suggest any other solution to try if possible.


Thanks,
Shaurabh


Pdf2 plugin not working with DITA-OT 3.5.4 #DITA-OT

Shaurabh
 

We have upgraded our application from DITA-OT 3.1.3 to 3.5.4. After upgrade, Pdf2 plugin has stopped working. Please suggest if any configuration changes is required in respective build.xml file or if any other change is required.


Re: markdown failure with OT 3.6 #DITA-OT #markdown

Aliza Merzel
 

Hi, Ben,

 

I had the same issue

It is a known issue

 

It happens when you call the dita-ot using the ant command

When using the dita command, it should be fine

 

https://github.com/jelovirt/dita-ot-markdown/issues/59

 

Aliza

 

 

Aliza Merzel

Senior Developer and XML Specialist

Phone: +972 8-976-0323

Email: alizam@...

 

Connect with us:  twitter.png   linked-in.png  youtube.png

 

Logo-for-email-signatures - smaller

 

From: main@dita-users.groups.io [mailto:main@dita-users.groups.io] On Behalf Of Ben Colborn via groups.io
Sent: Wednesday, April 14, 2021 9:45 PM
To: main@dita-users.groups.io
Subject: [dita-users] markdown failure with OT 3.6 #DITA-OT #markdown

 

Hi dita-users. After quite some time away (since before the move to groups.io in fact), I'm dipping my toes into the lightweight DITA world and running into some issues. Right now I'm using the remotelighting.ditamap sample with just the markdown topics. Using Oxygen 23.0 (which I believe has OT 3.6) it transforms to HTML5 or PDF without any issues.

Not so with the dita command in a fresh install of OT 3.6 or 3.6.1, which I can see includes the org.lwdita plugin. The files fail to parse.

gen-list:                                                                                   
 [gen-list] Using Xerces grammar pool for DTD and schema caching.                           
 [gen-list] Processing file:/C:/Users/ben/Documents/tech-content/tech-content-tools/sample/r
emotelighting-md.ditamap                                                                    
 [gen-list] Processing file:/C:/Users/ben/Documents/tech-content/tech-content-tools/sample/m
dita/led-specs.md                                                                           
 [gen-list] [DOTJ013E][ERROR] Failed to parse the referenced file 'file:/C:/Users/ben/Docume
nts/tech-content/tech-content-tools/sample/mdita/led-specs.md'.: com.elovirta.dita.markdown.
MDitaReader                                                                                 
 [gen-list] Processing file:/C:/Users/ben/Documents/tech-content/tech-content-tools/sample/m
dita/product-specs.md                                                                       
 [gen-list] [DOTJ013E][ERROR] Failed to parse the referenced file 'file:/C:/Users/ben/Docume
nts/tech-content/tech-content-tools/sample/mdita/product-specs.md'.: com.elovirta.dita.markd
own.MDitaReader                                                                             


Output of docsrc/userguide.ditamap to html5 using the dita command works fine. Am I missing something that's needed to process the markdown topics? Thank you for any insight.

Ben


markdown failure with OT 3.6 #DITA-OT #markdown

Ben Colborn
 

Hi dita-users. After quite some time away (since before the move to groups.io in fact), I'm dipping my toes into the lightweight DITA world and running into some issues. Right now I'm using the remotelighting.ditamap sample with just the markdown topics. Using Oxygen 23.0 (which I believe has OT 3.6) it transforms to HTML5 or PDF without any issues.

Not so with the dita command in a fresh install of OT 3.6 or 3.6.1, which I can see includes the org.lwdita plugin. The files fail to parse.
gen-list:                                                                                   
 [gen-list] Using Xerces grammar pool for DTD and schema caching.                           
 [gen-list] Processing file:/C:/Users/ben/Documents/tech-content/tech-content-tools/sample/r
emotelighting-md.ditamap                                                                    
 [gen-list] Processing file:/C:/Users/ben/Documents/tech-content/tech-content-tools/sample/m
dita/led-specs.md                                                                           
 [gen-list] [DOTJ013E][ERROR] Failed to parse the referenced file 'file:/C:/Users/ben/Docume
nts/tech-content/tech-content-tools/sample/mdita/led-specs.md'.: com.elovirta.dita.markdown.
MDitaReader                                                                                 
 [gen-list] Processing file:/C:/Users/ben/Documents/tech-content/tech-content-tools/sample/m
dita/product-specs.md                                                                       
 [gen-list] [DOTJ013E][ERROR] Failed to parse the referenced file 'file:/C:/Users/ben/Docume
nts/tech-content/tech-content-tools/sample/mdita/product-specs.md'.: com.elovirta.dita.markd
own.MDitaReader                                                                             

Output of docsrc/userguide.ditamap to html5 using the dita command works fine. Am I missing something that's needed to process the markdown topics? Thank you for any insight.

Ben


Re: Update DITA For Print for OT 3.x? What say ye?

Ozana Dragomir
 

Yes, please!

Best regards,
Ozana


Re: Update DITA For Print for OT 3.x? What say ye?

stinakab
 

Yes! An update would be very much appreciated.
Best,
Christina


Re: Update DITA For Print for OT 3.x? What say ye?

Larry Kunz
 

Add me to the "yes, please" list, Leigh. DITA for Print is my Bible for PDF transforms. 

Larry Kunz


Re: Presenting In-browser transforms and microcontent at ConVEx

Larry Kunz
 

Thanks for posting this, Chris. I just watched your ConVEx presentation and took a lot of good ideas from it. I appreciate your transparency -- both in sharing the details of your implementation, and in describing the pros and cons. Great job!

Larry Kunz 


Re: Update DITA For Print for OT 3.x? What say ye?

Danielle Wong
 

Yes, please. It would definitely be helpful!

Danielle


On Tue, Apr 13, 2021 at 11:07 AM, Leigh White
<lwwhite5@...> wrote:
Hi all,

Taking an informal poll here. Better late than never (I guess) but I'm considering updating DITA For Print for OT 3.x, as there have been some substantial changes, especially to the build process. It's a considerable effort, though, so I'd like to see if there is actually any demand. Chime in and let me know if you'd find it useful...or not.

Thanks!
Leigh


Re: Update DITA For Print for OT 3.x? What say ye?

Nicholas Mucks
 

Hi Leigh,
It’s a useful book. I wish it extended into other plugins a bit more. Our biggest challenge in the upgrade to 3.X for PDF was with preprocess2, but we liked the benefits of map-first preprocessing. We also decided to transform all root ditamaps to bookmaps before preprocessing to streamline some of the downstream templates. We of course had changes to styles with things like @scalefit and @orient as well. For some reason we had a horrible time wrestling with table formatting this time around but FOP has welcome improvements.

Take care,
- Nick

Sent from mobile

On Apr 13, 2021, at 8:07 AM, Leigh White <lwwhite5@...> wrote:

Hi all,

Taking an informal poll here. Better late than never (I guess) but I'm considering updating DITA For Print for OT 3.x, as there have been some substantial changes, especially to the build process. It's a considerable effort, though, so I'd like to see if there is actually any demand. Chime in and let me know if you'd find it useful...or not.

Thanks!
Leigh


Re: Is there a limit to the number of heading levels for a PDF? #PDF

Aliza Merzel
 

The topic title styles are not applied directly with xsl:use-attribute-sets

They are applied with a xsl:call-template name=”new-attr-set-reflection

 

So you need to add your style to:

plugins\org.dita.pdf2\xsl\common\attr-set-reflection.xsl

 

Aliza Merzel

Senior Developer and XML Specialist

Phone: +972 8-976-0323

Email: alizam@...

 

Connect with us:  twitter.png   linked-in.png  youtube.png

 

Logo-for-email-signatures - smaller

 

From: main@dita-users.groups.io [mailto:main@dita-users.groups.io] On Behalf Of Zoë Lawson via groups.io
Sent: Wednesday, April 14, 2021 5:10 AM
To: main@dita-users.groups.io
Subject: Re: [dita-users] Is there a limit to the number of heading levels for a PDF? #PDF

 

I’m replying from my phone, so can’t dig in, so did you make the similar change in the xsl file that calls the attribute set you defined?

 

Each style generally has two parts:

  •  a template in the not *-attr.xsl file that sets up the fo:blocks that call attribute sets
  • An attribute set in the *_attr.xsl file that defines the styles. 

Apologies I can’t remember the folder names. I’m going from memory. 

 

HTH,

 

Zoë Lawson


From: main@dita-users.groups.io <main@dita-users.groups.io> on behalf of clum@... <clum@...>
Sent: Tuesday, April 13, 2021 5:11:29 PM
To: main@dita-users.groups.io <main@dita-users.groups.io>
Subject: [dita-users] Is there a limit to the number of heading levels for a PDF? #PDF

 

We have merged several user manuals into a large DITA project that is used to output both WebHelp and PDF. For the PDF, we are using XSL-FO. 

Because there is so much material, the hierarchy runs quite deep--7 levels. We have customized our commons-attr.xsl to define the heading styles for six levels. Since the 7th level is not define, it comes out as plain body text in the PDF, which makes it all but invisible. So I went into commons-attr.xsl to define the style for a 7th level. It looks like this:


    <xsl:attribute-set name="topic.topic.topic.topic.topic.topic.topic.title"

        use-attribute-sets="base-font common.title">

        <xsl:attribute name="space-before">0.25in</xsl:attribute>

        <xsl:attribute name="space-after">0.1in</xsl:attribute>

        <xsl:attribute name="font-size">12pt</xsl:attribute>

        <xsl:attribute name="line-height">18pt</xsl:attribute>

        <xsl:attribute name="font-family">OpenSansSemibold</xsl:attribute>

        <xsl:attribute name="start-indent">0pt</xsl:attribute>

        <xsl:attribute name="keep-with-next.within-column">always</xsl:attribute>

    </xsl:attribute-set>


However when I compile the PDF, the formatting shown here is not applied to my 7th level--it still comes out in plain text. All the formatting for the first six levels are correct.

Is there a limit to the number of heading levels that I can define for a PDF? 


Re: Is there a limit to the number of heading levels for a PDF? #PDF

Zoë Lawson
 

I’m replying from my phone, so can’t dig in, so did you make the similar change in the xsl file that calls the attribute set you defined?

Each style generally has two parts:
  •  a template in the not *-attr.xsl file that sets up the fo:blocks that call attribute sets
  • An attribute set in the *_attr.xsl file that defines the styles. 
Apologies I can’t remember the folder names. I’m going from memory. 

HTH,

Zoë Lawson


From: main@dita-users.groups.io <main@dita-users.groups.io> on behalf of clum@... <clum@...>
Sent: Tuesday, April 13, 2021 5:11:29 PM
To: main@dita-users.groups.io <main@dita-users.groups.io>
Subject: [dita-users] Is there a limit to the number of heading levels for a PDF? #PDF
 
We have merged several user manuals into a large DITA project that is used to output both WebHelp and PDF. For the PDF, we are using XSL-FO. 

Because there is so much material, the hierarchy runs quite deep--7 levels. We have customized our commons-attr.xsl to define the heading styles for six levels. Since the 7th level is not define, it comes out as plain body text in the PDF, which makes it all but invisible. So I went into commons-attr.xsl to define the style for a 7th level. It looks like this:

    <xsl:attribute-set name="topic.topic.topic.topic.topic.topic.topic.title"
        use-attribute-sets="base-font common.title">
        <xsl:attribute name="space-before">0.25in</xsl:attribute>
        <xsl:attribute name="space-after">0.1in</xsl:attribute>
        <xsl:attribute name="font-size">12pt</xsl:attribute>
        <xsl:attribute name="line-height">18pt</xsl:attribute>
        <xsl:attribute name="font-family">OpenSansSemibold</xsl:attribute>
        <xsl:attribute name="start-indent">0pt</xsl:attribute>
        <xsl:attribute name="keep-with-next.within-column">always</xsl:attribute>
    </xsl:attribute-set>

However when I compile the PDF, the formatting shown here is not applied to my 7th level--it still comes out in plain text. All the formatting for the first six levels are correct.

Is there a limit to the number of heading levels that I can define for a PDF? 


Re: Update DITA For Print for OT 3.x? What say ye?

Zoë Lawson
 

Yes please!

I definitely considered your book as the one true source as I was trying to figure out how to design a PDF with the DITA-OT. I got tripped up a few times due to differences, and would love a revision for the next time I dig in. 

Zoë Lawson


From: main@dita-users.groups.io <main@dita-users.groups.io> on behalf of Owen <ewan1000@...>
Sent: Tuesday, April 13, 2021 3:40:03 PM
To: main@dita-users.groups.io Group Moderators <main@dita-users.groups.io>
Subject: Re: [dita-users] Update DITA For Print for OT 3.x? What say ye?
 
It would certainly be useful, Leigh.

Kind regards,
Owen Rowe


On Tue, Apr 13, 2021 at 5:07 PM Leigh White <lwwhite5@...> wrote:
Hi all,

Taking an informal poll here. Better late than never (I guess) but I'm considering updating DITA For Print for OT 3.x, as there have been some substantial changes, especially to the build process. It's a considerable effort, though, so I'd like to see if there is actually any demand. Chime in and let me know if you'd find it useful...or not.

Thanks!
Leigh


Is there a limit to the number of heading levels for a PDF? #PDF

clum@...
 

We have merged several user manuals into a large DITA project that is used to output both WebHelp and PDF. For the PDF, we are using XSL-FO. 

Because there is so much material, the hierarchy runs quite deep--7 levels. We have customized our commons-attr.xsl to define the heading styles for six levels. Since the 7th level is not define, it comes out as plain body text in the PDF, which makes it all but invisible. So I went into commons-attr.xsl to define the style for a 7th level. It looks like this:

    <xsl:attribute-set name="topic.topic.topic.topic.topic.topic.topic.title"
        use-attribute-sets="base-font common.title">
        <xsl:attribute name="space-before">0.25in</xsl:attribute>
        <xsl:attribute name="space-after">0.1in</xsl:attribute>
        <xsl:attribute name="font-size">12pt</xsl:attribute>
        <xsl:attribute name="line-height">18pt</xsl:attribute>
        <xsl:attribute name="font-family">OpenSansSemibold</xsl:attribute>
        <xsl:attribute name="start-indent">0pt</xsl:attribute>
        <xsl:attribute name="keep-with-next.within-column">always</xsl:attribute>
    </xsl:attribute-set>

However when I compile the PDF, the formatting shown here is not applied to my 7th level--it still comes out in plain text. All the formatting for the first six levels are correct.

Is there a limit to the number of heading levels that I can define for a PDF? 


Re: Update DITA For Print for OT 3.x? What say ye?

Owen
 

It would certainly be useful, Leigh.

Kind regards,
Owen Rowe


On Tue, Apr 13, 2021 at 5:07 PM Leigh White <lwwhite5@...> wrote:
Hi all,

Taking an informal poll here. Better late than never (I guess) but I'm considering updating DITA For Print for OT 3.x, as there have been some substantial changes, especially to the build process. It's a considerable effort, though, so I'd like to see if there is actually any demand. Chime in and let me know if you'd find it useful...or not.

Thanks!
Leigh


Re: Update DITA For Print for OT 3.x? What say ye?

mganir@...
 

That would be very helpful!

141 - 160 of 46295