DITAToo DITA CMS 1.95 Is Released!

We’ve just rolled out the new version of our DITAToo DITA CMS! The new version provides fixes to the issues encountered in previous versions, improves performance, includes minor usability improvements, and introduces new features that enhance the user experience.

Here’s an overview of what the improvements you’ll find in DITAToo 1.95:

Branching a Project

This is a feature that many our customers wanted. Up until now, you could only branch individual files. From now on, you can also branch entire projects. When branching a project, you can define what you want to do with the referenced topics:

  • Create a copy of the DITA map and all the referenced topics. In this case, all files to which topics refer (for example, images) are branched as well.
  • Create a copy of the DITA map with empty topics. In this case, the referenced topics are branched too. However, the contents of the topics, except their title, is deleted.
  • Create a copy of the DITA map only. In this case, the referenced topics are not branched. The map refers to the original topics and therefore, the links in the map are updated accordingly.

 

Searching Translations

In addition to the existing search options, you can now search for files that are not translated or need to be updated in one query.

 

Multiple Selection on the Projects Tab

DITAToo 1.95 enables you to select multiple projects on the Projects tab.

 

Basic Support for subjectScheme Maps

With DITAToo 1.95, you can upload subjectScheme maps to the DITAToo content repository.

Note for DITAToo customers: if you bought DITAToo directly from us, you will receive shortly the detailed information on how to get the new version. If you bought DITAToo from one of our value-added resellers or implementation partners, you will receive this information from them.

2 Thoughts on “DITAToo DITA CMS 1.95 Is Released!

  1. Astrid Ras on June 2, 2015 at 4:11 pm said:

    Our company would like to use the new branching feature for ditamaps, but we are unsure about the consequences. As we understand, there are 3 ways to do this, but which one will work for us? Is there additional information available on the consequences on the size/performance of the database and on translations for example? We could really use the extra info. Regards, Astrid Ras, technical writer, Planon, The Netherlands.

    • When you branch a project,a copy of the DITA map and possibly (depending on the option you selected, ) its topics is created. Which option will work for you in the most efficient way depends on the scenario you need to support:

      1. If you want to create a snapshot of the entire project and then you are going to modify the topics, but still want to use the existing content as basis, select “Branch project, branch topics”.

      2. If you want just to clone the DITA map itself and modify just the map, but you are not going to modify the topics, choose “Branch project, use original topics”.

      3. If you want to create a brand new project that will have the same structure as the original project, and use the same topic names as the original project, but the contents will be entirely different, then go with “Branch project, create empty topics”.

      So it’s just three different scenarios.

      Hope this helps. But please don’t hesitate to post here any further questions.

      Alex

Leave a Reply to Alex Masycheff Cancel reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Post Navigation