Date   

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.


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

Marsh, Ed
 

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


Apply to join the DITA users group #admin

Bella Zhao
 

Hi,

 

I’m a technical writer in China and I’d like to join the DITA user group as it is now closed on yahoo. I’m very interested in DITA and want to learn more from this group. Can you grant me access so I can receive the emails?

 

Best regards,

Bella Zhao

Technical Writer

 

 


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

Radu Coravu
 

Hi Matt,

You could use a custom CSS which would define the glossterm and the glossdef as cells. And the parent element would have display table row. Something like:

*[class~="glossentry/glossterm"],
*[class~="glossentry/glossdef"]{
display:table-cell !important;
}

*[class~="glossentry/glossentry"]{
display:table-row !important;
}

This should work with our latest nightly build of the Oxygen Chemistry publishing engine.
If you are using the PDF Chemistry engine from Oxygen 21.1 and this does not work for you, maybe you can try using some display:inline-block displays on the elements.

Regards,
Radu

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

On 1/28/2020 10:09 PM, Matt Lorenzi via Groups.Io wrote:
I am using Oxygen to create a PDF output from a ditamap.
I would like my *glossentry* and *glossterm* sit next to each other rather than stacked, which is the default <block> behaviour.
I've tried to modify the CSS, playing around with display, position, padding, etc. Nothing works as I would like, so I think the best solution is to create a two-column table.
I am guessing this is something that has to be done with. *XSLT*? I have found snippets of code that should work, but don't know if I have to create a new XSLT file, or if there is one I can ad this to.
I'm in a bit of a crunch, so don't have time to dig too deep right now.


Glossary in a table #glossary #PDF #Oxygen

Matt Lorenzi <mjlorenzi@...>
 

I am using Oxygen to create a PDF output from a ditamap.
I would like my glossentry and glossterm sit next to each other rather than stacked, which is the default <block> behaviour.
I've tried to modify the CSS, playing around with display, position, padding, etc. Nothing works as I would like, so I think the best solution is to create a two-column table.
I am guessing this is something that has to be done with. XSLT? I have found snippets of code that should work, but don't know if I have to create a new XSLT file, or if there is one I can ad this to.
I'm in a bit of a crunch, so don't have time to dig too deep right now.


Re: Is anyone using DITA's SVG domain without using the technical content package (i.e. concept/task/reference/troubleshooting)? #SVG

Kristen James Eberlein
 

Hi, Jonathan.

We talked about your e-mail on today's DITA Technical Committee call. I am going to respond to one part of your question, and another TC member will address another.

So, why is the hazard statement domain included in the base package?

The base package was designed to include the most fundamental pieces of the DITA architecture:

  • Topic
  • Map
  • Subject scheme
  • The most basic domains: DITAVAL, hazard statement, highlighting, and utilities

Identified users for the package included marketing and medical information. We thought that the hazard statement domain would be necessary for medical information or marketing information about drugs or medical devices.

For more information about the three packages of DITA 1.3, see http://docs.oasis-open.org/dita/dita-1.3-why-three-editions/v1.0/dita-1.3-why-three-editions-v1.0.html

Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)

On 1/24/2020 3:00 PM, Jonathan Hanna wrote:
Hi Kris,

As mentioned previously, I am new to DITA, so please forgive the ignorance behind my questions and comments. 

Again, it seems odd that the SVG and MathML domains would not be included as part of the base package. Both SVG and MathML are commonly used with HTML. MS-Word comes with the ability to insert equations and markup images in documents by default and not as an add-on package. I would think that users would expect this to be part of the base DITA package as well. What is the rationale for not including these domains in the base package?

I also find it odd that the hazard statement domain would be included with the base package. The hazard statement domain seems like a natural fit for the technical content package, especially since they are specializations of notes. What is the rationale for including the hazard statement domain in the base package?

I know that these are discussions for technical committee meetings and I am not trying to start a debate. I am just a curious newbie :-).

Thanks,
Jonathan Hanna


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

ekimber@contrext.com
 

If you can manage it, replacing all references from topics to other things (so conrefs, cross references, etc.) to use keys is the best way to go. Within maps it may or may not make sense to use keys, for example, from navigation topicrefs to separate resource-only keys for the topics, depending on your re-use patterns.

I've made a number of presentations over the years about using keys and you can find them all on SlideShare, including:

* https://www.slideshare.net/drmacro/ki-qi-key-the-way-of-dita-harmony-with-keys-and-key-references
* https://www.slideshare.net/drmacro/dita-reuse-challenges-and-response
* https://www.slideshare.net/drmacro/they-worked-before-what-happened-understanding-dita-crossbook-links

Cheers,

E.

--
Eliot Kimber
http://contrext.com


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

Thanks, Chris, this is exactly the discussion I'm looking for (though I wasn't quite looking for it then!).

We're moving from a bespoke DITA-to-Confluence system to a static site generator (Hugo). We have to refactor our links (and our file structure) and I'm hoping to take this opportunity to Keyref All The Things, just wasn't sure if this was the 'right' way to go.

I may be reaching out offline :)

I should also add a huge thanks to Radu who sent over an XSL solution.

Ed.


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

Marsh, Ed
 

Thanks, Chris, this is exactly the discussion I'm looking for (though I wasn't quite looking for it then!).

We're moving from a bespoke DITA-to-Confluence system to a static site generator (Hugo). We have to refactor our links (and our file structure) and I'm hoping to take this opportunity to Keyref All The Things, just wasn't sure if this was the 'right' way to go.

I may be reaching out offline :)

I should also add a huge thanks to Radu who sent over an XSL solution.

Ed.


Are you using the DITA 1.3 troubleshooting topic? #troubleshooting

Kristen James Eberlein
 

I'm curious; how many companies and implementations are using the DITA 1.3 troubleshooting topic?

The troubleshooting topic arrived with DITA 1.3; it was championed by the DITA Technical Communication subcommittee and much of the work was done by Bob Thomas, Tagsmiths.

There is an excellent white paper that Bob authored for the DITA Adoption TC: https://www.oasis-open.org/committees/download.php/53517/DITA13TroubleshootingArticle_FINAL_03jul14.pdf

Anyhow, who is using the troubleshooting topic? Are there things that work for you? Things that don't work for you?

For DITA 2.0 we (the DITA TC) are looking at the following enhancements:

  • A diagnostic element
  • Allowing <draft-comment> as an option child of <remedy>
--
Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)

1141 - 1160 of 46276