Release: InCatalog 6/7.2.7 for InDesign CS4/CS5

This release of InCatalog for InDesign adds support for InDesign CS5 to that for CS4, drops support for CS2/CS3, adds full XPress-tagged text support bi-directionally without needing our Xtags product, adds anchored text frame support in Xtags, changes the link markers to display as brackets (like in Xcatalog), adds link markers for tagged page items, merges the Pro and non-Pro binaries, adds support for abitrary per-field or all-field WHERE clause prefixes when using ODBC, adds full Unicode support when communicating with FileMaker, and fixes some long-standing bugs.

Notes

If you’re using CS5, updating to the latest version of InCatalog is as simple as starting up Adobe Extension Manager, selecting InCatalog and clicking Update.

With this release, the CS5 plug-in now requires a valid InCatalog 7 (CS5) serial number.

These release bundles include the InFlow companion plug-in.

Changes

Added support for InDesign CS5.

Changed text link markers to display as brackets (like in Xcatalog) rather than as highlighting (which was hard to see in some situations). See InCatalog’s User Interface preferences for new, related settings.

Added link markers for tagged page items.

Fixed a problem where an overly long key field could cause a crash.

Fixed a long-standing problem which could, in rare cases, cause the “don’t save on close” snapshot option to not work properly.

Added full, bi-directional support for XPress-tagged text and anchored box tags in tagged text fields. The (new) <"..." qualifier can be added to the DD file’s key field to select the style of tags — "X" for XPress-style tags, "I" for InDesign-style tags (the default) — for all tagged fields in the DD. For example,sku[K <"X"] description[T]
would select XPress-tagged text for all tagged text fields (like description), for both document and data updates.

Note that support for XPress-tagged text is now built into InCatalog. Our Xtags plug-in is not required for this feature to work!

Folded all Pro features, which previously lived in a separate Pro plug-in, into the single primary InCatalog plug-in. Pro-ness (meaning ODBC support) is now automatically enabled when the product is activated with a “Pro” serial number. No changes to existing installations should be necessary: if you have a Pro serial number and you replace an older InCatalog Pro plug-in with this latest InCatalog plug-in, you will still have access to all Pro features. (The InCatalog > About dialog will display [Pro] after your serial number.)

Added a simple, Pro-only facility for prefixing InCatalog-generated WHERE clauses with arbitrary predicates. These prefix predicates may be specified for individual fields using the DD’s new V"..." qualifier. Any prefix specified for a key field is applied to all fields. Prefix predicates are always combined with the generated predicate using AND. For example, the DDSKU[K D"foo" V"STATE='NY'"] description[T]
would generate an SQL update statement likeSELECT description FROM foo WHERE STATE='NY' AND SKU='12345'

Added full bi-directional support for Unicode data when communicating directly with FileMaker Pro 7 (or newer).

Fixed a long-standing problem where some characters (mainly tabs and CRs) were being lost when updating a document using a direct FileMaker Pro connection.

Fixed a long-standing problem which was causing record creation to always fail when communicating directly with FileMaker Pro 7 (or newer).

Added support for Mac OS X’s native ODBC Administrator. Use of OpenLink’s ODBC Administrator is no longer required. (Pro only)

Removed support for the Mac OS X iODBC framework. Installation of the iODBC framework is no longer required for ODBC connectivity since InCatalog Pro now supports Mac OS X’s native ODBC mechanism directly (see above). DSNs created in OpenLink’s ODBC Administrator should continue to work properly without modification. (Mac OS/Pro only)

Fixed a problem when working with a DBMS via ODBC where an Update Data of a field whose value hadn’t changed from the value already in the DBMS would be result in an erroneous “Row not found” message. (Pro only)