Date   

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

ekimber@contrext.com
 

As others have pointed out, the titles of submaps are not retained and do not contributed to the title hierarchy of the result document.

 

This seems to be a common misunderstanding and it’s easy to see why people might naturally assume that subtopic titles will contribute to the publication’s title hierarchy, but nevertheless they do not.

 

[NOTE: If your PDF generation process treats submap titles as part of the publication title hierarchy *it is doing the wrong thing*. Submap titles are metadata and should *never* contribute to the publication title hierarchy because to do so is to create an serious incompatibility with normal DITA processing. In this case, your data is incorrectly structured and needs to be fixed. Of course, if you’re in this situation you may not be in a position to correct the data, but do understand that your data is not correct and really needs to be fixed. At a minimum, the PDF generation code should have a very prominent comment somewhere that it is treating submap titles as though they were topic heads as a *workaround* to a data problem.]

 

Note that by “topichead” we don’t mean “the <topichead> element”, we mean “A topicref of any type that does not refer to a resource (no @href or @keyref) and has a <navtitle>”. Any specialization of topicref that is not explicitly set to a processing role of “resource-only” should able to function as a topichead as long as it allows <topicmeta> and <navtitle> and does not also require @href or @keyref. So <keydef> cannot be a topichead (because it is explicitly resource-only) but all the topicref specializations in bookmap can be.

 

This means you can create a topichead using <chapter> in <bookmap>

 

<bookmap>

  <bookmeta>

   …

</bookmeta>

 

<chapter>

  <topicmeta>

     <navtitle>Installation</navtitle>

   </topicmeta>

   <mapref href=”install-chapter-topics.ditamap”/>

</chapter>

</bookmap>

 

This works and should produce a result identical to having a reference to a title-only topic for PDF output.

 

However, for HTML output you get different behaviors for topicheads and title-only topics—you definitely see this in Open Toolkit’s HTML transforms—a topichead is reflected in the ToC but does not get its own HTML page.

 

 

 

--

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 11:37 AM
To: <main@dita-users.groups.io>
Subject: Re: [dita-users] How can I treat a <mapref> as a level of TOC hierarchy?

 

Hi Dan,

Thanks for the suggestion! I can't use <topichead> directly in the <bookmap> because

  • A <bookmap> does not permit <topichead> at its top level, only <chapter>, <appendix>, and other book-like things.
  • Even if allowed, it would add a level to the book's TOC when the book PDF is published.


Hi Lionel,

Thanks also for the suggestion! I can wrap each <mapref> in a <topichead>, but that doesn't allow me to use the book's intrinsic title as the title for that level.

As a last resort, I could variable-ize each book's title, then reach into each book's scope to get that variable, but I'm hoping to find a better way (because that would require me to modify hundreds of books).

 - Chris


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

Chris Papademetrious
 

Hi Dan,

Thanks for the suggestion! I can't use <topichead> directly in the <bookmap> because

  • A <bookmap> does not permit <topichead> at its top level, only <chapter>, <appendix>, and other book-like things.
  • Even if allowed, it would add a level to the book's TOC when the book PDF is published.

Hi Lionel,

Thanks also for the suggestion! I can wrap each <mapref> in a <topichead>, but that doesn't allow me to use the book's intrinsic title as the title for that level.

As a last resort, I could variable-ize each book's title, then reach into each book's scope to get that variable, but I'm hoping to find a better way (because that would require me to modify hundreds of books).

 - Chris


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

Lionel Moizeau
 

Hey Chris,

What about using topicheads as a parent to the mapref?

Lionel


Le sam. 19 juin 2021 à 17:05, Dan Vint <dvint@...> a écrit :
I don't work with bookmarks but use map so I'm not sure of all the title derails. Sub maps do not interject structure and then don't introduce their own titles, they disappear as you have seen. The OT strip the map elements and chains them together during processing.

You had the right solution with the topic head, just make that the first element in your bookmap (if allowed). Put a simple title on the bookmap itself and make the text of your topchead contain the conditions to make the correct title.



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Chris Papademetrious <chrispitude@...>
Date: 6/19/21 7:41 AM (GMT-08:00)
Subject: [dita-users] How can I treat a as a level of TOC hierarchy?

Hi fellow DITA users,

We are exploring Oxygen's WebHelp Responsive transformation, so I am exploring DITA-OT chunking to understand how to control the help structure.

I have multiple <bookmap> files referenced from a top-level <map>:

<map>
    <title>Online Help</title>
    <mapref href="book1.ditamap"/>
    <mapref href="book2.ditamap"/>
</map>

When I publish this (as WebHelp or as plain html5), the <bookmap> levels evaporate and I get a flat TOC of all book chapters:

  • Chapter 1
    • ...topics...
  • Chapter 2
    • ...topics...
  • Chapter 1
    • ...topics...
  • Chapter 2
    • ...topics...

But what I need is for each book to provide its own navigation level derived from its book title:

  • Book 1 Title
    • Chapter 1
      • ...topics...
    • Chapter 2
      • ...topics...
  • Book 2 Title
    • Chapter 1
      • ...topics...
    • Chapter 2
      • ...topics...

Wrapping each <mapref> in a <topichead> creates a level, but that approach doesn't inherit the book title. (Our books are conditional and often have conditional text, references to variables *within* the book scope, etc.).

I looked at the @chunk attribute documentation and experimented, and:

  • The to-navigation value sounds like what I need, but it is deprecated.
  • The to-content value did create a TOC level named after the book (hooray!), but proceeded to collapse the entire book's contents into a single flat topic (boo!).
  • Other values had no effect when applied to the <mapref> element. (Values set on a <bookmap> apply a policy to the entire map, which felt too intrusive to try.)

Books are big, important things. Hopefully there's a way to do this!

 - Chris


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

Dan Vint
 

I don't work with bookmarks but use map so I'm not sure of all the title derails. Sub maps do not interject structure and then don't introduce their own titles, they disappear as you have seen. The OT strip the map elements and chains them together during processing.

You had the right solution with the topic head, just make that the first element in your bookmap (if allowed). Put a simple title on the bookmap itself and make the text of your topchead contain the conditions to make the correct title.



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Chris Papademetrious <chrispitude@...>
Date: 6/19/21 7:41 AM (GMT-08:00)
To: main@dita-users.groups.io
Subject: [dita-users] How can I treat a as a level of TOC hierarchy?

Hi fellow DITA users,

We are exploring Oxygen's WebHelp Responsive transformation, so I am exploring DITA-OT chunking to understand how to control the help structure.

I have multiple <bookmap> files referenced from a top-level <map>:

<map>
    <title>Online Help</title>
    <mapref href="book1.ditamap"/>
    <mapref href="book2.ditamap"/>
</map>

When I publish this (as WebHelp or as plain html5), the <bookmap> levels evaporate and I get a flat TOC of all book chapters:

  • Chapter 1
    • ...topics...
  • Chapter 2
    • ...topics...
  • Chapter 1
    • ...topics...
  • Chapter 2
    • ...topics...

But what I need is for each book to provide its own navigation level derived from its book title:

  • Book 1 Title
    • Chapter 1
      • ...topics...
    • Chapter 2
      • ...topics...
  • Book 2 Title
    • Chapter 1
      • ...topics...
    • Chapter 2
      • ...topics...

Wrapping each <mapref> in a <topichead> creates a level, but that approach doesn't inherit the book title. (Our books are conditional and often have conditional text, references to variables *within* the book scope, etc.).

I looked at the @chunk attribute documentation and experimented, and:

  • The to-navigation value sounds like what I need, but it is deprecated.
  • The to-content value did create a TOC level named after the book (hooray!), but proceeded to collapse the entire book's contents into a single flat topic (boo!).
  • Other values had no effect when applied to the <mapref> element. (Values set on a <bookmap> apply a policy to the entire map, which felt too intrusive to try.)

Books are big, important things. Hopefully there's a way to do this!

 - Chris


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

Chris Papademetrious
 

I'm attaching the tiny testcase I used for experimentation.

 - Chris


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

Chris Papademetrious
 

Hi fellow DITA users,

We are exploring Oxygen's WebHelp Responsive transformation, so I am exploring DITA-OT chunking to understand how to control the help structure.

I have multiple <bookmap> files referenced from a top-level <map>:

<map>
    <title>Online Help</title>
    <mapref href="book1.ditamap"/>
    <mapref href="book2.ditamap"/>
</map>

When I publish this (as WebHelp or as plain html5), the <bookmap> levels evaporate and I get a flat TOC of all book chapters:

  • Chapter 1
    • ...topics...
  • Chapter 2
    • ...topics...
  • Chapter 1
    • ...topics...
  • Chapter 2
    • ...topics...

But what I need is for each book to provide its own navigation level derived from its book title:

  • Book 1 Title
    • Chapter 1
      • ...topics...
    • Chapter 2
      • ...topics...
  • Book 2 Title
    • Chapter 1
      • ...topics...
    • Chapter 2
      • ...topics...

Wrapping each <mapref> in a <topichead> creates a level, but that approach doesn't inherit the book title. (Our books are conditional and often have conditional text, references to variables *within* the book scope, etc.).

I looked at the @chunk attribute documentation and experimented, and:

  • The to-navigation value sounds like what I need, but it is deprecated.
  • The to-content value did create a TOC level named after the book (hooray!), but proceeded to collapse the entire book's contents into a single flat topic (boo!).
  • Other values had no effect when applied to the <mapref> element. (Values set on a <bookmap> apply a policy to the entire map, which felt too intrusive to try.)

Books are big, important things. Hopefully there's a way to do this!

 - Chris


Re: Anyone Using Elasticsearch to Index DITA Content?

ekimber@contrext.com
 

I have created the GitHub project https://github.com/dita-community/org.dita-community.elastic as a place to capture my experimentation with using Elasticsearch to store and query DITA content.

 

It’s super minimal at the moment—I’m mostly using it to drive my learning of Elasticsearch by giving me a data set I understand.

 

At the moment there’s just one very small XSLT transform intended to be run against the output of the built-in Open Toolkit normalization transform (transtype “dita”). The transform generates a JSON file for the input file where each element is represented by a separate JSON “document” (in Elasticsearch terms), where each document captures the XML and DITA details, as well as the parentage of each non-root element, and the element’s full text (including the text of any subelements—this lets you quickly find both leaf and ancestor elements that that contain given text {writing this just now I think I need to capture the children elements of each non-leaf element}).

 

This is all very much “as is” and I make no guarantee I’ll do anything more with it after next week but it’s there and maybe it will be useful.

 

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: Thursday, June 10, 2021 at 4:46 PM
To: <main@dita-users.groups.io>
Subject: Re: [dita-users] Anyone Using Elasticsearch to Index DITA Content?

 

That sounds very interesting. I'll take a look at that docs-bulk.html link.

 

Cheers,

 

E.

 

--

Eliot Kimber

 

 

On 6/10/21, 10:44 AM, "Toshihiko Makita" <main@dita-users.groups.io on behalf of tmakita@...> wrote:

 

    I have experienced to develop DITA full test search pilot project last year via AWS Elasticsearch before the conflict between AWS and elastic.co.

    This search is integrated into the DITA to HTML (or .php) publishing result. Following are several things I have done:

 

    * Use "curl" (or "awscurl") to generate index in AWS Elastic search.

    * Convert DITA map & topics into JSON and execute "bulk" operation.

    * Develop PHP program that accepts search request from client browser and return the search result from Elasticsearch as JSON.

    * The JSON search results are edited by JavaScript and displayed in the browser.

    * By clicking the search result, a user can reach the target  Web page.

 

    It was very exciting experience because I must learn about AWS operations and develop PHP and JavaScript (TypeScript) programs which I haven't ever knew.

    Unfortunately it is still pilot project. However it will be integrated into user Web publishing system in the feature.

 

    --

    /*--------------------------------------------------

     Toshihiko Makita

     Development Group. Antenna House, Inc. Ina Branch

     Web site:

     --------------------------------------------------*/

 

 

 

 

 

 

 

 

 

 

 

 

 


[ann] Version 3.1.0 of the Oxygen Batch Documents Converter add-on has been released! #Oxygen

alin_belu@...
 

Hello,   
 
We are excited to announce that version 3.1.0 of the Oxygen Batch Documents Converter add-on is now available in the Oxygen XML default add-on repository!    
 
Version 3.1.0 of the Oxygen Batch Documents Converter add-on comes with these useful new improvements:   
* Cross-references are now handled properly when converting Word to HTML/DITA. 
* Index entries, footnotes, and endnotes are now handled properly when converting Word to DITA. 
* References to local HTML documents are now automatically updated when converting HTML to DITA. 
* Fixed an issue with HTML to DITA/DocBook conversions where extra new lines were added when converting "pre" elements. 
* Fixed an issue with Excel to DITA conversions that sometimes resulted in table elements with invalid IDs (#51). 
* Fixed an issue with Word/HTML to DITA/DocBook conversions that caused spaces between inline elements to be removed. 
 
To install the add-on, follow these instructions:    
1. Go to Help->Install new add-ons to open an add-on selection dialog box. 
2. Enter or paste https://www.oxygenxml.com/InstData/Addons/default/updateSite.xml in the Show add-ons from field. 
3. Select the Batch Documents Converter add-on and click Next. 
4. Read the end-user license agreement. Then select the I accept all terms of the end-user license agreement option and click Finish. 
5. Restart the application. 
 
For more information, see the details for the Oxygen Batch Documents Converter add-on on GitHub:    
 
We hope you will find this add-on useful and, as always, your feedback is welcomed!    
 
Best regards, 
Alin   

--
Alin Belu
Oxygen XML Editor


Re: Xpath for validating if href in xref element is pointing to <fn> element #XSLT

Chris Papademetrious
 

If you are using Oxygen as your editor, there is a setting to always set @type in new <xref> elements:

<xref href="test.dita#test_overview/fn_5fc" type="fn"/>

You can find this setting in Preferences > DITA > Topics, then enable Type in the Always set values for the following attributes list. We use this setting, and it makes this sort of processing and validation much easier.

Otherwise, maybe you could (1) write a function to extract the ID from an @href, (2) put all <fn> ID values in the current document in a variable, and (3) write something like

<xsl:variable name="fnXCount" select="count($prmElement/descendant::*[contains(@class,' topic/xref ')][get_ID(@href) = $all_fn_IDs])"/>

When the '=' operator is given lists, it returns true if there are common items between the lists. In this case, the ID returned by get_ID() would be a list of one string value.

(Disclaimer: I am not an XSLT expert myself.)

 - Chris


Re: Xpath for validating if href in xref element is pointing to <fn> element #XSLT

Shaurabh
 

Hi Chris,

I am not trying to validate if all footnotes are used or not. I am just trying to find the count for all xrefs which are targeting to footnotes. As i said earlier, I am able to find the count for all xrefs being used inside <tgroup> irrespective of their target element using below xpath-

<xsl:variable name="fnXCount" select="count($prmElement/descendant::*[contains(@class,' topic/xref ')][@href])"/>

  But i want the total count for only those xrefs which are pointing to <fn> element.


Thanks,
Shaurabh


Re: Xpath for validating if href in xref element is pointing to <fn> element #XSLT

Chris Papademetrious
 

Hi Shaurabh,

Because <fn> elements with IDs don't generate content themselves, I keep them self-contained inside the table that references them. This way, they move along with the table if I copy/move/conref it to a different topic.

Are you trying to validate that all footnotes are used, and none have gone silently unused?

Is this check going into a Schematron file, or is it being put into some other XSLT file?

 - Chris


Xpath for validating if href in xref element is pointing to <fn> element #XSLT

Shaurabh
 

I have a test.dita file which consists of a table element as shown below. As you can see few cells inside <tgroup> element consists of xref element which are targeting to <fn> element. I want to have total count of <xref> elements targeting to <fn> element.
I am able to have the count of xref elements having href attribute using below xpath-

<xsl:variable name="prmElement" select="."/>
<xsl:variable name="fnXCount" select="count($prmElement/descendant::*[contains(@class,' topic/xref ')][@href])"/>

In addition to above, I want to validate if @href is pointing to <fn> element.  Please help me to improve above xpath for fn count validation.
test.dita

<topic id="test_overview">
    <title id="title_id">Test Title</title>
    <body>
        <table>
            <title>My table</title>
            <desc>
                <p>
                    <fn id="fn_5fc">My first footnote.</fn>
                </p>
                <p>
                    <fn id="fn_vfc">My second footnote.</fn>
                </p>
            </desc>
            <tgroup cols="3">
                <colspec colname="col1" colwidth="1.01*" colnum="1"/>
                <colspec colname="col4" colwidth="1.01*" colnum="2"/>
                <colspec colname="col5" colwidth="1*" colnum="3"/>
                <thead>
                    <row>
                        <entry>Col1</entry>
                        <entry>Col2</entry>
                        <entry>Col3</entry>
                    </row>
                </thead>
                <tbody>
                    <row>
                        <entry align="center">Cell <xref
                                href="test.dita#test_overview/fn_5fc"
                            />
                        </entry>
                        <entry align="center">Cell <xref
                                href="test.dita#test_overview/fn_5fc"
                            />
                        </entry>
                        <entry align="center">Cell <xref
                                href="test.dita#test_overview/fn_vfc"
                            />
                        </entry>
                    </row>
                </tbody>
            </tgroup>
        </table>
    </body>
</topic>
 


Regards,
Shaurabh


Re: java.lang.OutOfMemoryError: GC overhead limit exceeded

Radu Coravu
 

Hi Scott,

Looks like an out of memory error, if you are using the DITA OT from the command line there is some documentation about this in the DITA OT docs:

https://www.dita-ot.org/dev/topics/other-errors.html#troubleshooting__out-of-memory-error

https://www.dita-ot.org/dev/topics/increasing-the-jvm.html

Regards,

Radu

Radu Coravu
Oxygen XML Editor
On 6/13/21 01:35, scott ashmead via groups.io wrote:

Hi friends,

Has anyone received and fix this error while generating a PDF using DITA-OT 3.6.1?
I think this is related to Garbage Cleanup, but I don't know why I would get this while generating a 350 page PDF. Is that too large?

transformation failed. C:\dita-ot-3.6.1\plugins\org.dita.pdf2.fop\build_fop.xml:145: java.lang.OutOfMemoryError: GC overhead limit exceeded

Thank you,
Scott

  


Re: Links that are both local and cross-deliverable in shared topics

ekimber@contrext.com
 

Cross-deliverable links are a challenge for a number of reasons, but chief among them is the potential configuration complexity inherent in the fact that a single set of root maps can produce many different deliverables of different types and with different configurations. If there's an exact one-to-one mapping from source root maps to deliverables the problem is easy, but as soon as you can have two or more deliverables from a single root map, the problem gets much more challenging.

The DITA *source* markup makes it possible to unambiguously create a reference to any element in any topic in the context of a specific root map. This is necessary but not sufficient.

When you produce a given a deliverable from a root map you have to be able to control how the source-to-source links translate to deliverable-to-deliverable links when there are multiple possible deliverables for a given target root map.

That's exactly the scenario you described with the use of filtering applied to root maps to produce multiple deliverables from a single root map reflecting different filtering conditions.

Thus there has to be some way to configure the deliverable production process so that sets of related deliverables are produced correctly, i.e., for a set of inter-linked root maps, some way to ensure that the same filtering conditions (or the *correct* set of filtering conditions) is applied to a set of deliverable production processes so that the resulting deliverables are correctly linked to each other. This requires some sort of deliverable production project manager that gives you a way to configure the deliverable generation details.

For example, if you need to produce a set of interlinked deliverables that all reflect macOS, you need a way to specify not just the filtering but the deliverable URIs *as published* to that the links will be to the right place.

Using different wrapper maps that have different ditaval refs and result in different deliverable names is one way to do that and might be the easiest but it seems like that could quickly get either unwieldy or confusing or just impractical.

DITA OT's new project facility seems like at least a start for this kind of production processing configuration manager but more is probably required to fully coordinate the production of multiple interlinked deliverables that have different input parameters (different filtering conditions, etc.) and different result details (different publishing locations for the deliverables).

It sounds like you're able to impose simplifying assumptions that make the problem easier to solve in your environment, which is good--keeping it as simple as you can and still meeting requirements is always a good idea.

A challenge for a tool like DITA OT is that a more general solution starts to become pretty complex pretty quickly, which makes it less likely anyone will take a stab at implementing it...

Cheers,

E.

--
Eliot Kimber
http://contrext.com


On 6/13/21, 8:29 PM, "Chris Papademetrious" <main@dita-users.groups.io on behalf of chrispitude@gmail.com> wrote:

Hi Eliot,

The bug with Oxygen is when option #2 is used ((1) the current book A has its own local scope A, and (2) it references a peer book B with scope B, and (3) you drag-and-drop a topic from map B into a topic in map A to create a cross-book link), the link is incorrectly created as "B.B.topic1" instead of "B.topic1". SyncroSoft has confirmed it's a bug.

It would be hard to separate writers from their maps here. Each technical writer is assigned 1-3 products, and they own the user guides and reference manuals for those products. Because the map controls both PDF and OLH content delivery, the writers work with maps as tightly as they do the topics.

So, I try to empower the writers to manage their own maps by


* Keeping map structures and rules as simple as possible
* Using Schematron rules to keep writers on the right path
* Relying on Oxygen to make things like cross-book link creation easy

So far, this combination has allowed us to be successful without the need for map/key managers and such, and without the writers having to get too much into the technical DITA stuff. For the most part, it's just writing and Oxygen GUI stuff. And I'll ride that for as long as I can! (And quite frankly, we're not resourced for anything more.)

We're already using peer-book scopes, so local scopes should be a straightforward conceptual extension for the writers to learn. Once this double-scoping bug is fixed in Oxygen, we should be in good shape for creating cross-book links in topics reused across books, which is really cool.

The next hurdle is creating cross-book links between books that use profiling conditions to publish one map to multiple deliverables. Writers want the ability to cross-link to specific conditional versions of books, and also to cross-link automatically between same-condition books. I've had some success prototyping this with a "wrapper map," which is a simple <map> that has only a <ditavalref> and a <mapref> to a full <bookmap>. I plan to share more about that here when the loose ends are ironed out.

The tip about books being able to provide overriding key definitions is a good one - thank you!

- Chris


Re: Links that are both local and cross-deliverable in shared topics

Chris Papademetrious
 

Hi Eliot,

The bug with Oxygen is when option #2 is used ((1) the current book A has its own local scope A, and (2) it references a peer book B with scope B, and (3) you drag-and-drop a topic from map B into a topic in map A to create a cross-book link), the link is incorrectly created as "B.B.topic1" instead of "B.topic1". SyncroSoft has confirmed it's a bug.

It would be hard to separate writers from their maps here. Each technical writer is assigned 1-3 products, and they own the user guides and reference manuals for those products. Because the map controls both PDF and OLH content delivery, the writers work with maps as tightly as they do the topics.

So, I try to empower the writers to manage their own maps by

  • Keeping map structures and rules as simple as possible
  • Using Schematron rules to keep writers on the right path
  • Relying on Oxygen to make things like cross-book link creation easy
So far, this combination has allowed us to be successful without the need for map/key managers and such, and without the writers having to get too much into the technical DITA stuff. For the most part, it's just writing and Oxygen GUI stuff. And I'll ride that for as long as I can! (And quite frankly, we're not resourced for anything more.)

We're already using peer-book scopes, so local scopes should be a straightforward conceptual extension for the writers to learn. Once this double-scoping bug is fixed in Oxygen, we should be in good shape for creating cross-book links in topics reused across books, which is really cool.

The next hurdle is creating cross-book links between books that use profiling conditions to publish one map to multiple deliverables. Writers want the ability to cross-link to specific conditional versions of books, and also to cross-link automatically between same-condition books. I've had some success prototyping this with a "wrapper map," which is a simple <map> that has only a <ditavalref> and a <mapref> to a full <bookmap>. I plan to share more about that here when the loose ends are ironed out.

The tip about books being able to provide overriding key definitions is a good one - thank you!

 - Chris


preserve submap metadata in merged file #pdf #PDF

Leigh White
 

Hi all,

I'm following up on an old thread that doesn't seem to have reached a conclusion, or at least not a conclusion that I can understand. In short, I am trying to preserve the metadata of submaps in a bookmap. I'm using OT 3.5.4, PDF. I have tried adding preprocess.clean-map-check.skip=true to my build.properties file and to configuration.properties. I have also added it to my plugin's plugin.xml file. None of these seems to have any effect: the submaps' metadata does not appear in the merged file. Was that even the intent?

The thread I am referring to (https://github.com/dita-ot/dita-ot/pull/2739 and https://dita-ot.slack.com/archives/C02DW51E3/p1620311367058800) is about 4 years old, and a lot has changed since then.

I do see mode="preserve-submap-title-and-topicmeta" in maprefImpl.xsl and it appears to be default behavior but that is not what I am seeing. The metadata I am trying to preserve is straightforward topicmeta metadata like so:

<topicmeta>
    <critdates>
      <created date="1999-08-11"/>
      <revised modified="2019-10-25"/>
    </critdates>
    <permissions view="internal"/>
    <metadata>
      <audience type="user"/>
      <prodinfo>
        <prodname>Widget</prodname>
        <brand>Pro3</brand>
      </prodinfo>
    </metadata>
    <category>XYZ</category>
    <othermeta name="product-code" content="wid-1234"/>
    <othermeta name="docnumber" content="WIDP34567"/>
    <othermeta name="doctype" content="User Guide"/>
    ...

So...is there a straightforward (or even a non straightforward) way to preserve this metadata in the merged file?

Thanks,
Leigh


java.lang.OutOfMemoryError: GC overhead limit exceeded

scott ashmead
 

Hi friends,

Has anyone received and fix this error while generating a PDF using DITA-OT 3.6.1?
I think this is related to Garbage Cleanup, but I don't know why I would get this while generating a 350 page PDF. Is that too large?

transformation failed. C:\dita-ot-3.6.1\plugins\org.dita.pdf2.fop\build_fop.xml:145: java.lang.OutOfMemoryError: GC overhead limit exceeded

Thank you,
Scott


Re: Word2Dita?

Leigh White
 

Hi all...I'd like to clarify that IXIASOFT has acquired Stilo's AuthorBridge product, but we have not acquired Stilo the company. In case anyone was curious. :-) https://www.ixiasoft.com/ixiasoft-announces-authorbridge-acquisition/.

Best,
Leigh


Re: Word2Dita?

ekimber@contrext.com
 

I concur--if you have easy access to Stilo it might be the fastest route to DITA from your Word doc.

Cheers,

E.

--
Eliot Kimber
http://contrext.com


On 6/10/21, 7:49 PM, "teamwis" <main@dita-users.groups.io on behalf of dfanster@gmail.com> wrote:

To the best of my knowledge, you might want to have Stilo
International do the work for you because Ixiasoft has acquired Stilo
early on, your company should have no problem using Stilo to do the
conversion, depending on your budgets. Go to
https://www.stilo.com/migrate-dita/ for more info.

Cheers
Ray

On 6/10/21, Nancy Roberts <nanr93@gmail.com> wrote:
> Hi all,
>
> For the first time since 2009, I need to convert a Word doc to DITA that is
> too big to be done manually. What is the Word2Dita plugin? What does it plug
> in to? The OT? My company uses the Ixiasoft CMS, if that makes a difference.
> Any advice is much appreciated.
>
> Thanks,
> Nancy
>
>
>
>
>
>


--
Keep an Exacting Eye for Detail


Re: Word2Dita?

teamwis
 

To the best of my knowledge, you might want to have Stilo
International do the work for you because Ixiasoft has acquired Stilo
early on, your company should have no problem using Stilo to do the
conversion, depending on your budgets. Go to
https://www.stilo.com/migrate-dita/ for more info.

Cheers
Ray

On 6/10/21, Nancy Roberts <nanr93@gmail.com> wrote:
Hi all,

For the first time since 2009, I need to convert a Word doc to DITA that is
too big to be done manually. What is the Word2Dita plugin? What does it plug
in to? The OT? My company uses the Ixiasoft CMS, if that makes a difference.
Any advice is much appreciated.

Thanks,
Nancy





--
Keep an Exacting Eye for Detail

301 - 320 of 46584