dita-ot | DITA Open Toolkit — the open-source publishing engine | Content Management System library

by dita-ot Java Version: 4.0.2 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(5)Vulnerabilities Install Support

kandi X-RAY | dita-ot Summary

dita-ot is a Java library typically used in Web Site, Content Management System applications. dita-ot has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has high support. You can download it from GitHub, Maven.

DITA Open Toolkit — the open-source publishing engine for content authored in the Darwin Information Typing Architecture.

Support

Quality

Security

License

Reuse

Support

dita-ot has a highly active ecosystem.

It has 340 star(s) with 188 fork(s). There are 81 watchers for this library.

It had no major release in the last 12 months.

There are 228 open issues and 2861 have been closed. On average issues are closed in 175 days. There are 25 open pull requests and 0 closed requests.

It has a positive sentiment in the developer community.

The latest version of dita-ot is 4.0.2

Quality

dita-ot has 0 bugs and 0 code smells.

Security

dita-ot has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

dita-ot code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

dita-ot is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

dita-ot releases are available to install and integrate.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

dita-ot saves you 226499 person hours of effort in developing the same functionality from scratch.

It has 224523 lines of code, 3474 functions and 1634 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed dita-ot and discovered the below as its top functions. This is intended to give you an instant insight into dita-ot implemented functionality, and help decide if they suit your requirements.

Handle an end element
Serialize a DOM Node to a SAX stream
Write linktext element
Write alt element
Process an XML start element
Create topicmeta node
Generate output file name
Searches for a specific subtree
Writes the XML to a file
Returns the filters for processing
Compiles the stylesheet
Log a message based on priority
Process a single file
Process an start element
Execute the move links module
Synchronized
Process an XML start tag
Load variable files
Write DITA document to a file
Handle a start element
Performs rewrite
Get processing filters for a given file
Entry point for keyref module
Entry point for merging
Entry point
Process start element

Get all kandi verified functions for this library.

dita-ot Key Features

No Key Features are available at this moment for dita-ot.

dita-ot Examples and Code Snippets

No Code Snippets are available at this moment for dita-ot.

Community Discussions

Trending Discussions on dita-ot

How to apply small-caps to a string via XSL FO

Hide a topic from PDF output at xsl level

How can I add auto generated labels for topic titles in PDF output using DITA-OT?

How can I make DITA catalog.xml work in VS Code?

Can I configure Dita-OT 2.1 to output only the topic.fo file and not the pdf

QUESTION

How to apply small-caps to a string via XSL FO

Asked 2021-Apr-23 at 05:46

I am trying to customize the PDF2 plugin in DITA-OT. I want to apply small caps to the string "Chapter" and chapter number that appear at the start of every chapter.

What I did so far

In my custom plugin, I modified the following the __chapter__frontmatter__name__container attribute-set in the static-content-attr.xsl file to include small-caps :

...

ANSWER

Answered 2021-Feb-05 at 15:34

Your syntax is correct (rather, it will be correct in the result tree). See https://www.w3.org/TR/xsl11/#font-variant

However, FOP does not support font-variant. See https://xmlgraphics.apache.org/fop/compliance.html#fo-property-font-variant

You may be able to get small caps if you use a small caps-only font. The FOP font page at https://xmlgraphics.apache.org/fop/2.6/fonts.html notes that OpenType includes small caps but then notes that FOP doesn't support OpenType features.

There are other formatters that do support small caps and that work with the DITA-OT.

Source https://stackoverflow.com/questions/66063729

QUESTION

Hide a topic from PDF output at xsl level

Asked 2021-Jan-12 at 15:20

I have a topic, which only contains some metadata (childs of prolog and some custom elements too) of the documentation. The contents of these elements is displayed in headers and footers in the acutal PDF output.

My problem: now the referred topic itself included in the pdf as an empty chapter.

Setting the processing-role to resource-only or filtering the topic does not solve the problem, as the content of the elements is needed in the further steps of the transformation (headers, footerst ect..)

My best guess is to somehow exclude this one topic and the needless page sequence based on its ID with..

.. adding some attributes in a custom xsl template?

.. modification of topic processing?

.. an obvious method that didn’t occur to me?

but I’m a beginner, so a little guidance would be nice.

Currently using: DITA-OT 2.1; Oxygen 17.1; Bookmap spec.; XSL FO based transformations;

Thanks in advance!

...

ANSWER

Answered 2021-Jan-12 at 15:20

Maybe instead of keeping that content inside the topic, you could keep it inside the main DITA Map, maybe using some DITA "data" elements like:

Source https://stackoverflow.com/questions/65668373

QUESTION

How can I add auto generated labels for topic titles in PDF output using DITA-OT?

Asked 2021-Jan-08 at 13:29

I'm generating a PDF using DITA-OT. I'd like to add labels to topic titles such as "Exercise 1:". I know that we can do this by adding variables to the en.xml file for section titles, chapter titles, etc. How can we extend this functionality to topic titles?

More specifically, I want to add "Exercise: #" and "Task: #" to Heading level 1 and Heading level 2 topic titles.

...

ANSWER

Answered 2021-Jan-08 at 13:29

In the XSLT stylesheet "dita-ot/plugins/org.dita.pdf2/xsl/fo/topic.xsl" there is a template which matches the topic title:

Source https://stackoverflow.com/questions/65625395

QUESTION

How can I make DITA catalog.xml work in VS Code?

Asked 2020-Nov-11 at 14:31

I am using VS Code and the "XML Language Support by Red Hat". I am pointing to the catalog file inside the DITA OT directory dita-ot-3.3.3\catalog-dita.xml. My DITA file looks like this:

...

ANSWER

Answered 2020-Nov-11 at 14:31

Edit settings.json to validate against DTD using catalog file as follows:

You must set "xml.catalogs","xml.javahome", "xml.validation.resolveExternalEntities" respectively.

Then you can get the succeeded validation result:

By the way, your DITA file is originally not valid against DITA DTD.

Source https://stackoverflow.com/questions/64782816

QUESTION

Can I configure Dita-OT 2.1 to output only the topic.fo file and not the pdf

Asked 2020-Apr-14 at 08:26

Is there a method when creating dita-ot 2.1 pipeline to only output the topic.fo and not go on to create the PDF?

Regards Conteh

...

ANSWER

Answered 2020-Apr-14 at 08:26

As far as I know there is no such a parameter available by default. If you look in the ANT build file "DITA-OT/plugins/org.dita.pdf2/build.xml" there is a "transform.fo2pdf" target. I guess you could manually make changes to the build file in order to avoid calling this target from the "transform.topic2pdf" target.

Change:

Source https://stackoverflow.com/questions/61170625

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install dita-ot

You can download it from GitHub, Maven.
You can use dita-ot like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the dita-ot component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: