Release Notes for Arbortext Editor,

Styler, and Architect

Arbortext 5.3 M030

Arbortext
A PTC Product Family
Release Notes for Arbortext Editor,
Styler, and Architect
Arbortext 5.3 M030

Corporate Office:
PTC - Arbortext
1000 Victors Way
Ann Arbor, MI 48108 USA
Tel: +1 734.997.0200 www.ptc.com
Fax: +1 734.997.0201 [email protected]
Copyright © 2007 Parametric Technology Corporation. All Rights Reserved.
User and training guides and related documentation from Parametric Technology Corporation and its subsidiary
companies (collectively “PTC”) is subject to the copyright laws of the United States and other countries and is provided
under a license agreement that restricts copying, disclosure, and use of such documentation. PTC hereby grants to the
licensed software user the right to make copies in printed form of this documentation if provided on software media,
but only for internal/personal use and in accordance with the license agreement under which the applicable software is
licensed. Any copy made shall include the PTC copyright notice and any other proprietary notice provided by PTC.
Training materials may not be copied without the express written consent of PTC. This documentation may not be
disclosed, transferred, modified, or reduced to any form, including electronic media, or transmitted or made publicly
available by any means without the prior written consent of PTC and no authorization is granted to make copies
for such purposes.
Information described herein is furnished for general information only, is subject to change without notice, and should
not be construed as a warranty or commitment by PTC. PTC assumes no responsibility or liability for any errors or
inaccuracies that may appear in this document.
The software described in this document is provided under written license agreement, contains valuable trade secrets and
proprietary information, and is protected by the copyright laws of the United States and other countries. It may not be
copied or distributed in any form or medium, disclosed to third parties, or used in any manner not provided for in the
software licenses agreement except with written prior approval from PTC.
UNAUTHORIZED USE OF SOFTWARE OR ITS DOCUMENTATION CAN RESULT IN CIVIL DAMAGES
AND CRIMINAL PROSECUTION.
For Important Copyright, Trademark, Patent, and Licensing Information:
For Windchill products, select About Windchill at the bottom of the product page. For InterComm products, on the
Help main page, click the link for Copyright 2007. For other products, select About from the Help menu on the main
menu for the product.
UNITED STATES GOVERNMENT RESTRICTED RIGHTS LEGEND
This document and the software described herein are Commercial Computer Documentation and Software, pursuant
to FAR 12.212(a)-(b) (OCT’95) or DFARS 227.7202-1(a) and 227.7202-3(a) (JUN’95), and are provided to the US
Government under a limited commercial license only. For procurements predating the above clauses, use, duplication, or
disclosure by the Government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical
Data and Computer Software Clause at DFARS 252.227 7013 (OCT’88) or Commercial Computer Software-Restricted
Rights at FAR 52.227 19(c)(1)-(2) (JUN’87), as applicable. 02202007
Parametric Technology Corporation, 140 Kendrick Street, Needham, MA 02494 USA

July 31, 2007

CONTENTS

Chapter 1 Release requirements and support .................................... ........... 1

General information ........................................................................... ........... 1
Platform support ................................................................................. ........... 2
Localization ............................................................................................... 2
CJK support ............................................................................................... 2
Browser support for web preview and output ........................................... 3
Browser support for Web/Wireless Composer .......................................... 3
Product support .................................................................................. ........... 3

Chapter 2 Updates in this release ...................................................... ........... 5

Configuration changes ........................................................................ ........... 5
Arbortext Editor changes ................................................................... ........... 5
Localized online help ................................................................................ 5
Localized Arbortext Help Center .............................................................. 6
Compose for Digital Media Publisher ....................................................... 6
Intelligent graphics support changes ......................................................... 7
XML inclusion error messages ................................................................. 8
Arbortext Styler changes .................................................................... ........... 8
Generated Text Editor changes .................................................................. 8
DITA Application changes ................................................................. ........... 8
Service Manual Application ............................................................... ........... 8
PTC Server connection changes ........................................................ ........... 9
Upgrading Arbortext Editor or your PTC Server ...................................... 10
Repository Adapter changes .............................................................. ........... 10
Dynamic Link Manager changes ....................................................... ........... 12
Migration ................................................................................................... 12
New features .............................................................................................. 12
Updates to existing features ...................................................................... 14
Configuration file changes ......................................................................... 15
DLM markup resolution changes .............................................................. 16
API changes ............................................................................................... 17
Menu and dialog box changes ................................................................... 23
Miscellaneous ACL changes .............................................................. ........... 24
What’s fixed ....................................................................................... ........... 25
Arbortext Editor fixes ................................................................................ 25
Composition and publishing fixes ............................................................. 25
DITA application fixes .............................................................................. 27
Dynamic Link Manager fixes .................................................................... 27
Arbortext Styler fixes ................................................................................ 28
Arbortext Import/Export fixes ................................................................... 29
Repository adapter fixes ............................................................................ 29
ACL fixes .................................................................................................. 29

i
Release Notes for Arbortext Editor, Styler, and Architect

AOM fixes ................................................................................................. 30

Appendix A. Included 5.3 M020 updates 31

Arbortext Editor changes ........................................................................ ........... 31
JRE updated ............................................................................................... 31
JVM allocation changes ............................................................................ 31
Intelligent graphics support ....................................................................... 32
Composing files for use with Digital Media Publisher ............................. 35
press.pdfcf PDF configuration file removed ............................................. 35
Copyright information changes ................................................................. 35
Arbortext Import MapTemplate changes ................................................ ........... 36
Arbortext Adapter to IBM Document Manager support for DITA
documents .......................................................................................... ........... 36
PTC Server connection and multiple Arbortext Publishing Engine
sessions ............................................................................................... ........... 37
PTC Server connection and Windchill ProjectLink ................................ ........... 37
Dynamic Link Manager availability ....................................................... ........... 38
Miscellaneous ACL changes ................................................................... ........... 38
What’s fixed ............................................................................................ ........... 38
Arbortext Editor fixes ................................................................................ 38
Composition and publishing fixes ............................................................. 39
Arbortext Import/Export fixes ................................................................... 39
Repository adapter fixes ............................................................................ 40
ACL fixes .................................................................................................. 41

Appendix B. Included 5.3 M010 updates 43

Configuration changes ............................................................................ ........... 43
Arbortext Editor changes ........................................................................ ........... 44
Arbortext Import/Export updates ............................................................ ........... 44
Arbortext Help Center changes ............................................................... ........... 45
Web browser support ................................................................................. 45
Personal configuration ............................................................................... 45
Miscellaneous Arbortext Help Center changes ......................................... 46
Limitations ................................................................................................ 46
Dynamic Link Manager availability ....................................................... ........... 47
Miscellaneous ACL changes ................................................................... ........... 47
What’s fixed ............................................................................................ ........... 47
Arbortext Editor fixes ................................................................................ 47
Composition and publishing fixes ............................................................. 54
Arbortext Styler fixes ................................................................................ 58
Arbortext Import/Export fixes ................................................................... 59
Repository adapter fixes ............................................................................ 61
Arbortext Architect fixes ........................................................................... 63
XUI fixes ................................................................................................... 63
ACL fixes .................................................................................................. 63
AOM fixes ................................................................................................. 64
Miscellaneous fixes ................................................................................... 65

ii
 Contents

Appendix C. Included 5.3 F000 new features 67

Product installation changes ................................................................... ........... 67
Arbortext Publishing Engine supports backward compatibility for
Arbortext Editor clients ........................................................................ 67
Configuration changes ............................................................................ ........... 68
PDF configuration file updates .................................................................. 68
Arbortext Editor startup command syntax ................................................ 68
Stylesheet presentation order .................................................................... 68
APTPRFWCF environment variable and epic.wcf preferences file
deprecated ............................................................................................. 69
Arbortext Editor changes ........................................................................ ........... 69
DITA Application ...................................................................................... 69
Column view ............................................................................................. 74
New user preferences file .......................................................................... 74
Supported document types ........................................................................ 75
StylerSheet updating ................................................................................. 75
Miscellaneous Arbortext Editor changes .................................................. 75
New API .................................................................................................... 77
Arbortext Styler changes ......................................................................... ........... 81
Update existing StylerSheets ..................................................................... 81
Custom table support ................................................................................. 81
XPath numbering ....................................................................................... 81
Miscellaneous Arbortext Styler changes ................................................... 82
New API .................................................................................................... 82
Arbortext Import/Export updates ............................................................ ........... 83
Arbortext Import configuration changes ................................................... 83
Arbortext Publishing Engine migration considerations ............................ 85
PDF file importing ..................................................................................... 85
Arbortext Import Workbench and MapTemplate Editor updates .............. 86
Miscellaneous Arbortext Import updates .................................................. 87
Arbortext Export updates .......................................................................... 87
Known limitations ..................................................................................... 88
Dynamic Link Manager availability ....................................................... ........... 89
Composition changes .............................................................................. ........... 89
Stylesheet associations now supported for Arbortext Publishing
Engine ................................................................................................... 89
Arbortext XSL support ........................................................................... ........... 90
PTC Server connection (Windchill connection) changes ....................... ........... 90
Repository Adapter changes ................................................................... ........... 90
XUI (XML-based User Interface) changes ............................................. ........... 91
Interchange no longer available for download ........................................ ........... 94
AOM changes ......................................................................................... ........... 94
New and changed AOM interfaces ........................................................... 94
Miscellaneous ACL changes ................................................................... ........... 95
New ACL set command options ............................................................... 95
New ACL functions .................................................................................. 96
Changed ACL functions ............................................................................ 96
Environment variables ............................................................................ ........... 96
New manual for Arbortext PE programmers .......................................... ........... 97

iii
CHAPTER
1
Release requirements and support
General information ............................................................................................. 1
Platform support................................................................................................... 2
Product support .................................................................................................... 3

General information
The Release Notes for Arbortext Editor, Styler, and Architect contain release
information for the 5.3 M030 version of Arbortext Editor and its options. To use the
information in these release notes, you should be familiar with the operating system
at your site and with standard system administration tasks.

The 5.3 M030 release can be installed as a stand-alone release. 5.3 M030 does not
need to be installed over an existing 5.3 installation. If installed over an existing
5.3 installation on Windows, only those components installed with the earlier 5.3
release(s) will be updated. To add or remove components when installing 5.3
M030 on Windows, first perform the update, then rerun the installer to modify the
installation.

On Windows, you can upgrade your current installation to 5.3 M030 if you are
running version 5.3 F000, 5.3 M010, M011, M020, M021, M022 or M023. Refer to
the Installation and Licensing Guide for Arbortext Editor, Styler, and Architect for
additional details on upgrading from previous 5.3 releases.

On UNIX, the 5.3 M030 release is installed as a stand-alone release. Do not install
the upgrade over the previous release.

This release also includes updates included in the earlier 5.3 releases of Arbortext
Editor. Refer to the appendixes in these release notes for descriptions of these
features. If you are upgrading from a version prior to Arbortext Editor 5.3,
refer to the release notes of any interim version by visiting the Support area of
http://www.ptc.com.

1
Release Notes for Arbortext Editor, Styler, and Architect

Platform support
The following table lists the supported platforms and versions for this version of
Arbortext Editor. PTC only provides product support for Arbortext Editor used on
hardware or operating systems described in our documentation.

Table 1–1 Arbortext Editor supported platforms

Solaris Windows
8 9 10 2000 XP Server 2003
X X X X X X
X — certified
If you are performing a Windows installation to share with Windows client
installations, install to one of the Windows servers.

Note
Certain features are not available on all platforms. Refer to the Installation and
Licensing Guide for Arbortext Editor, Styler, and Architect for complete version
and platform information.

Localization
This release of Arbortext Editor supports English, French, German, Italian, Japanese,
Korean, Simplified Chinese, Spanish, and Traditional Chinese localizations of the
user interface and online help. Refer to the online help topic titled LC-MESSAGES —
Specifying the locale for user interface for details on enabling alternate localizations
of Arbortext Editor.

As in previous releases, only the topics targeted to document authors are localized in
the online help. Those topics delivered in English are identified as such in the help
Table of Contents. To view the localized online help once it is installed, ensure
that your LC_MESSAGES environment variable is set to the desired locale, start
Arbortext Editor, and choose Help→Help Topics.

The following documents are also localized in this release:

■ Getting Started with Arbortext Editor for Administrators

■ Installation and Licensing Guide for Arbortext Editor, Styler, and Architect

■ Release Notes for Arbortext Editor, Styler, and Architect (5.3 M020 release)

CJK support
CJK languages (Chinese, Japanese, or Korean) are automatically enabled in
Arbortext Editor when the appropriate operating system locale is enabled.

2
 Chapter 1 Release requirements and support

Table 1–2 Arbortext Editor supported systems for CJK

Solaris Windows
8 9 10 2000 XP Server 2003
X X X X X X
X — certified
If you’re performing a Windows installation to share with Windows client
installations, install to one of the Windows servers.

Browser support for web preview and output

The web browser support applies to the Compose to HTML File web preview. The
supported browser versions also apply to the Web/Wireless Composer output.

Table 1–3 Web browser support

Browser and version Windows Solaris
XP 2000 8 9 10
Microsoft 7.0 X X NA NA NA
Internet 6.0 X X NA NA NA
Explorer
Mozilla Firefox 2.0 X X X X X
Mozilla 1.7 X X X X X
Navigator
X — certified
NA — not available

Browser support for Web/Wireless Composer

The Web/Wireless Composer is available on all Arbortext Editor supported
platforms and systems. Refer to the table in Browser support for web preview and
output for supported browser versions.

If this installation of Arbortext Editor will be using Arbortext Publishing Engine to

perform document composition, Print Composer and/or the Web/Wireless Composer
product options also must be installed on the Arbortext Editor client to make the
composition menu choices available.

Product support
Product support for all Arbortext products is available through PTC Technical
Support at the PTC web site at www.ptc.com. Contact PTC Technical Support to
report problems with your software.

3
CHAPTER
2
Updates in this release
Configuration changes.......................................................................................... 5
Arbortext Editor changes..................................................................................... 5
Arbortext Styler changes ..................................................................................... 8
DITA Application changes .................................................................................. 8
Service Manual Application ................................................................................ 8
PTC Server connection changes ......................................................................... 9
Repository Adapter changes ................................................................................ 10
Dynamic Link Manager changes ........................................................................ 12
Miscellaneous ACL changes ............................................................................... 24
What’s fixed.......................................................................................................... 25

The following sections describe the new and changed features in this release. What’s
fixed on page 38 includes lists of specific fixes included in this release.

Configuration changes
After installing this release, you must recompile each of your custom SGML
DTDs. Refer to Compiling Document Types in the Arbortext Editor online help for
instructions on recompiling document types.

If you have added specialized DITA document types beyond the default ones
supported by Arbortext Editor, refer to DITA Application changes on page 8 for
information on changes to the default DITA document type configuration.

Arbortext Editor changes

The following changes to Arbortext Editor have been made in this release.

Localized online help

This 5.3 M030 release delivers localized Arbortext Editor version 5.3 online help
and support documentation in the following languages on all supported Arbortext
Editor and Arbortext Publishing Engine platforms: French, German, Italian,
Japanese, Korean, Simplified Chinese, Spanish, and Traditional Chinese.

5
Release Notes for Arbortext Editor, Styler, and Architect

Localized documentation is available from the PTC Support web site as a companion
download to the base 5.3 M030 release. Unzip the downloaded archive file to
a temporary directory and run the file setup.exe. Then, follow the onscreen
instructions to install the localized online help.

As in previous releases, the topics targeted to document authors are localized in the
online help. Those topics delivered in English are identified as such in the help Table
of Contents. To view the localized online help once it is installed, ensure that your
LC_MESSAGES environment variable is set to the desired locale, start Arbortext
Editor, and choose Help→Help Topics.

The following documents are also localized in this release:

■ Getting Started with Arbortext Editor for Authors

■ Installation and Licensing Guide for Arbortext Editor, Styler, and Architect

■ Release Notes for Arbortext Editor, Styler, and Architect

The setting of the LC_MESSAGES environment variable also determines which

localized versions of the documents are displayed from the Help→Documentation
menu.

Localized content is current through the 5.3 M020 release. New and changed
content in the 5.3 M030 documentation is not reflected in the localized versions
of the documentation.

Localized Arbortext Help Center

In this release, the Arbortext Help Center also provides the localized Arbortext Editor
version 5.3 online help and support documentation. The localized documentation is
provided as an update to 5.3 M030 Help Center. The localized Help Center update is
available from the PTC Support web site as a companion download to the base 5.3
M030 release. Unzip the downloaded archive file to a temporary directory and run
the file setup.exe to install the localized Help Center update. After installation,
the Help Center will apply the update the next time you invoke Help Center from
Arbortext Editor.

Once you have applied the update, you can switch the Help Center to any of the
localized documentation sets through the Help Center Configuration tab.

Compose for Digital Media Publisher

You can now directly publish documents in the format required to be included as
part of a Digital Media Publisher (DMP) document set. Choosing File→Compose
for Digital Media Publisher publishes the current document as HTML files with
an accompanying table of contents based on the document’s organization and a list
of index terms. Composing documents for DMP uses the styles defined for HTML
Help output in your Arbortext Styler stylesheets. Composing files for use with DMP
does not require that Digital Media Publisher be installed.

To compose files for DMP, the Web/Wireless option must be installed and the
following settings must exist in the feature.cf file:

6
 Chapter 2 Updates in this release

featureWebPublishing = on
featureDMPPublishing = on

A new set featureDMPPublishing option is available to enable and disable

the compose to DMP feature. Refer to set featureDMPPublishing in the Arbortext
Editor online help for details.

Intelligent graphics support changes

The following changes to the Arbortext Editor intelligent graphics support have
been made in this release:

■ The PVZ and ISOZ graphic formats are supported. Refer to PVZ and ISOZ in the
Arbortext Editor online help for details.

■ Intelligent graphics containing animations are supported and have associated

toolbar buttons in the Arbortext IsoView control embedded in Arbortext Editor.
Refer to Viewing an intelligent graphic in the Arbortext Editor online help for
details.

■ The set isoviewfileformats option now supports the EDZ, PVZ, and
ISOZ graphic formats. Refer to set isoviewfileformats in the Arbortext Editor
online help for details.

■ The default size of an EDZ graphic has been changed to four inches by three
inches. This default size only applies if the defaultReproWidth or
defaultReproHeight attributes defined in the GraphicDefaults element in
the document type configuration file (.dcf) are not set.

For EDZ graphics, if the reproWidth, reproHeight, and scaleToFit

attributes are enabled in the .dcf file for a document type, you must enable
the scaleToFit attribute for an EDZ graphic before the reproWidth and
reproHeight attributes will work.

Intelligent graphics support has the following known limitations in this release:

■ For some graphic cards, opening a 3D intelligent graphic in Arbortext Editor

results in a black box that covers some or all of the graphic.

■ For EDZ and PVZ graphics, using the intelligent graphics toolbar in Arbortext
Editor or published HTML output might cause extra toolbar buttons to appear
in the toolbar and might cause the Arbortext IsoView Preferences dialog box
to appear.

■ For EDZ and PVZ graphics, clicking a mouse button inside of the embedded
Arbortext IsoView control might cause the graphic to disappear. The graphic
reappears when you move the cursor out of the Arbortext IsoView control.

■ On some workstations, 3D intelligent graphics rendered using IsoView may not

appear in previewed, printed, and PDF documents.

7
Release Notes for Arbortext Editor, Styler, and Architect

XML inclusion error messages

When you open a document that contains invalid XML inclusions, Arbortext Editor
no longer displays an error message for each invalid inclusion. With this release,
information about invalid XML inclusions is displayed in the message window.

Arbortext Styler changes

Generated Text Editor changes
A new Arbortext Styler Generated Text Editor Advanced menu item is now
available. Advanced→Set Attribute lets you set a value for an attribute based on
content in the document. The content may be specified with an XPath expression.
This feature could be used, for example, to obtain scale-to-fit behavior with graphics
when the graphic element in your document type does not have a scale-to-fit
attribute. You can insert a graphic in generated text, set its scale-to-fit attribute to
on, and obtain path and other attribute values from the element in the document.

DITA Application changes

The DITA Application now enables you to develop custom document types for the
resolved documents. This enables you to integrate DITA topic specializations into
the resolved document types without having to include the specializations in the
standard DITA Ditabase document type. This also enables you to develop DITA map
specializations that do not apply to all users at your site.

The document type configuration file (.dcf) now contains the following new
attributes on the Options element:

■ ditaRDEdit — Enables you to set the document type for the resolved
document for editing.

■ ditaRDStyle — Enables you to set the document type for the resolved
document for styling.

You can use these attributes to set custom resolved document types in the .dcf
file for your DITA maps. By default, the resolved document for editing uses the
rdedit document type and the resolved document for styling uses the rdstyle
document type. Refer to Specifying the DITA resolved documents for editing and
styling and Adding specialized DITA document types in the Arbortext Editor online
help for details.

Service Manual Application

The Service Manual Application (SMA) is designed to deliver dynamic publishing
capabilities for maintenance and repair operations. SMA provides production-quality
stylesheets for output to print, PDF, and the web. The technology is based on the
Darwin Information Technology Architecture (DITA) standard for content creation.

8
 Chapter 2 Updates in this release

SMA uses industry best practices to organize, illustrate, and format sets of
instructions, procedures, fault isolation sequences, cautions, warnings, and
regulatory requirements as intelligible documents or electronic modules.

Features supported by the Service Manual Application include:

■ Dynamic rendering of complex service pages

■ User friendly customization for output

■ Intelligent graphics with IsoView 7.0 that includes capability to launch expanded
views of vector graphics.

Specialized topics introduced for the Service Manual Application include:

■ Troubleshooting — A topic designed to organize troubleshooting information

for ease of navigation by the reader.

■ Procedure — A flexible topic that allows side-by-side text and associated graphics
for steps within a procedure or a flow of text and graphics embedded within steps.

Specialized domains introduced with the Service Manual Application include:

■ Hazard statements — Based on a proposal for DITA 1.2, the hazard statements
proposed by the DITA Machine Industry Subcommittee are included.

■ Step — Step/substep model is provided to incorporate text and graphics within

procedures.

Documentation for the Service Manual Application is delivered in the following

three documents found by choosing Help→Service Manual Help in Arbortext
Editor:

■ Arbortext Service Manual Application Tutorial Guide

■ Arbortext Service Manual Application Language Reference

■ Arbortext Service Manual Application Configuration Guide

PTC Server connection changes

The PTC Server connection now supports two-way metadata. Two-way metadata
enables XML element content or attribute values to be passed to PTC Server
instance based attributes (IBA) during document import or check in and PTC Server
IBA values to be passed to XML elements or attributes during document check out.

Two-way metadata is configured through a new twowaymetadatarule element in

the document-type-specific burst configuration file. Refer to Assigning PTC Server
properties in the Arbortext Editor online help for details.

The system-wide burst configuration file has a new twowaymetadata attribute

for the createdefaults element that enables you to disable two-way metadata. Refer
to Configuring system default values in the PTC Server connection section of the
Arbortext Editor online help for details.

9
Release Notes for Arbortext Editor, Styler, and Architect

Upgrading Arbortext Editor or your PTC Server

Before upgrading either Arbortext Editor or your PTC Server, delete the
cache directory defined by the WindchillAdapterHomeDir parameter of the
userprefs.xml configuration file. If you do not delete the cache directory,
Arbortext Editor might prematurely exit when you try to connect to the PTC Server.

Be sure to check in or upload any documents on which you are working before
deleting the cache directory. Refer to Configuration files in the PTC Server
connection section of the Arbortext Editor online help for more information about
the cache directory.

Repository Adapter changes

This release contains the following repository adapter updates:
■ Arbortext Adapter to Documentum

The Arbortext Adapter to Documentum now supports two-way metadata.

Two-way metadata enables XML element content or attribute values to be passed
to Documentum attributes during document import or check in and Documentum
attribute values to be passed to XML elements or attributes during document
check out.

Two-way metadata is configured through a new twowaymetadatarule element in

the document-type-specific burst configuration file. Refer to Assigning repository
metadata: With the Arbortext Adapter to Documentum in the Arbortext Editor
online help for details.

The system-wide burst configuration file has a new twowaymetadata attribute

for the createdefaults element that enables you to disable two-way metadata.
Refer to Configuring system defaults: With the Arbortext Adapter to Documentum
in the Arbortext Editor online help for details.
■ Arbortext Adapter to Documentum/WDK
□ If you are running Documentum Webtop 5.3 SP5, contact Documentum’s
Technical Support group to obtain the Documentum hotfix for bug 141453.
Without this hotfix you cannot do inline checkouts of child objects, and all child
object checkouts will require the All, root and descendents checkout option.
□ The Arbortext Adapter to Documentum/WDK now supports working with
DITA documents. The DITA Application Resource Manager can insert topic
references and content references for DITA objects stored in a Documentum
Docbase. Sample Documentum XML applications are provided in a sample
DocApp for the following DITA document types:
• Map

• BookMap

• Concept

• Topic

• Task

10
 Chapter 2 Updates in this release

• Reference

• Ditabase

• Glossary

Refer to Overview of DITA support with the Arbortext Adapter to

Documentum/WDK in the Arbortext Editor online help for details.
Note
Using the DITA Application with the Arbortext Adapter to Documentum/WDK
requires Documentum Webtop 5.3 SP5 with the Documentum DITA_hotfix
package. Contact Documentum’s Technical Support group to obtain this
package. Note that the hotfix for bug 141453 is included in the DITA_hotfix
package.

Also, there is a known Documentum issue where DITA maps that reference
multiple topics might take a long time to check out. Documentum is aware of
this issue, and the fix for it will be included in the DITA_hotfix package once
the fix is available.

■ Arbortext Adapter to IBM Document Manager

The Arbortext Adapter to IBM Document Manager now supports two-way

metadata. Two-way metadata enables XML element content or attribute values
to be passed to IBM Document Manager properties during document import or
check in and IBM Document Manager property values to be passed to XML
elements or attributes during document check out.

Two-way metadata is configured through a new twowaymetadatarule element in

the document-type-specific burst configuration file. Refer to Assigning repository
metadata in the Arbortext Adapter to IBM Document Manager section of the
Arbortext Editor online help for details.

The system-wide burst configuration file has a new twowaymetadata attribute

for the createdefaults element that enables you to disable two-way metadata.
Refer to Configuring system default values in the Arbortext Adapter to IBM
Document Manager section of the Arbortext Editor online help for details.
■ Arbortext Adapter to Oracle CM SDK

The Arbortext Adapter to Oracle CM SDK now supports two-way metadata.

Two-way metadata enables XML element content or attribute values to be passed
to Oracle CM SDK attributes during document import or check in and Oracle
CM SDK attribute values to be passed to XML elements or attributes during
document check out.

Two-way metadata is configured through a new twowaymetadatarule element in

the document-type-specific burst configuration file. Refer to Assigning repository
metadata: With the Arbortext Adapter to Oracle CM SDK in the Arbortext Editor
online help for details.

The system-wide burst configuration file has a new twowaymetadata attribute

for the createdefaults element that enables you to disable two-way metadata.
Refer to Configuring system defaults: With the Arbortext Adapter to Oracle CM
SDK in the Arbortext Editor online help for details.

11
Release Notes for Arbortext Editor, Styler, and Architect

Dynamic Link Manager changes

This release of Arbortext Editor is the first 5.3 release to support Dynamic Link
Manager. This release offers several updates and changes to the way Dynamic Link
Manager (DLM) operates. These release notes summarize the DLM-related changes.

When updating to this version of DLM, be aware of the following items:

■ When using DLM on a version 5.3 Arbortext Publishing Engine server, all
Arbortext Editor clients must also be at version 5.3. Version 5.2 (or earlier)
Arbortext Editor clients are not supported with version 5.3 Arbortext Publishing
Engine servers.

■ DITA document types are not currently supported by Dynamic Link Manager.

For more detailed information on using the DLM changes included in this release,
refer to the Arbortext Editor online help, the DLM Javadoc, and the DLM chapter of
the Customizers’ Guide.

Migration
The structures of the underlying DLM databases have changed in this release. Refer
to the instructions in the migration section of the DLM chapter of the Customizers’
Guide for utilities and procedures for migrating from earlier versions of DLM.

New features
The following DLM features are new in this release.

Sample DLM application

A sample DLM application is now included in your Arbortext Editor installation
directory. This sample provides a quick means to explore the configuration and
capabilities of DLM. Once the sample is installed, the DLM Repository will be
populated with targets that can be used to create links in a newly created DLM
document. The sample documents can be edited and published to HTML and PDF to
illustrate the results of linking using DLM.

Inline and reference linking modes

You can now create and store link information in two ways:

■ Inline linking — Link data is created and maintained in the bodies of documents
in atidlm:link elements and stored in the DLM Repository when registering a
document. Inline linking is the mode in which links were created and stored in
previous versions of DLM.

■ Reference linking — Link data is stored directly in the DLM Repository at the
time of creation. At that same time, markup referencing a link key is inserted in
the document. Reference links can be reused in multiple locations across multiple
documents. Updating the link in the repository will automatically change the way
each reference link resolves at publishing time.

12
 Chapter 2 Updates in this release

Third-party links
You can now create links that connect two pieces of content without the link being
explicitly represented in either piece of content. Referred to as third-party links, the
link source and target data connecting the two pieces of content exists solely in the
repository. Refer to Resolution of third-party links on page 16 for details on resolved
third-party link markup.

Context-sensitive linking and authoring based on document

sets
Authoring DLM documents and linking (reference and third-party links) now occurs
in the context of document sets. A link belongs to one (and only one) document set,
and resolves based on the members of that particular document set. Links can be
copied to other document set. These copied links will resolve based on the members
of their own document sets.

Registration and browsing of translated content

Translated content can now be registered in the DLM Repository. You can also
browse the repository in non-English languages. The language used for browsing
resources is determined based on the user’s locale. Refer to the description of
TRANSLATED_METADATA_NAME in DCAConfig.properties changes on page
16 for details on registering translated content. Refer to Resolution of language
sensitive metadata on page 17 for details on resolving language-sensitive metadata.

Link resolution stylesheets

The following stylesheets can be used to display link markup after resolution has
occurred.

■ Arbortext-path\lib\xsl\debug\reveal_markup.xsl — An
XSL-FO stylesheet that renders the XML data in a highly readable manner,
allowing you to review the results of your resolution stylesheet, including your
resolved link markup. This stylesheet is also useful when reviewing the results of
custom CCF filters and how CCF file changes impact the resulting markup.

■ Arbortext-path\lib\xsl\debug\identity.xsl — An XSL
stylesheet that outputs an unstyled document that is the result of the input XML
being processed by the composition pipeline. Reviewing this result can be useful
when passing documents with resolved link markup to Arbortext Styler or other
custom processes.

Configuration validation
DLM now examines .dlmcf configuration files for potential problems, generating
a detailed report of errors and warnings. When running Arbortext Editor, the error
report is displayed in a dialog box. When running Arbortext Publishing Engine,
the error report is written to a log file.

Automatic validation of DLM configuration files is enabled by setting the

dlmautovalidateconfig set option to on.

13
Release Notes for Arbortext Editor, Styler, and Architect

Session status monitor

Previously, a lost DLM session was not detected during registration until after
substantial processing prior to the actual registration. This release introduces the
dlmsessionheartbeat set option and Advanced Preference. When a session
is established by connecting to the DLM server, the session monitor automatically
starts and checks the status of the session when the configured number of seconds
has elapsed. If the monitor detects an outage, the user is notified that the connection
to the DLM server has been lost and is presented with the option of reconnecting
or working offline.

Database archiving
Many DLM-related problems are site-specific and are tied to the database state at
the time errors occur. This release includes a database archiving tool which exports
the contents of the database to a compressed archive. PTC Support can use the
same tool to recreate the database, greatly improving the chances of reproducing
the site-specific issues.

DLM toolbar
A new DLM toolbar provides quick access to common DLM actions such as
moving between links in a document, opening the DLM Explorer, and registering a
document. The DLM toolbar is available only when a DLM document is open in
Arbortext Editor.

Updates to existing features

The following DLM features are updated in this release .

Memory performance improvements

To improve registration performance, this release introduces the
ability to break registration into more manageable pieces with
the dlmregistrationblocksize set option. The value of
dlmregistrationblocksize determines the amount of data processed
and sent to the DLM server in a single block of data. For example, setting
dlmregistrationblocksize to a value of 200 causes data to be sent to the
server every time 200 links or resources have been read from the document.

Content management system support

DLM now supported for use with the following repositories:

■ Arbortext Content Manager and Windchill PDMLink

■ Documentum Content Server (using Documentum Desktop Client or

Documentum Webtop)

■ IBM Document Manager

When installing Arbortext Editor with both DLM and a supported repository adapter,
integration between DLM and the adapter is enabled automatically.

14
 Chapter 2 Updates in this release

Usability improvements
■ The look of the Link Manager is simplified. Advanced information about links is
now displayed and concealed by clicking on the new More and Less buttons.

■ The DLM Explorer was a new menu selection, Tools→Where Used. Choosing
this new selection reports on links to the selected target.

■ Many informational messages related to DLM operation have been reworded to

improve understanding.

■ When viewing the contents of the DLM repository, the state of the displayed
objects is now maintained throughout your DLM session. You will no longer
need to traverse the DLM repository again to view the location of the most
recently used object. Contents of folders are now refreshed each time the folder is
collapsed and expanded.

■ Target property information is now available for targets in the Link Manager
search results and when viewing the contents of the DLM repository.

■ Client logging is now automatically enabled.

Configuration file changes

This release contains updates to two DLM-related configuration files: the .dlmcf
file and the DCAConfig.Properties file.

.dlmcf file changes

■ The format of the location URL specified with the ServiceLocation element has
changed. Previously, the URL had the format:

http://<server_name>:<port>/e3/services/DCAService

Beginning in this release, the DCAService portion no longer needs to be

specified. The new form is:

http://<server_name>:<port>/e3/services/

■ A new value, attr, is available for the pathType attribute on the Name and
Metadata elements. When creating TargetTag elements, set pathType to attr
when the path attribute specifies the name of an attribute set to the value to use
as metadata or a target name.

■ The .dlmcf has the following new and changed elements:

□ EnclosingTargetFolder — (New) Specifies that the folder of an enclosing

target element should be inserted within the folder path at this location.

□ LinkRefTag — (New) Specifies the name and attributes of an element to use

as a DLM link reference.

□ LinkRefTags — (New) Specifies the elements which may be used as link

references. The LinkRefTags section of the configuration file is unused when
authoring documents in inline linking mode. (The LinkTags section of the
configuration file is ignored when authoring in reference linking mode.)

15
Release Notes for Arbortext Editor, Styler, and Architect

□ LinkTag — (Changed) Now a child of both the LinkTags and

ServerLinkTypes elements.

□ ServerLinkTypes — (New) Specifies 0 or more LinkTag elements for use in

third-party links.

DCAConfig.properties changes
The optional property TRANSLATED_METADATA_NAME is new in the
DCAConfig.properties file. The value of TRANSLATED_METADATA_NAME
is the metadata name which can be used as a translated display name when browsing
the repository.

DLM markup resolution changes

The following DLM markup resolution changes are included in this release .

Resolution of link references

All resolved atidlm:link tags now have an atidlm:resolutionType attribute
describing how the link was resolved. It has the following possible values:

■ Inline — The link was resolved from an inline atidlm:link tag in the source.

■ ThirdParty — The link is a resolved third-party link drawn from the

repository, not represented in any markup in the source document.

■ ThirdPartyByReference — The link is resolved from reference-mode link

markup (a link reference) in the source document.

■ UNRESOLVED — The inline link or link reference in the source document refers
to a link that is not present in the DLM repository. This signifies a failure to
resolve the link.

In reference mode, the markup for the link reference itself will be represented in its
entirety within the atidlm:linkcontent element of the resolved link.

The resolution stylesheet for the document being resolved is used to style the
resolved link markup.

Resolution of third-party links

Resolved link markup for third-party link references is the same as for inline links,
except for the following differences:

■ The atidlm:link element has only atidlm:key and atidlm:branchLabel attributes.

■ A resolved third-party link does not contain an atidlm:linkcontent.

■ The atidlm:resolutionType attribute has the value ThirdParty.

16
 Chapter 2 Updates in this release

Resolution of language sensitive metadata

Each piece of metadata is stored in the DLM Repository with a locale identifier.
These identifiers are strings that start with a two character language code, followed
by an optional underscore, and ending with a two-character country code. For
example, fr_FR. The locale identifier value xx_XX represents the case where the
locale does not matter.

This version of DLM introduces two new algorithms to determine the metadata
to include during resolution. Each algorithm uses the locale identifier for the
metadata item in the repository. Each algorithm uses the composition pipeline
CCF parameter dcam.Locale for the requested locale. The algorithm to use is
controlled by the value of the composition configuration file (CCF) parameter
dcamMetadataLocaleResolution.

API changes
The following DLM-related API changes are included in this release .

Java API updates

The DLM Java API is significantly updated in this release. Following is a summary
of the updates. Refer to the DLM Javadoc at Arbortext-path\docs\
javadoc\dlm for a detailed description of the Java API.

DLMClient interface
DLMClient has the following new methods:

int getLinkingMode();

Returns the linking mode (DLMClient.REFERENCE_MODE or

DLMClient.INLINE_MODE) currently in use by the DLM client.

void setLinkingMode(int linkingMode );

Sets the linking mode for the DLM client to the mode specified by linkingMode
(DLMClient.REFERENCE_MODE or DLMClient.INLINE_MODE).

DLMDocSet getCurrentDocSet();

Returns the document set currently in use. By default, registration and link creation
occur in the context of the current document set.

void setCurrentDocSet(DLMDocSet docSet);

Sets the current document to the document set passed in. By default, registration and
link creation occur in the context of the current document set.

DLMDocSet interface
DLMDocSet has the following new method:

DLMObjectIterator getLinks();

Returns all third-party links associated with a document set.

17
Release Notes for Arbortext Editor, Styler, and Architect

DLMDocument interface
New methods
DLMDocument has the following new methods:

int getLinkingMode();

Returns the linking mode (DLMClient.REFERENCE_MODE or

DLMClient.INLINE_MODE) for the document.

void setLinkingMode(int linkingMode );

Sets the linking mode for the document to the mode specified by the passed in String.

Changed methods
DLMDocument has the following changed methods:

void insertLinkAt(DLMLink link, , Range location, , String markupType,, String

namespaceURI);

Inserts markup for a given link at the specified range in the document using
the tag name specified by markupType. If inserting a link in inline mode, the
namespaceURI parameter is ignored.

void appendLinkToNode(DLMLink link, , Node node, , String markupType,,

String namespaceURI);

Appends the given link to the children of the given node using the tag name specified
by markupType. If inserting a link in inline mode, the namespaceURI parameter is
ignored.

void insertLinkBefore(DLMLink link, , Node refNode, , String markupType,,

String namespaceURI);

Inserts the given link before the specified node using the tag name specified by
markupType. If inserting a link in inline mode, the namespaceURI parameter is
ignored.

DLMFolder interface
DLMFolder has the following changed methods:

DLMObjectIterator getContents(int typeFilter, , DLMDocSet docSetFilter);

Retrieves objects contained in the DLM folder filtered by type and document set.

DLMKey interface
DLMKey has the following new method:

long getDocSetKey();

Returns the numerical document set key.

18
 Chapter 2 Updates in this release

DLMLink interface
DLMLink has the following new methods:

DLMLink cloneLink(DLMDocSet docSet);

Clones a link for use in a different document set. The newly created link has the
same properties and resource pairs as the calling link, but their respective document
set associations are different.

int getLinkType();

Returns the type (DLMLink.INLINE_LINK or

DLMLink.THIRD_PARTY_LINK) for the link

DLMObjectIterator findAllDocSets();

Returns all documents sets which contain a link with the same link key as the
specified key.

DLMSession interface
New methods
DLMSession has the following new methods:

DLMLink createLink(DLMDocSet docSet);

This method creates a new link belonging to the document set specified by docSet.
Third-party links created in inline mode and all links created in reference mode
must be associated with a document set. In other words, these links must belong to
one and only one document set.

DLMObjectIterator findAllDocSetsForLink(DLMLink link);

Returns all of the document sets in which the passed-in link exists.

DLMObjectIterator cloneLinks(DLMLink[] links, , DLMDocSet docSet);

Clones an array of links for use in a different document set. This function returns a
DLMObjectIterator of newly created links with the same properties and resource
pairs as the passed in links, but their respective document set associations are
different.

Changed methods
DLMSession has the following changed methods:

DLMLink findLink(DLMKey key);

Because DLMKey now has a document set key attribute, links that belong to a
particular document set can now be found.

DLMKey createKey(long keyValue, , String branchLabel, , String profileGroup, ,

long docSetKey);

Generates a placeholder key which can be used with the findLink and findTarget
methods. This is an overload of an existing method in the API.

19
Release Notes for Arbortext Editor, Styler, and Architect

New ACL functions

The following DLM-related functions are new in this release. Refer to the Arbortext
Editor online help for details on each function.

Table 2–1 New ACL Functions

dlm_auto_logfile Returns the full path to the automatic DLM
client log file.
dlm_doc_get_linking_mode Returns the linking mode of a specific
document.
dlm_doc_set_linking_mode Assigns a linking mode to a specific document.
dlm_get_current_docset Returns the id and name of the current
document set.
dlm_get_recently_used_links_ Returns the maximum number of links
maxsize displayed on the Recently Used tab of the
Select Link dialog box.
doc_get_translation_locale Returns the translation locale of a specific
document if the document is a translated
version of another document.
doc_get_translation_orig_uri Returns the original URI value (if known) of
the document for which a specific document is
a translation.
doc_is_translation Determines whether a specific document is a
translated version of another document.
dlm_set_current_docset Sets the current document set to a specific
document set.
dlm_set_recently_used_links_ Sets the maximum number of links displayed
maxsize on the Recently Used tab of the Select Link
dialog box.
doc_set_translation_locale Sets the translation locale of a specific
document and marks the document as a
translated version of another document.
doc_set_translation_orig_uri Sets the original URI value of the document
for which a specific document is a translation
and marks the document as a translation.
dlm_verify_session Determines whether a valid DLM connection
to the DLM server exists.

New ACL hooks

The following DLM-related hooks are new in this release. Refer to the Arbortext
Editor online help for details on each hook.

20
 Chapter 2 Updates in this release

Table 2–2 New ACL hooks

componentnamehook This hook is invoked during DLM registration
to determine the display name for a document
component (file entity, Documentum object
boundary, and so on). This display name is used
to populate the document set members during
registration.
dlmmodechangedhook This hook is invoked when the dlmmode set
option’s value changes. The new value is passed as a
parameter.
dlmrefidtolinkidhook Takes a document ID and the link ID value stored
in a link reference element, and returns either a
numerical link ID for the link or an empty string if
the input value should be used.
dlmlinkidtorefidhook Takes a document ID and a numerical DLM ID,
and returns either the string to use in link reference
markup or the empty string to use the numerical ID.
oidlocalehook Called on the root OID of a document during
registration or publishing to determine the locale to
use for resource metadata. In this release, only the
root OID of a document will be passed to the hook
for performance reasons.

New and changed ACL set options

The following DLM-related set options (also available as Advanced Preferences)
are new or changed in this release. Refer to the Arbortext Editor online help for
details on each set option.

Table 2–3 New set options

set dlmautovalidateconfig Determines whether DLM configuration files
are automatically validated.
set dlmconfirmcmssession Determines whether users are prompted when
they try to register a DLM document when a
DLM-enabled CMS adapter is installed, but
they are not logged on.
set dlmmode Specifies the default linking mode for new
DLM documents.
set dlmregistrationblocksize Determines the amount of data processed and
sent to the DLM server in a single block of
data.
set dlmresolveserverlinks Determines whether to insert resolved markup
for each third-party link in the published
document when the third-party link source is
part of the document being published.
set dlmsessionheartbeat Determines whether the DLM session status
is monitored.

21
Release Notes for Arbortext Editor, Styler, and Architect

Composer configuration file (CCF) changes

The following DLM-related composer configuration file (CCF) parameters are new
in this release.

Table 2–4 New composer configuration file parameters

dcamThirdPartyLocation Determines the point at which third-party
links are resolved during composition.
dcamThirdPartyLocation can be either of
the following values:

■ afterStart — (The default.)

Third-party links are resolved immediately
after the start tag of the link’s source
element.
■ beforeEnd — Third-party links are
resolved immediately before the end tag
of the link’s source element.

Third-party links are not resolved

during composition unless the
dlmresolveserverlinks set option is
set to on.
dcamMetadataLocaleResolution Controls which metadata is included
during the resolution process.
dcamMetadataLocaleResolution can
be any of the following values:

■ BestMatch — (The default.) DLM

examines all of the metadata records with
the same name for the link target and only
returns the best match by locale.
■ PreciseMatch — A metadata record
is returned when the locale in the record
exactly matches the requested locale and
when the locale in the record has the
format xx_XX (for example, en_US).
Two metadata records are returned when
an exact match occurs and a locale with
the format xx_XX exists in the repository.
■ All — Returns all metadata records
found for the target.

Previous versions of DLM

resolved metadata as described for
PreciseMatch. Beginning in this
release, BestMatch is the default value
of dcamMetadataLocaleResolution, which
may result in metadata resolution differences
from previous releases.

22
 Chapter 2 Updates in this release

New processing instructions (PIs)

The following DLM-related PIs are new in this release. Refer to the Arbortext Editor
online help for details on each PI.

Table 2–5 New PIs

_translation Identifies the document as having been (or being)
localized to other languages. When this PI is present
in a document, certain Arbortext Editor and Arbortext
PE features are disabled, prohibiting changes to the
document which otherwise would not be reflected in
the localized version.

Menu and dialog box changes

The following DLM-related menu and dialog box changes are included in this
release .

Changed menus
■ Tools menu — Choosing Tools→Dynamic Link Manager presents a new
Validate Configuration menu item. Choosing Validate Configuration lets
you view errors in the DLM configuration file. Validate Configuration is only
available when a DLM configuration file is open in Arbortext Editor.

New and changed dialog boxes

This release contains the following new and changed dialog boxes. When using
DLM, click the Help button on each dialog box for detailed information about the
dialog box.

■ Add Links dialog box — (New) Add links to the current document set by
importing them from another document set.

■ Document Set Entry Properties dialog box — (Updated) Specify the properties
of a new entry in the current document set and edit the properties of an existing
entry in the document set.

■ Document Set Properties dialog box — (Updated) Restructure the dialog box to
better work with documents, document sets, and third-party links.

■ Link Outside Document Set dialog box — (New) Inserts, creates, or copies a
link reference when you attempt to insert or modify a link reference that does not
exist or is not in the current document set.

■ Preferences dialog box — (Updated) The DLM category has a new check box
option Check for a CMS Session Before Registration. When checked, you will
be prompted if you attempt to register a document when there is a DLM-enabled
CMS adapter installed, but you are not logged in.

■ Print Composed View dialog box — (Updated) A Document Set button is now
available when publishing DLM documents.

23
Release Notes for Arbortext Editor, Styler, and Architect

■ Search DLM Links dialog box — (Updated) Added the ability to search on link
keys and document sets.

■ Select Link dialog box — (New) Select the link or link reference to insert in
the current document.

■ Select Source & Target Resources dialog box — (New) Select the source and
target resources when authoring new third-party links in the DLM repository.

■ Select Target dialog box — (Updated) You can now filter the target list by
document set.

■ Third Party Link Properties (specific context) dialog box — (New) View and
update the properties of third-party links in a specific document set.

■ Third Party Link Properties (with contexts) dialog box — (New) View and
update the properties of third-party links across multiple document sets.

■ Validate Link and Validate Links dialog boxes — (Updated) Validate that links
contain at least one resource pair after profiling is applied. When in reference
linking mode, validate that link references use keys that exist for the specified
document set.

■ Validation Report dialog box — (New) View the link validation report generated
when using reference mode linking, define new links to correct unknown links
(link references not within the current document set), and import links form other
document sets to correct unknown links.

■ Configuration File Errors and Warnings dialog box — (New) View errors in the
DLM configuration file currently open in Arbortext Editor.

Miscellaneous ACL changes

The following ACL commands, functions, callbacks, and predefined variables are
new or changed in this release and not covered elsewhere.

■ The ACL set debugcomposition is new in this release. When this option
is on, Arbortext Editor creates a log directory for each composition operation
and stores the composer log and intermediate files for the composition request.
After each composition operation finishes, the log directory will be saved to a zip
archive and then the directory will be deleted.

When an application save directory is created on the Arbortext Editor client

using Tools→Save Application), the save directory will contain a file named
compose.zip. The zip archive contains the temporary directory for each
composition operation performed while set debugcomposition was set to
on. When Arbortext Editor exits, the temporary files will be deleted.

■ The ACL preview command has two new arguments in this release. The wait
option makes editing unavailable in Arbortext Editor until a preview request
completes. The nowait option (the default) allows editing in Arbortext Editor
while a preview request is being processed.

24
 Chapter 2 Updates in this release

What’s fixed
This release contains several fixes for issues identified by and with the help of
Arbortext customers. Fixes are categorized by general product area and are ordered
by Software Performance Report (SPR) number. Descriptions typically apply to the
specific reported issue.

Arbortext Editor fixes

The following fixes related to Arbortext Editor are included in this release.

Table 2–6 Arbortext Editor fixes

SPR Fix Description
1325032 and Comparing documents now succeeds in some cases that previously
1340902 resulted in "unknown error in compare" messages.
1334257 Opening a document that contains many XML inclusions with invalid
file or path names no longer results in a series of prompts that a
document path does not exist. These messages are now displayed in
a parser message window.
1338361 Fixed error in the handling of some WMF files that prevented correct
processing when printing.
1358556 Using Edit→Paste Excel now works properly with Excel workbooks
containing ampersands in the Excel file name.
1362946 The Insert Markup dialog box is now more robust in displaying
in-context tags when an alias map is being used.

Composition and publishing fixes

The following composition-related fixes are included in this release.

Table 2–7 Composition and publishing fixes

SPR Fix Description
1300817 The preview command now has a wait option. Specifying preview
wait causes Arbortext Editor or Arbortext PE Interactive to suspend
execution until the preview operation is complete and the preview
window opens.
1333677 The composer log is now properly set up for data merging operations
when performing XML-to-XML transformations on a PE server.
1333749 A column break no longer also forces a page break when occurring in
the final span of the page.
1336334 Using newline processing instructions (PIs) no longer causes unexpected
breakpoints. When a newline PI is used, fill is now used in any ragged
right paragraph. Previously, fill was only used if the newline PI was in a
paragraph in a table cell.

25
Release Notes for Arbortext Editor, Styler, and Architect

SPR Fix Description

1346731 Links in PDF files are now consolidated when they are adjacent and
point to the same target.
1350283 The formatting engine no longer generates overfull pages due to
instances where prespace is miscalculated.
1350472 A long line of characters in an index will now be broken even when
there is a soft keep specified in _sfe:IndexHeading and all letters of the
alphabet have been specified as brkafchr in the hyphrule.
1355925 The publication process no longer terminates unexpectedly when
formatting very large documents (> 20,000 pages) that require multiple
formatting passes.
1357191 Spaces within a link adjacent to an underlined phrase that were
previously underlined in error are no longer underlined.
1357867 When publishing content to the Web using an Arbortext Styler stylesheet,
scoped tables of contents now are produced inline (in the body frame).
1361461 Corrected issues with PE Services operation.
1363063 The composition engine now attempts to make all columns in a
multi-column span have optimum height, preferring to make them as
short as possible when the page is full.
1365051 When publishing documents with the deepcontentsplitting Advanced
Preference and set option set to on, pages with keeps violations that
may have previously published as overfull should no longer publish
as overfull.
1367024 All cross references now link to their targets in PDF files. Previously, in
some cases, the links were not active.
1370400 Composing a table with one column no longer produces a spurious
error message.
1370762 Applications that use layout::apply, including the built in line
numbering application, now have better line break fidelity.
1375530 The first underscore of a CJK string is no longer too wide when
following any string that is not underscored.
1381300 Formatting no longer misaligns multi-column material when content
is kept together with hard keeps.
1382626 Addressed issues causing paragraph formatting driven by a layout file
to be incorrect when words containing hyphens break over lines within
the word after the hyphen.
1409567 In certain rare circumstances, in XSL outputs from Arbortext Styler,
multiple cross references to an element in the same document would
point to the last such cross reference in the document instead of to the
target of the cross reference. This has been fixed.

26
 Chapter 2 Updates in this release

DITA application fixes

The following fixes related to the DITA application are included in this release.

Table 2–8 DITA application fixes

SPR Fix Description
1326027 The DITA Resource Manager now sets the navtitle attribute on topicref
or topicref specializations from a referenced topic’s navtitle, if there is
one. If a navtitle does not exist, the topic’s title is used. In previous
versions the navtitle attribute was set to the value of the referenced
topic’s title, and only if the title didn’t exist would the topic’s navtitle
value be used.
1364423 Reduced the time it takes to open a DITA Resolved Document for
Editing from DITA maps with larger numbers of topic references.
136893 and DITA topics with references containing IDs or href values longer than
1376436 60 characters now work correctly.
1370083 The case of file and path names is now preserved when an absolute
file or path name is changed into a relative file or path name as part of
ditapath processing.
1371056 When using the DITA Resource Manager, same-document
subtopic references will now be created correctly with the syntax
#topicid/elementid. Previously, the incorrect syntax
#elementid was used under certain circumstances.
1381608 The DITA Resource Manager now correctly sets the format attribute
to the value dita for Windchill CMS objects. Previously, the format
attribute would occasionally be set to the value other.
1405461 In DITA documents, correct links are now generated for same-topic
element references when the element being referenced is a separate
CMS object.

Dynamic Link Manager fixes

The following Dynamic Link Manager -related fixes are included in this release.

Table 2–9 Dynamic Link Manager fixes

SPR Fix Description
1274727 Improved the comments in the SQL Server database migration script
from 5.2 to 5.3.
1299753 Many repeated registrations no longer causes Oracle cursor limits to
be exceeded.
1308919 When an apostrophe is included in a search of the DLM repository, the
search no longer fails with a malformed SQL database error.
1312144 Improved DLM performance when registering a document with a large
database.

27
Release Notes for Arbortext Editor, Styler, and Architect

SPR Fix Description

1338839 When inserting a link using the Link Manager, the inserted markup now
properly matches the selected markup type.
1347873 Migrating from 5.1 and earlier versions of DCAM (DLM) no longer fails
when invalid links are encountered. Now, when a 5.1 link with a link
ID that does not exist in the repository is encountered in a document,
the 5.1 link is converted into a new link pointing to the Undefined
target, and the link is given a new ID. A comment is inserted before the
broken link providing its original ID.
1372447 If registration fails, DLM is now capable of reverting the document to
its unregistered state, regardless of the number of link changes being
registered.
1403904 DLM markup changes now correctly force Documentum to create a
new version of an object on check-in, even when there are no other
changes to the object.
1406600 When setting the protectdlm set option to off, you can now open a
document from a previous version of DLM programmatically without
triggering a migration prompt. After opening the document, you should
set protectdlm to on. Otherwise, DLM may not function properly,
leading to data corruption.

Arbortext Styler fixes

The following Arbortext Styler-related fixes are included in this release.

Table 2–10 Arbortext Styler fixes

SPR Fix Description
1229074 When composing a document with graphics referenced from the
stylesheet, HTML output types (HTML file, Web, HTML Help, and
DMP) no longer have missing graphics. (The graphics must be in a
directory included in the graphics path, be of a file format supported by
the Web browser, and be sized correctly.)
1405682 Arbortext Styler no longer terminates unexpectedly when clicking the
right mouse button over a control on the Gentext tab when a condition is
selected and Properties to editis set to an output without any properties.
1407024 Arbortext Styler now handles content tests for (Any element or text) or
(Text content) correctly in non-English locales.

28
 Chapter 2 Updates in this release

Arbortext Import/Export fixes

The following Arbortext Import/Export-related fixes are included in this release.

Table 2–11 Arbortext Import/Export fixes

SPR Fix Description
1358531 The MIF Import driver now supports table header and footer rows, as
well as table cell alignment values.
1367460 Generated text that contains _font processing instructions specifying
fonts with names having spaces in them and in which a word in the
font name starts with digits no longer causes a failure when exporting
a document to RTF.

Repository adapter fixes

The following adapter-related fixes are included in this release.

Table 2–12 Repository adapter fixes

SPR Fix Description
1354836 Importing or checking in an XML document using the Arbortext Adapter
to IBM Document Manager no longer fails silently if the document
references a graphic file that does not exist.

ACL fixes
The following Arbortext Command Language (ACL)-related fixes are included
in this release.

Table 2–13 ACL fixes

SPR Fix Description
1215957 Changed logic in the set pdfconfigfile command so that relative names
such as standard.pdfcf are searched for in the \document,
\doctype, \custom\lib, and \pubdir directories. Previously
only absolute names were handled correctly.
1369388 Setting the set writenobreakattag option no longer causes empty tags
and PIs to be in SGML format instead of XML.

29
Release Notes for Arbortext Editor, Styler, and Architect

AOM fixes
The following AOM-related fixes are included in this release.

Table 2–14 AOM fixes

SPR Fix Description
1348997 Fixed importNode() method to work correctly when importing from an
XML document to an SGML document.
1363600 When a huge number of AOM methods are called from Java to traverse
a big document during the creation of a XUI dialog, Arbortext Editor
performance no longer degrades.

30
APPENDIX
A
INCLUDED 5.3 M020 UPDATES
Arbortext Editor changes.........................................................................................31
Arbortext Import MapTemplate changes ................................................................36
Arbortext Adapter to IBM Document Manager support for DITA documents...36
PTC Server connection and multiple Arbortext Publishing Engine sessions ......37
PTC Server connection and Windchill ProjectLink...............................................37
Dynamic Link Manager availability .......................................................................38
Miscellaneous ACL changes ...................................................................................38
What’s fixed..............................................................................................................38

The following updates from the 5.3 M020 release are also included in this release.
The descriptions detail these features as introduced in that release. Go to the Support
area of www.ptc.com for release notes covering earlier releases of Arbortext Editor.

Arbortext Editor changes

The following changes to Arbortext Editor have been made in this release.

JRE updated
The Java Runtime Environment (JRE) has been updated to version 1.5.0_11 in
this release.

JVM allocation changes

The default maximum size of the Java Virtual Machine (JVM) memory allocation
pool has been increased from 128MB to 256MB. If this change causes Arbortext
Editor or Arbortext Publishing Engine to report an error finding the Java runtime
environment, use the javavmemory set option to reduce the amount allocated.

31
Release Notes for Arbortext Editor, Styler, and Architect

Intelligent graphics support

This release adds support for intelligent graphics to Arbortext Editor. An intelligent
graphic is a type of graphic that includes metadata enabling interactivity. Types of
interactivity include moving the image, zooming in and out, rotating the image,
and selecting parts of the image.

You can perform the following operations with intelligent graphics:

■ Insert intelligent graphics into your document.

Only CGM, EDZ, and ISO intelligent graphics on the Windows platform are
currently supported.

■ Manipulate the display of an intelligent graphic in the Arbortext Editor window.

■ Link to different views stored within an intelligent graphic.

A view is a predefined version of an intelligent graphic that is stored within the

graphic. An intelligent graphic can have several views defined in its graphics file.

■ Publish intelligent graphics.

For more information, refer to the Intelligent graphics overview topic in the
Arbortext Editor online help.

User interface changes to support intelligent graphics

The following changes in the Arbortext Editor user interface support intelligent
graphics:

■ New View→Toolbars→Intelligent Graphic menu choice

■ New Intelligent Graphic toolbar

This toolbar is only for EDZ graphics.

■ Modified dialog boxes:

□ Insert Link — Contains a new View drop-down list when an intelligent graphic
is the target of a link.

□ Compose HTML File — Contains a new Convert Intelligent Graphics

checkbox.

□ Compose for Web — Contains a new Convert Intelligent Graphics checkbox.

For more information, refer to the help topics in the Arbortext Editor online help for
these user interface elements.

API changes to support intelligent graphics

The following new commands and functions support intelligent graphics:

■ set graphicdefaultwebformat — Specifies the graphic file format to

which intelligent graphics are converted when published to HTML.

32
 Appendix A Included 5.3 M020 updates

■ set intelligentgraphicsconversion — Specifies whether to convert

intelligent graphics to a web-friendly graphic format when published to HTML.

■ set isoviewdownloaduri — Specifies a URI where the Arbortext IsoView

web installer is located.

■ set isoviewfileformats — Specifies the graphic file formats that should

be displayed using the embedded Arbortext IsoView dialog in Arbortext Editor.

■ graphic_viewer — Returns the name of the embedded ActiveX dialog used to

display an intelligent graphic.

■ graphic_views — Fills an array with all of the views that are defined in an
intelligent graphic file.

■ oid_dialog — Returns the window ID of the XUI dialog associated with the
specified object identifier (OID).

■ oid_graphic_current_view — Returns the current view displayed for the EDZ or

ISO intelligent graphic referenced by the specified OID.

■ oid_graphic_viewer — Returns the name of the embedded ActiveX dialog used

to display the intelligent graphic identified by the specified OID.

The following changed commands and functions support intelligent graphics:

■ set graphicfilter — Now supports the EDZ and ISO graphic formats.

■ graphic_attr_name — Supports a new view role.

For more information, refer to the help topics in the Arbortext Editor online help for
these commands and functions.

Document type configuration (.dcf) file changes to

support intelligent graphics
The following changes to the Specials element in the document type configuration
file (.dcf) support intelligent graphics:

■ New GraphicDefaults element — Enables you to set the following default

settings for EDZ graphics:

□ defaultReproWidth — Specifies the default width for EDZ graphics displayed

in Arbortext Editor.

□ defaultReproDepth — Specifies the default height for EDZ graphics displayed

in Arbortext Editor.

■ Modified Graphic element — Defines the following new attribute for individual
graphics that enables you to modify an intelligent graphic:

□ view — Specifies the attribute that controls the initial view to display for an
intelligent graphic.

For more information, refer to the Enabling graphics support for a document type
and Setting defaults for EDZ graphics topics in the Arbortext Editor online help.

33
Release Notes for Arbortext Editor, Styler, and Architect

Namespaced attribute to support intelligent graphics

An additional attribute for intelligent graphics is defined in the
www.arbortext.com/namespace/graphics namespace. You can use this
attribute to define the initial view to display in an intelligent graphic. Refer to the
namespace web page for more information about this attribute.

Arbortext Styler support for intelligent graphics

The Graphic Details dialog box in Arbortext Styler has a new View role. This
role specifies the graphic attribute that controls the initial view to display for an
intelligent graphic.

For more information, refer to the Graphic Details dialog box topic in the Arbortext
Styler online help.

Arbortext Publishing Engine support for intelligent

graphics
A new parameter named graphic-web has been added to the Arbortext Publishing
Engine f=convert function. This parameter specifies whether intelligent graphics
in input documents are converted to a web-friendly graphic format (for example,
a GIF or JPEG graphic) during composition. Conversion of intelligent graphics is
only supported on the Windows platform.

For more information, refer to the Arbortext Publishing Engine Programmers’

Guide.
Note
When publishing, converting intelligent graphics to another graphics type with
Arbortext Publishing Engine is only supported on the Windows platform. For more
information on when intelligent graphics are converted during publishing, refer to
the Publishing an intelligent graphic topic in the Arbortext Editor help.

Intelligent graphics limitations

Be aware of the following issues with intelligent graphics support when using this
release:

■ The Arbortext Editor File→Print Editor View operation does not support
intelligent graphics.

■ If an initial view is set for an ISO graphic, that view is not used when publishing
to print or PDF. The default view is used instead. The default view is also used if
ISO graphics are converted to web-friendly graphics when publishing to HTML
or the web. The initial view is used when ISO graphics are included in published
HTML or web documents.

■ The Link/Xref tab on the DITA Application Resource Manager does not support
the view attribute for an intelligent graphic.

■ Arbortext Editor only supports 3D EDZ graphics.

34
 Appendix A Included 5.3 M020 updates

■ If you have used Arbortext Editor to view ISO or CGM intelligent graphics and
want to uninstall Arbortext Editor, be sure to log out and log back into your
system before uninstalling. This ensures that all Arbortext Editor components
are removed by the uninstall process.

Composing files for use with Digital Media

Publisher
A new composition output, For Digital Media Publisher, has been added to the
File→Compose menu choices. Arbortext Editor must be licensed for Web/Wireless
composition to enable this menu choice.

Composing a document for Digital Media Publisher (DMP) creates a set of HTML,
table of contents, and index files that can be used as source files when building
a project with DMP. When composing a document for DMP, you must use an
Arbortext Styler stylesheet. The stylesheet’s styles defined for HTML Help output
are used when composing for Digital Media Publisher.

Refer to the documentation accompanying the forthcoming 5.3 M020 release

of Digital Media Publisher for more details on working with files created using
File→Compose→For Digital Media Publisher.

press.pdfcf PDF configuration file removed

In previous releases, the PDF configuration file press.pdfcf was provided to be
used to create PDF/X output for prepress data interchange as part of a technology
preview . The file press.pdfcf is no longer included in the release. If you wish
to create PDF/X output, consider copying and modifying the <Compatibility>
settings in the existing print.pdfcf file. Refer to the pdfconfig DTD for
more information.

Because it is a technology preview, creating PDF/X output is not supported by

PTC Technical Support.

Copyright information changes

The Help→About Arbortext Editor→Version menu choice now provides both
version and copyright information.

The Help→About Arbortext Editor→Copyright menu choice has been removed.

35
Release Notes for Arbortext Editor, Styler, and Architect

Arbortext Import MapTemplate

changes
When migrating your Arbortext Import MapTemplates from 5.2 to 5.3, be aware of a
change in ppXML markup when importing FrameMaker MIF documents.

When processing documents with text runs alternating between italic and non-italic
text, Arbortext Import 5.2 did not include <SPECIALTEXT> wrappers around the
non-italic text. Beginning in the 5.3 release, <SPECIALTEXT> wrappers surround
the non-italic text. This change is not obvious in the MapTemplate Editor ppXML
display unless you refresh the ppXML by choosing Rerun Initial Transformation....
on the Source File menu.

This change of behavior is advantageous when the non-italic text needs its
own markup. A description of this change was missing from the 5.3 migration
documentation.

Arbortext Adapter to IBM Document

Manager support for DITA
documents
The Arbortext Adapter to IBM Document Manager provides new support for
managing DITA documents in the following areas:

■ Support for bursting DITA documents

The document-type-specific burst configuration file contains the following new

elements and attributes to support bursting DITA documents:

□ New customrefspec and customref elements that enable you to configure how
references in DITA documents are handled during a burst operation.

For more information, refer to the Configuring DITA reference importing topic
in the Arbortext Adapter to IBM Document Manager online help.

□ New filemapping attribute on the burstspec, element, attrbndryrule,

and xpathbndryrule elements that enables you to control the format used
for object reuse information.

For more information, refer to the Setting a document-type-specific burst

configuration and Configuring document object boundaries topics in the
Arbortext Adapter to IBM Document Manager online help.

□ New operation attribute on the namerule element that enables you to set
the condition under which a naming rule applies.

For more information, refer to the Configuring naming rules topic in the
Arbortext Adapter to IBM Document Manager online help.

□ New %import-filename%, %import-filename-ext%, and

%id-attr% sub-expressions for the expression attribute on the namerule
element that enable you to specify additional names for an object.

36
 Appendix A Included 5.3 M020 updates

For more information, refer to the Configuring naming rules topic in the
Arbortext Adapter to IBM Document Manager online help.

■ Default burst configuration files for all DITA document types

The following directory contains default burst configuration files for all of the
DITA document types:

Arbortext-path\adapters\com.arbortext.adapters.ibmdm\
bursting

■ Show in Resource Manager button on the Browser

This button displays the object currently selected in the Browser in the
appropriate tab in the DITA Application Resource Manager.

PTC Server connection and

multiple Arbortext Publishing
Engine sessions
If you are configuring an Arbortext Editor installation that is expected to run
multiple Arbortext Publishing Engine sessions, then do not assign a value
for the WindchillAdapterHomeDir parameter in the PTC Server connection
userprefs.xml configuration file. If you assign a value to this parameter, all
Arbortext Publishing Engine sessions running after the first session starts will
terminate with an error message similar to the following:

Failed to connect to the server

Number of conflicts found:2

K03_UWGM_CACHE_IN_USE:The server cache for

’http://i2928.acme.com/PDMPJL90’ is already
in use by another process and cannot be accessed in
this session.

K01_UWGM_WS_GOING_OFFLINE:Workspace forced to switch

to offline mode.

PTC Server connection and

Windchill ProjectLink
In this release, the PTC Server connection supports only Arbortext Content Manager
and Windchill PDMLink. If you connect to a Windchill server that has Windchill
ProjectLink in addition to Arbortext Content Manager or Windchill PDMLink,
ProjectLink projects might appear in the PTC Server connection Browser. However,
you cannot access these projects through the Browser.

37
Release Notes for Arbortext Editor, Styler, and Architect

Dynamic Link Manager availability

The Dynamic Link Manager is not available in this release. Areas of the
documentation, however, reference DLM as if it was available. DLM will be
available as a part of an upcoming maintenance release.

Miscellaneous ACL changes

The following ACL commands, functions, callbacks, and predefined variables are
new or changed in this release and not covered elsewhere.

■ The ACL set option and Advanced Preference featureDMPPublishing is

new in this release. This option enables and disables the File→Compose→For
Digital Media Publisher feature.

■ The doc_add_callback function has a new reference_modify callback type for

modifying DITA references.

What’s fixed
This release contains several fixes for issues identified by and with the help of
Arbortext customers. Fixes are categorized by general product area and are ordered
by Software Performance Report (SPR) number. Descriptions typically apply to the
specific reported issue.

Arbortext Editor fixes

The following fixes related to Arbortext Editor are included in this release.

Table A–15 Arbortext Editor fixes

SPR Fix Description
1282948 Addressed issues resulting in virtual memory errors when processing
certain XML inclusions used in generated text.
1324436 The Arbortext Editor table editor no longer re-recognizes a table when
the table’s processing instructions are modified outside the table editor.
1328433 Improved context checking performance for large documents.

38
 Appendix A Included 5.3 M020 updates

Composition and publishing fixes

The following composition-related fixes are included in this release.

Table A–16 Composition and publishing fixes

SPR Fix Description
1323416 Boxed regions no longer incorrectly break between the top box rule
and the contained graphic.
1325294 File names with special characters no longer cause formatting to fail.
1327799 On Solaris and Linux, PDF output of landscaped pages is now oriented
correctly in the PDF viewer.
1336433 Improved publishing of tables with vertical spans that break across a
page when publishing documents with the deepcontentsplitting set
option and Advanced Preference set to on.
1337432 Fixed a composition problem in Arbortext 5.3 where compound words
separated by a dash character were not being hyphenated as they were
in Arbortext 5.2. This problem was causing overfull lines in some
cases where there were long words.
1342043 Improved edge condition balancing of text with small leading.
1348408 Interaction of non-repeating floats with keeps:floatsout no
longer leads to overfull pages.
1349464 Page breaks no longer occur between vertically spanned rows of a
table that is in a region that is kept together.
1350029 A rule is now added to the bottom of the vertical span when the table
breaks between rows in that span.
1352115 Improved alignment of algrouped graphics breaking across a page.

Arbortext Import/Export fixes

The following Arbortext Import/Export-related fixes are included in this release.

Table A–17 Arbortext Import/Export fixes

SPR Fix Description
1293039 The Arbortext Import Lookup Map feature now correctly translates
lowercase character ranges.
1336308 Beginning in the 5.3 F000 release of Arbortext Import, when importing
FrameMaker MIF files, blank paragraphs were no longer imported
as ppXML <paragraph> elements. This update release provides a
Remove Blank Paragraphs MIF driver option that lets you specify
whether empty paragraphs should be imported or ignored when
importing FrameMaker documents. Remove Blank Paragraphs is
set to a value of false by default, which emulates how FrameMaker
documents were imported in the 5.2 version of Arbortext Import.

39
Release Notes for Arbortext Editor, Styler, and Architect

SPR Fix Description

After installing the update release on each workstation and Arbortext
Publishing Engine server, perform the following steps to configure
your site to use the new driver option:

1. On each Arbortext Editor workstation used for MapTemplate

development, open Arbortext Editor and choose
File→Import/Export→Import Workbench Configuration.
2. Click Update to update your Configuration Directory.

Note
If your Windows HOME environment variable is set to a network
directory, the APTIMPORTEXPORTHOME environment
variable must be set to your Arbortext Import/Export Import
Configuration directory. Otherwise, the Update button will be
disabled.

3. For each MapTemplate deployed on the Arbortext Publishing

Engine server, update the MapTemplate with the new option
setting by opening the template in the MapTemplate Editor,
resaving the MapTemplate, and redeploying it to the Arbortext
Publishing Engine server.
1336923 The Arbortext Import Workbench no longer causes a startup failure
when the contents of the Import Configuration Directory have been
deleted.

Repository adapter fixes

The following adapter-related fixes are included in this release.

Table A–18 Repository adapter fixes

SPR Fix Description
1205628 Temporary files used for repository objects how have file name
extensions, allowing for identification of file type.
1341549 Using the Arbortext Adapter to Documentum/WDK, changes are no
longer lost upon check in if an author checks out an entire document
and pastes a Documentum object reference into a child component
without making other changes.
1343102 Using the Arbortext Adapter to IBM Document Manager, searches
specifying multiple criteria no longer fail with the error “Invalid
dmLogicalOp value" in non-English locales.
1350906 The Arbortext Adapter to IBM Document Manager no longer checks
out graphic CMS objects with unrecognized types when the Object
And Descendents option is used.
1351165 The Arbortext Adapter to IBM Document Manager no longer deletes
an item completely from the Document Manager library if you attempt
to delete a specific version.

40
 Appendix A Included 5.3 M020 updates

ACL fixes
The following Arbortext Command Language (ACL)-related fixes are included
in this release.

Table A–19 ACL fixes

SPR Fix Description
1329778 The delete_tag callback type is now called when a PI is deleted using
the table editor.
1331657 oid_offset() once again returns the proper value when the cursor is
positioned inside text.

41
APPENDIX
B
INCLUDED 5.3 M010 UPDATES
Configuration changes..............................................................................................43
Arbortext Editor changes.........................................................................................44
Arbortext Import/Export updates.............................................................................44
Arbortext Help Center changes...............................................................................45
Dynamic Link Manager availability .......................................................................47
Miscellaneous ACL changes ...................................................................................47
What’s fixed..............................................................................................................47

The following updates from the 5.3 M010 release are also included in this release.
The descriptions detail these features as introduced in that release. Go to the Support
area of www.ptc.com for release notes covering earlier releases of Arbortext Editor.

The following sections describe the new and changed features in 5.3 M010. What’s
fixed on page 47 lists specific fixes included in this release as well as fixes included
in the 5.3 F000 release.

Configuration changes
Beginning with the 5.3 F000 release, the PTC Server connection is installed by
default. If you have the PTC Server connection installed, you cannot change your
Java class path once Arbortext Editor has started.

If you place your custom Java jar and class files in the <custom_dir>\classes
directory, the files will automatically be included in the Arbortext Editor Java class
path. If you must reference files outside the custom directory, do so by adding the
following line to a file in your <custom_dir>\init directory:

append_javaclass_path("<path_name>")

<path_name> is the list of directories the Arbortext Editor embedded JVM will
search to locate Java classes when Java methods are called from within Arbortext
Editor. Refer to the help topic append_javaclass_path for more details.

If you are not using the PTC Server connection, disable its loading by editing the
Arbortext-path\lib\feature.cf file to include the following line:

set featureAdapterWindchill=off

43
Release Notes for Arbortext Editor, Styler, and Architect

Arbortext Editor changes

With this release, a new \ditarefs directory has been added to the custom
directory. This directory and its first level of subdirectories are searched for content
referenced from DITA documents. If you are upgrading from a release prior to 5.3
F000, also review the significant updates to Arbortext Editor, particularly those
relate to DITA, described in Arbortext Editor changes on page 69.

When using this release, be aware of the following issue when inserting graphics.
When using the Insert Graphic menu to insert an image in a new document that uses
only the entity reference method, the automatically-assigned entity name will not be
set to the image’s file name if the document has yet to be saved. The work around is
to save the document before inserting the image.

Arbortext Import/Export updates

This release addresses several issues with Arbortext Import. Refer to Arbortext
Import/Export fixes on page 59 for a list of specific fixes. If you are upgrading
from a release prior to 5.3 F000, also refer to Arbortext Import/Export updates
on page 83 for a description of new features and configuration changes related to
Arbortext Import.

In addition to the listed fixes, the Arbortext Import Workbench now has menu
selections and buttons for displaying online help and the Arbortext Import/Export
Reference Manual for Importing Documents has been updated to support the new
features of Arbortext Import.

Be aware of the following items when using this release of Arbortext Import:

■ The Arbortext Editor File→Import/Export→Open Import Project and

File→Import/Export→New Import Project menu items are disabled until after
you have selected File→Import/Export→Import Workbench Configuration to
initialize your Configuration and Repository Directories. For more information
on initializing these directories, refer to the online help topic Import Workbench
Configuration dialog box.

■ When calling Arbortext Import MapTemplates, XSL processes, or external

applications from pre-processor or post-processor driver options, the new
keyword {RelativeDir} can be used to avoid hard-coded system paths when
referring to .std, .xsl, or other files called from the driver.

The resulting path is relative to the location of the calling MapTemplate (the
parent MapTemplate). The braces are required. Assume that {RelativeDir}
resolves to fully-qualified path with no trailing path separator (/ or \). You must
add the necessary path separator. For example:

{RelativeDir}/preprocess.xsl

Refer to the Customizers’ Guide for information on configuring your workstation

and site to use Arbortext Import/Export.

44
 Appendix B Included 5.3 M010 updates

Arbortext Help Center changes

The Arbortext Help Center was first introduced in the 5.2 M020 release. The
Help Center is a Digital Media Publisher (DMP) application that contains the
documentation for the following Arbortext products:

■ Arbortext Editor and all of its product options

■ Arbortext Architect

■ Arbortext Styler

■ Arbortext Publishing Engine

The Arbortext Help Center contains both HTML and PDF versions of the
documentation for these products. All of the documentation is available in HTML
format. The PDF manuals that are generally distributed with the products are also
included in the Help Center, as is the JavaDoc. Refer to the Arbortext Help Center
Overview in the Help Center for more information about the Arbortext Help Center
and its features. You can access the Help Center through the Help→Help Center
menu choice.

The following Arbortext Help Center additions and changes have been made in
this release.

Web browser support

The Arbortext Help Center is supported on the following web browsers and versions:

■ Internet Explorer 6.0

■ Mozilla Firefox 1.7 and above

■ Mozilla Navigator 1.7 and above

The Help Center contains an embedded browser based on Internet Explorer for
the Windows platform, but uses the installed Mozilla browser on the Solaris and
Linux platforms.

Note
The text size you set for the standard web browser on your system (for example,
View→Text Size in Internet Explorer) affects the size of the text displayed in the
Help Center.

Personal configuration
The Help Center now has a Configuration tab where you can customize the Help
Center to meet your individual preferences. You can change the Help Center
configuration for a single session or save your settings so they apply to future
sessions as well.

The following configuration areas are available:

■ Search Term Highlighting — Enables you to indicate how you want the Help
Center to highlight search terms in the search result documents.

45
Release Notes for Arbortext Editor, Styler, and Architect

■ Profile Settings — Enables you to indicate the types of documents you would
like to access in the Help Center, based on Arbortext product or type of user.

Miscellaneous Arbortext Help Center changes

This version of Arbortext Help Center also contains the following updates not
covered elsewhere:
■ When you invoke the Help Center from Arbortext Editor, an Arbortext icon
appears in the Windows taskbar notification area and remains available for the
current Arbortext Editor session. If you close the Help Center during that session,
you can double-click on that icon to quickly reopen the Help Center.

Note that this feature is only available on the Windows platform.

■ There is a new Help toolbar button that displays the Arbortext Help Center
Overview.
■ Search terms are retained in the Search field when you switch between simple
and advanced searches.
■ The advanced search now enables you to restrict your search based on Arbortext
product or user role.
■ When you open a document to which you have added a comment, the comment
opens automatically.
■ The book icons in the table of contents have links when there is a document
associated with them.
■ The JavaDoc table of contents entries have been reorganized to match the
JavaDoc overview format.
■ Tertiary index entries are now supported.

Limitations
Please be aware of the following limitations when using this release:
■ The Arbortext 5.3 M010 Release Notes for Arbortext Editor, Styler, and
Architect are not included in the Arbortext Help Center. Instead, the release
notes for the 5.3 F000 release are available in the Help Center. The 5.3
M010 release notes are available in the compressed archive release files
for the 5.3 M010 release and on the PTC Reference Documents web site
(www.ptc.com/appserver/cs/doc/refdoc.jsp).
■ No localized documentation is included in this version of the Help Center, and
there is not a Language tab. Localized documentation will be available in a later
release.
■ Performance might be slow when you initially invoke the Arbortext Help Center.
■ The first time you open the Index tab, you must allow the index to finish loading
before selecting a term.
■ Search term highlighting is not supported for PDF documents.

46
 Appendix B Included 5.3 M010 updates

■ Using the advanced search to target your search to different types of document
headers is not supported for PDF documents.
■ On the Solaris and Linux platforms, the Mozilla browser startup script must
accept command line arguments.

Dynamic Link Manager availability

The Dynamic Link Manager is not available in this release. Areas of the
documentation, however, reference DLM as if it was available. DLM will be
available as a part of an upcoming maintenance release.

Miscellaneous ACL changes

This section describes miscellaneous ACL commands, functions, callbacks, and
predefined variables that are new or changed in this release and not covered
elsewhere.
■ The new ACL hook, formaterrorhook, is called each time a warning or error is
generated while formatting a document.

What’s fixed
This release contains a significant number of fixes for issues identified by and with
the help of Arbortext customers. Fixes are categorized by general product area,
are ordered by Software Performance Report (SPR) number, and include issues
resolved in the 5.3 F000 and 5.3 M010 releases. Descriptions typically apply to the
specific reported issue.

Arbortext Editor fixes

The following Arbortext Editor-related fixes are included in this release.

Table B–20 Arbortext Editor fixes

SPR Fix Description
1197440 Arbortext Editor no longer displays repeating dialog boxes stating that
you cannot search for text in an element which does not allow text (a
singleton).
1198219 Adding a new column PI will no longer incorrectly restrict the depth
of subsequent columns on the page.
1198358 On Windows, shifted key mappings for non-US keyboards are now
handled correctly.
1198710 Installations are now performed per system rather than per user.
1198886 When deleting punctuation (commas, periods, and so on) after a word,
Arbortext Editor no longer incorrectly deletes the space following
the punctuation.
1199329 The middot character is now considered a valid XML character.

47
Release Notes for Arbortext Editor, Styler, and Architect

SPR Fix Description

1199512 XML character validation is now performed using the XML version
(1.0 or 1.1) from the current document.
1199753 Automatic updating of generated text on a table no longer causes
Arbortext Editor to terminate unexpectedly.
1199774 Improved rendering of CGM images.
1200132 Newly inserted tables are now drawn properly when completeness
checking causes additional markup to be added.
1200725 Inserting a tag template that contains a placeholder template field
now works correctly.
1201010 Arbortext Editor now correctly recognizes TIFF images in generating
PDF files without redundant conversion into GIF.
1201642 Arbortext Editor now correctly allows insertion of a link target in
some circumstances.
1201661 Insertion of processing instruction text that contains single or double
quotes is now handled properly.
1201907 Modified drag-and-drop checks for valid drop or paste locations
to allow the drop or paste to continue as a drop or paste when the
source and destination documents are of different document types.
In some cases, some markup may be omitted and the drop or paste
will succeed. If the drop or paste would be invalid, a message will be
display saying the drop or paste is not allowed.
1201971 The entity_flatten and doc_flatten ACL functions (and their aliases)
no longer cause Arbortext Editor to stop responding when an entity
declared as a file entity in the internal subset is declared as a text
entity in the document type. This also addresses the same issue for the
Convert Stylesheet feature on the Styler menu.
1202144 Fixed issues with Arbortext Editor not using the correct color for
change tracking content.
1202782 Arbortext Editor no longer autocorrects content in elements that are
not spelling checked.
1203356 Fixed issues with alignment inheritance in table entries.
1203377 Arbortext Editor no longer terminates unexpectedly when spanning
certain table cells when tracking changes.
1203744 DITA conref attributes are no longer included when a table selection
is copied and pasted.
1203833 The table row ruler is now drawn properly when a table is partially
scrolled off of the screen.
1203834 Arbortext Editor no longer writes the entity declarations that are
declared in parameter entities to the internal subset.
1203992 The fragmentheader set option and Advanced Preference is now
applied when created an XML inclusion.

48
 Appendix B Included 5.3 M010 updates

SPR Fix Description

1204035 Opening documents containing certain uncommon types of .gif
images no longer causes Arbortext Editor to display a Pixel Stack
Overflow in GIF file error message in the status bar.
1204150 Arbortext Editor now writes Japanese characters to entity declarations
properly.
1206559 Improved performance with large tables.
1207398 Limited the length of text displayed in the tree control to prevent
Arbortext Editor from terminating unexpectedly. All text is stored in
the stylesheet. Only the display text in the tree control is truncated.
When the XPath test is edited, all text is preserved.
1207717 The current Arbortext Editor window is now set as the foreground
window after a spawned process closes. This may cause the Arbortext
Editor Windows taskbar item to flash without Arbortext Editor coming
to the front of other open windows.
1208270 Arbortext Editor now supports schema at remote URLs that include
other schema referenced with relative paths.
1208917 Improved rendering of CGM images.
1210400 The inlineediting set option and Advanced Preference now controls
file-system documents referenced as XML inclusions.
1210568 Keyboard shortcuts that use the CTRL and SHIFT keys now work for
Canadian multi-lingual keyboards.
1210651 When searching a document by choosing Find→Find/Replace,
searching now also finds text that contains markup. For example, if
the document contains the content:
set to <literal>off</literal>
searching for “set to off” will find this occurrence. This
behavior does not apply if Match Markup is selected and the search
string contains tags.
1210814 The fragmentheader set option and Advanced Preference is now
functional.
1210940 Menus are no longer reloaded unnecessarily.
1211034 Fixed installer problem that corrupted file associations during a
modifying installation.
1211189 When using the Find/Replace dialog box to replace a string of
characters with a text entity, Arbortext Editor no longer reports
"Region to substitute is protected or read-only" and prevents you from
making the replacement.
1211729 Fixed issues with indenting in no tags mode.
1213121 Arbortext Editor now properly recognizes a text entity declaration in
the DTD when the declaration contains uppercase characters.
1213888 Fixed computation of the position in a screen line.
1214453 When opening an entity which was externally edited, Arbortext Editor
now correctly reloads the content in all cases.

49
Release Notes for Arbortext Editor, Styler, and Architect

SPR Fix Description

1215492 Arbortext Editor now preserves the line break that follows the <?Pub
Caret> in as-is elements.
1216145 The style (bold, italic, underline) toolbar buttons will now be applied
properly to all table cells when multiple cells are selected.
1216237 Arbortext Editor now immediately recognizes table markup as a table
when it’s pasted from the system clipboard.
1217432 Arbortext Editor no longer terminates unexpectedly when a document
is closed during its initialization.
1217504 The style (bold, italic, underline) toolbar buttons will now be applied
properly when the cursor is inside an empty element.
1219773 On Windows, shifted key mappings for non-US keyboards are now
handled correctly.
1221758 Fixed issues with drawing underlined content with a fixed underline
offset next to underlined content without a fixed underline offset.
1222187 When using the Find/Replace dialog box to search for terms that
exist before and after the current cursor location, Arbortext Editor
now properly wraps to the beginning of the document and completes
the search.
1226052 Fixed height of empty lines at the beginning of a table cell.
1227247 Fixed drawing of nested tables whose width is specified as a
percentage.
1227327 Fixed a problem with the representation of black-and-white PNG
graphics so scaling can favor black.
1227435 Added a new tooltip for tags that are not completely displayed due to
the width of the window or of a column.
1227548 Fixed issues with indenting within table cells.
1227826 Installations are now performed per system rather than per user.
1228317 On Windows, an attempt to access a protected WebDAV resource will
now result in a prompt for credentials.
1228927 On Windows, the command set menuaccelerators=off now works
as documented.
1232278 Fixed issues with vertical spacing within table cells.
1232401 Arbortext Editor now handles non-fixed namespace declarations.
1233278 Updated the prefix to "PE" for the names of import templates installed
on the Arbortext Publishing Engine server.
1236798 Arbortext Editor now properly handles the pasting of table markup
cells that replaces existing cells in a table.
1240812 Improved rendering of CGM images.
1242726 Fixed an issue where CALS tables could not be inserted in certain
structurally-valid locations.

50
 Appendix B Included 5.3 M010 updates

SPR Fix Description

1243042 Improved the algorithm for creating temporary files (for example, for
downloaded graphics) to allow many more names.
1243418 (UNIX) You can now specify that toolbars are hidden on UNIX using
the preferences file.
1244979 FOSI Editor panels now remain properly displayed if you choose
File→Print Preview.
1245473 On Windows, shifted key mappings for non-US keyboards are now
handled correctly.
1248741 Fixed installation issues with Windows workstations not having C:
drives.
1250712 Improved rendering of CGM images.
1251798 Addressed issues that caused Arbortext Editor to intermittently
terminate unexpectedly when pressing the ENTER key (or performing
other actions) with the caret placed to the right of a collapsed element.
1251895 When using the Find/Replace dialog box to replace all occurrences
of some highlighted text, the string that was originally highlighted is
no longer replaced twice.
1252735 Fixed the drawing of the continuation arrow in a table cell.
1253174 Arbortext Editor now exits gracefully, regardless of the COM setup.
1254912 Arbortext Editor no longer reports errors parsing large files with no
lone breaks.
1255923 Generated text acquired from an attribute value which contains the
’<’ or ’>’ characters will now properly show these characters in the
generated text.
1257960 Arbortext Editor is now able to validate the base64Binary type in
element content.
1260616 Arbortext Editor now properly disallows pasting at the end of a
document.
1260928 Fixed issue where a free-from element with allowed content is
considered as not allowing content.
1263783 Arbortext Editor now inserts required elements correctly with the
following DTD construct <!ELEMENT A (B+, C+, D+)>
1264494 Arbortext Editor now treats an undefined element as valid if it is a
descendant of a wildcard element and it meets the wildcard description
in the schema.
1266611 Using the Find dialog box to search for text that is longer than 8192
characters now works properly.
1267227 Arbortext Editor no longer terminates unexpectedly when the
tabletagdisplay set option and Advanced Preference is set to cycle.

51
Release Notes for Arbortext Editor, Styler, and Architect

SPR Fix Description

1267228 Some previous versions of Arbortext Editor did not validate attribute
values for namespace compliance. Arbortext Editor will now properly
ensure that there are no colons within the values of attributes of types
ID, IDREF(S), ENTITY(IES), or NOTATION.
1268367 (UNIX) When using the Find/Replace dialog box, the Find Next and
Cancel buttons now work properly.
1270754 (UNIX) The Find dialog box no longer moves downward when a
button is selected.
1271474 Improved rendering of CGM images.
1272238 The gentextdisableautoupdate set option and Advanced Preference
now accepts the value never specifying that generated text automatic
updates can be made to occur for documents of any size.
1272513 Arbortext Editor now recognizes the document type for an SGML
fragment when an extra space exists in the Arbortext fragment
comment area.
1273117 Arbortext Editor no longer incorrectly reports a document as read-only
when a user tries to display the QuickTag menu in an expanded file
entity.
1274010 Arbortext Editor now properly handles free-form alias files.
1275778 Fixed display of character entities in some situations.
1276887 Arbortext Editor now ignores the linefeed following the <?Pub *...
PI, allowing fragments to be used without generating warnings in both
mixed-content models and element-only content models.
1276909 The Arbortext Editor data merging feature now works properly with
query definition files located on UNC paths.
1280022 The Update on Compose data merging feature is now working
properly for FOSI-based composition.
1282411 Found elements are now properly expanded in the document map.
1283058 Table operations now implicitly lock a file entity.
1284061 Fixed the display of accents over characters in some situations.
1287653 Arbortext Editor no longer stops responding when opening documents
containing some CGM images that use TrueType fonts while not
logged in with administrative privileges.
1287769 Arbortext Editor no longer terminates unexpectedly with an assertion
failure related to the use of scoped time-independent FOSI variables.
1288281 Arbortext Editor no longer terminates unexpectedly when
automatically correcting content in some locations.
1289457 Fixed issues with the modify_current_query ACL function used
when merging data.
1289860 URLs with commas are no longer truncated when passed to a running
instance of Internet Explorer after a double click.

52
 Appendix B Included 5.3 M010 updates

SPR Fix Description

1290674 The Modify Attributes dialog box no longer warns about attribute
values that are not displayed.
1291854 Arbortext Editor no longer stops responding when scrolling in tag
mode in certain situations.
1293694 Typing and inserting text no longer slows when editing with
interactive spelling check enabled in documents that contain tables
when the text being inserted is in a paragraph one or two paragraphs
before the table or between two tables.
1293792 When parsing an instance using a document type with a .ptd file,
certain namespaced elements now match the element declared in the
document type.
1294797 Arbortext Editor no longer mistakenly prompts you to reload
externally modified content in some edit and save scenarios when the
saverenames set option and Advanced Preference is set to off.
1295797 XML inclusions which bring in large text fragments are now handled
properly.
1295833 Arbortext Editor now properly handles character entities in non-cdata
attributes.
1299091 CGM graphics containing some PNG bitmap elements no longer
display solid black.
1299296 Arbortext Editor no longer breaks lines at tag delimiters by default.
1300576 Inserting a tag with multiple cells selected will now apply to all cells.
1300935 The element names in the Quick Tags menu are now sorted properly.
1301338 XML inclusions declaring the xi:fallback attribute with an EMPTY
content model are now supported.
1303136 When using the Find dialog box to find terms before the current cursor
location, Arbortext Editor now properly wraps around the ends of
the document and finds the terms.
1305110 Custom tables with locally-scoped elements are now properly
recognized.
1306686 CGM images containing polygon sets with the join style set to
mitreand with a large default mitre limit now render properly when
published to PDF using the rasterize option.
1310294 Arbortext Editor no longer terminates unexpectedly when editing
a table caption that spans lines.
1312777 Arbortext Editor no longer writes unnecessary change tracking
markup.
1321184 When editing resolved DITA topics, you can no longer enter elements
that are allowed in ditabases, but not allowed in individual topics.

53
Release Notes for Arbortext Editor, Styler, and Architect

SPR Fix Description

1321240 Arbortext Editor no longer stops responding with some workstation
configurations with a particular (non-Arbortext) software component
loaded when a DITA document is opened or when the DITA Resource
Manager dialog is opened.
1324715 Arbortext Editor now works properly when you change a DITA
document to untagged mode and then change it back to tagged mode.
1328936 When using Column View, selecting multiple elements to move up,
move down, promote and demote no longer gives unexpected results
or leaves the wrong elements selected following the operation.

Composition and publishing fixes

The following composition-related fixes are included in this release.

Table B–21 Composition and publishing fixes

SPR Fix Description
1197016 On Windows, CJK fonts with no bold, italic, or bolditalic faces will
automatically appear with simulated bold or italic faces if so requested.
1198985 Table cell horizontal alignment now properly ignores the charvalue
unless text-align="char".
1199311 In the XSL FO table model, the properties break-after,
keep-with-next, keep-with-next.within-column,
keep-with-next.within-page are now supported on
fo:table-row. They are used to help compute the break penalty
on a row.
1200019 Wrapping as-is lines in XSL-FO documents now works as expected.
1200548 For PDF documents created using File→Compose PDF File with
the usedistiller set option and Advanced Preference set to off,
following a link in the PDF now scrolls the document such that the
target location is in the top part of the screen. Formerly, the document
was scrolled to the top of the page containing the target.
1201062 Fixed issues where the &cir; and &compfn; character entities
were printed using the wrong symbol.
1202525 FOSI generated text handling now works correctly if the variable
being saved to by a savetext is also referenced in the conrule
attribute. Also, FOSI generated text handling has been improved
when detecting infinite recursion when many levels of tag nesting are
involved for each level of recursion.
1202627 Arbortext Editor no longer terminates unexpectedly due to unresolved
entities in FOSI variable values tested by specval.
1202900 Fixed issues where the &circ; character entity definition was
printed using the wrong symbol.

54
 Appendix B Included 5.3 M010 updates

SPR Fix Description

1202996 Improved internal composition handling of file names with non-ASCII
characters.
1204070 Fixed issues with indenting within table cells.
1206758 Publishing will no longer terminate unexpectedly when controlling
deep content splitting tolerances from a .tmx file.
1210324 When publishing documents containing scaled images with
File→Compose→HTML File, the resulting images are now properly
scaled.
1210621 Touch up is now retained in composition output with profiling
specified
1210621 Fixed issues with using touch up Pis with profiled content.
1210938 Fixed issues where certain character entities such as &reg; were not
displayed with the proper vertical displacement or foreground and
background colors.
1211155 Fixed issues where characters from the Windows WingDings symbol
font were not printed properly in some cases.
1211271 Space is no longer introduced around processing instructions even
with indent="yes" set in the XSL stylesheet
1211625 (Windows) For PDF documents created using File→Compose PDF
File with the usedistiller set option and Advanced Preference set
to off, bold and italic rendering is now supported for CJK, Arial
Unicode MS, and other fonts that do not have native bold or italic
forms.
Refer to the documentation in Arbortext-path\doctypes\
pdfconfig\pdfconfig.dtd for information on adjusting the
angle of italic typefaces and strength of bold typefaces using the
simulation element and its children.
1214003 PDF bookmarks no longer include the literal string
<atidmd:bookmark> in certain instances.
1214091 Addressed issues with table cell width calculation when a
block-container is inside of a table cell
1215263 (UNIX) Improved the speed of composed printing of documents with
CGM graphics on UNIX. Also reduced the size of the print jobs for
these documents.
1216165 Inserting a list into a division or formal block no longer changes
cross-references to use the value of the last item in the list instead of
the division or formal block. This issue occurred when using FOSIs
created with Arbortext Styler.
1220759 Fixed a "Dimension Too Large" error that stopped composition
of documents containing very long hard keeps sections where page
breaking was disallowed even if pages got too long. Now a page break
is forced in these cases.

55
Release Notes for Arbortext Editor, Styler, and Architect

SPR Fix Description

1229610 (Windows) For PDF documents created using File→Compose PDF
File with the usedistiller set option and Advanced Preference set
to off, bold and italic rendering is now supported for CJK, Arial
Unicode MS, and other fonts that do not have native bold or italic
forms.
Refer to the documentation in Arbortext-path\doctypes\
pdfconfig\pdfconfig.dtd for information on adjusting the
angle of italic typefaces and strength of bold typefaces using the
simulation element and its children.
1231369 Publishing documents to PDF no longer fails with documents
containing links to URLs with addresses longer than 127 characters.
1239870 Added an extension to provide rules on the top and bottom of table
rows that have been broken across a page. This is controlled using a
.tmx file.
1244386 For PDF documents created using File→Compose→PDF File with
the usedistiller set option and Advanced Preference set to on, the
Euro currency sign (€) no longer renders unexpectedly in place of
other characters.
1244386 The Euro sign may be used in Bookmarks in PDF files created
using File→Compose PDF File with the usedistiller set option and
Advanced Preference set to off.
1245442 For CALS tables using the SGML DTD fragment, vertical cell
alignment for cells within the <thead> element are now properly
being inherited from the <thead> element.
1256361 Table column width is now set to
proportional-column-width(1) if not explicitly specified.
1258790 Improved breaking of table content with vertical spans when the
deepcontentsplitting set option and Advanced Preference is set to on.
1261000 Corrected page breaking issues when publishing documents with
deepcontentsplitting set to on.
1261027 If CJK characters are underscored and the line is stretched (also known
as “tracking”), gaps between the underscores will no longer appear.
1263006 Corrected issue where table rules may be missing when publishing
documents with deepcontentsplitting set to on.
1264130 When choosing Edit→Profiles→View Profiled Document, the
selected or associated stylesheet is now used to render the document
instead of the default stylesheet.
1265329 Hyphenation of a word at the start of a paragraph when within a link
or when a target of a link is now allowed
1266923 When publishing documents with the deepcontentsplitting set option
and Advanced Preference set to on, horizontal cells rules are now
maintained at the bottom of the page when tables break between rows.

56
 Appendix B Included 5.3 M010 updates

SPR Fix Description

1266964 Corrected issues when publishing documents with
deepcontentsplitting set to on where page breaks were
occurring in elements that do not allow page breaks.
1266951 Certain floats (for example, repeating table heads) no longer appear
when many float classes are defined in the stylesheet.
1268252 When using change bars, the extra prespace before a table (causing
misaligned tables) is now gone.
1268300 Eliminated debug message displayed when choosing File→Save As
HTML.
1269367 Boxed regions using dashed borders now publish properly with the
deepcontentsplitting set option and Advanced Preference set to on.
1272919 The e-i-c choosing code now properly handles elements not in the
document type.
1275328 Hyphenation of a word at the start of a paragraph when within a link
or when a target of a link is now allowed
1275451 Tables in Styler XSL-based outputs are now counted properly
(ignoring tables in generated text).
1280199 The size of PDF files produced using Arbortext Styler stylesheets
has been reduced in most cases.
1281259 Fixed off-by-one problem with the scope of repeating floats.
1281502 Short columns at the bottom of a nearly full page are now allowed to
stretch to fill the page, even if the page break is forced.
1282074 Addressed a regression which produced empty page faults when
formatting a document with repeating floats.
1283631 An HTML file can be composed successfully even if the name of the
document path contains Japanese characters.
1287096 Non-frame ruling for tables in Arbortext Styler HTML-based outputs
is now properly obeyed.
1294347 Test values (specvals) with the settings attloc="system-var"
and attname="screen-only" are now correctly recognized and
handled the same as if attname were set to editor-only.
1297898 <_font> PIs no longer display as visible <span...> markup in
the browser window when using an Arbortext Styler-exported
XSL-HTML stylesheet to style XML files in Internet Explorer 6.0.
1300188 Nested tables that are broken across a page between rows will now
maintain the table rule at the bottom of the page.
1306213 Addressed issues with adding atipl namespace markup to pages
with multiple page-bottom floats (such as footnotes).
1310316 A page is no longer allowed to end in a table with only a header and/or
a footer when the first table row has prespace.
Publishing no longer fails when processing certain stylesheet
1333650 savetext categories.

57
Release Notes for Arbortext Editor, Styler, and Architect

Arbortext Styler fixes

The following Arbortext Styler-related fixes are included in this release.

Table B–22 Arbortext Styler fixes

SPR Fix Description
1197200 Use of Insert→Element Content and Insert→Attribute Content in
Arbortext Styler generated text or headers and footers, and use of
XPath Tests in conditions are now much less likely to cause slow
performance.
1199273 In Arbortext Styler stylesheets, choosing Insert→Attribute Content
now works for generated text that appears before or after the element
content. In FOSIs, #CONTENT(attrname) now works with
placemnt="after".
1204165 In Arbortext Styler XSL-FO output, page number references to
elements with a user assigned ID now work properly.
1207894 Fixed issues with some Arbortext Styler XSL-FO and XSL-HTML
cases where tables were generating titles improperly.
1208814 Custom table support has improved and now allows for variable
column widths.
1220340 Addressed issues where some titles in the Table of Contents were
missing their generated text (for example, their label and number)
with XSL outputs when the Arbortext Styler context had conditions.
In other cases, titles that shouldn’t have been included in the Table of
Contents were getting included.
1220354 Arbortext Styler stylesheets with edited FOSI source including
putgraph elements will not introduce line breaks in graphic path
names. This prevents segment violations.
1231934 Addressed certain cases where DITA hierarchical numbering wasn’t
working properly.
1237204 Arbortext Styler will display "Has source edits" in the Description
area for elements with edited source. The color of this text can be
changed with the new stylerhassourceeditsfontcolor set option and
Advance Preference.
1243137 Arbortext Styler will now always save stylesheets with Arbortext
PI’s regardless of the setting of the writepi set option and Advance
Preference.
1251899 Fixed a problem in the New Attribute Test dialog box so that UFEs
and SFEs are not shown in the ancestor list.
1252900 Arbortext Editor no longer stops responding or terminates
unexpectedly when XPath expressions are longer than 255 in XPath
tests of conditions in Arbortext Styler stylesheets or in attname
attributes of FOSIs. Arbortext Styler allows you to enter expressions
450 characters long. In FOSIs, expressions of up to 1000 characters
are handled correctly.

58
 Appendix B Included 5.3 M010 updates

Arbortext Import/Export fixes

The following Arbortext Import/Export-related fixes are included in this release.

Table B–23 Arbortext Import/Export fixes

SPR Fix Description
1197425 Deleting an Input Rule node no longer triggers an error in the
MapTemplate Editor.
1200789 When using the MapTemplate Editor, a .NET exception no longer
occurs when you click the XPath Search button when using a schema
which employs a default namespace. You can now also search
schemas (including the SPL schema) by using an underscore as the
prefix for the default namespace. This fix also corrects an issue in the
DTD/Schema view of the MapTemplate Editor that caused import
statements in the schema to be handled incorrectly.
1201026 The ppXML schema and corresponding .style file have been
updated to reflect changes with this release.
1203941 The directory Arbortext-path\lib\importexport\data\
STDTemplates is now included by default as a path value for the
importexportpath set option and Advanced Preference. You can now
optionally remove this directory from the path list to better control
the MapTemplate list displayed to an author using Arbortext Import
on a client workstation to import documents. Be aware that you
must include Arbortext-path\lib\importexport\lib\
(included by default when using %D in the path) in the newly-defined
path.
1204232 A new sample MapTemplate, mif2dita.std, is included in
the folder <Arbortext-path>\lib\importexport\data\
STDTemplates\ArbortextSamples. Refer to the readme file
in Arbortext-path\samples for more information.
1206120 Deleting or renaming a child MapObject no longer triggers an error.
1210887 CJK Word documents can now be imported, including CJK text, style
names, and fields. CJK text is now supported in the import of MIF
documents. CJK documents, including text, style names, and fields,
can now be exported
1223061 When importing MIF files, special characters are properly imported
to Unicode characters file. Special hyphen characters are imported to
<BREAK> elements whose type attribute reflects the hyphenation
type.
1228848 The MapTemplate annotations in the sample files have been modified
to display more useful information to the Arbortext Editor user when
deployed on the PE server.
1232658 When importing Word documents, all character style names are now
properly identified.

59
Release Notes for Arbortext Editor, Styler, and Architect

SPR Fix Description

1233278 Updated the prefix to "PE" for the names of import templates installed
on the Arbortext Publishing Engine server.
1251994 The MapTemplate Editor now correctly loads XML schemas which
use default namespaces (such as S1000D schemas).
1256363 Support for converting embedded graphics to PNG has been improved
to support additional types of pasted images.
1262384 Contiguous footnotes no longer combine improperly into a single
footnote when importing from Word.
1262738 When publishing documents on Windows 2000, the character t is no
longer missing when using certain PostScript Type 1 fonts.
1266269 Support for importing footnotes in MIF documents has been improved.
1266273 SPECIALTEXT elements which contain only a single space are now
properly displayed in the MapTemplate Editor.
1266277, Recognition of inline format changes has improved during the import
1266278 of MIF documents.
1266902 When importing Word documents, paragraphs which contain character
styles assigned to the entire paragraph (including the paragraph
marker) now clearly delineate both the paragraph style and the
character style in the ppXML markup.
1269950 When importing Word tables which have minute discrepancies in row
and cell widths, Arbortext Import correctly creates the proper number
of columns and applies spanning where possible.
1270002 Arbortext Import now correctly recognizes special hyphen characters
when importing Word documents and imports them as BREAK
elements when the driver option Include Hyphens is set to true:

■ non-breaking hyphen (character 30 - CTRL_) imports as BREAK

type=non-breaking-hyphen.
■ soft hyphen (character 31 - CTRL-) imports as BREAK
type=soft-hyphen.

If Include Hyphens is set to false, special hyphens are

imported as normal hyphen text characters (character 45).
1270005 When composing very large documents to PDF on Windows,
the composition process may fail with an "Out of virtual
memory space" error message. This situation can occur when the
composition process encounters a Windows 2GB memory addressing
limitation. After installing this release, enable this fix by performing
the following steps.

CAUTION
Ensure that you make the following change exactly as described.
Incorrectly modifying system files can leave your workstation in an
unstable state.
Use the instructions at the following location on Microsoft’s web site
to update the contents of the file c:\boot.ini:

60
 Appendix B Included 5.3 M010 updates

SPR Fix Description

http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx

1273493 Corrected issues with algroup breaking when publishing documents

with deepcontentsplitting set to on.
1275330 You can now publish PDF documents on Linux with usedistiller set
to off.
1278174 Corrected issues with breaking in algroups containing soft keeps when
publishing documents with deepcontentsplitting set to on.
1278962 The composition pipeline now correctly handles the base_uri
parameter specified in the XSLT document(uri, base_uri) function.
The base_uri was previously ignored and the working directory was
used instead.
1281496 When importing RTF files, the deprecated LINK field is supported
when it points to embedded images. A new graphics conversion option
allows conversion of EMF graphics to PNG.
1281503 Support for special characters has been improved when importing
RTF documents.
1281509 When importing RTF documents using the Include Lists option,
ppXML <LIST> elements are no longer created when the option is
disabled.
1282138 When profiling, the current stylesheet is now properly used throughout
the formatting process. The default stylesheet is no longer used in
error.
1283026 mailto syntax in URIs is now properly processed when composing
to PDF.
1293775 In the MapTemplate Editor the Initial XML Representation window
now reflects the results of the last preprocessing run.
1299801 When importing MIF documents, special Marker types are now
supported.
1312674, Import and Export now work properly with file names containing
1312714 CJK characters.

Repository adapter fixes

The following adapter-related fixes are included in this release.

Table B–24 Repository adapter fixes

SPR Fix Description
1246449 When connected to a CMS, if a burst configuration file is not found
for the document’s document type, a status of "Unable to load
burst configuration file" is displayed.
1305173 The Arbortext Adapter to IBM Document Manager menus are now
displayed correctly in non-English locales.

61
Release Notes for Arbortext Editor, Styler, and Architect

SPR Fix Description

1309920 The Arbortext Adapter to IBM Document Manager can now browse
and search Document Manager libraries residing on servers in
non-English locales.
1327493 The Arbortext Adapter to IBM Document Manager no longer displays
the following error messages if the user is not a member of any
Document Manager Group:
Could not find a Java class for object
Cannot set ’WITHDRAW’ attribute to the item ’ShowInRMBtn’

1221487 Arbortext Editor no longer terminates unexpectedly if a user without

a home folder chooses Save As Object with the Arbortext Adapter
to Oracle CM SDK.
1259944 When connected to the Arbortext Adapter to Oracle CM SDK,
when the Object→Share Object menu item is selected, Arbortext
Editor will no longer attempt to check for boundary rules against the
selection if a burst configuration file is not found for the document’s
document type.
1295941 The Arbortext Adapter to Oracle CM SDK is now able to search for
objects that are encoded with the UTF-8 character set.
1206008 The Arbortext Adapter for Documentum/WDK now honors the
Documentum processing instruction <?dctm xml_app="ignore"?>,
not processing documents with this PI in the prolog.
1209030 The Arbortext Adapter to Documentum/WDK can now handle XML
Applications that have graphics set up with the link as peer
option.
1264387 The Arbortext Adapter to Documentum/WDK browser no longer
generates an exception error when you choose Edit from the Virtual
Document view in Arbortext Editor.
1271476 The Arbortext Adapter to Documentum/WDK now supports the
use of objects that specify XML as the value of the Documentum
format_class attribute of the dm_Format object.
1312936 The Arbortext Adapter to Documentum/WDK now performs inline
checkouts correctly when the Document Map view is being used and
the object content is collapsed.
1281964 The Arbortext Adapter to Documentum/WDK and Arbortext Adapter
to Documentum/XML now correctly handle the case where a change
tracking deletion entry covers a complete XML element.

62
 Appendix B Included 5.3 M010 updates

Arbortext Architect fixes

The following Arbortext Architect-related fixes are included in this release.

Table B–25 Arbortext Architect fixes

SPR Fix Description
1245365 Arbortext Architect no longer may create template documents that are
missing required elements.
1251809 The ENTER key now functions properly in the FOSI Editor when the
Quick Tags option is enabled.
1268958 The Arbortext Architect DTD Editor no longer fails to open document
types.

XUI fixes
The following XUI-related fixes are included in this release.

Table B–26 XUI fixes

SPR Fix Description
1204428 Users now can change the width of a combobox control in a XUI
toolbar by setting the width attribute of the <combobox> element.
1209385 The value attribute of the XUI <tablecontrol> is now set to the text in
the first cell of the selected row.
1245702 The size of a XUI textbox control can now be set to a size smaller
than its natural size.
1258676 The XUI tabbox control now issues a DOMActivate event when the
user presses CTRL+PAGEDOWN or CTRL+TAB to select the next tab.
1261754 File entities in XUI documents are now supported.

ACL fixes
The following Arbortext Command Language (ACL)-related fixes are included
in this release.

Table B–27 ACL fixes

SPR Fix Description
1210005 Fixed the find command to allow searching using alias names.
1210501 The write command no longer loads a stylesheet if the document was
opened with the doc_open() 0x200 flag.
1212084 The doc_incomplete() function now includes checking the schema
identity constraint construct.
1212944 The newline command now implicitly locks file entities.

63
Release Notes for Arbortext Editor, Styler, and Architect

SPR Fix Description

1214111 When creating a PNG file, oid_write_graphic now sets the graphic’s
resolution.
1218102 A second icon can now be set on an element using oid_set_icon().
1223333 The function declare_filep_entity now works correctly. It previously
gave an erroneous error message about the entity name.
1225110 Restored behavior of the tag_has_attr() function with respect to
undeclared attributes.
1261084 Arbortext Editor no longer terminates unexpectedly when
url_decode() is called with a string containing a percent (%) sign.
1263044 Calling cloneNode() upon an SGML tag no longer causes the
application to terminate unexpectedly.
1271029 APTOID PIs are no longer returned when calling the function
oid_contents on a cloned document.
1271386 oid_find_children() now properly handles content with change
tracking markup.
1274706 The command substitute -ais now synonymous with substitute -a
-wrap and substitute -a -nowrapdepending upon the value of the
wrapscan set option and Advanced Preference.
1303721 The find command no longer skips over tags when matching text if
the -t or -m option is given.
1305658 The write command now works properly if given a WebDAV URL
already locked by Arbortext Editor for a resource.
1323516 The use of the link and linkuri callbacks from the DITA application
has been reworked to not interfere with the use of these callbacks by
other applications.

AOM fixes
The following AOM-related fixes are included in this release.

Table B–28 AOM fixes

SPR Fix Description
1210629 The SAVE_NOHEADER (0x40) flag to the Adocument.save()
method now works as documented.
1303397 Proper context checking is now done when inserting content using
AOM.

64
 Appendix B Included 5.3 M010 updates

Miscellaneous fixes
The following miscellaneous fixes are included in this release.

Table B–29 Miscellaneous fixes

1213851 A new allowStyler option has been added to the .dcf file
<Options> element. When using Arbortext Editor without Arbortext
Styler, the Styler menu item will not appear if this option is set to
"no".
1249857 Arbortext Editor no longer creates an out-of-context document when
using the DOM to insert content into a document containing tracked
changes.
1258241 The pubcmd.exe utility now works correctly on Windows,
letting you issue an ACL command from a terminal window to an
epic.exe application running on a host machine.
1258938 javaendorseddirs now includes the default Arbortext Editor endorsed
directory. This avoids composition issues when javaendorseddirs is
set to a custom directory without also including the default directory.
1259371 Arbortext Editor now handles the case of a newly inserted element
being deleted before the prompt for its attributes is displayed.
1263789 Arbortext Editor no longer terminates unexpectedly when a table is
deleted using a DOM event.
1263971, Addressed context issues with schemas declaring elements with both
1264431 local and global scope or having complex types derived by extension.
1269552 DOM notifications are now sent when the change case operation is
performed.
1273934 Fixed so all Arbortext formatting tags (not just _touchup) follow the
.dcf file setting to disallow them.
1277209 Fixed the display of the More Windows menu to show the proper
window titles.

65
APPENDIX
C
INCLUDED 5.3 F000 NEW
FEATURES
Product installation changes ....................................................................................67
Configuration changes..............................................................................................68
Arbortext Editor changes.........................................................................................69
Arbortext Styler changes .........................................................................................81
Arbortext Import/Export updates.............................................................................83
Dynamic Link Manager availability .......................................................................89
Composition changes ...............................................................................................89
Arbortext XSL support ............................................................................................90
PTC Server connection (Windchill connection) changes ......................................90
Repository Adapter changes ....................................................................................90
XUI (XML-based User Interface) changes ............................................................91
Interchange no longer available for download.......................................................94
AOM changes...........................................................................................................94
Miscellaneous ACL changes ...................................................................................95
Environment variables..............................................................................................96
New manual for Arbortext PE programmers .........................................................97

The following updates from the 5.3 F000 release are also included in this release.
The descriptions detail these features as introduced in that release. Refer to the
Support area of www.ptc.com for complete release notes covering earlier releases
of Arbortext Editor.

Product installation changes

The following installation changes have been made in this release.

Arbortext Publishing Engine supports backward

compatibility for Arbortext Editor clients
The Arbortext Publishing Engine version 5.3 F000 is compatible with Arbortext
Editor version 5.2 M030 through Arbortext Editor version 5.3 F000. This backward
compatibility support allows sites to migrate their Arbortext Publishing Engine

67
Release Notes for Arbortext Editor, Styler, and Architect

upgrade first and then roll out upgrades to Arbortext Editor clients, reducing the
downtime associated with synchronizing upgrades for client and server.

Configuration changes
The following configuration changes have been made in this release.

PDF configuration file updates

There is a new default PDF configuration file, standard.pdfcf. Several new
elements and attributes have been added to enhance configuration in .pdfcf files:

■ The new Simulation element has two new child elements, Bold and Italics for
bold and italic face simulation.

■ The new Open elements sets the properties for opening the PDF file in the PDF
viewer.

■ The Color element has new defaultRGB, defaultGray, and defaultCMYK

attributes.

■ The Compression element has new quality and type attributes.

■ The FontName element has a new simulateMode attribute.

■ The PDF element has a new level value 1.6 for Adobe Acrobat 7.0.

■ The PDFX element has a new set of level values.

■ The Annotations tag has a new attribute nameddestToPage to convert named

destinations to page numbers.

The image resolution values in the .pdfcf files delivered with Arbortext Editor
have been increased to provide higher quality images in composed PDF files. This
change will result in PDF files larger than those created using earlier versions of
the .pdfcf files.

The Customizers’ Guide provides information about configuring PDF output using
.pdfcf files.

Arbortext Editor startup command syntax

With the Arbortext Editor startup command (epic.exe on Windows and epic
on UNIX), you can now launch multiple documents by specifying more than
one document file name. Refer to the Arbortext Editor online help topic Startup
command syntax for more details using Arbortext Editor startup commands.

Stylesheet presentation order

Stylesheet presentation order can be configured in the document type .dcf using
the new PEStylesheetOrder element. Refer to the online help topic Configuring
stylesheet order in a list.

68
 Appendix C Included 5.3 F000 new features

APTPRFWCF environment variable and epic.wcf

preferences file deprecated
The APTPRFWCF environment variable and associated epic.wcf file
are deprecated in this release. The settings from the old epic.wcf file are
automatically migrated to a new arbortext.wcf preferences file the first time
you invoke the upgraded Arbortext Editor. By default, the new preferences file is
stored in the user’s home directory. Note that the value of the old APTPRFWCF
environment variable is not automatically migrated. If you want to store the new
preferences file in a location other than the home directory, you must set the new
APTWCF environment variable.

Arbortext Editor changes

The following Arbortext Editor additions and changes have been made in this release.

DITA Application
The DITA (Darwin Information Typing Architecture) standard was pioneered at
IBM and is sponsored by OASIS (Organization for the Advancement of Structured
Information Standards), a not-for-profit, international consortium that drives the
development, convergence, and adoption of e-business standards.

OASIS defines DITA as “an architecture for creating topic-oriented,

information-typed content that can be reused and single-sourced in a variety of
ways. It is also an architecture for creating new information types and describing
new information domains based on existing types and domains.”

To support the DITA standard, Arbortext Editor provides the DITA Application.
The DITA Application is an optional product feature that provides a sophisticated,
flexible environment for authoring and publishing DITA documents. The DITA
Application is installed by default as part of a typical Arbortext Editor installation. If
you do not install the DITA Application, none of the DITA document types will be
available in Arbortext Editor.

The DITA Application provides customized configurations for authoring DITA

topics and DITA maps. The application also provides a new Arbortext Editor
document view called Column view and a new tool called the Resource Manager
that assists you with locating content to include in your DITA maps and topics. These
tools greatly assist you with authoring DITA maps by enabling you to locate content
to include in a DITA map, to quickly insert references to one or more documents
into the map, and to rearrange the map hierarchy with great flexibility. The Arbortext
Editor configuration for editing DITA documents is highly configurable, so you
can customize it to suit your work style.

Once you have authored a DITA document, the DITA Application enables you to
publish a DITA topic or map to several different output types. Default stylesheets for
all of the DITA document types are included with the DITA Application. Arbortext
Styler enables you to customize and enhance these stylesheets or to create your
own stylesheets for DITA documents.

For more information on the DITA Application, refer to the Authoring DITA
documents section of the Arbortext Editor online help.

69
Release Notes for Arbortext Editor, Styler, and Architect

Resolved document for editing

The DITA Application enables you to produce an assembled version of your DITA
map called the resolved document. The resolved document contains all of the content
referenced in the map. You can produce a resolved document for your DITA map
through the Edit→Edit Resolved Document→For Editing menu choice. When you
select this menu choice, the DITA Application assembles all of the content in your
DITA map into an intermediary XML document and opens that resolved document
in a new Arbortext Editor window.

The resolved document enables you to edit the topics included in your DITA map.
It also enables you to execute a spell check or find/replace operation for all of the
topics referenced in your map. Any changes you make to the content of the resolved
document are saved to the relevant source documents referenced in the map.

For more information, refer to the Authoring DITA maps topic in the Arbortext
Editor online help.

User interface changes

The DITA Application provides the following updates to the Arbortext Editor user
interface:

■ Column view — A new Arbortext Editor view specifically designed to support

document types that primarily consist of element and attribute content.

Column view combines a hierarchical view of a DITA map with a series of rows
and columns, similar to a spreadsheet, where you can view and edit the attributes
of the elements in the map. You can use the Column view hierarchy to arrange the
elements in your DITA map. From a map, you can also open and edit referenced
documents in separate Arbortext Editor windows. For more information, refer to
the Authoring DITA maps topic in the Arbortext Editor online help.

■ Resource Manager — A new Arbortext Editor dialog box containing tabs that
enables you to manage the references in your DITA topics and maps.

The Resource Manager tabs enable you to insert content references, topic
references, images, links, and cross references into DITA documents. The
Resource Manager also enables you to create a new DITA topic and insert a
topic reference to that topic into your DITA map. For more information, refer to
the Resource Manager overview topic in the Arbortext Editor online help.

■ Insert Relationship Table dialog box — A new Arbortext Editor dialog box
enabling you to define a relationship table and insert it into a DITA map.

For more information, refer to the Insert Relationship Table dialog box topic in
the Arbortext Editor online help.

■ DITA Application toolbar — A new Arbortext Editor toolbar enabling you to

move topic references and other elements in the hierarchy of a DITA map.

For more information, refer to the DITA Application toolbar topic in the Arbortext
Editor online help.

■ Resource Manager button on the Edit toolbar — Invokes the Resource Manager.

70
 Appendix C Included 5.3 F000 new features

■ Modified dialog boxes:

□ Modify Attributes dialog box — Provides a new browse button to invoke a

version of the Resource Manager for modifying href and conref attributes.
Also provides a new button to generate an ID value for id attributes.

□ File Locations category in the Preferences dialog box — Contains a new

DITA References option.

□ Columns category in the Preferences dialog box — Provides a new

preferences category for Column view options.

For more information, refer to the help topics for these dialog boxes in the
Arbortext Editor online help.

■ New and modified Arbortext Editor menu choices — Depending on the type of
DITA document you are editing, several menu choices might be added or changed
in the following Arbortext Editor menus:

□ File menu

□ Edit menu

□ View menu

□ Insert menu

□ Table menu

□ Help menu

For more information, refer to the help topics for these menus in the Arbortext
Editor online help.

New environment variable

The new APTDITAPATH environment variable supports the DITA Application.
This variable specifies the default list of path names to directories used to locate
content referenced from DITA documents.

Document type configuration (.dcf) file changes

The following changes to the document type configuration (.dcf) file support
the DITA Application:

■ New NewTopicDialog element — Configures the document types to display in

the New Topic tab of the Resource Manager and in the Insert Relationship
Table dialog box.

For more information, refer to the Specifying the document types displayed in the
Resource Manager topic in the Arbortext Editor online help.

■ Modified Options element — The following options have been added to the
Options element

□ assignId — Enables and disables the user override of generated DITA IDs.

71
Release Notes for Arbortext Editor, Styler, and Architect

For more information, refer to the Enabling and disabling DITA ID assignment
topic in the Arbortext Editor online help.

□ ditaResolvedMapEditing — Enables and disables editing of text in

a resolved document.

For more information, refer to the Enabling and disabling resolved document
editing topic in the Arbortext Editor online help.

□ idAttribute — Specifies an attribute in the document type that should be

processed like an ID type attribute.

For more information, refer to the Specifying an ID attribute topic in the

Arbortext Editor online help.

Arbortext Styler support

Arbortext Styler provides new support for styling DITA documents in the following
areas:

■ Resolved document for styling — To assist you with styling DITA maps, the
DITA Application enables you to generate an assembled version of your map
called the resolved document for styling.

You can produce a resolved document for your DITA map through the Arbortext
Editor Edit→Edit Resolved Document→For Styling menu choice. When you
select this menu choice, Arbortext Editor assembles all of the content in your
map into a resolved document and opens that document in a new Arbortext
Editor window. You can then use the resolved document to style the content of
your DITA map.

For more information, refer to the Working with the resolved document topic in
the Arbortext Styler documentation.

■ Fallback generalization support for specialized DITA elements

The DITA standard class attribute enables an element to be labeled as

a specialization of another element. Output and other processing can treat
occurrences of the specialized element as if they were the base element used for
the specialization. This process is called generalization or fallback processing.
Arbortext Styler supports fallback generalization in several areas.

For more information, refer to the Working with specialized elements topic in
the Arbortext Styler documentation.

For more information on styling DITA documents, refer to the DITA styling overview
topic in the Arbortext Styler documentation.

PTC Server connection support

The PTC Server connection provides new support for managing DITA documents
in the following areas:

■ Support for bursting DITA documents

72
 Appendix C Included 5.3 F000 new features

The document-type-specific burst configuration file contains the following new

elements and attributes to support bursting DITA documents:
□ New customrefspec and customref elements that enable you to configure how
references in DITA documents are handled during a burst operation.

For more information, refer to the Configuring DITA reference importing topic
in the PTC Server connection online help.
□ New filemapping attribute on the burstspec, element, attrbndryrule,
and xpathbndryrule elements that enables you to control the format used
for object reuse information.

For more information, refer to the Setting a document-type-specific burst

configuration and Configuring document object boundaries topics in the PTC
Server connection online help.
□ New operation attribute on the namerule element that enables you to set
the condition under which a naming rule applies.

For more information, refer to the Configuring naming rules topic in the PTC
Server connection online help.
□ New %import-filename%, %import-filename-ext%, and
%id-attr% sub-expressions for the expression attribute on the namerule
element that enable you to specify additional names for an object.

For more information, refer to the Configuring naming rules topic in the PTC
Server connection online help.
■ Default burst configuration files for all DITA document types

The Arbortext-pathadapters\com.ptc.prowt.arbortext\
bursting directory contains default burst configuration files for all of the DITA
document types.
■ Show in Resource Manager button on the Browser

This button displays the object currently selected in the Browser in the
appropriate tab in the Resource Manager.

DITA Application limitations

In addition to the limitations documented in the DITA Application limitations
topic in the Arbortext Editor online help, the DITA Application has the following
limitations in this release:
■ An image element with values in both the href and conref attributes is not
supported.
■ Tables of contents and indexes are supported for the DITA BookMap document
type in the default stylesheets, but not for the DITA Map document type.
■ The default stylesheets contain minimal styling or do not support the following
elements or attributes:
□ fragref element

73
Release Notes for Arbortext Editor, Styler, and Architect

□ groupchoice element

□ groupcomp element

□ groupseq element

□ synblk element

□ syntaxdiagram element

□ The map element’s toc and print attributes.

The map element’s toc attribute only applies to Web and HTML Help output
types. The map element’s print attribute can be used with profiling, but is not
supported more directly in this release.

■ References in the link and xref elements are supported when composing from a
DITA map, but have limitations when composing from an individual DITA topic.

■ A DITA document that is the target of a content reference may sometimes be

opened as read-only when the document is opened directly in Arbortext Editor
at the same time that document is open as a content reference from another
document.

■ Duplicate topics might be included in composed output when topic references to

non-DITA content are included in the main sequence or in a relationship table in
a DITA map.

■ Numbering is not correct when a topic reference to a non-DITA document does

not include a navtitle attribute value on the topic reference in the DITA map.

Column view
Column view is a new Arbortext Editor view specifically designed to support
document types that primarily consist of element and attribute content and have
relative little text or other inline content. Column view combines a structural view of
a document with a series of rows and columns, similar to a spreadsheet, where you
can view and edit the attributes of the elements in the document. To use Column
view for a document type, it must be configured in the document type configuration
(.dcf) file. Once Column view is enabled for a document type, you can use the
Columns category of the Preferences dialog box to configure how the column
are displayed.

Column view is the default view for the DITA Map, DITA Book Map, and XUI
document types. For more information, refer to the Column view overview topic in
the Arbortext Editor online help.

New user preferences file

The name and format of the user preferences file has changed. The file is now
named arbortext.wcf on Windows or .arbortext.wcf on UNIX. A new
environment variable APTWCF specifies the location of the preferences file.
The old epic.wcf preferences file and associated APTPRFWCF environment
variable are deprecated.

74
 Appendix C Included 5.3 F000 new features

The settings from the old epic.wcf file are automatically migrated to the new
preferences file the first time you invoke the upgraded Arbortext Editor. By default,
the new arbortext.wcf is stored in the user’s home directory. Note that the
value of the old APTPRFWCF environment variable is not automatically migrated.
If you want to store the new preferences file in a location other than the home
directory, you must set the new APTWCF environment variable.

You can now save different window configuration preferences for different document
types by specifying a window class for a document type in the document type
configuration (.dcf) file. For more information, refer to the Specifying a window
class topic in the Arbortext Editor online help.

Supported document types

The following document types are no longer delivered with Arbortext Editor:
■ Article
■ Arbortext Catalog
■ Arbortext Very Simple XML DocBook Article
■ Book
■ Arbortext MIL-M-38784C
■ Correspondence
■ General Purpose Document
■ News Release

The following document types have been renamed:

■ ASCII — Renamed Text
■ Arbortext Simplified XML DocBook Article — Renamed Arbortext Article
(XML DocBook v4.0)

The DocBook V4.0 document type is no longer displayed in the New dialog, but is
still in the Arbortext Editor install at Arbortext-path\doctypes\docbook.

StylerSheet updating
You must update all of your existing StylerSheet .style files before using them for
composition in this release. See Updating Stylersheets in the online help for more
information on updating StylerSheets.

Miscellaneous Arbortext Editor changes

This version of Arbortext Editor also contains the following updates not covered
elsewhere :
■ The Tools menu has a new selection Compare Config with PE. This tool can
generate a report comparing composition configuration on the Arbortext Editor
client with composition configuration on the Arbortext PE server. The returned

75
Release Notes for Arbortext Editor, Styler, and Architect

Composition Configuration Comparison report notes the differences between the

composition environment on the client and the server. This menu item appears
only if you are using Arbortext Publishing Engine for composing documents. This
information can help PTC Technical Support diagnose problems.

■ Dialog boxes, menu selections, and error messages have been updated to replace
the phrase “XInclude” with “XML inclusion” as appropriate. You may need to
update custom scripts that expect the previous phrasing. The following specific
changes are included in this release:

□ The following Edit menu choices have changed:

• Create XInclude from Selection is now Create Inclusion from Selection.

• Edit All Entities and Includes is now Edit All Entities and Inclusions.

□ The following Edit window popup menu choices have changed:

• Edit Include is now Edit Inclusion.

• Edit Entity or Include is now Edit Entity or Inclusion.

The Preferences dialog box choices has the following changes:

□ For the Colors category, Include is now XML Inclusion.

□ For the Compare category, Includes is now Compare XML Inclusions.

■ The following View menu choices have changed:

□ The Document Map submenu is removed. The Document Map menu choice
now changes the current view to the Document Map. The Synchronize Views
and Expand Attributes choices from the submenu have been moved to the
main View menu. The other options on the menu have been moved to the View
category of the Preferences dialog box.

□ A new Edit View menu choice changes the current view to the Edit view.

□ A new Column View menu choice changes the current view to Column view, if
Column view is configured for the current document type.

■ A new Close View menu choice has been added to the Edit window popup menu.

■ The Document Map toolbar button now cycles through the Document Map, Edit
view, and Column view (if Column view is configured for the current document
type).

■ The Preferences dialog box now has a Columns category, if Column view is
configured for the current document type.

■ The View category of the Preferences dialog box has been rearranged to include
sections for Edit view and Document Map preferences.

■ The color of the Attribute and Graphic icons have been changed from red to
blue to aid accessibility.

■ In the Document Map, the Attribute icon now has a plus or minus sign, showing
whether the associated attributes are open for inline editing.

76
 Appendix C Included 5.3 F000 new features

■ Support for defining column widths and rule styles has been added to custom
tables. Support has been added to the document type configuration (.dcf) file
for defining default column widths and rule styles for custom tables. For more
information, refer to the Defining custom tables topic in the Arbortext Editor
online help.

■ System performance when editing large tables is greatly improved.

■ Graphics path processing no longer includes the current working directory when
resolving relative graphic path references.

■ Applications that open a document without a stylesheet using the 0x200

flag to the doc_open function or the OPEN_NOSTYLE flag to the
Application.openDocument method may notice a change in behavior since
a subsequent write or save command will no longer load the stylesheet.
Without a stylesheet, the document will be serialized differently since all original
line breaks must be preserved (as is the case for Free-form documents with no
stylesheet). If this change is not wanted, do not specify the 0x200 flag.

New API

New ACL set command options

The following new ACL set commands support Arbortext Editor.

Table C–30 New ACL set command options

Set command option Description
set cmsautoconnect Determines whether a repository adapter
connect dialog is automatically displayed
when you attempt to open a file that is stored
in the repository and no session is currently
established with the repository.
set ditainsertallwarning Determines whether Arbortext Editor displays
a warning dialog when more than a designated
number of topic references are being inserted
into a DITA map in a single operation.
set ditapath Specifies a list of directories to search for
content referenced from DITA documents.
set docmaphighlight Specifies the color value used to highlight the
Document Map line containing the cursor.
set doctypecachesize Controls the size of an internal cache that
retains document type information and
associated stylesheets during an Arbortext
Editor or Arbortext Publishing Engine session.
Setting this option to a non-zero value will
greatly improve performance of opening the
second and subsequent documents of a given
document type at the expense of consuming
more memory for the duration of the session.

77
Release Notes for Arbortext Editor, Styler, and Architect

Set command option Description

set view Determines the view displayed in the
Arbortext Editor window.
set viewmode Determines the default view displayed in the
Arbortext Editor window.
set xmlversion Controls the XML version used when creating
and saving an empty document using the ACL
function doc_open or the AOM Application
interface openDocument() method.

Changed ACL set command options

The following changed ACL set commands support Arbortext Editor.

Table C–31 Changed ACL set command options

Command Description
set docmapmode This command is deprecated.
set docmappercent This command also supports Column view.
set docmapshowattrs This command also supports Column view.
set docmapside This command also supports Column view.
set docmapsync This command also supports Column view.
set docmapview This command is deprecated.

Changed ACL commands

The following changed ACL commands support Arbortext Editor.

Table C–32 Changed ACL commands

Command Description
modify_tag Supports a new inline option to open a Column view
attribute value cell for modification.

New ACL functions

The following new ACL functions support Arbortext Editor.

Table C–33 New ACL functions

Function Description
adapterstatehook Provides information about state changes from a
repository adapter.
buffer_clipboard_ Copies the contents of a specified format from the
contents system clipboard to a scalar variable.

78
 Appendix C Included 5.3 F000 new features

Function Description
buffer_clipboard_ Fills an array with the names of the application
formats registered clipboard formats currently available on
the system clipboard.
columnview_cell_focus Changes the focus from one Column view cell to
a different cell.
columnview_is_defined Indicates whether Column view is defined in the
document type configuration file (.dcf) for the
indicated document.
dcf_option Returns the value from attributes on the Options
element in the document type configuration file
(.dcf).
ditaref_resolve Resolves a reference to content in a DITA document
and returns the path where the referenced content is
located.
doc_first_dobj Returns the first document object in the given
document.
doc_next_dobj Returns the document object following the specified
object in the same document.
doc_type_dita Determines whether a given document is a DITA
document.
drop_file_info Returns the path name of a file involved in a drag
and drop operation.
import_graphic_folder Imports all of the graphics stored in a specified
file system directory into the connected document
repository.
marking Determines whether a selection operation is in
progress for a given document.
oid_namespace_prefix_ Determines whether a specified URI is defined.
defined
window_get_ Retrieves the Column view settings for a window
columnview view.
window_set_columnview Sets the Column view settings for a window view.

Changed ACL functions

The following changed ACL functions support Arbortext Editor.

Table C–34 Changed ACL functions

Function Description
buffer_is_clipboard Has a new format parameter.
burst_multiple Has a new 0x1000 flag indicating to use
location rules for child objects even when
useroverride="on" in the burst configuration
file.

79
Release Notes for Arbortext Editor, Styler, and Architect

Function Description
doc_add_callback Has new attribute_default_value, generate_id, and
reference_path callback types.
doc_open When an application opens a document without a
stylesheet using the 0x200 flag, a subsequent write
or save operation will not load the stylesheet.
legal_name The XML version for a document is now stored in the
document’s XML declaration processing instruction
(PI). That version is used as the basis for testing an
XML element or attribute stored in the document.
mouse_at Has new attrval.Name, cellattrval.Name,
columnview.ruler_boundary, and
icon.ElementInlineContent return types.
oid_get_icon Has a new index parameter.
oid_graphic_pathname Now first attempts to resolve relative paths using
the base URI for the location the graphics element
is located before attempting to resolve the path
using the document directory or directories from the
graphicspath. In addition, if the graphics reference
value is a relative file name that cannot be resolved
to an absolute path name because the file does not
exist, the string returned will be the absolute path
name for the document directory concatenated with
the relative path name.
oid_expose Now supports Column view.
oid_set_icon Has a new index parameter.
oid_show_attr Now supports Column view.
option_type Has a new bgcolor return type.
sess_doc_burst Has a new 0x1000 flag indicating to use
location rules for child objects even when
useroverride="on" in the burst configuration
file.
session_add_callback Has a new drop_file_over callback type.
tag_has_attr Has a new dtdOnly parameter.
tbl_obj_attr_get Supports a new FRAMERULES set table attribute.
tbl_obj_attr_set Supports a new FRAMERULES set table attribute.
window_add_callback For the WINDOW_DOCK_CHANGED event of the
notify callback type, the data parameter now holds
the old docking state.
window_create Has a new 0x080000 flag indicating to not update
the filelist option, the Arbortext Editor File menu
list of recently edited documents, or the Microsoft
Windows list of recently edited documents with the
path name associated with the specified document.

80
 Appendix C Included 5.3 F000 new features

Arbortext Styler changes

The following Arbortext Styler additions and changes have been made in this release.

Update existing StylerSheets

You must update all of your existing .style files before using them for composition
in this release. See the Arbortext Styler help topic Updating StylerSheets for more
information on updating StylerSheets.
Note
If your 5.2 stylesheet contains custom tables and uses modules, make sure all of the
elements related to a custom tables are stored in the same module. If the custom table
elements are in different modules, your custom tables will not be updated correctly.

Custom table support

Support for custom tables has been enhanced in this release. Custom tables are now
considered mergeable definitions for Arbortext Styler modules and have enhanced
features, including the capability to set column widths and table rules. The following
modified and new user interface elements support custom tables:
■ Custom Table Details dialog box — Now enables you to assign an existing
custom table definition to an element.
■ Custom Tables dialog box — Enables you to manage custom table definitions.

■ Custom Table dialog box — Enables you to create or edit a custom table
definition.
■ Format→Custom Tables menu choice — Invokes the Custom Tables dialog box.

For more information, refer to the Custom table styling overview topic and the topics
for the custom table dialog boxes in the Arbortext Styler documentation.

XPath numbering
A new XPath override for current level option has been added to the following
dialog boxes:
■ Division Title Number

■ Footnote Number

■ Formal Block Title Number

■ Number Details

■ List Item Number

You can use this option to hold an XPath expression that is used to determine a
number or marker to use for the current numbering level. This option has two
associated buttons. A Delete button deletes the current XPath expression. An Edit
button invokes the new Edit XPath Override for Current Level dialog box in which
you can enter an XPath expression.

81
Release Notes for Arbortext Editor, Styler, and Architect

Miscellaneous Arbortext Styler changes

This release also contains the following Arbortext Styler updates that are not
covered elsewhere:

■ The ID reference attribute option on the Footnote tab is renamed Reference

attribute.

■ The Options element in the document type configuration (.dcf) file has a new
allowStyler option that enables you to disable the free version of Arbortext
Styler.

For more information, refer to the Disabling the free version of Arbortext Styler
topic in the Arbortext Editor online help.

■ A new Options→Synchronize Elements with Editor menu choice enables you

to determine whether the element selected in the Elements list is affected by the
element containing the cursor in Arbortext Editor.

New API
The following new ACL commands support Arbortext Styler behavior.

New ACL Set command options

The following new ACL set command supports Arbortext Styler.

Table C–35 New ACL set command options

Set command option Description

set stylersyncelements Enables you to determine whether the

element selected in the Elements list is
affected by the element containing the
cursor in Arbortext Editor.

New ACL functions

The following new ACL functions supports Arbortext Styler.

Table C–36 New ACL functions

Function Description
styler_get_styled_ Takes a the stylesheet path and returns the document
elements identifier of a Free-form XML document containing
a list of all of the styled elements in the stylesheet.

Changed ACL functions

The following changed ACL functions support Arbortext Styler.

82
 Appendix C Included 5.3 F000 new features

Table C–37 New ACL functions

Function Description
styler If the .dcf file disables the free version of Arbortext
Styler, this function does not work and returns an
error message.
stylesheet_new If the .dcf file disables the free version of Arbortext
Styler, this function does not work and returns an
error message.

Arbortext Import/Export updates

Refer to the Customizers’ Guide for information on configuring your workstation
and site to use Arbortext Import/Export. Arbortext Import/Export has the following
updates in this release

Arbortext Import configuration changes

■ Arbortext Import 5.2 Configuration Directories are incompatible with Arbortext
Import 5.3. When attempting to use a Configuration Directory from an earlier
version of Arbortext Import, you will be prompted whether you wish to update
the Configuration Directory. The menu items File→Import/Export→Open Import
Project and File→Import/Export→New Import Project are disabled until you
run the File→Import/Export→Import Workbench Configuration menu item to
update your Configuration and Repository Directories.

Be aware that updating your Configuration Directory will make the files in that
directory unusable with earlier version of Arbortext Import.

To leave your Configuration Directory compatible with earlier versions of

Arbortext Import, use the value of APTIMPORTEXPORTHOME to specify the
particular directory you wish to use with each version of Arbortext Import. The
Repository Directory path is defined in a file in the Configuration Directory. If
you choose to use different Configuration Directories for different versions of the
Import Workbench, ensure the Repository Directories are different too.

Two ways exist to define APTIMPORTEXPORTHOME for running different

versions of Arbortext Import/Export: as an environment variable or as an ACL
global variable. They are:

□ Assign a path for the environment variable APTIMPORTEXPORTHOME

in a batch file which launches epic.exe. Your batch file could contain the
following lines:

set APTIMPORTEXPORTHOME=c:\custom
start Arbortext-path\bin\epic.exe -newinstance -styler

The environment variable will only affect the Arbortext session launched by
the start command.

83
Release Notes for Arbortext Editor, Styler, and Architect

□ Assign a value to the ACL global variable APTIMPORTEXPORT in an

ACL file in \custom\init. For example, you could create a file named
importexportinits.acl with the following content:

global APTIMPORTEXPORTHOME=’c:\custom’

In both of these cases, the location of the Configuration Directory will

be c:\custom\importexport\config because the Arbortext
Import/Export appends importexport\config to the specified path
automatically.

■ A new File→Import/Export→Import Workbench Configuration menu selection

displays the new Import Workbench Configuration dialog box. This dialog box
provides you information about the current configuration of Arbortext Import, and
allows you to easily make changes to that configuration.

□ If the Arbortext Import configuration directory does not exist (defined

by APTIMPORTEXPORTHOME or the HOME path), and
ImportMapping is enabled in the workstation’s feature.cf file, the
File→Import/Export→New Import Project and File→Import/Export→Open
Import Project menu items are disabled. The new Import Workbench
Configuration menu item is enabled, allowing you to initialize the
Configuration and Repository Directories.

□ If the configuration directory exists, but is from a previous version of Arbortext

Import, the New Import Project and Open Import Project menu items are
disabled. The Import Workbench Configuration menu item is enabled.

The Import Workbench Configuration dialog box has the following controls.

□ HOME Path — The value to which the Windows HOME environment variable
is set.

□ APTIMPORTEXPORTHOME environment variable — The value to which the

APTIMPORTEXPORTHOME environment variable is set.

□ Configuration Directory: (using APTIMPORTEXPORTHOME) — The

value of the APTIMPORTEXPORTHOME environment variable
if it is set. If APTIMPORTEXPORTHOME is not set, this is the
HOME\importexport\config.

□ Status of Configuration Directory — Shows the status of your Arbortext

Import configuration. If the configuration has any conditions that may lead to
failures when importing documents, this status will recommend changes to
the configuration.

□ Repository Directory — Specifies the location of the Import Repository

Directory. This location can be a network location. You must be able to save
files to this location.

□ Update — Updates your configuration with any changes. Update is disabled

when:

• The Configuration Directory is a network location.

84
 Appendix C Included 5.3 F000 new features

• Neither the HOME nor APTIMPORTEXPORTHOME environment

variables is defined.

• A Repository Directory is not specified.

• The Configuration Directory and the Repository Directory are the same path.
This is not desirable because the content of the Configuration Directory is
workstation-dependent, whereas the Repository Directory contains user files
which may be deployed on different workstations.

■ The Arbortext Import/Export ACL functions and general import, export, and
mapping functionality uses the Arbortext event log mechanism. The following
error return codes for these operations are new in this release.

Description Value
Path name is too long (greater than 1024 characters) 26
Cannot open the Driver Factory file 27
Configuration Directory does not exist 28
System preferences file not found 29

Arbortext Publishing Engine migration

considerations
■ If any default drivers (that is, the .std files in the STDTemplates\Common
directory) or customized versions of the MapTemplates delivered in earlier
releases have been placed in a custom location on the server, the table of
driver options within each .std file should be reviewed by the MapTemplate
administrator.

■ Update your server MapTemplates. When migrating to Arbortext Import version

5.3, load all user-defined MapTemplates into the MapTemplate Editor and save
them. This ensures new version attributes are updated.

PDF file importing

Arbortext Import now supports importing PDF files. The Select a Document
to Import dialog box now offers *.pdf as a file type to import. The New
Transformation Wizard and the Input Driver drop down list on the MapTemplate
Editor Processing Drivers dialog box include the PDF driver.

Importing PDF files is a more labor-intensive process than the import of more
structured word processor formats. MapTemplates can capture division titles and
lists, based on such formatting items as font size, text patterns, indentation, and
vertical spacing, but most of the details within the structure are best handled in
Arbortext Editor using drag-and-drop, copy-and-paste, or change markup operations.

A mapping option which can facilitate the manual cleanup process is the
use of namespaced elements for ambiguous content. Refer to the default
MapObject in the sample MapTemplate in your Repository Directory
at\STDTemplates\ArbortextSamples\word2dita.std as an example
of how to import ambiguous constructs to a namespaced element using a temporary

85
Release Notes for Arbortext Editor, Styler, and Architect

namespace URL and prefix (import:). This method inserts elements that avoid
triggering context errors in your imported document and makes manual cleanup
easier because it facilitates working with a valid XML instance.

If your PDF source files contain elements (referred to as tagged PDF) or PDF
bookmarks determining and mapping to the intended document structure is easier. If
your PDF files contain numerous tables or very large tables, you can use the PDF
Table Manifest Editor (described later in this section) to clarify the structure of
each table in each source document. In cases where a body of documents, such as
periodic reports, have identical layouts and table formatting, a Table Manifest can
assist in the batch processing of the PDF files, reducing or eliminating the need for
manual table editing in Arbortext Editor.

PDF files are page-based, layout-based files. Consequently, the text runs are
indistinguishable from one another except for their formatting properties and the
location of the text on the page. Arbortext Import is quite successful at importing
text runs which make up a individual paragraphs. However, Arbortext Import is
less successful recognizing text runs in multi-column layouts and tables. The text
data is preserved, the hierarchical structure and document order may not reflect the
document’s intentions. The imported files may require extensive post-import editing
to restore the intended structure and document order.

Importing PDF documents is best suited for the following situations:

■ PDF files are the only source files available. Consider importing RTF, HTML, and
other formats, if available or possible, before mapping for and importing PDF files.

■ PDF files contain few or no tables. Table markup may or may not exist in the
PDF version of the ppXML file.

■ PDF files contain single-column layouts. Multicolumn layouts will most likely
require extensive drag-and-drop editing in the imported XML document.

Also, consider saving XML or RTF versions of the PDF files. With Adobe Acrobat
Professional, you can save PDF files to RTF and generic XML. Either format can be
imported with Arbortext Import, although issues with table layout and multi-column
formats are still problematic in many cases.

A sample MapTemplate for importing PDF files to XML using the asdocbook
document type is available at the following location:

Arbortext-path\lib\importexport\data\STDTemplates\
ArbortextSamples\pdf-to-asdocbook.std

Refer to the file

Arbortext-path\samples\importexport\asdocbook-sample.pdf

as an example of importing a PDF document with the sample MapTemplate.

Arbortext Import Workbench and MapTemplate

Editor updates
■ Several layout and window changes have been made to the Arbortext Import
Workbench and MapTemplate Editor to improve their usability.

86
 Appendix C Included 5.3 F000 new features

■ When creating and editing a MapTemplate, you can now perform, undo, redo, cut,
copy, and paste operations with the MapTemplate Editor. In the Edit Input Rules
dialog box you can cut, copy, and paste individual rules. Right-click any input
rule node for a popup menu. In the Output Hierarchy window you can cut, copy,
and paste output steps. Right-click any output step node for a popup menu.

■ Searching in the MapTemplate Editor is improved. Searches are case-sensitive.

■ When deleting an output step on the Output Rules tab of the MapTemplate Editor,
children of that step are no longer deleted.

Miscellaneous Arbortext Import updates

■ You can now import Framemaker MIF files containing CJK characters with
Arbortext Import.

■ File names which contain CJK characters are now supported.

■ Improved the support of importing footnotes and endnotes.

■ Importing Word nested fields and nested tables is now supported. Fields nested
two levels deep are supported. When importing RTF files with nested tables, one
level of nesting is supported.

■ When importing Word documents, FORMCHECKBOX, FORMDROPDOWN,

and FORMTEXT fields are now supported.

■ When importing a document using Arbortext Architect, a new dialog box will let
you cancel the import process.

■ A sample MapTemplate for importing MIF files to DITA topics is available at

the following location:

Arbortext-path\lib\importexport\data\STDTemplates\
ArbortextSamples\mif2dita.std

Refer to the file

Arbortext-path\samples\importexport\ditasample.mif

as an example MIF file to convert to DITA markup using this MapTemplate.

For information supporting the Import capabilities of Arbortext Import/Export,

refer to the Arbortext Import/Export Reference Manual for Importing Documents
available when running the Arbortext Import Workbench by choosing
Help→Documentation→Reference Manual.

Arbortext Export updates

■ Tooltips are now available for controls on the Arbortext Styler Field dialog box.

■ Nested tables can be exported to RTF.

■ The export of RTF footnotes has been improved, allowing the footnote text and
footnote reference numerals to be styled in a manner which emulates the behavior
of Word.

87
Release Notes for Arbortext Editor, Styler, and Architect

■ Special characters in RTF style names no longer cause incorrect results.

■ Contiguous tables are no longer merged into one table in Word.

■ Tables with no borders are exported properly.

■ File names which contain CJK characters are now supported.

■ You can override the default value of the importexportpath option to control
the display of MapTemplates when importing using PE composition.

For information supporting the Export capabilities of Arbortext Import/Export, refer

to the topics beginning with Overview of Exporting in the Arbortext Styler online
help.

Known limitations
The following known limitations exist with Arbortext Import/Export.

General import limitations

■ .NET Framework v1.1.4322 must be installed on any workstation used for
developing MapTemplates. Earlier and later versions of .NET are not supported.

■ When cutting and copying objects in the MapTemplate Editor, copying a top-level
MapObject to a child MapObject and copying a child-level MapObject to the
Windows Clipboard are not supported.

■ When performing searches in the MapTemplate Editor, regular expression

searches are not supported.

■ When editing MapTemplates, deleting an object or changing priorities cannot be

undone.

■ Importing symbols used as footnote reference markers is not supported.

■ When importing .doc files, a new MARKEREND element is included in the

ppXML markup to denote the end of a bookmark range. This is only supported
using the Word Java driver (word2xmlj.std).

■ Importing Unicode text files is not supported. 8-bit text characters are supported
for import.

■ When importing RTF files, only CJK characters which use Unicode encoding are
supported. When running Word under CJK locales, Word may not save the RTF
text characters with Unicode encoding. Word may use the native code page for the
locale. The known workarounds include:

□ Save the RTF file as a .doc file and import the .doc file.

□ Switch to a non-CJK locale and re-save the RTF file to a new file name. This
triggers Unicode encoding in the RTF data.

88
 Appendix C Included 5.3 F000 new features

General export limitations

■ Exporting markup fragments results in composition errors. A workaround is to
include the fragments in a valid parent XML document and export that document.
■ Export to RTF does not support the \listpicture keyword which defines
custom pictures for list enumerations, such as user-defined pictures for bullet
shapes.

Dynamic Link Manager availability

The Dynamic Link Manager is not available in this release. Areas of the 5.3 F000
documentation, however, reference DLM as if it was available. DLM will be
available as a part of a maintenance release after the release of Arbortext Editor
5.3 F000.

Composition changes
The following compositions additions and changes have been made in this release.

Stylesheet associations now supported for

Arbortext Publishing Engine
If an Arbortext Editor client has a stylesheet association processing instruction
embedded in a document or uses the set output-typestylesheet options,
these are now supported for composition performed on the Arbortext PE server. A
stylesheet association can specify a URL or a file path. If a stylesheet association
is specified using a path, Arbortext Publishing Engine will attempt to locate a
stylesheet of the same name on the Arbortext PE server (meaning that the path to
the stylesheet is ignored and only the stylesheet name is used). If a stylesheet of the
same name exists on the server, it will appear in the Arbortext Editor stylesheet list
of selections for the Print and Compose dialog boxes with the (pe) notation.

Stylesheet presentation order can be configured in the document type .dcf using
the new PEStylesheetOrder element. Refer to the online help topic Configuring
stylesheet order in a list.

The following set command options support stylesheets of the same name on
the Arbortext PE server (meaning that the path to the stylesheet is ignored and
only the stylesheet name is used). If a stylesheet of the same name exists on the
server, it will appear in the Arbortext Editor stylesheet list of selections for the Print
and Compose dialog boxes with the (pe) notation. They are documented in the
Arbortext Editor online help:
■ set promptstylesheetassociations
■ set stylesheetassociations
■ set printstylesheet
■ set htmlstylesheet
■ set htmlhelpstylesheet

89
Release Notes for Arbortext Editor, Styler, and Architect

■ set webstylesheet

Arbortext XSL support

Arbortext XSL support in the 5.3 release is unchanged from the support in the
5.2 release. Because the support did not change, the Arbortext XSL Support
documentation still contains 5.2 version information. Arbortext XSL FO support is
documented in Arbortext’s XSL Support — An annotated excerpt of the Extensible
Stylesheet Language (XSL) Version 1.0. The current version of this documentation is
available by visiting the Support area of http://www.ptc.com.

The Arbortext XSL support documentation is also installed with Arbortext Editor
and available in HTML at:

Arbortext-path\docs\ati_xsl_support\ati_xsl.htm

A PDF version of the same documentation is available at:

Arbortext-path\docs\ati_xsl.pdf

PTC Server connection (Windchill

connection) changes
This release also contains the following PTC Server connection updates that are
not covered elsewhere:
■ The Windchill connection has been renamed the PTC Server connection and now
support the Arbortext Content Manager, as well as Windchill.
■ A new Object→Create Object from Selection menu choice invokes the Share
Properties dialog box. This dialog box enables you to create document objects
out of selected reusable regions in the document.
■ The Save As Properties dialog box has a new Use location rules for child
objects check box that indicates whether only the top-level object in a document
is stored in the specified folder.
■ The PTC Server connection default bursting configuration files are now in
the Arbortext-path\adapters\com.ptc.prowt.arbortext\
bursting directory.

Repository Adapter changes

This release also contains the following Adapter updates that are not covered
elsewhere:
■ Arbortext Adapter to Documentum updates:
□ All directories and files associated with the Arbortext Adapter
to Documentum have been moved to the Arbortext-path\
adapters\com.ptc.arbortext.adapters.documentum.dmcl
directory. This includes the default burst configuration files,

90
 Appendix C Included 5.3 F000 new features

which are now in the Arbortext-path\adapters\

com.ptc.arbortext.adapters.documentum.dmcl\bursting
directory. The directory structure is the same on Windows and UNIX.

□ The Save As Properties dialog box has a new Use location rules for child
objects check box that indicates whether only the top-level object in a
document is stored in the specified folder.

■ Arbortext Adapter to Oracle CM SDK updates:

□ All directories and files associated with the Arbortext Adapter to

Oracle CM SDK have been moved to the Arbortext-path\
adapters\com.ptc.arbortext.adapters.oracle.cmsdk
directory. This includes the default burst configuration files,
which are now in the Arbortext-path\adapters\
com.ptc.arbortext.adapters.oracle.cmsdk\bursting
directory. The directory structure is the same on Windows and UNIX.

□ The Save As Properties dialog box has a new Use location rules for child
objects check box that indicates whether only the top-level object in a
document is stored in the specified folder.

■ Arbortext Adapter to IBM Document Manager updates:

□ The Arbortext Adapter to IBM Document Manager is now an optional product

feature in the Arbortext Editor installation. Configuration information for the
adapter and DB2 Document Manager is in the Arbortext Adapter to IBM
Document Manager help topics in the Arbortext Editor online help.

□ The Connect dialog box no longer enables you to select a DB2 Document
Manager group. A new Object→DM Group submenu enables you to change
your active group during a repository session. The group currently selected in
this submenu when you disconnect from the repository, or your default group,
will be the active group the next time you connect to the repository.

□ The Save As Properties dialog box has a new Use location rules for child
objects check box that indicates whether only the top-level object in a
document is stored in the specified folder.

□ You can now create new top level folders in DB2 Document Manager using
the Browser.

□ The Arbortext Adapter to IBM Document Manager default bursting

configuration files are now in the Arbortext-path\adapters\
com.arbortext.adapters.ibmdm\bursting directory.

XUI (XML-based User Interface)

changes
The following updates to XUI are new or newly documented in this release.
Complete and updated XUI documentation is in the Working with XUI (XML-based
User Interface) dialog boxes chapter of the Customizers’ Guide.

91
Release Notes for Arbortext Editor, Styler, and Architect

■ You can now create XUI tree controls that let users select multiple items in
the tree. Multiple selection mode is available on the Windows platform only,
and is accessible using ACL only. Refer to the treecontrol element updates in
the following table.

The following ACL functions have been updated to work with multiple item
selections in XUI tree controls:

□ dlgitem_get_select_array(window, dlgitem, array)

□ dlgitem_get_selected_appdata(window, dlgitem)

□ dlgitem_get_selected_listtag(window, dlgitem)

□ dlgitem_select_list_at(window, listtag, row)

□ dlgitem_get_selected_listtag_array(window, dlgitem, array)

■ You can now perform standard Windows drag and drop operations on XUI tree
control items. XUI tree control drag and drop operations are available on the
Windows platform only, and are accessible using ACL only. Drag and drop
operations let you transfer data to and from the XUI tree control from and to other
applications that also support drag and drop operations.

Drag and drop functionality is enabled by handling the following new drag and
drop events in your custom ACL application:

□ DRAGDROPBEGIN — Signals the beginning of a drag and drop operation

in a XUI tree control.

□ DRAGDROPENTER — Signals a drag and drop operation has entered the target
tree control.

□ DRAGDROPOVER — Signals a drag and drop operation is over the target tree
control.

□ DRAGDROPLEAVE — Signals a drag-and-drop operation has left the target

tree control.

□ DRAGDROPDROP — Signals a drop has occurred in the target tree control.

□ DRAGDROPEND — Signals a drag and drop operation that started in the tree
control has ended.

■ You can now select single cells in XUI tables. Refer to the cell and tablecontrol
element updates in the following table.

■ You can now allow carriage returns in text boxes. Refer to the textbox element
updates in the following table.

■ You can allow and restrict column sorting in tables. Refer to the tablecontrol
element updates in the following table.

92
 Appendix C Included 5.3 F000 new features

Table C–38 Changed XUI elements

Element Description
cell The following attribute is new:

■ selected — Specifies whether the cell is selected. If

the parent tablecontrol element’s type attribute is set
to cell, clicking in the table selects the cell and sets
the selected attribute to true.
colordropdown The following attributes are new:

■ valuetype — Determines if the value attribute of the

<colordropdown> element is set a standard HTML
color name or to the hexidecimal color code defining
the color selected in the color dropdown control.
tablecontrol The following attributes are new:

■ nosortheader — (Windows only.) Specifies whether

clicking on the column heading will resort the
column contents.
■ type — Added the possible value cell. When type is
set to cell, clicking in the table selects a single cell
and sets the cell element’s selected attribute to true.
textbox The following attribute is new:

■ wantreturn (Multi-line text boxes only.) Specifies

whether a carriage return is inserted when the user
presses the ENTER key while entering text.
treecontrol The following attributes are new:

■ haslines — Specifies whether dotted lines will be

displayed among tree nodes to indicate the hierarchy
of tree nodes.
■ seltype — When set to single, only one only one
tree node can be selected at a time. If multiple
(Windows only), more than one tree node can be
selected at one time.
window The following attributes are new:

■ margin — Specifies the margin around the content of

the dialog box in pixels.

93
Release Notes for Arbortext Editor, Styler, and Architect

Interchange no longer available for

download
Interchange was replaced by Arbortext Import/Export in a previous Arbortext
Editor release. Beginning with this release, Interchange is no longer available from
the PTC Support site. For further information on Interchange, contact your PTC
representative or the Arbortext Product Manager at [email protected].

AOM changes
New and changed AOM interfaces
This version of Arbortext Editor and Arbortext Publishing Engine contain the
following new and changed interfaces, enumerations, methods, and attributes.

Refer to the Programmers’ Guide for detailed descriptions of the interfaces,

enumerations, attributes, and methods covered in this section.

Table C–39 Changed AOM interfaces

Changed AOM Description
interface
ANode Added the following attribute:

■ icon2 — Gets or sets the name of a second display

icon that appears to the left of the Node (if any).
The icons appear in the Document Map and in the
Edit window whenever element tags are set to full or
partial display. If this Node has no icon, icon2 returns
the string "None".
CMSObject Added the following method:

■ invokeExtension — Invokes an adapter-specific

extension function. Some adapters provide
functionality beyond the standard CMS API.
CMSBrowseItem Added the following attributes:

■ applyOverlay — Specifies whether the CMS browser

should apply its default icon overlay logic (the
corresponding value is 1.) Overlay icons represent an
object’s lock status. A 0 value means the display icon
is a composite icon that includes a lock status icon.
This attribute is optional. The default is 1. A 0 value
is ignored when no displayIcon is provided.
■ displayIcon — Specifies the graphic icon used to
represent this object instance in the Arbortext Editor
CMS browser. The value is a relative path name, and
the standard search path is used. This attribute is
optional and may contain an empty string.

94
 Appendix C Included 5.3 F000 new features

Miscellaneous ACL changes

This section describes miscellaneous ACL commands, functions, callbacks, and
predefined variables that are new or changed in Arbortext Editor 5.3 and not covered
elsewhere in these Release Notes.

New ACL set command options

The following ACL set command options are new in Arbortext Editor 5.3 and not
covered elsewhere in these Release Notes:

Table C–40 New ACL set command options

Set command option Description
set bigjobthreshold Sets the level at which composition pipeline
output is written to disk by specifying
the number of document fragments in the
document. When the number of document
fragments in a document exceeds its n integer,
the content pipeline writes its output to disk
first before reading it into memory.
set gentextdisableautoupdate Generated text automatic updating can slow
down processing of documents. The points at
which the slowing occurs is based on several
factors and varies by document type. The
points at which the slowing impacts the user
also varies. Setting gentextdisableautoupdate
lets you specify when to disable generated
text auto-updating to prevent unacceptable
processing times for various size documents.
set pegraphicpi Specifies whether to send graphics from
the Arbortext Editor client to the Arbortext
Publishing Engine for composed outputs that
use a DVI file (Print Preview, PostScript,
and the direct to PDF feature). When set to
on (the default), a graphic PI representing
data about the graphic is sent in place of the
graphic file, reducing the amount of data sent
to and retrieved from the server. When set to
off, the graphics used in the document can be
sent along with the document to the Arbortext
Publishing Engine. This avoids a problem with
graphic processing instructions that are not
handled properly by some XSL stylesheets.
set stricterrors When set to on, a reference to an undeclared
ACL variable in a package declared with the
_STRICT_ global variable will be flagged as
an error. If set to off, a warning message is

95
Release Notes for Arbortext Editor, Styler, and Architect

Set command option Description

sent to the Debug Messages window if set
debug = 1. Otherwise, no warning or error is
generated.
set writenobreaktag When set to on, line breaks can be inserted
at element boundaries or before the element
close character (>) when writing and saving
XML documents. The default is off.

New ACL functions

The following ACL functions are new in Arbortext Editor 5.3 and are not covered
elsewhere in these Release Notes:

Table C–41 New ACL functions

Function Description
dlgitem_exists Determines whether a specified control exists
in a window.
doc_estimate_dfs Returns an estimate of the number of
document fragments in a document. Taking
into consideration the overall size of the
document, this value can help determine the
setting for the set bigjobthreshold option.
windows_disabled Determines if a modal dialog is currently
displayed or the user interface is disabled.
This function may be useful in a timer or
channel callback to delay or avoid processing
if the user interface is blocked.

Changed ACL functions

The following ACL functions have been changed in Arbortext Editor 5.3 and are not
covered elsewhere in these Release Notes:

Table C–42 Changed ACL functions

Function Description
window_add_callback A WINDOW_DOCK_CHANGED event sets the
notify callback type data parameter to the
old docking state. In previous releases, data
was set to the new docking state.

Environment variables
The following environment variables are new in Arbortext Editor 5.3 and are not
covered elsewhere in these Release Notes:

96
 Appendix C Included 5.3 F000 new features

Table C–43 New environment variables

Name Description
APTFONTCONFIGLOG Specifies whether custom font process
diagnostic information is written to a specified
log file.
APTLIGATURESENABLED Specifies whether ligatures are used when
publishing documents. Ligatures can also be
enabled and disabled on a per-document and
per-document type basis.
APTNAMEDDESTTOPAGE Set to any value to convert named destinations
to page numbers in PDF links.
APTREVBWIMGREP Specifies whether to reverse monochrome
images.
APTWATERMARKTEXT Set to the text that will overlay output pages
for formatting, printing, or composing a PDF.

New manual for Arbortext PE

programmers
This release includes a new guide for programmers using the Arbortext Publishing
Engine. The Arbortext Publishing Engine Programmers’ Guide is delivered in
Arbortext-path\docs\pe_prog_guide.pdf, making it available for
Arbortext PE users and administrators as well as Arbortext Editor users who may be
creating custom applications that run on the Arbortext PE server. The new manual
provides more detailed information on the concept, structure, and components of the
Arbortext Publishing Engine. Some of the material in this manual was previously
covered in the Programmers’ Guide and has been enhanced for this release.

97
INDEX

A B
ACL browser support. . . . . . . . . . . . . . . . . . . . . 3
changes . . . . . . . . . . . . . . . . . . . . . . . . . 24 Web Composer . . . . . . . . . . . . . . . . . . . 3
fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
ACL functions
updates . . . . . . . . . . . . . . . . . . . . . . . . . 20
ACL hooks
updates . . . . . . . . . . . . . . . . . . . . . . . . . 20 C
ACL set options
updates . . . . . . . . . . . . . . . . . . . . . . . . . 21
CJK platform support . . . . . . . . . . . . . . . . 2
adapters
composition
fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
AOM
fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Arbortext Editor
advanced menu . . . . . . . . . . . . . . . . . . . 8
changes . . . . . . . . . . . . . . . . . . . . . . . . .
composing for Digital Media
5 D
Publisher . . . . . . . . . . . . . . . . . . . . . . . 6
DITA Application . . . . . . . . . . . . . . . . . 8 database archiving. . . . . . . . . . . . . . . . . . . 14
fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Digital Media Publisher
intelligent graphics support. . . . . . . . . . 7 composition. . . . . . . . . . . . . . . . . . . . . . 6
localized Arbortext Help Center . . . . . . 6 DITA application
localized documentation . . . . . . . . . . . . 5 fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
PTC Server connection . . . . . . . . . . . . . 9 DLM
repository adapters . . . . . . . . . . . . . . . . 10 fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Service Manual Application . . . . . . . . . 8 documentation
XML inclusions . . . . . . . . . . . . . . . . . . 8 Arbortext Help Center. . . . . . . . . . . . . . 6
Arbortext Help Center localization . . . . . . . . . . . . . . . . . . . . . . 5
localization . . . . . . . . . . . . . . . . . . . . . . 6 Dynamic Link Manager . . . . . . . . . . . . . . 12
Arbortext Import/Export ACL function updates . . . . . . . . . . . . . . 20
fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 ACL hook updates . . . . . . . . . . . . . . . . 20
Arbortext Styler ACL set option updates. . . . . . . . . . . . . 21
fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 composer configuration file. . . . . . . . . . 22
configuration file changes . . . . . . . . . . . 15
database archiving. . . . . . . . . . . . . . . . . 14
.DCAConfig.Properties changes . . . . . . 16
dialog box changes . . . . . . . . . . . . . . . . 23
DLM toolbar . . . . . . . . . . . . . . . . . . . . . 14

99
Release Notes for Arbortext Editor, Styler, and Architect

.dlmcf changes . . . . . . . . . . . . . . . . . . .
document sets . . . . . . . . . . . . . . . . . . . .
15
13
O
inline linking . . . . . . . . . . . . . . . . . . . . . 12
Java API updates. . . . . . . . . . . . . . . . . . 17 online help
memory improvements . . . . . . . . . . . . . 14 localization . . . . . . . . . . . . . . . . . . . . . . 5
menu changes . . . . . . . . . . . . . . . . . . . . 23
metadata resolution . . . . . . . . . . . . . . . . 17
monitoring session status . . . . . . . . . . . 14
processing instructions changes . . . . . . 23
reference linking . . . . . . . . . . . . . . . . . . 12 P
reference markup resolution . . . . . . . . . 16
resolution stylesheets . . . . . . . . . . . . . . 13 platform support . . . . . . . . . . . . . . . . . . . . 2
third-party link markup resolution . . . . 16 preview command. . . . . . . . . . . . . . . . . . . 24
third-party linking . . . . . . . . . . . . . . . . . 13 processing instructions
translated content . . . . . . . . . . . . . . . . . 13 changes . . . . . . . . . . . . . . . . . . . . . . . . . 23
validating configuration files . . . . . . . . 13 product support . . . . . . . . . . . . . . . . . . . . . 3

F R
fixes included in this release release notes
ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 previous versions . . . . . . . . . . . . . . . . . 1
AOM . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Arbortext Editor . . . . . . . . . . . . . . . . . . 25
Arbortext Import/Export . . . . . . . . . . . . 29
Arbortext Styler . . . . . . . . . . . . . . . . . . 28
composition. . . . . . . . . . . . . . . . . . . . . .
DITA application . . . . . . . . . . . . . . . . .
25
27
S
Dynamic Link Manager . . . . . . . . . . . . 27
publishing . . . . . . . . . . . . . . . . . . . . . . . 25 Service Manual Application . . . . . . . . . . . 8
repository adapter . . . . . . . . . . . . . . . . . 29 set debugcomposition command. . . . . . . . 24

J T
Java API troubleshooting
updates . . . . . . . . . . . . . . . . . . . . . . . . . 17 archiving databases . . . . . . . . . . . . . . . . 14

L W
localization . . . . . . . . . . . . . . . . . . . . . . . . 2 web browser support
Arbortext Help Center. . . . . . . . . . . . . . 6 Web Composer . . . . . . . . . . . . . . . . . . . 3
documentation. . . . . . . . . . . . . . . . . . . . 5
online help. . . . . . . . . . . . . . . . . . . . . . . 5

100
140 Kendrick Street
Needham, Massachusetts
02494

© 2006 Parametric Technology Corporation (PTC). All rights reserved.