Date   

Font substitution in PDF SVGs?

Nicholas Mucks
 

Hi!
For HTML we run an ANT target against the output directory to replace certain strings in all svgs with another string. It’s just one older font name to another.

What’s the best way to accomplish this task in PDF? We notice that the topic.fo file references the source file locations, not temp or output locations. In testing we modified our ANT target to use the source folder instead of the output folder and although it works we don’t want to edit the source files.



Take care,
- Nick

Sent from mobile


Componize is looking for its Product Ambassador

Jean-Luc Borie
 

Hi all,

The next generation of our solution is waiting for its Ambassador! The position is based at our HQ in Aix-en-Provence (partial teleworking): https://www.linkedin.com/jobs/view/2618710765/
Enjoy your summer,
--
Kind regards,

Jean-Luc Borie
Mob : +33 628 848 252
Skype : jlborie


Re: Need to change the decimal page number into topic title abbreviation #DITA-OT #PDF

stinakab
 

Hi,

I guess this has been resolved with the following Oxygen forum entry, correct? https://www.oxygenxml.com/forum/topic22984.html


Re: Relationship Table links disappear with branch filtering. #branch-filtering

Adam Myers
 

Thanks Radu. 

Yes, that worked. Thanks.


Re: Relationship Table links disappear with branch filtering. #branch-filtering

Radu Coravu
 

Hi Adam,

Once you start using branch filtering, key scoping, you need to start using everywhere key references to refer to topics. So you need to define keys for your topics and in the reltable use only topicref with keyref instead of topicref with href.

That's because branch filtering will dynamically rename DITA topic file names during publishing and with keyrefs the publishing engine knows more precisely to what specific topic it should refer.

Can you take your sample project, use topicref with keyrefs in the reltables and see if that works better with the DITA OT 3.6 bundled with Oxygen XML Editor? If not please re-attach the project to an email (either here or directly to support@...).

Regards,

Radu

Radu Coravu
Oxygen XML Editor
On 6/24/21 23:36, Adam Myers via groups.io wrote:

I tried this with a project that Radu updated here: https://dita-users.groups.io/g/main/message/45318

It doesn't work in that project when I do a webhelp transformation, either. I'm using the latest Oxygen XML Editor 23.1, build 2021061407 with dita-ot 3.6. Thanks

  


Re: Need to change the decimal page number into topic title abbreviation #DITA-OT #PDF

boopathyks@...
 

Thanks Christina, Its working fine as per your suggestion, but i'm having some issue to apply the changes for all the child topic, actually my input dita file having topics like this

<topic outputclass="h1">
   <title outputclass="CD_Map_Heading-hide">HIDE TOPIC</title>
   <topic outputclass="h2">
      <title>DEFINITION</title>
   </topic>
   <topic outputclass="h3">
      <title>REVOLUTION</title>
   </topic>
</topic>
static-content.xsl
<xsl:template name="insertBodyOddFooter">
    <fo:static-content flow-name="odd-body-footer">
        <fo:block>&#160;</fo:block>
        <fo:block xsl:use-attribute-sets="__body__odd__footer">
            <xsl:choose>
                <xsl:when test="contains(@outputclass, 'h2')">
                    <xsl:text>DEF</xsl:text>
</xsl:when>
<xsl:when test="contains(@outputclass, 'h3')">
                    <xsl:text>REV</xsl:text>
</xsl:when>
<xsl:otherwise> <fo:block-container position="absolute"> <fo:block padding-top="20pt" text-align="center"> <fo:page-number/> </fo:block> </fo:block-container> </xsl:otherwise> </xsl:choose> </fo:block> </fo:static-content> </xsl:template>

I'm getting only DEF as footnote for all the topics.But I need separate footnote for each child topic. For the h3 attribute I need to get REV as footer value. But I'm getting only DEF. So please help me to get the footer value for that corresponding chils topic pages. Thanks in advance!!!


Re: Relationship Table links disappear with branch filtering. #branch-filtering

Adam Myers
 

I tried this with a project that Radu updated here: https://dita-users.groups.io/g/main/message/45318

It doesn't work in that project when I do a webhelp transformation, either. I'm using the latest Oxygen XML Editor 23.1, build 2021061407 with dita-ot 3.6. Thanks


Relationship Table links disappear with branch filtering. #branch-filtering

Adam Myers
 

Hi,

I have a ditamap with multiple sub-ditamaps. A few of these ditamaps share topics. I am using a ditaval file to exclude content in the topics in one of the ditamaps. 

When I transform (webhelp) the branch-filtered ditamap by itself, the content is excluded and all of the relationship table links appear correctly. When I transform the main ditamap with all of the sub-maps, the content is filtered correctly, but there are no related links in the filtered submap.

I'm not sure what I am doing wrong and would appreciate any help/direction possible. I can provide more information if necessary.

Thanks,

Adam


Re: Simple Plugin to List Attr Vals per File in Map

despopoulos_chriss
 

Hi Nick...  I need more than that.  We use metadata to store the names of specific data objects that we are documenting/referencing in different places of an API guide.  When the data object changes, we need to track down the topics and incorporate the changes.  I want a report that lists by file, all the data objects that we reference.  That way I can see which files need to be updated.  And no, we can't just automagically pick up the code changes...  We have to cover our explanations of usage for these data objects as well.  There might be more clever ways to handle this, but at least this is a start.  Maybe after we have the report, we can run some other checker against the changes and automatically list only the files we need to edit.  But I think it starts with the report.


Re: Simple Plugin to List Attr Vals per File in Map

despopoulos_chriss
 

Thanks Reece...  It took a little doing (I don't really hack the OT at all) but I got a custom plugin based on this together, and I can run the merge, then run it through one of those stylesheets.  I just need to massage that stylesheet now to get the data I want -- that should be easy enough.  It's a brave new world for me!!!

cud


Re: Simple Plugin to List Attr Vals per File in Map

Nicholas Mucks
 

Hi Chris,
Isn’t there a file in the temp directory that lists all files after preprocessing?

If not, you can always parse the .job.xml file to get what you need.

Take care,
- Nick

Sent from mobile

On Jun 23, 2021, at 5:09 AM, despopoulos_chriss via groups.io <despopoulos_chriss@...> wrote:

Hi all...

Asking whether there is an existing OT plugin that is truly minimal...  Goes through a doc map and simply lists the file name for each topic, followed by the value of a given attribute.  Actually, I would settle for a plugin that simply lists each topic filename so I can start from there, but who would ever create something that does only that?  I need to do a specific type of report.

Thanks in advance for any pointers.


Re: Simple Plugin to List Attr Vals per File in Map

r.roggen
 

I’ve used the “dita-merged” plugin for transformations like this.

https://github.com/oxygenxml/dita-merged

It sounds like one of the stylesheets included in the possible-applications folder may give you a good starting point. 

-Reece


Simple Plugin to List Attr Vals per File in Map

despopoulos_chriss
 

Hi all...

Asking whether there is an existing OT plugin that is truly minimal...  Goes through a doc map and simply lists the file name for each topic, followed by the value of a given attribute.  Actually, I would settle for a plugin that simply lists each topic filename so I can start from there, but who would ever create something that does only that?  I need to do a specific type of report.

Thanks in advance for any pointers.


Re: Need to change the decimal page number into topic title abbreviation #DITA-OT #PDF

stinakab
 

Hi,

You haven't mentioned which DITA OT version you're using but I guess this applies to all versions.
I think the page number is added with the static-content.xsl file. In there, there are templates for headers and footers where fo:page-number inserts the page number. I think the startPageNumbering template in the commons.xsl only allows you to enable start numbering on the first page of your document.
So maybe you could insert a conditional test in static-content.xsl and see if that works for you.

Best,
Christina


Need to change the decimal page number into topic title abbreviation #DITA-OT #PDF

boopathyks@...
 

Hi,

I'm doing the dita-ot pdf conversion, using lot of topic dita template and requirement is to changing the decimal page numbers into the topic title abbreviation for one topic alone, other topic it should be in decimal page number only

In the commons.xsl

<xsl:template match="*[contains(@class, ' topic/topic ')]">

<xsl:when test="not(ancestor::*[contains(@class, ' topic/topic ')]) and not(ancestor::ot-placeholder:glossarylist)">
<fo:page-sequence master-reference="{$page-sequence-reference}" xsl:use-attribute-sets="__force__page__count" initial-page-number="1">
<xsl:call-template name="startPageNumbering"/>
</fo:page-sequence>
</xsl:when>


</xsl:template>

Commons-attr.xsl:

    <xsl:attribute-set name="__force__page__count">
        <xsl:attribute name="force-page-count">
            <xsl:choose>
                <xsl:when test="name(/*) = 'bookmap'">
                    <xsl:value-of select="'even'"/>
                </xsl:when>
                <xsl:otherwise>
                    <xsl:value-of select="'auto'"/>
                </xsl:otherwise>
            </xsl:choose>
        </xsl:attribute>
    </xsl:attribute-set>
 

There is no any templates for startPageNumbering, as per the initial-page-number and force_page_count, decimal page number getting reset for every topic as starting with page number 1. So that I just want to change the one topic decimal page number into the corresponding topic title abbreviation

for eg:

<topic class="- topic/topic ">
<title class="- topic/title " outputclass="CD_Section_Heading">DEFINITIONS</title>
</topic>


for this DEFINITIONS topic page number should "DEF" as like that I have few topic that should get abbreviation as page number for that corresponding topic pages. Please help me and let me know if you need any more. Thanks in Advance!!!


[ANN] Release of XMLmind XML Editor v9.5.1

Hussein Shafie
 

Release of XMLmind XML Editor v9.5.1. Highlights:

- Made the automatic upgrade of user-installed add-ons after a new version of XXE is installed simpler, more reliable and more systematic.

However these new simplicity and reliability come at a price: using the "Install Add-ons" dialog box, it is no longer possible to install, uninstall or upgrade any of the bundled add-ons found inside the XXE installation directory (XXE_install_dir/addon/). (It's still possible to do this “manually” though.)

More information in: The "Install Add-ons" dialog box. See http://www.xmlmind.com/xmleditor/_distrib/doc/help/com.xmlmind.xmleditapp.app.part.InstallAddonsDialog.html

- Updated several software components (XMLmind DITA Converter, XMLmind Word To XML, etc).

- XMLmind XML Editor is now officially supported on Java™ 16 platforms.

More information in http://www.xmlmind.com/xmleditor/changes.html

--------------------------------------------------
What is XMLmind XML Editor?

Home page: http://www.xmlmind.com/xmleditor/

Personal Edition is free to use by many persons and organizations. Download:

http://www.xmlmind.com/xmleditor/download.shtml
--------------------------------------------------


Re: How can I treat a <mapref> as a level of TOC hierarchy?

ekimber@contrext.com
 

I just realized that in the example, by putting the keyscopes on the topicheads, you can remove the keyscope qualification from the keyrefs on the <ph> elements in the navigation titles, further simplifying the markup.

 

Cheers,

 

E.

 

--

Eliot Kimber

http://contrext.com

 

 

 

From: <main@dita-users.groups.io> on behalf of "ekimber@..." <ekimber@...>
Reply-To: <main@dita-users.groups.io>
Date: Sunday, June 20, 2021 at 9:44 AM
To: <main@dita-users.groups.io>
Subject: Re: [dita-users] How can I treat a <mapref> as a level of TOC hierarchy?

 

If these submaps are individual publications and are also used as root maps in their own right then I would be tempted to refer to them as peer-scoped resources and have that trigger the preprocessing you’re using. Alternatively you could refactor the maps so you have one root map just for standalone publication and another for this combined publication use and use either submaps or conref from the root maps to pull in the parts. That would be painful and ugly, but it would work.

 

The semantic of scope=”peer” on map references is “this is a separate root map”, which is I think the semantic you have here, even though you’re publishing them as a single HTML result.  You could just as easily publish them independently to the same parent location and get the same effect as long as you had a way to construct the top-level navigation over the otherwise-independent publications being published together.

 

It looks like I made a bad assumption about your use case—I had assumed that you had submaps used from a root bookmap where you were expecting the submap titles to contribute to the book’s title hierarchy—I’ve just had that case in a client’s content so that case was fresh in my mind (and I’ve seen it before—as I said it’s not a crazy assumption to make that submaps would work that way so it’s not surprising that people do it).

 

So I think you’ve shown a general requirement for an HTML publishing process that can publish a set of otherwise-independent publications together, either as a single publishing action or as multiple publishing actions where the results are coordinated so the final published result is correct. For example, I might have a system that can use the map you show (with scope=”peer” on the mapsrefs) to generate the top-level navigation over the books and then publish each book separately under this navigation parent so that, once published, all the navigation works.

 

I also noticed that you’ve put @keyscope on the <mapref> but I don’t think that’s what you want, because if those are bookmaps, they don’t have a single root topicref to act as the key scope root (although Open Toolkit will synthesize a <topicgroup> for the map and put the keyscope on that, so I guess it’ s OK, at least there), but I would put the @keyscope on the topicheads, as those become the root topicrefs for each publication:

 

    <topichead keyscope=”book1”>
      <topicmeta>
        <navtitle><ph keyref="book1.BookTitle"/></navtitle>
      </topicmeta>
      <mapref href="book1.ditamap" format="ditamap"/>
    </topichead>

    <topichead keyscope="book2">

      <topicmeta>
        <navtitle><ph keyref="book2.BookTitle"/></navtitle>
      </topicmeta>
      <mapref href="book2.ditamap" format="ditamap"/>
    </topichead>


It’s important to remember that a mapref is really a reference to the topicrefs contained by the referenced map, so if the map you’re referencing doesn’t itself have a single root topicref, the merged result will not either, thus the need to add the topiceheads you have here (or you could have referenced title-only topics if you preferred).

 

I think the BookMap design might have been better if it had used a required root topicref to represent the publication root and hold the publication-level title and metadata. That design would have avoided this problem entirely, but that ship has long sailed and I didn’t even take that route in my DITA for Publishers PublicationMap design (although I should have, I now realize).

 

Cheers,

 

Eliot

 

--

Eliot Kimber

http://contrext.com

 

 

 

From: <main@dita-users.groups.io> on behalf of Chris Papademetrious <chrispitude@...>
Reply-To: <main@dita-users.groups.io>
Date: Saturday, June 19, 2021 at 3:59 PM
To: <main@dita-users.groups.io>
Subject: Re: [dita-users] How can I treat a <mapref> as a level of TOC hierarchy?

 

Hi Eliot,

As always, thanks for jumping in!

We use SyncroSoft's PDF Chemistry for PDF publishing. And it behaves correctly - it doesn't create navigation hierarchy from submap titles. My previous comment was that topichead levels added inside a <bookmap> would alter the book PDF's TOC, so modifying the <bookmap> is not an option.

However, your mention of <navtitle> within <topicmeta> pointed me in the right direction! I get the desired result by variable-izing the book titles, then creating a top-level map as follows:

<map>
    <title>Online Help</title>

    <topichead>

      <topicmeta>
        <navtitle><ph keyref="book1.BookTitle"/></navtitle>
      </topicmeta>
      <mapref href="book1.ditamap" format="ditamap" keyscope="book1"/>
    </topichead>

    <topichead>

      <topicmeta>
        <navtitle><ph keyref="book2.BookTitle"/></navtitle>
      </topicmeta>
      <mapref href="book2.ditamap" format="ditamap" keyscope="book2"/>
    </topichead>

</map>


When I publish this map (either with the DITA-OT's html5 transformation or with Oxygen's WebHelp Responsive transformation), each book has its own hierarchy item, named after the book title. Success!

With this success under my belt, I started poking around in the preprocess2 pipeline to see if I could automate the creation of these <topichead>/<navtitle>/<mapref> constructs with a user-specified attribute as a convenience:

      <mapref href="book1.ditamap" format="ditamap" keyscope="book1" outputclass="topichead"/>
      <mapref href="book2.ditamap" format="ditamap" keyscope="book2" outputclass="topichead"/>

It is achievable, but there are some complexities with ensuring that book titles with profiling conditions and book-local variables are handled properly. I might keep at it just to learn more about the processing pipeline. But for production, I think it's better to stick with pure DITA without adding yet another plugin dependency.

 - Chris


Re: How can I treat a <mapref> as a level of TOC hierarchy?

ekimber@contrext.com
 

If these submaps are individual publications and are also used as root maps in their own right then I would be tempted to refer to them as peer-scoped resources and have that trigger the preprocessing you’re using. Alternatively you could refactor the maps so you have one root map just for standalone publication and another for this combined publication use and use either submaps or conref from the root maps to pull in the parts. That would be painful and ugly, but it would work.

 

The semantic of scope=”peer” on map references is “this is a separate root map”, which is I think the semantic you have here, even though you’re publishing them as a single HTML result.  You could just as easily publish them independently to the same parent location and get the same effect as long as you had a way to construct the top-level navigation over the otherwise-independent publications being published together.

 

It looks like I made a bad assumption about your use case—I had assumed that you had submaps used from a root bookmap where you were expecting the submap titles to contribute to the book’s title hierarchy—I’ve just had that case in a client’s content so that case was fresh in my mind (and I’ve seen it before—as I said it’s not a crazy assumption to make that submaps would work that way so it’s not surprising that people do it).

 

So I think you’ve shown a general requirement for an HTML publishing process that can publish a set of otherwise-independent publications together, either as a single publishing action or as multiple publishing actions where the results are coordinated so the final published result is correct. For example, I might have a system that can use the map you show (with scope=”peer” on the mapsrefs) to generate the top-level navigation over the books and then publish each book separately under this navigation parent so that, once published, all the navigation works.

 

I also noticed that you’ve put @keyscope on the <mapref> but I don’t think that’s what you want, because if those are bookmaps, they don’t have a single root topicref to act as the key scope root (although Open Toolkit will synthesize a <topicgroup> for the map and put the keyscope on that, so I guess it’ s OK, at least there), but I would put the @keyscope on the topicheads, as those become the root topicrefs for each publication:

 

    <topichead keyscope=”book1”>
      <topicmeta>
        <navtitle><ph keyref="book1.BookTitle"/></navtitle>
      </topicmeta>
      <mapref href="book1.ditamap" format="ditamap"/>
    </topichead>

    <topichead keyscope="book2">

      <topicmeta>
        <navtitle><ph keyref="book2.BookTitle"/></navtitle>
      </topicmeta>
      <mapref href="book2.ditamap" format="ditamap"/>
    </topichead>

It’s important to remember that a mapref is really a reference to the topicrefs contained by the referenced map, so if the map you’re referencing doesn’t itself have a single root topicref, the merged result will not either, thus the need to add the topiceheads you have here (or you could have referenced title-only topics if you preferred).

 

I think the BookMap design might have been better if it had used a required root topicref to represent the publication root and hold the publication-level title and metadata. That design would have avoided this problem entirely, but that ship has long sailed and I didn’t even take that route in my DITA for Publishers PublicationMap design (although I should have, I now realize).

 

Cheers,

 

Eliot

 

--

Eliot Kimber

http://contrext.com

 

 

 

From: <main@dita-users.groups.io> on behalf of Chris Papademetrious <chrispitude@...>
Reply-To: <main@dita-users.groups.io>
Date: Saturday, June 19, 2021 at 3:59 PM
To: <main@dita-users.groups.io>
Subject: Re: [dita-users] How can I treat a <mapref> as a level of TOC hierarchy?

 

Hi Eliot,

As always, thanks for jumping in!

We use SyncroSoft's PDF Chemistry for PDF publishing. And it behaves correctly - it doesn't create navigation hierarchy from submap titles. My previous comment was that topichead levels added inside a <bookmap> would alter the book PDF's TOC, so modifying the <bookmap> is not an option.

However, your mention of <navtitle> within <topicmeta> pointed me in the right direction! I get the desired result by variable-izing the book titles, then creating a top-level map as follows:

<map>
    <title>Online Help</title>

    <topichead>

      <topicmeta>
        <navtitle><ph keyref="book1.BookTitle"/></navtitle>
      </topicmeta>
      <mapref href="book1.ditamap" format="ditamap" keyscope="book1"/>
    </topichead>

    <topichead>

      <topicmeta>
        <navtitle><ph keyref="book2.BookTitle"/></navtitle>
      </topicmeta>
      <mapref href="book2.ditamap" format="ditamap" keyscope="book2"/>
    </topichead>

</map>


When I publish this map (either with the DITA-OT's html5 transformation or with Oxygen's WebHelp Responsive transformation), each book has its own hierarchy item, named after the book title. Success!

With this success under my belt, I started poking around in the preprocess2 pipeline to see if I could automate the creation of these <topichead>/<navtitle>/<mapref> constructs with a user-specified attribute as a convenience:

      <mapref href="book1.ditamap" format="ditamap" keyscope="book1" outputclass="topichead"/>
      <mapref href="book2.ditamap" format="ditamap" keyscope="book2" outputclass="topichead"/>

It is achievable, but there are some complexities with ensuring that book titles with profiling conditions and book-local variables are handled properly. I might keep at it just to learn more about the processing pipeline. But for production, I think it's better to stick with pure DITA without adding yet another plugin dependency.

 - Chris


Re: How can I treat a <mapref> as a level of TOC hierarchy?

Chris Papademetrious
 

Hi everyone,

I created a plugin that can automatically add navigation hierarchy for submaps:

https://github.com/chrispy-snps/DITA-mapref-topichead

 - Chris


Re: How can I treat a <mapref> as a level of TOC hierarchy?

Chris Papademetrious
 

Hi Eliot,

As always, thanks for jumping in!

We use SyncroSoft's PDF Chemistry for PDF publishing. And it behaves correctly - it doesn't create navigation hierarchy from submap titles. My previous comment was that topichead levels added inside a <bookmap> would alter the book PDF's TOC, so modifying the <bookmap> is not an option.

However, your mention of <navtitle> within <topicmeta> pointed me in the right direction! I get the desired result by variable-izing the book titles, then creating a top-level map as follows:

<map>
    <title>Online Help</title>

    <topichead>

      <topicmeta>
        <navtitle><ph keyref="book1.BookTitle"/></navtitle>
      </topicmeta>
      <mapref href="book1.ditamap" format="ditamap" keyscope="book1"/>
    </topichead>

    <topichead>

      <topicmeta>
        <navtitle><ph keyref="book2.BookTitle"/></navtitle>
      </topicmeta>
      <mapref href="book2.ditamap" format="ditamap" keyscope="book2"/>
    </topichead>

</map>


When I publish this map (either with the DITA-OT's html5 transformation or with Oxygen's WebHelp Responsive transformation), each book has its own hierarchy item, named after the book title. Success!

With this success under my belt, I started poking around in the preprocess2 pipeline to see if I could automate the creation of these <topichead>/<navtitle>/<mapref> constructs with a user-specified attribute as a convenience:

      <mapref href="book1.ditamap" format="ditamap" keyscope="book1" outputclass="topichead"/>
      <mapref href="book2.ditamap" format="ditamap" keyscope="book2" outputclass="topichead"/>

It is achievable, but there are some complexities with ensuring that book titles with profiling conditions and book-local variables are handled properly. I might keep at it just to learn more about the processing pipeline. But for production, I think it's better to stick with pure DITA without adding yet another plugin dependency.

 - Chris

21 - 40 of 46324