Date   
Re: XSL-FO two-page layout

Nicholas Mucks
 

Hi Mica,
That's it: page imposition.
We're using Antenna House.

How might you approach this instead?

On Monday, June 29, 2020, 10:17:10 AM PDT, Mica Semrick <mica@...> wrote:


Hey Nick,

Which PDF formatter are you using?

I think your approach might be off, as this generally isn't page level formatting. The feature is called "page imposition."

-m

On June 29, 2020 9:15:22 AM PDT, "Nicholas Mucks via groups.io" <urbanrobots@...> wrote:
Hello,
We're trying to create a two-page layout where each printed page has two pages on it.  Although creating a two-column layout is simple enough, we're having difficult with the static content since it still shows one footer that spans the bottom of the page across the two columns.

Has anyone created a PDF that displays two pages side by side in landscape orientation?

Thanks for your time.
- Nick

Re: XSL-FO two-page layout

Mica Semrick
 

Hey Nick,

Which PDF formatter are you using?

I think your approach might be off, as this generally isn't page level formatting. The feature is called "page imposition."

-m


On June 29, 2020 9:15:22 AM PDT, "Nicholas Mucks via groups.io" <urbanrobots@...> wrote:
Hello,
We're trying to create a two-page layout where each printed page has two pages on it.  Although creating a two-column layout is simple enough, we're having difficult with the static content since it still shows one footer that spans the bottom of the page across the two columns.

Has anyone created a PDF that displays two pages side by side in landscape orientation?

Thanks for your time.
- Nick

XSL-FO two-page layout

Nicholas Mucks
 

Hello,
We're trying to create a two-page layout where each printed page has two pages on it.  Although creating a two-column layout is simple enough, we're having difficult with the static content since it still shows one footer that spans the bottom of the page across the two columns.

Has anyone created a PDF that displays two pages side by side in landscape orientation?

Thanks for your time.
- Nick

Re: Chapter numbering issue when using <topicgroup>

Toshihiko Makita
 

Hi Chiris,

Sorry for the late reply.

As PDF2 plug-in has extension point named "org.dita.pdf2.xsl.topicmerge", you can override default topicmerge stylesheet processing by making plug-in.

Here is my example.

https://1drv.ms/u/s!AkbL99fLhxKUhp50UTIXM1xI7FSmlg?e=2Jrj9Q

You can integrate this plug-in and change PDF2 topicmerge processing. In my testing, I could succeed to remove topicgroup elements from the map portion of the merged middle file in DITA-OT 2.5.4.

If there are any problems, please let me know.

Regards,

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

Tracking mentions for an index or glossary?

Daud Vyd
 

While typing in a <p> or other tag, is it possible to annotate content so that it can be ad-hoc searched while working in Oxygen and also added to a dynamically generated index or glossary? For example, how would you markup this DITA topic:


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic id="genre">
    <title>Genre</title>
    <body>
        <p>Genre refers to the broad artistic category of a story while setting refers to specific example of a genre. Genre helps to determine the types of people and places a story might include without identifying named instances. Setting provides named instances and richly described details. For example, Fantasy (genre) often includes wizards and castles while Arthurian Legend (setting) describes Merlin and Camelot in particular.
    </body>
</topic>


Merlin is:
  • an instance-of a person
  • a child-of the Authorian Legend setting
Authorian Legend is:
  • an instance-of a setting
  • a parent-of Merlin
Fantasy is:
  • a instance-of a genre
  • a parent-of Authorian Legend

Is it possible to markup the text so that I can later query across all DITA files for the relationships described in bullet points or for a list of mentioned genres and where they are discussed? Could I insert a dynamically generated list of these mentions at the bottom of the Genre DITA page above to display in the final document?

Incidentally, Setting will be a DITA topic like Genre. Should every mention of these words be hyperlinked? In MS Word, I might just capitalize them and display in italics or bold them like I've done here.


Thank you,
d. vyd

[ann][webinar] Tailored Authoring Experience with Oxygen Web Author #Oxygen

alin_belu@...
 

Hello everyone, 
 
“Tailored Authoring Experience with Oxygen Web Author”, the 6th live event from our current weekly series of webinars, will take place on July 1st. 
 
Bogdan Dumitru, Web Author software developer, aims to inspire you with some of the most exciting ways to improve your authoring experience. You will learn about the various ways Web Author can be customized and the new framework customizations. Some of the subjects that will be discussed include:
* Validation for Markdown documents 
* Text-to-markup corrections 
* How to easily navigate through large documents with the Outline view 
* In-place actions 
* Diff as a service 
 
This is a free event and you can register at http://www.oxygenxml.com/evs2020-6.html
 
Check the full list of the upcoming webinars and follow the links to see more details and register for free: 
 
Best regards, 
Alin


--
Alin Belu
Oxygen XML Editor

Re: Help customising PDF plugin for displaying related information #DITA-OT

chichak1995@...
 

Hi Dragomir,

I think that you need to edit rel-links.xsl file. There is a template that matches linklist, maybe it is located there. 

Good luck
oJun,

Help customising PDF plugin for displaying related information #DITA-OT

Ozana Dragomir
 

Hi all,

I need some help customizing the DITA-OT PDF plugin (currently using DITA-OT 3.4.1).

We use reltables with different types of entries for the destination, for example:
  • cross-refences to other topics within the same book
<topicref keyref="key_A"/>

  • reference to topics which may or may not be within the same book:
<topicref keyref="key_B" scope="peer">
  <topicmeta>
    <linktext>For more information, see the <ph><cite>ABC</cite></ph> document.</linktext>
   </topicmeta>
</topicref>

  • static references to other documents:
<topicref>
    <topicmeta>
        <linktext>See the <ph><cite>BLABLA</cite></ph> document </linktext>
    </topicmeta>
</topicref>

The cross-references to topics within the same book will be grouped under a "Related Topics" heading. The other ones will be grouped under a "Related Information" heading.

I would like in each case to display the related info as a bulleted list. For example:

Related Topics:
  • Introduction
  • Configuring Stuff
  • More about stuff
Related Information:
  • For details about this, see ABC Core User Guide
  • BLABLA Reference Manual

What I am getting at the moment is this:

Related Topics:
Introduction
Configuring Stuff
More about stuff
Related Information:
For details about this, see ABC Core User Guide
BLABLA Reference Manual

I can "hack" the one using <linktext> to add a bullet in the beginning, but that's as far as I got.

I've been looking at links.xsl in the PDF plugin (we have already customised some of the templates in links.xsl) but I can't figure out which template is the one I need to edit and how.

Any help is appreciated :)


Thanks a lot,
Ozana

Using only relationship tables in related links?

Tonia
 

Hi all,
I’m looking at the Rellinks.arg and wondering how to publish related links only if the ditamap has a relationship table.

For ditamap that aren’t using a relationship table, the desired behavior is that no related links are shown. I’m told that this configuration also blocks inclusion of a relationship table.

We’d like to serve both use cases with the same output transform. Is this possible?

Thanks for any guidance,
Tonia

Re: specialization and lightweight DITA #specialization

Radu Coravu
 

Hi Eric,

The "nbsp" entity is a deprecated entity but it's still part of the DITA DTDs, it is still defined in the DITA 1.3 DTDs defined in the module file:

plugins/org.oasis-open.dita.v1_3/dtd/base/dtd/topic.mod

<!-- Use of this entity is deprecated; the nbsp entity will be
     removed in DITA 2.0.                                          -->
<!ENTITY nbsp                   "&#xA0;"                             >
I think the only way to avoid defining it would be for them to have their own "topic.mod" in their DTD specialization.

Usually in cases in which you want to prohibit certain constructs, Schematron checks would prove useful but in this case the entity reference is expanded by the processor before the Schematron checks are applied so you cannot test with Schematron if an entity reference is present or not.

Regards,

Radu

Radu Coravu
Oxygen XML Editor
On 6/23/20 6:59 PM, Eric Sirois wrote:
Hi,

No, nbsp is not part of the DITA dtds. Most folks avoid entities like Covid-19. 

So someone either added it to the DTDs or it’s getting picked from somewhere else. Possibly MathML DTDs I think they have a file that defines a whole bunch of entities.

Eric

On Tuesday, June 23, 2020, 11:36 AM, Westley W. <wamsley@...> wrote:

Tagging onto this topic; I'm new to this group.  I'm on DITA 1.2, and I have a scenario where I need to remove &nbsp; as an entity.  Would this be a situation where I can apply a constraint?

Re: specialization and lightweight DITA #specialization

Eric Sirois
 

Hi,

No, nbsp is not part of the DITA dtds. Most folks avoid entities like Covid-19. 

So someone either added it to the DTDs or it’s getting picked from somewhere else. Possibly MathML DTDs I think they have a file that defines a whole bunch of entities.

Eric

On Tuesday, June 23, 2020, 11:36 AM, Westley W. <wamsley@...> wrote:

Tagging onto this topic; I'm new to this group.  I'm on DITA 1.2, and I have a scenario where I need to remove &nbsp; as an entity.  Would this be a situation where I can apply a constraint?

Re: specialization and lightweight DITA #specialization

Westley W.
 

Tagging onto this topic; I'm new to this group.  I'm on DITA 1.2, and I have a scenario where I need to remove &nbsp; as an entity.  Would this be a situation where I can apply a constraint?

Re: Setup standard section title for <screenshots> #PDF #FOP #XSLT

dabimak194@...
 

Solved the issue!

Re: specialization and lightweight DITA #specialization

jang
 

Hello Annet,

Please DO NOT move from your DITA to Lightweight DITA, as it is not going to make your content better. Although specialisation can be done from Lightweight DITA to re-introduce the elements you need, I would strongly recommend applying constraints on your DITA - allowing you to pick exactly what you need from DITA and effectively hide the rest from the authoring experience.

Using constraints means that all DITA processing tools will still work without any hiccups. If you start making specialisations that have any impact on the rendering at all, you will have to create those rendering parts for the Lightweight DITA tool chain. Constraints do NOT make your DITA incompatible with anything. I often wonder why companies shy away from this mechanism, as it is the only tool you normally need to tailor your DITA vocabulary to your authoring needs.

I have personally created a DITA constraints tool for FrameMaker that allows defining constraints without ever seeing an angular bracket. This is available in the FrameMaker 2019 product (i.e. no extra purchase or download - it is part of the product as Adobe has paid for the development). If you are using <oXygen> it is quite easy to edit the RelaxNG files that are the base for DITA since version 1.3. All my GUI for FrameMaker does is allowing non-geeks to edit those RelaxNG files in a safe manner.

I hope this helps you avoiding a path to lots of disasters.

Kind regards

Jang

Smart Information Design
Amsterdam, Netherlands
Cell: +31 646 854 996

On 23 Jun 2020, 09:50 +0200, annet.wezenbeek@..., wrote:
Trying to understand if we can move from full DITA to lightweight DITA. It seems very simplified and that would mean getting rid of some elements that worked really well. Is it possible to create a specialization in lightweight DITA that uses some of the elements from full DITA? 

Setup standard section title for <screenshots> #PDF #FOP #XSLT

dabimak194@...
 

Hi dita experts,

as title says, I'm trying to automatically generate title for <screenshots> every time when it comes up in my documentation. It should be same as section titles, but not the titles like with figures. Would this be possible?

Br,
Mak

specialization and lightweight DITA #specialization

annet.wezenbeek@...
 

Trying to understand if we can move from full DITA to lightweight DITA. It seems very simplified and that would mean getting rid of some elements that worked really well. Is it possible to create a specialization in lightweight DITA that uses some of the elements from full DITA? 

Re: Chapter numbering issue when using <topicgroup>

Chris Brand
 

Hi Toshihiko

 

I'm (still) using 2.5.4. Thanks for checking!!

 

Chris.

 

 

Von: main@dita-users.groups.io <main@dita-users.groups.io> Im Auftrag von Toshihiko Makita
Gesendet: Montag, 22. Juni 2020 15:47
An: main@dita-users.groups.io
Betreff: Re: [dita-users] Chapter numbering issue when using <topicgroup>

 

Hi Chiris,

> Do you have an idea where this specific template of yours has to be placed in the pdf2 section?

What DITA-OT version are you using? I will take a look at PDF2 plug-in tomorrow.

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

Re: Chapter numbering issue when using <topicgroup>

Toshihiko Makita
 

Hi Chiris,

> Do you have an idea where this specific template of yours has to be placed in the pdf2 section?

What DITA-OT version are you using? I will take a look at PDF2 plug-in tomorrow.

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

Re: Chapter numbering issue when using <topicgroup>

Chris Brand
 

Hi Toshihiko

 

Thanks! I'm using FOP and not AH for PDF conversion. Do you have an idea where this specific template of yours has to be placed in the pdf2 section? I tried all possible files but it had no effect ...

 

Greez,

Chris.

 

Von: main@dita-users.groups.io <main@dita-users.groups.io> Im Auftrag von Toshihiko Makita
Gesendet: Samstag, 20. Juni 2020 15:41
An: main@dita-users.groups.io
Betreff: Re: [dita-users] Chapter numbering issue when using <topicgroup>

 

Hi Chiris,

As <topicgroup> is specialization of topicref, it affects numbering wrongly. To avoid this problem, I always skip <topicgroup> in the merged middle file processing in PDF output.

See https://github.com/AntennaHouse/pdf5-ml/blob/master/com.antennahouse.pdf5.ml/xsl/dita2fo_convmerged.xsl Line 163 or near.

Hope this helps.

Regards,

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

Re: Chapter numbering issue when using <topicgroup>

Chris Brand
 

Hi Mica

 

<topicset> behaves same as <topicgroup> in PDF generation when it comes to wrong chapter numbers.

 

Greez,

Chris.

 

Von: main@dita-users.groups.io <main@dita-users.groups.io> Im Auftrag von Mica Semrick
Gesendet: Freitag, 19. Juni 2020 20:28
An: main@dita-users.groups.io; Chris Brand via groups.io <chrizzbee74@...>
Betreff: Re: [dita-users] Chapter numbering issue when using <topicgroup>

 

Hi,

You can try <topicset> instead.

-m

On June 19, 2020 8:12:48 AM PDT, "Chris Brand via groups.io" <chrizzbee74@...> wrote:

Hi
In my map structure, I started to use <topicgroup> with profiling. My chapters are all numbered based on a template derived from the DITA Generator code. This worked nice so far. I understood that <topicgroup> elements do not affect the map structure. In the PDF output this is indeed true, the <topicgroup> element doesn't show up and is not included in the TOC. But all children of the <topicgroup> are counted up one level, thus creating a false numbering.

Example:

1 Chapter
<topicgroup>
   1.1.1 Chapter
   1.1.2 Chapter
</topicgroup>
1.2 Chapter

I expect that the output is like this:

1 Chapter
<topicgroup>
   1.1 Chapter
   1.2 Chapter
</topicgroup>
1.3 Chapter

So the children of the <topicgroup> get the wrong chapter depth assigned.

Anyone knows a fix?

Thanks,
Chris.