What is new in Arbortext 6.0?

Details about what the new features are in the Arbortext 6.0 release

Arbortext is more than an Editor. Arbortext is really a full platform from editing to publishing and content management.

However, today, I’m just going to talk about Editor and maybe about Styler a little bit, but only if there’s time. The changes to Styler will fill an article all by themselves. So, here’s a little bit of a tour, with a focus on the improvements to DITA support. There are a lot of new changes that everyone who’s an everyday user has been happy to see.

APP is now the default rendering engine for print output

One thing to know is that default print engine is APP now. FOSI is still supported through Print composer, but it’s no longer the primary engine. APP produces magazine quality layout with complicated layout rules.

Usability improvements

The first thing anyone would notice is the new file dialog has been redesigned. There’s categorization in the left hand panel — People who had a lot of doctypes, there was a lot of scrolling to find what you wanted. Now, the File->New dialog is a lot more convenient: You can now have samples and templates and it’s all controlled through a preference now, out of the box.

Commenting out markup

Commenting out markup is easy now. If you comment out a paragraph, it won’t appear in your output. Now, Arbortext Editor supports wrapping markup inside the comment. The para tags are contained inside the comments and are restored if you remove the comment.

Tag Templates and File Entities.

This is much improved, you can better preview your templates. Particularly important for table markup. Before, you used to see the tags and it didn’t always make sense if you didn’t understnad what the markup looked like. Now, you see the table and you can see what it will look like in your content. You can edit just like it’s in editor. File entities are previewable, but not yet editible. Then again they’re file entities.

Find and replace — Attributes

In older Editor versions, you could find elements, but it was hard to replace values. Now you can replace them directly.  If you search for attribute role with value external, you can simply replace the value with another one.

Spell checking

Spell checking has lots of nice advantages now.  Now you don’t get red squiggly every time you type a url or email address.  And there’s a new file that handles all your Accept and Reject terms. Say you don’t want someone to use the word “can’t” for example, you add that word to the single file that handles spell checking and you’re all set. This used to be split into two files. Now it’s all in one file.

Improved table handling

The key here is the bars on the side of the window. If it’s fixed height, the bar will turn red – a visual indicator telling you that it’s changed. Makes it a lot harder to accidentally change row and table heights and not realize it.

Modify cell borders is redesigned

A lot easier to pick cell borders, and define color shading/alternate row coloring

Schematron support

ISO standard another way to validat content that DTDs (or schemas) aren’t able to do . Why do you have a list if you only have one item? The way to check for these errors, Schematron is now part of the Tools->Completeness Check. This is all done through .sch files and the .dcf file config changes. You used to have this in post processing. Schematron makes checking business rules a ton easier.

Some misc improvements

  • Join multiple adjacent tags. In the edit menu you will see a new ‘join elements’ option. Say you have 3 paras and want them to be merged into one. You used to have to do this one at a time. Now you can select all and join.
  • Equations now are parsed like other markup – This means equations have no size limit to them.
  • Preferences — these file listing are now editable in sub windows, so it’s easier to see, easier to change priorities. This is true of anything with file (file entities, where to find browser, etc..)

Resource manager

WC resource manager now has the right-click context menu built in. It’s much more seemless. You can check out, you can see properties and metadata from the repository, and search right from this context menu. You used to have to do this through the repository browser. Now it’s easy to drill in and find out what you need right in the resource manager.

Also, the “Look In” field is now synchronized across the tabs and it has a new History Tab, so you can go looking where you were looking recently.

DITA Support

DITA specializations: You no longer have to develop the Resolved Document for Editing (RDE) or the Resolved Document for Styling (RDS) for specialziation. This is huge. Prior to the 6.0 release, this was confusing and took up a lot of extra time. If you were adding math, you always specialized. Now you can edit both maps and topics in RDE.

Keyrefs: DITA 1.2 Keyrefs are fully supported in Editor. You can use keyrefs globally or locally. Best practice is to have a separate map that can change your key definitions. One nice feature is that the value of the keyref is resolved properly when you’re editing in Arbortext Editor; it gets resolved during publishing; and, it gets checked in the Completeness Check step. Arbortext Editor will show you all the keyrefs that are available in a document.

Arbortext 6.0 is released!

The scoop on what’s new with the Arbortext 6.0 release

Here’s the scoop on what’s new with the Arbortext 6.0 release

Enhanced support for DITA 1.2

The Arbortext 6.0 release demonstrates PTC’s continued commitment to supporting DITA.

With the new authoring UI for Key References in DITA 1.2, you can create and insert key references directly into your DITA documents with ease. If you are using Arbortext Content Manager, right-click on an object in the Resource Manager to quickly access a CMS context menu. Check-in and check-out content or even view its properties, for increased efficiency in authoring and reuse.

The Resource Manager also has improved usability, with a location field that is synchronized across tabs, eliminating the need to re-navigate as you switch tabs. In addition, it provides an author with various linking options for intelligent graphics. When setting up specialized DITA document types, the Resolved Document for Editing (RDE) and Resolved Document for Styling (RDS) document types are now automatically generated.

Continue reading “Arbortext 6.0 is released!”

Looking to upgrade your Arbortext install?

The data points to consider when planning a software upgrade

When you’re looking to upgrade your Arbortext install from one release to another, you want to get all the information you can about the differences between your version and a random other version. And you want to do a test deployment before rolling it out to everyone in your organization.

Generally speaking, if you are upgrading between point releases in the same major version, you can find all the information you need in the release notes. The release notes detail the differences between each point release and the version associated with that set of release notes. For example, the release notes for 5.3 M200 will detail the differences between F000 and M200, M010 and M200, M020 and M200… right up through M190, the most recent previous release to M200.

Now, if you’re changing between major versions, you need to consider several data points:

Major Minor Release date
Currently installed version 5.3 M050 1/31/2009
Desired target version 5.4 M080 12/17/2010
Latest point release available for major version currently installed 5.3 M220 2/3/2011
First release for major version of desired target 5.4 F000 6/4/2009

As you can see, there’s a lot of overlap in the timeline.  All of this information is available in the Product Calendar.

You’ll want to fetch the release notes from:

  • The desired target version
  • The F000 of the target version
  • The latest point release of your currently installed version

This way, you should be able to glean the differences between your point release and the next major version. You will also be able to see what changes were made to future point releases in your major version after the next major release came out.  And, you’ll be able to see what changes were made in the new major point releases after it came out and as both major versions were in development simultaneously.

There are two last dates to get from the Product Calendar. The dates that:

  • Maintenance Releases Discontinued
  • Standard Support Ends

In the meantime, if you’re following our release notes feed, you know that for most releases, we give you the list of SPRs that get fixed for software releases so you can check and see if your bug got fixed. For deep releases, when the release notes span some 200 pages, we give you the highlights and leave the rest an exercise for the reader.