Arbortext 6.0 M010 Released

Summary of SPR Fixes in Arbortext 6.0 M010 release

The M010 release of Arbortext 6.0 is now available for download. Point releases are free to all customers on active maintenance. Note, also, that with the 6.0 release, Unix platforms are no longer supported. But, IPv6 is.

The big fix here should be the update to the Java VM as 6.0. F000 came out just before a major bug was reported and fixed in Java. I can’t tell whether this is fixed in this release or not. I’ll update when I have better information.

Summary of fixes and changes

Here’s  the list of SPRs and enhancements added to a product release. We highly recommend you log in to the support site and read the release notes or the Fixed SPRs document (login required) or, for SPR details, just look below.

Products affected in this release

Product Release Datecode
Arbortext Digital Media Publisher 6.0 M010
Arbortext Publishing Engine 6.0 M010
Arbortext Editor 6.0 M010
Arbortext Editor Deployment Kit 6.0 M010

SPR Fixes Summary

  • Table border enhancements
  • DITA Application changes: Equation support is removed
  • New API for importing XLIFF files into Styler
  • Changes to the PTC Server adapter for Arbortext Content Manager, Windchill PDMLink, and Windchill ProjectLink
  • And lots of performance enhancing fixes.

For details, read on….

Continue reading “Arbortext 6.0 M010 Released”

Common Questions: Bursting

Bursting, chunking and content reuse in Arbortext

This week’s topic: Bursting

We start talking about something we call “bursting” when we get questions like the following:

Can a writer or translator work just on paragraph chunks while an editor can see entire sections?

This question is nearly always followed by this question:

Can this level of granularity be specified in ACM?

Before we can answer either question, we need to address some of the implicit assumptions here.

First, we’re assuming you’ve using the component content management functionality of Arbortext Content Manager (ACM). This means you have created reusable chunks, or have implemented bursting rules so that ACM creates the chunks for you. Once you have the chunks in ACM, you can set permissions so that individual users can only access those parts that they have permission to see.

In Arbortext, we call this process of automatically chunking your documents into individual, reusable pieces “bursting.”

Arbortext Content Manager performs document bursting based on configuration files that are stored on the server.  If no burst configuration is specified, the ACM will treat each document as a single document object. For some document types, such as the DITA document types, the burst configuration is used to import document objects rather than burst a larger document into smaller objects. DITA documents are already modular and typically do not require bursting.

Bursting rules are also used when you use the Documentum Adapter, the DB2 Adapter, or the Oracle Adapter with Arbortext Editor.

Note that much of the “work” involved in document bursting is researching your authors’ requirements and determining a burst configuration that meets their needs. It may be helpful to get some assistance defining your first burst configuration and then using an advisor to confirm your first solo bursting project.

As always, if you have a question that we haven’t answered or if you want more details, remember to send us your questions or add them to the comments!

Tweet Roundup: Arbortext User Meeting August 2010

Todd Nowlan on “Deploying and maintaining a large single-sourcing solution: Now what?” and understanding the complexity of this kind of solution and the benefits you get from moving to XML.

Here’s the tweet roundup for the Arbortext User Meeting for August 2010. The speaker was Todd Nowlan talking about “Deploying and maintaining a large single-sourcing solution: Now what?” As expected, it was a great presentation. As one attendee said his presentation was paced perfectly to allow everyone to understand the complexity of this kind of solution and the benefits you get from moving to XML.

If you want to see the original description, hop on over to the Arbortext PTC/User group August Meeting page to read the abstract. Or, if you missed it, watch the recording.

Also, if you want to hear more from Todd, he we posted an interview with him. He’s also a panelist on the upcoming webinar – “ROI of XML”.

Continue reading “Tweet Roundup: Arbortext User Meeting August 2010”