Date   

Re: Keyref/conkey ref conversion strategy - keyref all the things? #conref

Marsh, Ed
 

Thanks, Eliot. 

We're moving to a static site generator (Hugo) where the folder/file structure determines the structure of the site. Because all of our links are currently xrefs, I thought this would be a good time to visit keyrefs, since the link paths will be different in this new configuration. It's going to be messy, but I'm guessing this is probably the way to move forward.

Appreciate input!
Ed.


Re: Repeating table titles for tables that break on PDF output - Oxygen DITA #tables #CSS #PDF

Radu Coravu
 

Hi Matt,

As Chris said, we do have plans to improve on this aspect in the Oxygen Chemistry PDF processor, probably add some extra CSS extensions to control this repetition of the table title on subsequent pages. I added your contact details on the internal issue.

Regards,
Radu

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

On 1/30/2020 7:19 PM, Matt Lorenzi via Groups.Io wrote:
I am using using OxygenXML Author to publish a ditamap to PDF. I am generally happy with the PDF output. Most of the styling is done in CSS and I have not had to tweak any other files - yet.
In our old authoring tool (Structured FrameMaker), we had the *table title* repeat on each page if the table spanned more than one page. It would then also insert a snippet stating *(Sheet 1 of 2)*, then *(Sheet 2 of 2)* on the next page, etc.
The table headers already repeat themselves, so that is take care of - but how do I get the table title to repeat?
Here is what I am trying to achieve:
then this:
Any help would be appreciated!


Re: Glossary in a table #glossary #PDF #Oxygen

Radu Coravu
 

Hi Matt,

Oxygen XML Editor subscription users as far as I know always benefit of the newest releases:

https://www.oxygenxml.com/buy_subscription_e6_editor.html

Support and Maintenance Pack is included, this means priority technical support and free upgrades to all major and minor released versions during the subscription period.
Regards,
Radu

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

On 1/30/2020 7:38 PM, Matt Lorenzi via Groups.Io wrote:
That's cool! I imagine I will be able to upgrade to version 22 as a subscription user? Excited to try this function!


Re: Repeating table titles for tables that break on PDF output - Oxygen DITA #tables #CSS #PDF

Kristen James Eberlein
 

The one resource that I am aware of is Antenna House’s “Introduction to CSS for Paged Media.”

Kris


Re: Repeating table titles for tables that break on PDF output - Oxygen DITA #tables #CSS #PDF

Lief Erickson
 

There's no doubt that Leigh's book is the go-to resource for PDF output, if you're using XSL-FO. There isn't such a resource yet for CSS to PDF.


On Thu, Jan 30, 2020 at 6:08 PM Joe Williams <jdwinfodesign@...> wrote:
Eliot's right. There is a fix that involves putting the table title in a header row. Leigh White's book, DITA for Print is the go-to for PDF output from DITA.


unknown fo:block in a shortdesc in a link #PDF #shortdesc

Zoë Lawson
 

I am working on an fop PDF from DITA-OT 3.3.1.
I am including child links in the content, and have the shortdesc displaying.

There's some additional block inside of the link__shortdesc block that is mucking with my formatting, and I can't figure out what it is.

Anyone have a guess?

Thanks,
Zoë


Re: Repeating table titles for tables that break on PDF output - Oxygen DITA #tables #CSS #PDF

Joe Williams
 

Eliot's right. There is a fix that involves putting the table title in a header row. Leigh White's book, DITA for Print is the go-to for PDF output from DITA.


Re: Repeating table titles for tables that break on PDF output - Oxygen DITA #tables #CSS #PDF

Chris Papademetrious
 

Hi Matt,

We are moving from FrameMaker to DITA and we want this too. There's a message thread about this on the Oxygen forum; maybe you can add your vote there?


 - Chris


Re: Repeating table titles for tables that break on PDF output - Oxygen DITA #tables #CSS #PDF

Matt Lorenzi <mjlorenzi@...>
 

I suppose I can somewhat live with not having the table title repeat on the next page, but the problem might arise if the page were to become separated. There would be no way to identify the context of the table.


Re: Repeating table titles for tables that break on PDF output - Oxygen DITA #tables #CSS #PDF

ekimber@contrext.com
 

You probably have to make the table title be a row in the table header. The only other solution I can think of is to put the table title into page's running head but that's probably not what you want or what FrameMaker did.

Note that there a couple of CSS pagination limitations here relative to XSL-FO that would require proprietary extensions to accommodate:

1. CSS pagination lacks FO's table marker mechanism. This means there are certain use cases where the repeated header needs to reflect page-specific information and there's no good way to do that in standard CSS. An example is a multi-page table where the header reflects per-page subtotals of columns of figures. The PDF2 transform uses table markers to do the running heads that are in the back-of-the-book index, where each column of the index reflects the first index entry on the page.
2. The CSS page edge region model makes it hard to have running heads and feet where the text spans the page, so it might be difficult or impossible to put what would be a line or lines of text that go across the entire page body in the running head and have it formatted correctly.

Cheers,

E.

--
Eliot Kimber
http://contrext.com


On 1/30/20, 11:19 AM, "Matt Lorenzi via Groups.Io" <dita-users@groups.io on behalf of mjlorenzi=yahoo.com@groups.io> wrote:

I am using using OxygenXML Author to publish a ditamap to PDF. I am generally happy with the PDF output. Most of the styling is done in CSS and I have not had to tweak any other files - yet.

In our old authoring tool (Structured FrameMaker), we had the table title repeat on each page if the table spanned more than one page. It would then also insert a snippet stating (Sheet 1 of 2), then (Sheet 2 of 2) on the next page, etc.

The table headers already repeat themselves, so that is take care of - but how do I get the table title to repeat?

Here is what I am trying to achieve:




then this:



Any help would be appreciated!


Re: Glossary in a table #glossary #PDF #Oxygen

Matt Lorenzi <mjlorenzi@...>
 

That's cool! I imagine I will be able to upgrade to version 22 as a subscription user? Excited to try this function!


Repeating table titles for tables that break on PDF output - Oxygen DITA #tables #CSS #PDF

Matt Lorenzi <mjlorenzi@...>
 

I am using using OxygenXML Author to publish a ditamap to PDF. I am generally happy with the PDF output. Most of the styling is done in CSS and I have not had to tweak any other files - yet.

In our old authoring tool (Structured FrameMaker), we had the table title repeat on each page if the table spanned more than one page. It would then also insert a snippet stating (Sheet 1 of 2), then (Sheet 2 of 2) on the next page, etc.

The table headers already repeat themselves, so that is take care of - but how do I get the table title to repeat?

Here is what I am trying to achieve:



then this:



Any help would be appreciated!


Re: Are you using the DITA 1.3 troubleshooting topic? #troubleshooting

David Yin
 

We are using the Troubleshooting topic.  I believe I spoke to Bob back in 2017 about wanting to start using it.

 

I like the new topic type since it clearly identifies itself as separate from a procedure or a task.

 

The challenges we have are not directly related to the troubleshooting topic.  The issues are split between a pdf output style and DITA reuse strategy.

 

To your questions:

  • Diagnostic elements would be a good use; but you would need to define this structure really well or it will be useless.
  • Draft comments, I am surprised that it is restricted today.  I suppose we use <comments> instead.

 

 

David Yin

Technical Publication Manager  |  david.yin@...  |  940.591.4196

 


Re: Icon padding AH vs FOP #PDF

Toshihiko Makita
 

Hi Nicholas,

The xsl-fo syntax in the topic.fo is the same for both and we cannot find where Antenna House (or maybe FOP is ignoring) the additional padding.

Could your send me your XSL-FO file fragments or minimum example directly to me?
I will fined the time and investigate it.

Regards,

-- 
/*--------------------------------------------------
 Toshihiko Makita
 Development Group. Antenna House, Inc. Ina Branch
 E-Mail tmakita@...
 Web site:
 http://www.antenna.co.jp/
 http://www.antennahouse.com/
 --------------------------------------------------*/
 


Re: Apply to join the DITA users group #admin

Julio J Vazquez
 

Hi Bella, 

The Yahoo group is closed. This is the correct channel to get your questions answered. 

Julio J. Vazquez


Re: Glossary in a table #glossary #PDF #Oxygen

Radu Coravu
 

Hi Matt,

Right, in Oxygen 22 which we plan to release in about a week or two you will be able to mark those two elements as table cells and their parent as a table row and the PDF output will present them side by side.
But in the meantime you can try using inline-block display and see how far that takes you.

Regards,
Radu

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

On 1/29/2020 8:21 PM, Matt Lorenzi via Groups.Io wrote:
Hi Radu,
Thanks for the suggestion! Sadly the CSS you suggested did not work with the Oxygen Chemistry that is bundled with Oxygen 21.1 - returns a FATAL error. I will try some variations of display:inline-block for now.
Cheers,
Matt


Icon padding AH vs FOP #PDF

Nicholas Mucks
 

Hi!

Our topic.fo file for a custom pdf2 output renders fine in FOP for note label images in bullets. However, for some reason Antenna House adds something like 6pts of padding above the note label images.

The xsl-fo syntax in the topic.fo is the same for both and we cannot find where Antenna House (or maybe FOP is ignoring) the additional padding.

Any suggestions??

Take care,
- Nick

Sent from mobile


Re: Are you using the DITA 1.3 troubleshooting topic? #troubleshooting

Larry Kollar
 

We use it. We have several templates for it, depending on the complexity of the troubleshooting topic. Mine generally use one cause/remedy pair, but there are a few that use multiple troubleSolution.

We also support an @outputclass called "message" that makes minor tweaks to the output to support documenting syslog messages and the like. My thought was, the message itself is the condition, which has a cause and (maybe) an associated action. It works pretty well for that.


Re: Glossary in a table #glossary #PDF #Oxygen

Matt Lorenzi <mjlorenzi@...>
 

Hi Radu,

Thanks for the suggestion! Sadly the CSS you suggested did not work with the Oxygen Chemistry that is bundled with Oxygen 21.1 - returns a FATAL error. I will try some variations of display:inline-block for now.

Cheers,
Matt


Re: Keyref/conkey ref conversion strategy - keyref all the things? #conref

ekimber@contrext.com
 

Feel free to ask questions here.

An older paper I presented on key best practices suggests that you should always have resource-only topicrefs for your topics and then use those from the navigation topicrefs.

I've since refined that approach such that it's only really necessary when you have either a high degree of re-use of your topics or, for whatever reason, it's better for you to implement this pattern everywhere.

Otherwise, if you have relatively little reuse of topics within or across maps, the extra overhead of resource-only topicrefs just to then use navigation (normal-role) topicrefs to put those topics into the navigation tree is not justified. Just be sure that all your navigation topicrefs also have appropriate keys.

For topics that serve as resources for content reference, you should always use resource-only keys.

Cheers,

E.

--
Eliot Kimber
http://contrext.com


On 1/29/20, 8:55 AM, "Marsh, Ed" <dita-users@groups.io on behalf of Ed.Marsh@gs.com> wrote:

Hi Eliot,
I was studying your first link yesterday :) Will check out the remainder tonight.
Ed.

1081 - 1100 of 46224