Oxygen XML Forum

Hi Chris! Sorry for my late response and thanks a lot for your feedback. I'm still surprised that out-of-the-box any XHTML output doesn't include in the index.html the metadata declarations made in a topicmeta or bookmeta. I also noticed this behavior recently with change-histolrylist element and ot...

That is a pretty good question, Radu. Actually, I pushed content to a publishing delivery platform and I noticed extra processing was applied to the content after the DITA-OT processing. Typically, in my case, I've created a plugin that overrides the display of the title and adds additional metadata...

Hello, I am currently in a situation where I need, first, to apply a normalized DITA transformation. Then, with the source created, automatically start a second transformation with the new generated map and applying an HTML5 transtype. Currently, my build.xml takes this form and I just would like to...

Thanks Radu

Thanks Radu! That was very helpful and I succeeded in my task. I declared the following feature extensions in my plugin.xml <feature extension="dita.conductor.html5.param" file="buildHtml5Param.xml"/> <feature extension="dita.conductor.html5.toc.param" file="buildH...

Hello! I have topicrefs in a ditamap using outputclass with specific values. I'm trying to retrieve the value of the outputclass attribute and copy them within the referenced topics. Example with a chunked topic: <html lang="en"> <head> <meta http-equiv="Content-Type" content=&qu...

Hi folks!
I succeeded in matching the class. I had to target the whole class with the + sign:

Code: Select all

 <xsl:when test="@class, '+ topic/pre pr-d/codeblock '">

Hello, everyone! I'm currently trying to write an XSLT that matches a specific outputclass value and depending on the class, I need to display a specific label beforehand. I rely on a temporary output from a DITA concept. Here is a short sample: <?xml version="1.0" encoding="utf-8&quo...

Hello! I'm currently working on a plugin that replaces the values of outputclass attributes for different elements in a dita source. The XSLT itself works as expected when I test it solely, but once I integrate it in my plugin with a feature extension="dita.xsl.html5" and launch an HTML5 t...

Hi Julien! Thanks for your answer. That's exactly what I usually do for my plugins and in this case, I initially assumed the OT processing in the Saas server would provide the concatenated title to the publication. However, it seems their connector uses additional processing, among other things the ...

Hello, I recently stumbled upon a difficulty where I wanted to modify the display of a title to concatenate it with a metadata value. I succeeded in doing it by using a template to override the HTML5 transformation, however it finally seems in my case that my publishing platform resolves the title o...

I eventually found that I could use the template gen-user-panel-title-pfx and succeeded in applying the modification in topic.xsl and map2htmltocImpl.xsl :) <xsl:template name="gen-user-panel-title-pfx"> <xsl:apply-templates select="." mode="gen-user-panel-title-pfx"/> ...

Hello, everyone! I have a bookmap that includes plenty of information in its metadata. For instance, I have prodname or vrm version . In my situation, I would like to adapt the HTML5 output to concatenate the mainbooktitle with the prodname . I analyzed the map2html5-coverImpl.xsl in the plugin org....

Oh, yes, Radu, you are definitely right. However, the reason why I have been looking for this option is that I am forced to make the generation compatible with a script I have no control over. And as for the moment, before giving feedback to the developers who integrated the javascript function into...

Ok, I understand. Thanks for pointing that out. For now, I just changed the nature of the string in the utils xsl. I have a correct rendering of the attribute. Yet, I wonder if there's any way to remove the p attribute class as shown below: <p class=" p ft-expanding-block-link" data-target...

Ok, I'm back with a minor issue. I use the following xsl snippets to manage my custom attribute  <xsl:template name="setdataTargetId"> <xsl:if test="@data-target-id"> <xsl:call-template name="setdataTargetIdattr"> <xsl:with-param name=&qu...

Your help is invaluable and I cannot thank you enough for your support.
I used preprocess2 instead of preprocess and applied my preprocess.branch-filter.skip property.
Everything runs perfectly

Fantastic, Chris!
That solved the problem. Thank you

Sure!
Here it is attached.
I'm curious to see if you'd have the same behavior.

com.gbv.collapse.zip: (9.3 KiB) Downloaded 254 times

Hi again! There's something I don't get though. When I apply the integrator.xml after my changes and check the dita2html-base.xsl file to see if the xsl override file is correctly imported, I noticed the xsl override wasn't precisely targeted. Here is how the path is inserted: <xsl:import xmlns:dita...

Oh that's excellent! Thank you so much Chris for this workaround. I continued working on it yesterday and I understood that I needed to add an extension in my plugin.xml with <feature extension="dita.xsl.xhtml" value="./xsl/collapse.xsl"/> Then, I edited the dita2htmlImpl.xsl to ...

Hi Radu! Here is a quick update. I partially found out the reason for my problem. The situation occurred when I used the plugin online in a CCMS and I noticed that preprocessing with DITA-OT applied the filtering during the preprocessing and before the execution of the plugin that creates an archive...

Hello, I created a plugin to include a custom attribute in my topics. Concretely, I needed to add a data-target-id to a p element. My plugin and the associated dtd are now correctly recognized. image.png However, when publishing a test page, I noticed that the new attribute isn't processed in HTML. ...

This is an excellent tip, Chris! Thank you!

Problem solved!
I used this expression

Code: Select all

xref href="[^"]+.dita"\>

and I deactivated the XML search options.
Thanks for your help

Hi Radu

Thanks for your answer. Unselecting this option didn't help to retrieve the elements.
Even within a topic, it doesn't seem to work although I have one xref element under my eyes.
I'll continue looking if there are other options that could help.

: image.png (190.38 KiB) Viewed 784 times

Hello, I use the following grep command to find xref elements, whatever their reference filenames are. grep -ri 'xref href="[^"]\+"/>' * This works well. However, when I want to use the expression solely in Oxygen, I don't get any results. xref href="[^"]\+"/> image.png...

Thank you, Radu.
Indeed, it worked well with your publication. I recreated the map for my project and it worked. I did a comparison between the two sources and didn't notice any difference. Strange but luckily it is solved

Hi Radu, Indeed, I used an older version of the XSLT and updated it. However, you're right the ditaval should be included. Currently, my map references the ditaval, placed in a subfolder, with a ditavalref as its end: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE map PUBLIC &q...

Hello, I'm currently working on a plugin based on the one created by Radu: https://github.com/oxygenxml/dita-export-map It works well, but I notice that if I include a ditavalref in my map, the exportmap won't include the ditaval file in the archive, and in my case it is really necessary. I think th...

Search found 105 matches

Re: Insert metadata in the <head> for HTML5 files

Re: Automatically start a new transformation after another

Automatically start a new transformation after another

Re: Inconsistent table structure after applying an XSLT on title element

Re: How to transmit an attribute value from a topicref to a topic attribute

How to transmit an attribute value from a topicref to a topic attribute

Re: Can't match the topic/pre class

Can't match the topic/pre class

Inconsistent table structure after applying an XSLT on title element

Re: Apply a transformation in the dita source

Apply a transformation in the dita source

Re: Generate the map title with additional metadata

Generate the map title with additional metadata

Re: Custom attribute not pushed in the XHTML map

Re: Custom attribute not pushed in the XHTML map

Re: Custom attribute not pushed in the XHTML map

Re: Plugin selects all references except a ditavalref

Re: Custom attribute not pushed in the XHTML map

Re: Custom attribute not pushed in the XHTML map

Re: Custom attribute not pushed in the XHTML map

Re: Custom attribute not pushed in the XHTML map

Re: Plugin selects all references except a ditavalref

Custom attribute not pushed in the XHTML map

Re: Regex to match xrefs

Re: Regex to match xrefs

Re: Regex to match xrefs

Regex to match xrefs

Re: Plugin selects all references except a ditavalref

Re: Plugin selects all references except a ditavalref

Plugin selects all references except a ditavalref