Date   

Re: too big bother

Jonathan Hanna
 

Hi Aaron,

You do not have to limit yourself by using a task topic. When I started using DITA, I tried using the Concept, Task, and Reference topics and found they just did not work well for my projects. Instead of using a task topic, you may want to consider using a generic topic. Using a generic topic gives you a lot more freedom. I did not even realize using a generic task topic was an option when I started using DITA!

Best regards,
Jonathan


Re: too big bother

Chris Brand
 

Hi Aaron

I have similar (but not that complex) windows to describe, plus the use cases that come along. When I have set up my documentation concept in the beginning, I also thought about numbered callouts and a reference table. But then I decided against it, as I have to redo the screenshots (tons...) every half year or so and messing with the callouts every time I didn't like.

After some thoughts I came up with this:

  • I "translated" the whole UI into keys. So, each button, tab, title, table, checkbox, etc. got a key with its text.
  • In my "User Guide", I placed the window screenshots in separate "Functional Description" chapters.
  • Below the screenshots I listed and described all the UI elements a user can interact with in tabular form.
  • In the "Use" chapter, I then described the different use cases as tasks and placed a link back to the "Functional Description" chapter.

Separating how something works from procedures is what you should aim for. In a functional description you can describe everything to the last detail, where as in a task, only focus on the important bits.

See the two attached screenshots. Hope it helps.

Greez,
Chris.

Am 12.03.21 um 18:34 schrieb Aaron Mehl via groups.io:

Thanks,
The reason I didn't go for numbered call outs with a table is because throughout the rest of the document my graphics have call outs (arrows and text boxes) and doing this for one or two windows would be inconsistent. But you are right I may have no other choice. I just had a thought, what if I made every section of the window a different task. I could then put a graphic with call outs for only that task. Hmn...
Aaron

On Friday, March 12, 2021, 10:41:01 AM EST, Melissa Kershes <sarala557@...> wrote:


Hi Aaron.

 

The overall goal in this window (I suppose) is to “Edit a scheduled transaction” There are a few ways you can simplify this.

  1. Only document one way of using a control. Most windows users already know that there are multiple ways to do things based on standard controls. Use the most common path to enter the data.
  2. If you want to group things do it by section. So first describe the schedule name box etc. then move onto the Payment Information box.
  3. If you want to do a call out for controls with no label, number the image and then do the call outs in a table below. This will clean the interface of the image and allow for easier translation if that happens. DO NOT use call outs for controls that have labels. The users can read the label.

 

All of this together should significantly shorten your topic.

 

Melissa

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Aaron Mehl via groups.io
Sent: Friday, March 12, 2021 10:30 AM
To: DITA Users Group Moderators <main@dita-users.groups.io>
Subject: [dita-users] too big bother

 

Hi all,

I am just not sure how to author in Dita, large windows in the interface. The rule is for tasks to keep them short. This would mean breaking procedures into separate tasks. The problem I have is that I have some very busy windows in the interface I'm authoring and I would like to keep things in one place if at all possible. That said, I will give an example of a very busy window. I started adding call outs to the graphic, but stopped, since in my opinion it is just way to busy. 

The Dita task doesn't even come close to giving procedural steps for all the parts of the window. I want to K.I.S.S but I am not sure what to do. Maybe a table??

Any help/ideas would be most appreciated,

Aaron

 

So here is an example:

-----------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">

<task id="payment_information">

  <title>Payment Information</title>

  <shortdesc>

    <draft-comment author="aaron">This has to be totally redone and then the graphic with call outs

      needs adding (scheduleNew.png)</draft-comment>

  </shortdesc>

  <taskbody>

    <context>To schedule a salary deposit transaction:</context>

    <steps>

      <step>

        <cmd>Click on <uicontrol>Deposit</uicontrol> in the <uicontrol>Payment

            information</uicontrol> slider. </cmd>

      </step>

      <step>

        <cmd>Choose <term>Direct Deposit </term>as the payment method, from the drop down

          list. </cmd>

        <substeps id="substeps_yv4_nm3_d4b">

          <substep>

            <cmd>In the <uicontrol>Account</uicontrol> combo box, choose the account to deposit your

              salary in.</cmd>

          </substep>

          <substep>

            <cmd>From the <uicontrol>Pay to/from</uicontrol> drop down list choose

                <uicontrol>From</uicontrol>, if it isn't already selected.</cmd>

          </substep>

          <substep>

            <cmd>Type <term>Job</term> in the <uicontrol>payto/from name</uicontrol>field.</cmd>

            <info>If job is already listed, go to the <uicontrol>category</uicontrol> combo box,

              otherwise:</info>

          </substep>

          <substep>

            <cmd> A dialog box opens asking if you want to add this

              payee/receiver.</cmd>

          </substep>

          <substep>

            <cmd> Click <term>Yes</term>.</cmd>

            <stepresult>The new payee job is added to list of payees.</stepresult>

          </substep>

        </substeps>

      </step>

      <step>

        <cmd>Choose <term>Salary</term> in <uicontrol>Category</uicontrol> list.</cmd>

      </step>

      

      <step>

        <cmd>Enter the date you get paid in <uicontrol>Next due date</uicontrol> field, either: </cmd>

        <choices>

          <choice>Type the date.</choice>

          <choice>Use the up and down arrows to select the date.</choice>

          <choice>Click on the calendar icon and select the date.</choice>

        </choices>

      </step>

      <step>

        <cmd>Enter the amount you get paid in the <uicontrol>Amount</uicontrol> field, either:</cmd>

        <choices>

          <choice>Type in the amount</choice>

          <choice>Click on the calculator icon and enter the amount. </choice>

        </choices>

      </step>

    </steps>

  </taskbody>

</task>

----------------------------------------------------

Then here is the graphic as an attachment:

  


Re: too big bother

Aaron Mehl
 

Thanks,
The reason I didn't go for numbered call outs with a table is because throughout the rest of the document my graphics have call outs (arrows and text boxes) and doing this for one or two windows would be inconsistent. But you are right I may have no other choice. I just had a thought, what if I made every section of the window a different task. I could then put a graphic with call outs for only that task. Hmn...
Aaron

On Friday, March 12, 2021, 10:41:01 AM EST, Melissa Kershes <sarala557@...> wrote:


Hi Aaron.

 

The overall goal in this window (I suppose) is to “Edit a scheduled transaction” There are a few ways you can simplify this.

  1. Only document one way of using a control. Most windows users already know that there are multiple ways to do things based on standard controls. Use the most common path to enter the data.
  2. If you want to group things do it by section. So first describe the schedule name box etc. then move onto the Payment Information box.
  3. If you want to do a call out for controls with no label, number the image and then do the call outs in a table below. This will clean the interface of the image and allow for easier translation if that happens. DO NOT use call outs for controls that have labels. The users can read the label.

 

All of this together should significantly shorten your topic.

 

Melissa

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Aaron Mehl via groups.io
Sent: Friday, March 12, 2021 10:30 AM
To: DITA Users Group Moderators <main@dita-users.groups.io>
Subject: [dita-users] too big bother

 

Hi all,

I am just not sure how to author in Dita, large windows in the interface. The rule is for tasks to keep them short. This would mean breaking procedures into separate tasks. The problem I have is that I have some very busy windows in the interface I'm authoring and I would like to keep things in one place if at all possible. That said, I will give an example of a very busy window. I started adding call outs to the graphic, but stopped, since in my opinion it is just way to busy. 

The Dita task doesn't even come close to giving procedural steps for all the parts of the window. I want to K.I.S.S but I am not sure what to do. Maybe a table??

Any help/ideas would be most appreciated,

Aaron

 

So here is an example:

-----------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">

<task id="payment_information">

  <title>Payment Information</title>

  <shortdesc>

    <draft-comment author="aaron">This has to be totally redone and then the graphic with call outs

      needs adding (scheduleNew.png)</draft-comment>

  </shortdesc>

  <taskbody>

    <context>To schedule a salary deposit transaction:</context>

    <steps>

      <step>

        <cmd>Click on <uicontrol>Deposit</uicontrol> in the <uicontrol>Payment

            information</uicontrol> slider. </cmd>

      </step>

      <step>

        <cmd>Choose <term>Direct Deposit </term>as the payment method, from the drop down

          list. </cmd>

        <substeps id="substeps_yv4_nm3_d4b">

          <substep>

            <cmd>In the <uicontrol>Account</uicontrol> combo box, choose the account to deposit your

              salary in.</cmd>

          </substep>

          <substep>

            <cmd>From the <uicontrol>Pay to/from</uicontrol> drop down list choose

                <uicontrol>From</uicontrol>, if it isn't already selected.</cmd>

          </substep>

          <substep>

            <cmd>Type <term>Job</term> in the <uicontrol>payto/from name</uicontrol>field.</cmd>

            <info>If job is already listed, go to the <uicontrol>category</uicontrol> combo box,

              otherwise:</info>

          </substep>

          <substep>

            <cmd> A dialog box opens asking if you want to add this

              payee/receiver.</cmd>

          </substep>

          <substep>

            <cmd> Click <term>Yes</term>.</cmd>

            <stepresult>The new payee job is added to list of payees.</stepresult>

          </substep>

        </substeps>

      </step>

      <step>

        <cmd>Choose <term>Salary</term> in <uicontrol>Category</uicontrol> list.</cmd>

      </step>

      

      <step>

        <cmd>Enter the date you get paid in <uicontrol>Next due date</uicontrol> field, either: </cmd>

        <choices>

          <choice>Type the date.</choice>

          <choice>Use the up and down arrows to select the date.</choice>

          <choice>Click on the calendar icon and select the date.</choice>

        </choices>

      </step>

      <step>

        <cmd>Enter the amount you get paid in the <uicontrol>Amount</uicontrol> field, either:</cmd>

        <choices>

          <choice>Type in the amount</choice>

          <choice>Click on the calculator icon and enter the amount. </choice>

        </choices>

      </step>

    </steps>

  </taskbody>

</task>

----------------------------------------------------

Then here is the graphic as an attachment:

  


Re: too big bother

Melissa Kershes
 

Hi Aaron.

 

The overall goal in this window (I suppose) is to “Edit a scheduled transaction” There are a few ways you can simplify this.

  1. Only document one way of using a control. Most windows users already know that there are multiple ways to do things based on standard controls. Use the most common path to enter the data.
  2. If you want to group things do it by section. So first describe the schedule name box etc. then move onto the Payment Information box.
  3. If you want to do a call out for controls with no label, number the image and then do the call outs in a table below. This will clean the interface of the image and allow for easier translation if that happens. DO NOT use call outs for controls that have labels. The users can read the label.

 

All of this together should significantly shorten your topic.

 

Melissa

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Aaron Mehl via groups.io
Sent: Friday, March 12, 2021 10:30 AM
To: DITA Users Group Moderators <main@dita-users.groups.io>
Subject: [dita-users] too big bother

 

Hi all,

I am just not sure how to author in Dita, large windows in the interface. The rule is for tasks to keep them short. This would mean breaking procedures into separate tasks. The problem I have is that I have some very busy windows in the interface I'm authoring and I would like to keep things in one place if at all possible. That said, I will give an example of a very busy window. I started adding call outs to the graphic, but stopped, since in my opinion it is just way to busy. 

The Dita task doesn't even come close to giving procedural steps for all the parts of the window. I want to K.I.S.S but I am not sure what to do. Maybe a table??

Any help/ideas would be most appreciated,

Aaron

 

So here is an example:

-----------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">

<task id="payment_information">

  <title>Payment Information</title>

  <shortdesc>

    <draft-comment author="aaron">This has to be totally redone and then the graphic with call outs

      needs adding (scheduleNew.png)</draft-comment>

  </shortdesc>

  <taskbody>

    <context>To schedule a salary deposit transaction:</context>

    <steps>

      <step>

        <cmd>Click on <uicontrol>Deposit</uicontrol> in the <uicontrol>Payment

            information</uicontrol> slider. </cmd>

      </step>

      <step>

        <cmd>Choose <term>Direct Deposit </term>as the payment method, from the drop down

          list. </cmd>

        <substeps id="substeps_yv4_nm3_d4b">

          <substep>

            <cmd>In the <uicontrol>Account</uicontrol> combo box, choose the account to deposit your

              salary in.</cmd>

          </substep>

          <substep>

            <cmd>From the <uicontrol>Pay to/from</uicontrol> drop down list choose

                <uicontrol>From</uicontrol>, if it isn't already selected.</cmd>

          </substep>

          <substep>

            <cmd>Type <term>Job</term> in the <uicontrol>payto/from name</uicontrol>field.</cmd>

            <info>If job is already listed, go to the <uicontrol>category</uicontrol> combo box,

              otherwise:</info>

          </substep>

          <substep>

            <cmd> A dialog box opens asking if you want to add this

              payee/receiver.</cmd>

          </substep>

          <substep>

            <cmd> Click <term>Yes</term>.</cmd>

            <stepresult>The new payee job is added to list of payees.</stepresult>

          </substep>

        </substeps>

      </step>

      <step>

        <cmd>Choose <term>Salary</term> in <uicontrol>Category</uicontrol> list.</cmd>

      </step>

      

      <step>

        <cmd>Enter the date you get paid in <uicontrol>Next due date</uicontrol> field, either: </cmd>

        <choices>

          <choice>Type the date.</choice>

          <choice>Use the up and down arrows to select the date.</choice>

          <choice>Click on the calendar icon and select the date.</choice>

        </choices>

      </step>

      <step>

        <cmd>Enter the amount you get paid in the <uicontrol>Amount</uicontrol> field, either:</cmd>

        <choices>

          <choice>Type in the amount</choice>

          <choice>Click on the calculator icon and enter the amount. </choice>

        </choices>

      </step>

    </steps>

  </taskbody>

</task>

----------------------------------------------------

Then here is the graphic as an attachment:

  


too big bother

Aaron Mehl
 

Hi all,
I am just not sure how to author in Dita, large windows in the interface. The rule is for tasks to keep them short. This would mean breaking procedures into separate tasks. The problem I have is that I have some very busy windows in the interface I'm authoring and I would like to keep things in one place if at all possible. That said, I will give an example of a very busy window. I started adding call outs to the graphic, but stopped, since in my opinion it is just way to busy. 
The Dita task doesn't even come close to giving procedural steps for all the parts of the window. I want to K.I.S.S but I am not sure what to do. Maybe a table??
Any help/ideas would be most appreciated,
Aaron
 
So here is an example:
-----------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
<task id="payment_information">
  <title>Payment Information</title>
  <shortdesc>
    <draft-comment author="aaron">This has to be totally redone and then the graphic with call outs
      needs adding (scheduleNew.png)</draft-comment>
  </shortdesc>
  <taskbody>
    <context>To schedule a salary deposit transaction:</context>
    <steps>
      <step>
        <cmd>Click on <uicontrol>Deposit</uicontrol> in the <uicontrol>Payment
            information</uicontrol> slider. </cmd>
      </step>
      <step>
        <cmd>Choose <term>Direct Deposit </term>as the payment method, from the drop down
          list. </cmd>
        <substeps id="substeps_yv4_nm3_d4b">
          <substep>
            <cmd>In the <uicontrol>Account</uicontrol> combo box, choose the account to deposit your
              salary in.</cmd>
          </substep>
          <substep>
            <cmd>From the <uicontrol>Pay to/from</uicontrol> drop down list choose
                <uicontrol>From</uicontrol>, if it isn't already selected.</cmd>
          </substep>
          <substep>
            <cmd>Type <term>Job</term> in the <uicontrol>payto/from name</uicontrol>field.</cmd>
            <info>If job is already listed, go to the <uicontrol>category</uicontrol> combo box,
              otherwise:</info>
          </substep>
          <substep>
            <cmd> A dialog box opens asking if you want to add this
              payee/receiver.</cmd>
          </substep>
          <substep>
            <cmd> Click <term>Yes</term>.</cmd>
            <stepresult>The new payee job is added to list of payees.</stepresult>
          </substep>
        </substeps>
      </step>
      <step>
        <cmd>Choose <term>Salary</term> in <uicontrol>Category</uicontrol> list.</cmd>
      </step>
      
      <step>
        <cmd>Enter the date you get paid in <uicontrol>Next due date</uicontrol> field, either: </cmd>
        <choices>
          <choice>Type the date.</choice>
          <choice>Use the up and down arrows to select the date.</choice>
          <choice>Click on the calendar icon and select the date.</choice>
        </choices>
      </step>
      <step>
        <cmd>Enter the amount you get paid in the <uicontrol>Amount</uicontrol> field, either:</cmd>
        <choices>
          <choice>Type in the amount</choice>
          <choice>Click on the calculator icon and enter the amount. </choice>
        </choices>
      </step>
    </steps>
  </taskbody>
</task>
----------------------------------------------------
Then here is the graphic as an attachment:
  


Re: XSLT CALS to HTML5

Don Day
 

For what it's worth, this code and the discussion that follows has a reasonably capable CALS-to-HTML conversion. There are no elements in tables that are HTML5-specific that I am aware of, so this should be compatible with HTML5 content in general. The transform generates CSS classes that create borders for specific (t)op, (b)ottom, (l)eft, and (r)ight cell borders in order to avoid double borders on adjacent cells and rows. It seems to handle column calculations sensibly for resizable HTML rendering.

https://www.oxygenxml.com/archives/xsl-list/200505/msg01081.html

In my own application, to make the table presentation more like that of fig and simpletable, I added a wrapping div to encapsulate the title and description pulled outside of the usual CALS table structure.

--
Don Day       

On 3/9/2021 7:28 PM, scott ashmead via groups.io wrote:
Hi,

Does anyone have a reliable CALS to HTML5 XSLT transform that they can send me or point me to?
I've tried two sets of XSLT code for CALS table processing and they both have bugs.

Thank you for your help!

Scott



Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



Re: Group reltable Links by Topic Type #reltable

@l3arn4life
 

Thank you Radu for your reply. I admittedly don't know much about overriding templates using XSLT extension points but will look into it after my vacation.

Regards,
Ed


AEM + XML and version control

Kristen James Eberlein
 

I would be very interested in hearing from folks with existing AEM + XML implementations.

What practices are you using to best implement version control, for example:

  • When do authors create new versions of topics and maps? Does your implementation have conventions for what the "comments for new versions" include?
  • When are baselines created and edited? How many baselines exist? What are the conventions for naming baselines?
  • Have you implemented any custom workflows, for example, to force the creation of new topic when an author attempts to edit a topic in the "Done" document state?
  • Have you automated document state changes?

Thanks in advance for taking time to communicate about this.

--
Best,
Kris

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



Re: Group reltable Links by Topic Type #reltable

Radu Pisoi
 

Hi,

I think you are using the WebHelp Responsive transformation. In this case, the title of related links section is Related information.

An option to change this behavior is to use the com.oxygenxml.webhelp.xsl.dita2webhelp XSLT extension point that allows you to overwrite the whc:webhelp_related_links template. This template is located in the ${DITA-OT-DIR}/plugins/com.oxygenxml.webhelp.responsive/xsl/template/topicComponentsExpander.xsl file and it is used to generate the related links section.

I have registered an entry in our internal issue tracker for a future version to add a parameter that allows you to preserve the default DITA-OT output.

-- 
Regards,
Radu
--
Radu Pisoi
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com


[ann][webinar] What’s New in Oxygen 23.1 - Overview and Panel Discussion #Oxygen

alin_belu@...
 

Hello,
 
To celebrate the release of version 23.1 of the Oxygen XML suite of products, next Wednesday (March 17) you are invited to a special live webinar - “What’s New in Oxygen 23.1 - Overview and Panel Discussion”. 
 
See for yourself how this release builds upon the always expanding suite of our products by joining us for a one-of-a-kind discussion that will allow you to engage with the creative people behind Oxygen XML. Find out first-hand how you can benefit from the newly-implemented features in version 23.1, such as: 
* Concurrent editing and reviewing in Oxygen Content Fusion for streamlining your team's collaboration process. 
* The ability to ignore validation problems using Quick Fix actions to filter errors and warnings wherever they are presented. 
* The new Block-Level Comments functionality in Oxygen Feedback allows your users to add and manage comments contextually at a specific location within the WebHelp page. 
* Oxygen Styles Basket, the free web-based visual tool that helps you fine-tune the CSS file that is used to customize PDF or WebHelp output by picking and mixing aspects from galleries. 
* And much more. 
 
The panel will bring together George Bina, Alexandru Jitianu, Octavian Nadolu, Cristi Talau, Alin Balasa, and Julien Lacour. 
 
This is a free event and you can register at http://www.oxygenxml.com/evs2021-7.html 
 
Make sure to check the full list of our upcoming events: https://www.oxygenxml.com/events_programme.html 
 
Best regards,
Alin

--
Alin Belu
Oxygen XML Editor


Group reltable Links by Topic Type #reltable

@l3arn4life
 

Hello there fellow DITA-warriors,

we have successfully updated our system to DOT 3.5.1, running on the latest version from Oxygen. However, we have now come across a peculiarity we have not yet been able to resolve: tasks and concepts linked via relationship table are grouped under "related information" in the output. References from reltables, strangely, are put under a separate reference heading. Related links used to be grouped by topic type under their respective headings. We liked that and would like to have it back … I think we're basically looking for the reversal of what is being asked in this oxygen-forum-discussion.
So far we tried to delete the line containing <str name="Related information"> from all relevant localisation files, to no avail. Renaming the entry would still result in tasks and concepts being grouped under the same heading.
Any and all help is much appreciated!

Regards,
Ed


Re: Keyrefs no longer resolved within conrefs #keys #conref

Nicholas Mucks
 

Hi Christina,
Is your conref topic references as resource-only in your map? Map-first preprocessing will only process keys in topics referenced in the ditamap, so if you used a conref from a topic not in your ditamap then the conref will resolve but none of the keys in that conref will exist in your keyspace.

Take care,
- Nick

Sent from mobile

On Mar 10, 2021, at 3:06 AM, Radu Coravu <radu_coravu@...> wrote:



Hi Christina,

I'm not sure why this takes so long. Can you reproduce the large delay on your side?

If your DITA topics and maps are RNG based, there is a DITA OT issue for adding extra caching for RNG-based projects:

https://github.com/dita-ot/dita-ot/issues/3661

In Oxygen 23.1 which we released about a week ago the bundled DITA OT has this caching enabled and the publishing times for RNG-based projects should take about 2 times less. Our Oxygen 23.1 publishing engine based on the DITA OT (DITA-OT + our custom plugins and patches) should also have this caching enabled:

https://www.oxygenxml.com/publishing_engine.html

Regards,

Radu

Radu Coravu
Oxygen XML Editor
On 3/10/21 12:59, stinakab via groups.io wrote:

Following up on this topic.

Since this issue seems to be related to some of the issues on Github: https://github.com/dita-ot/dita-ot/issues?q=is%3Aissue+is%3Aopen+preprocess2,
I have decided to continue using preprocess instead of preprocess2 and add all the conrefed topics to our projects and use them as resource-only.
However, now all our projects happen to run so much slower on our build server. For some large projects, this can take up to 50 minutes longer, which is a bit unexpected.
Could it be that I have forgotten to add a setting somewhere that leads to a slowed down process?
The only things that I've noticed when comparing the old and the new logs is the following:

preprocess.init:
     [echo] *****************************************************************
     [echo] * input = d:\P1\re\274401104\b\projects\en\_my_project.ditamap
     [echo] * resources = ${args.resources}
     [echo] *****************************************************************

I don't know about this new args.resources parameter. What does it do? The DITA OT documentation tells me the following: "Specifies resource files." It would be great to know how to work with this parameter. Could somebody explain this to me, please?
Then I'm missing the following:
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\canditopics.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\conref.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\conreftargets.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\copytosource.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\fullditamap.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\fullditamapandtopic.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\fullditatopic.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\hrefditatopic.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\hreftargets.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\html.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\image.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\outditafiles.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\resourceonly.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\resourceonly.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\subjectscheme.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\subtargets.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\user.input.file.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl

Has this been moved to the JAVA code? Or do I just have to re-add this to the respective targets in the build-preprocess.xml?

And respectively, also the following is missing:
conrefpush:
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\conref.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl

I would be happy if somebody could help me out with this.

Thanks,
Christina









implement commonvariables.xsl in OT 2.5.4? #DITA-OT

Leigh White
 

Hi all,

I'm trying to implement the very useful commonvariables.xml file in a PDF plugin for OT 2.5.4. I've added that file to [myplugin]\cfg\common\vars folder. I've copied the strings.xml file from org.dita.pdf2\cfg\common\vars to [myplugin]\cfg\common\vars folder. To my copy of strings.xml, I've added the following line as the first in the file: <lang filename="commonvariables.xml" xml:lang=""/>. I've added a commonvariables.xml file to [myplugin]\cfg\common\vars and copied the common variables into it. I've added <feature extension="dita.xsl.strings" file="cfg/common/vars/strings.xml"/> to my [myplugin]\plugin.xml file and re-integrated. None of the variables in commonvariables are being picked up, so it seems there is some other piece of the puzzle. Is this even possible in 2.5.4?

Thanks,
Leigh


Re: XSLT CALS to HTML5

Toshihiko Makita
 

> If you have a time, try the following HTML5 plug-in.

I've noticed that this plug-in does not work DITA-OT 3.5 or later because there are significant changes of files generated in the temporary directory.

The following obsolete list files are no longer generated in the temporary directory: fullditatopic.list
I will work with this problem later.

Regards,

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


Re: XSLT CALS to HTML5

Toshihiko Makita
 

Hi Scott,

Which XSLT code are you tried? Is it DITA-OT bundled HTML5 or XHTML plug-in?
If you have a time, try the following HTML5 plug-in.

https://github.com/AntennaHouse/ah-html5

I have carefully implemented CALS table processing XSLT template based on the experience of DITA to XSL-FO plug-in.
Also any feedback is welcome via GitHub issue tracking.

Regards,

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


 


Re: Keyrefs no longer resolved within conrefs #keys #conref

Radu Coravu
 

Hi Christina,

I'm not sure why this takes so long. Can you reproduce the large delay on your side?

If your DITA topics and maps are RNG based, there is a DITA OT issue for adding extra caching for RNG-based projects:

https://github.com/dita-ot/dita-ot/issues/3661

In Oxygen 23.1 which we released about a week ago the bundled DITA OT has this caching enabled and the publishing times for RNG-based projects should take about 2 times less. Our Oxygen 23.1 publishing engine based on the DITA OT (DITA-OT + our custom plugins and patches) should also have this caching enabled:

https://www.oxygenxml.com/publishing_engine.html

Regards,

Radu

Radu Coravu
Oxygen XML Editor
On 3/10/21 12:59, stinakab via groups.io wrote:

Following up on this topic.

Since this issue seems to be related to some of the issues on Github: https://github.com/dita-ot/dita-ot/issues?q=is%3Aissue+is%3Aopen+preprocess2,
I have decided to continue using preprocess instead of preprocess2 and add all the conrefed topics to our projects and use them as resource-only.
However, now all our projects happen to run so much slower on our build server. For some large projects, this can take up to 50 minutes longer, which is a bit unexpected.
Could it be that I have forgotten to add a setting somewhere that leads to a slowed down process?
The only things that I've noticed when comparing the old and the new logs is the following:

preprocess.init:
     [echo] *****************************************************************
     [echo] * input = d:\P1\re\274401104\b\projects\en\_my_project.ditamap
     [echo] * resources = ${args.resources}
     [echo] *****************************************************************

I don't know about this new args.resources parameter. What does it do? The DITA OT documentation tells me the following: "Specifies resource files." It would be great to know how to work with this parameter. Could somebody explain this to me, please?
Then I'm missing the following:
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\canditopics.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\conref.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\conreftargets.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\copytosource.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\fullditamap.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\fullditamapandtopic.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\fullditatopic.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\hrefditatopic.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\hreftargets.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\html.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\image.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\outditafiles.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\resourceonly.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\resourceonly.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\subjectscheme.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\subtargets.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\user.input.file.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl

Has this been moved to the JAVA code? Or do I just have to re-add this to the respective targets in the build-preprocess.xml?

And respectively, also the following is missing:
conrefpush:
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\conref.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl

I would be happy if somebody could help me out with this.

Thanks,
Christina


  


Re: Keyrefs no longer resolved within conrefs #keys #conref

stinakab
 

Following up on this topic.

Since this issue seems to be related to some of the issues on Github: https://github.com/dita-ot/dita-ot/issues?q=is%3Aissue+is%3Aopen+preprocess2,
I have decided to continue using preprocess instead of preprocess2 and add all the conrefed topics to our projects and use them as resource-only.
However, now all our projects happen to run so much slower on our build server. For some large projects, this can take up to 50 minutes longer, which is a bit unexpected.
Could it be that I have forgotten to add a setting somewhere that leads to a slowed down process?
The only things that I've noticed when comparing the old and the new logs is the following:

preprocess.init:
     [echo] *****************************************************************
     [echo] * input = d:\P1\re\274401104\b\projects\en\_my_project.ditamap
     [echo] * resources = ${args.resources}
     [echo] *****************************************************************

I don't know about this new args.resources parameter. What does it do? The DITA OT documentation tells me the following: "Specifies resource files." It would be great to know how to work with this parameter. Could somebody explain this to me, please?
Then I'm missing the following:
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\canditopics.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\conref.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\conreftargets.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\copytosource.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\fullditamap.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\fullditamapandtopic.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\fullditatopic.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\hrefditatopic.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\hreftargets.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\html.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\image.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\outditafiles.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\resourceonly.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\resourceonly.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\subjectscheme.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\subtargets.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\user.input.file.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl

Has this been moved to the JAVA code? Or do I just have to re-add this to the respective targets in the build-preprocess.xml?

And respectively, also the following is missing:
conrefpush:
[job-helper] Processing d:\P1\re\274400090\b\pdfBuilds\en\temp\.job.xml to d:\P1\re\274400090\b\pdfBuilds\en\temp\conref.list
[job-helper] Loading stylesheet d:\P1\re\274400090\b\xml_framework\framework\DITA-OT\plugins\org.dita.base\xsl\job-helper.xsl

I would be happy if somebody could help me out with this.

Thanks,
Christina


XSLT for CALS to HTM5

scott ashmead
 

Hi,
Does anyone have a reliable XSLT transform for CALS to HTML5?
I've tried to transforms and they both have bugs.

Thank you!
Scott


XSLT CALS to HTML5

scott ashmead
 

Hi,

Does anyone have a reliable CALS to HTML5 XSLT transform that they can send me or point me to?
I've tried two sets of XSLT code for CALS table processing and they both have bugs.

Thank you for your help!

Scott


Re: MathML Rendering for PDF

Toshihiko Makita
 

Hi Bill,

we’re not sure that Antenna House MathML support is sufficient.
If you send me the sample DITA authoring, I can send your the rendering result with the newest AH Formatter release.

Regards,

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

221 - 240 of 46295