Date   
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.

Re: Chapter numbering issue when using <topicgroup>

Toshihiko Makita
 

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: Diagram XML markup/definition language within DITA?

Daud Vyd
 

Roger, this looks like exactly what I was looking for. Thank you!


From: main@dita-users.groups.io <main@dita-users.groups.io> on behalf of Hadley, Roger (Hillsboro) via groups.io <roger.hadley@...>
Sent: Thursday, June 18, 2020 7:59 PM
To: main@dita-users.groups.io <main@dita-users.groups.io>
Subject: Re: [dita-users] Diagram XML markup/definition language within DITA?
 
I use PlantUML in Oxygen for diagramming. So far using PlantUML Activity diagrams, which would not be the appropriate type of XML Schema. But PlantUML has many different diagrams types, one of which is likely appropriate. Here are some relelvant links:
https://plantuml.com/
https://blog.oxygenxml.com/topics/embedding_diagrams_in_dita_topics_using_plantuml.html

Re: Chapter numbering issue when using <topicgroup>

Mica Semrick
 

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.

Chapter numbering issue when using <topicgroup>

Chris Brand
 

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.

Re: XSL-FO PDF Title numbering + font style #FOP #XSLT #PDF

chichak1995@...
 

Not really sure, it was the decision authors made together, I'm just there as technical support.

[ann][webinar] Getting Started with DITA Using Oxygen XML Editor #Oxygen

alin_belu@...
 

Hello, 
 
On June 24, we will continue our weekly series of webinars with the 5th live event – “Getting Started with DITA using Oxygen XML Editor”. 
 
Sorin Carbunaru, software developer at Syncro Soft, invites you to a live discussion that will focus on introductory concepts of working with DITA documents in Oxygen XML Editor, covering everything from creating DITA maps and topics from scratch to basic publishing using out-of-the-box scenarios. Both beginner and advanced users will benefit from learning about subjects such as: 
  • The DITA UI perspective 
  • Creating and editing maps and topics 
  • Using the DITA Maps Manager 
  • Validate and Check for Completeness 
  • Basic publishing using predefined scenarios 
 
You can register for free at http://www.oxygenxml.com/evs2020-5.html
 
Check the full list of the upcoming webinars and follow the links to see more details and register for free: 
 
Regards, 
Alin


--
Alin Belu
Oxygen XML Editor

Re: XSL-FO PDF Title numbering + font style #FOP #XSLT #PDF

Julio J Vazquez
 

The real question is why are you messed that deep? That number of levels must be frustrating to authors and readers. 

Julio J. Vazquez

PDF Landscape page-sequence XSL:FO #FOP #PDF

chichak1995@...
 

I´ve been working on landscape for my custom PDF transformation for few months now (on and off project). I´ve picked it up again few days ago and I´m pretty close I think.
What I´m trying to do is detect if outputclass="landscape" was set for the topic and if yes process it in landscape mode, otherwise the page-sequence should stay default. So far this works very well, but not exactly how i want it to. I´ve implemented it in that way that by every topic processing, it checks which outputclass is defined and based on that it creates new <fo:page-sequence>. I just couldn´t find a better way when i started. The problem is that every page has its own page-sequence and this is a problem when I have a .dita file whos content covers only few rows of A4 paper. What I want to achieve is to just continue next .dita file after this paragraph in case the outputclass was same as the previously processed topic. I just can´t wrap my head around a right solution...

I´m hoping someone more experienced could help me with this matter and point me in right direction.

Here is my code: https://pastebin.com/J5xX9wG5