Earlier today we have released version 7.3 of FontoXML. This release includes some pretty nifty improvements to both the XML Editor as to the Content Quality and Document History Apps.
This quarter we took our time to focus on some often requested features.
OEM Embedded mode
FontoXML Editor is often integrated in a (external) CMS. We created the OEM embedded mode for scenarios where FontoXML only has limited screen space available.
Some examples of how we made FontoXML ready to blend in more easily:
- we reduced the height of the masthead by putting the toolbar tabs in a dropdown menu;
- we hide the statusbar by default;
- the content takes as much space as it can;
- we use FontoXML’s neutral theme to reduce the FontoXML branding in the UI.
Multiple occurrences of the same document
You can now open multiple occurrences of the same document in FontoXML. For example, it is now possible to load DITA maps with multiple topicref elements pointing to the same topic. Each instance is editable, with edits automatically visible in all other instances. To reduce the confusion that this situation may cause, FontoXML marks these documents with an explanatory message in both the editor and structure view.
Retry loading individual documents that failed to load
This release adds the option to retry loading individual documents that failed to load initially, for instance, due to temporary connectivity issues. Users can use this option in many cases to avoid having to restart the entire editor session when issues have been resolved.
Improved performance for loading documents
We have made several improvements regarding performance for this release. One of these improvements was aimed at the amount of time spent loading documents and time spent reloading documents when the order changes in a collection. We believe we have created a truly noticeable difference. Our performance benchmark shows an overall improvement of 26% on loading times.
However, this change did not come without a small sacrifice, something we don’t take lightly. While one of our goals has always been to avoid introducing regression, it is sometimes needed to introduce significant progression in another area. Due to the changes we’ve made, Find and replace now handles everything in actual document order instead of visual order. This affects elements such as footnotes.
We would like to hear your thoughts on this change, and if you believe this may impact your authors. Using that information we will be able to more precisely implement a solution in the future.
Various bug fixes and improvements
For more details on other new features, improvements, and bug fixes you can read the release notes.
In a further effort to enhance our transparency we have added a “Known issues” section to our documentation. This list will be kept up-to-date and we will mark issues when they are resolved in later releases.
Content Quality App
- Added support for capture groups in the RegexAnnotator.
- Allowed the usage of underscores in environment variables when referencing them from an analysis file.
- Added support for operations which use support the overrideRange argument to the content-quality-execute-operation and content-quality-get-context-node-id-and-range.
- Changed the annotate request and fragments per request limits in an editor.
- Fixed an issue within the error logs when using the DictionaryAnnotator with an httpSource that incorrectly logged the endpoint as being
- Fixed an issue where similar annotations without a namespace would not be recognized as such resulting in sub optimal UX when resolving annotations.
- Resolved Microsoft Security Advisory ASPNETCore-Mar18.
Please refer to your implementation partner for further details on how to acquire release 1.2.0 for your instance of FontoXML Content Quality. For more details on everything mentioned above, other new features, improvements, and bug fixes you can read the release notes.
Document History App
This is our very first version of the Document History App with open documentation available. You will find a high level overview of the application and an integration guide to help you get started. If you want to get access to Document History, please reach out to us.
This is what’s new in this release:
- We redesigned the revision selector to make it more clear which revisions you’re comparing and whose changes you will see
- Optimised the performance! We now only render the so-called “sheetframes” when a user scrolls them into view.
- We introduced a preview version of Document Compare. This allows you to compare two arbitrary documents.
- You are now able to copy from the change log in Document History. This puts the visible content on your clipboard.
- You can now more easily mark multiple changes as seen by making a selection across changes in in the content.
- Tons of small improvements under the hood that allow us to develop more cool features in the releases to come.