Summary of SPR Fixes in Arbortext 7.0 F000 release
Arbortext 7.0 was released last week. We saw a preview of what was coming last month and have been eagerly awaiting the release. There’s some big improvements with this release and some special treats for the early adopters.
7.0 will require new license generation, but 7.0 licenses are backwards compatible and will support older releases at the same time. If you have an active maintenance contract, you can download Arbortext 7.0 at no additional cost from the PTC website.
We’re testing 7.0 for our customers right now and we’ll be talking about what we find in the Mastermind session in October. Come to the Mastermind if you want a look at 7.0 before you start testing your environment and getting ready to upgrade. If you need any help testing your customizations or stylesheets, we can help! Join the Arbortext Mastermind or contact us at email@example.com.
For now, this post will take you through the highlights of the release. Details on each feature and specific bug fixes contained in the release can be found in the release notes on the PTC website.
If you want details about what’s in the release, read on… Continue reading “Arbortext Version 7.0 Released”
Support for DITA 1.3 now available in Arbortext 7.0 — no plugins or additional modules required
Arbortext 7.0 includes support for DITA 1.3 — no plugins or additional modules required.
With the release of Arbortext 7.0, all DITA 1.x documents are supported by the Arbortext suite of products. Arbortext has had support for DITA since 2004, when it was originally being designed by IBM.
Although DITA 1.3 Draft Specification went out for Public Commentary in July and has not yet been finalized, vendors like PTC/Arbortext, who participate on the OASIS DITA Technical Committee, have already updated Arbortext to support the changes to DITA as outlined in the latest draft DITA 1.3 specification.
So, what’s in DITA 1.3 that you might want?
Continue reading “DITA 1.3 available with Arbortext 7.0 release”
APP became available to anyone who wanted to do high-quality print output about midway through the 5.4 release stream. Since 6.0 we’ve been encouraging people creating new stylesheets to use APP as their main rendering engine over FOSI. It’s new technology for many of us, but it’s so powerful that the benefits curve has always surpassed the learning curve.
In 6.0, APP source edits were new and a bit tough to learn. Documentation was there, but there was a lot of it and it was unfamiliar. It changed as APP Desktop features got more exposed in Styler throughout the 6.0 and 6.1 releases.
From time to time, we still find customers using FOSI when they’re creating new stylesheets. (We even find it in new stylesheets created by some of the other PTC partners.) Doing this now carries a serious risk: With 7.0 PTC has moved FOSI and XSL-FO engines to Sustained Support. You should be using APP as the base rendering engine for Arbortext PDF output.
There are a few APP coding courses around out there — all in the hands of Qualified Arbortext Channel Partners. Until now, your only option was to take in-person or in-center training from one of them.
The IDE has code completion. It has syntax validation. It has a debugger. It’s never been easier to find out if what you think is happening in your stylesheet is what actually is happening. And that’s invaluable to stylesheet developers.
If you’re ready to move your Stylersheets to APP, we’re one of the partners ready to train you. Just drop us a line and we’ll help you understand how to train your brain to think APP and move on from FOSI.