|
|
 |
|
InCatalog/InCatalog Pro Release History
Changes at 4/5/6.2.6.6 release
Fixed a problem where updating a styled price could cause its link marker to disappear.
Links are now maintained through any character or paragraph style changes that a price
style might apply.
Fixed a problem where updating a styled price with an empty field would cause its
link marker to disappear.
Such empty styled price links are now preserved with a placeholder character.
For Windows 7, Vista and XP users with administrative privileges,
the plug-in's registration information is once again stored in the
registry under HKEY_LOCAL_MACHINE/Software/Em Software, where it
will be available for all users of the machine.
Registration information for users lacking administrative privileges
remains in HKEY_CURRENT_USER/Software/Em Software where it will be
available only to that user.
Changes at 4/5/6.2.6.5 release
Fixed a problem where pictures specified as being relative to the document's
file weren't being found for "converted" documents
(those templates and documents from previous versions of InDesign).
[2609, 2610, 2611]
Fixed a problem where the presence of an aliased folder in a partial picture
path would cause the picture to not be found.
For example, a picture specified with the path ":Food Pix:1 Broccoli.jpg"
will now import properly even when "Food Pix" is a folder alias rather
than an actual folder. (Mac OS X only) [2608]
Changes at 4/5/6.2.6.4 release
Worked around a Mac-only problem where some ODBC drivers were overwriting memory,
causing the loss of characters in large updates and general instabilities that could lead to crashes.
Fixed a problem where fitting large images into small frames could leave the image
too large after bumping up against our previous 10% scaling limit.
InCatalog now allows the scaling of pictures down to 0.1%.
Changes at 4/5/6.2.6.3 release
Changes at 4/5/6.2.6.2 release
Changes at 4/5/6.2.6.1 release
The file paths of tagged pictures are now exported properly in CS4.
Text-based links marked as InDesign Tagged no longer disappear when updated with empty data.
Fixed a problem with the log dialog which was preventing it from displaying long ODBC error messages.
Fixed a problem with the log dialog which preventing it from displaying the number of remaining errors.
(Windows only)
Changes at 4/5/6.2.6 release
Added support for InDesign CS4, including IDML import & export.
Fixed a problem where changing the tagger's hot keys in
InCatalog > Preferences > User Interface could often result in an error message.
Changes at 4/5.2.5.2 release
Exposed all data source and data destination sub-menu items in the keyboard shortcut editor.
The plug-in's registration information is now properly retained for all users.
Previously, Windows XP and Vista users whose accounts had limited privileges were being asked
for a serial number each time they started InDesign.
Changes at 4/5.2.5.1 release
Fixed a problem which was preventing the "(No Link)" entry in the
palette's field popup from removing an existing link (was resulting in a
"You can't use this field..." error).
Unicode-encoded data files generated via Create Data... or Create Data
File... are once again written as UTF-8. (A problem introduced in the
4-5.2.5 release had them being written as UTF-16.)
Exposed InCatalog > Clear All Links > in Selection
to InDesign's keyboard shortcuts editor
(Edit > Keyboard Shortcuts..., Product Area: InCatalog,
Commands: in Selection).
Fixed a data update problem where links in tables could output an
incorrect page number.
Fixed a problem where changing keyboard shortcuts in InCatalog >
Preferences > User Interface... could cause a crash.
(InDesign CS3 only)
Fixed a problem where closing and then opening the palette could cause the
palette to draw incorrectly.
(InDesign CS3 only)
Changes at 4/5.2.5 release
Changes at 3/4.2.4.1 release
-
Fixed a problem which caused attempts to export page references via
scripting to result in the error "Spread #1 can't be mapped to its
constituent pages (internal error)".
-
Fixed a problem where the most-recently active DD set's price style
file wasn't being read on startup. Reloading the DD in order to gain
access to its price styles is no longer necessary.
New features/changes at 3/4.2.4 release
-
Fixed a problem that in certain circumstances was slowing screen
redrawing substantially, as well as causing drop shadows to draw
incorrectly.
-
Fixed a problem where the tagged text link tags (<cEmDataLink:...>
and <tEmCellDataLink>) were being ignored on import.
-
InCatalog no longer issues spurious "A link with global field
'page' was found on the pasteboard on spread 1, and thus has no
associated page number." warnings when updating data using a DD that
specifies the page number qualifier [#].
-
Fixed a problem where sending more than 256 characters to Microsoft Access
via ODBC would result in a "Invalid precision value" error.
-
Fixed an OS X 10.4 "get file" dialog problem where some files with
valid types or names were no longer being displayed as
selectable. (Mac OS only)
-
Fixed a Mac OS problem where filenames like myfile. (with a
period but no extension) could crash our "get file" dialogs. (Mac OS
only)
-
Fixed a scripting issue that prevented the simultaneous setting of
an initially empty text container's contents and catalog link data
properties without leaving a zero-width space around.
-
Neighboring links are no longer joined into a single link when a
link-containing text frame is dragged and dropped from a library.
(CS2 only)
-
Fixed a problem where InCatalog could crash if a document generated
with a previous version of InDesign being opened in InDesign CS2
happened to contain text with catalog link-bearing zero-space-break
characters. (InDesign CS2 only)
-
Dragging grouped items (InCatalog linked or not)
to a library or exporting grouped items to an
INX file no longer causes InDesign to crash.
-
Added support for CS2 snippets and libraries. Frame and text catalog
links are now preserved in the snippet or library file and restored
when the snippet or library item is reconstituted.
-
Added support for Adobe's InDesign Interchange file format in CS and
CS2. Frame and text catalog links are now preserved through the
interchange process.
-
Added direct access to catalog links via scripting. We've added two
new properties: "catalog DD set" and "catalog link data".
The "catalog DD set" property lives on the document, is read/write and
contains the DD Set that is associated with the document. (It's the DD
set that was active when the document's initial catalog link was
applied.) It's simply the name of the folder containing the DD files
used by the document's links. Setting this property is equivalent to
selecting a new DD with the Alt/Option key held down.
The "catalog link data" property lives on text, page items and table
cells, is read/write and describes the link associated with that
element. When getting the property you'll receive either the "nothing"
enumeration if there's no active link or an ordered list of values: DD
name, key name, field name, key type, subfield, picture position,
price style, is price, is tagged and convert quotes. Getting the
property from a text element containing more than one link will return
only the first link.
You may set the "catalog link data" property to either "nothing" (to
remove/deactivate an existing link) or to a similar list of values:
-
DD name (string) may be an explicit name or "default" to specify
the application's active DD.
-
key name (string) may be an explicit key name or an empty string if
no key is required for the specified key type. (This value is
essentially ignored if key type resolves to a value other than key
from link.)
-
field name (string) must be a valid field name from the specified
DD.
-
key type (catalog key type enumeration) may be omitted (or
"default") if either the specified DD is active and the field's DD
entry provides a value via the L"x" qualifier or the key name value is
a valid non-empty string. In the latter case, the key type defaults to
key from link.
-
subfield (integer) defaults to 0 (zero) for no subfield if
omitted; otherwise, the one-based subfield.
-
picture position (catalog picture position enumeration)
defaults to "as is" if omitted.
-
price style (string) defaults to an empty string unless the
specified DD is active and the field's DD entry provides a value via
the P"style" qualifier.
-
is price (boolean) defaults to false unless the specified DD is
active
and the field's DD entry provides a value via the P, T, or U
qualifier.
-
is tagged (boolean) defaults to false unless the specified DD is
active
and the field's DD entry provides a value via the P, T, or U
qualifier.
-
convert quotes (boolean) defaults to true unless the specified
DD is active and the field's DD entry provides a value via the T, or U
qualifier. Only meaningful if is tagged is true; specifies whether
straight quotes in tagged text should be converted to typographer's
quotes.
A simple example, creating a link on the second word of the first
story, with the document's default DD set and key value of 1-100,
linking the price field, would be:
set catalog link data of word 2 of story 1 to {default,"1-100","price"}
If setting the catalog link data of a text element, note that the
link will be applied to only that text element. The change will not
be propagated to other text elements to which that same link may
extend. For example, for the story:
The qu[ick bro]wn fox.
(where the [ ] denotes a link), the AppleScript statement
set catalog link data of character 8 of story 1 to nothing
would split the one link into two links, like
The qu[i]c[k bro]wn fox.
whereas the statement
set catalog link data of word 2 of story 1 to
{default,"1-101","partno"}
would split the existing link into two adjoining links, like
The [quick][ brown] fox.
The Applescript statement
set catalog link data of word 2 of story 1 to nothing
would clear the link from only word 2, as in:
The quick[ bro]wn fox.
Note that this behavior differs from the UI (where a change to any
part of a link affects the entirety of the link) and prevents
neighboring links from being joined when imported from snippets.
New features/changes at 3.2.3/4.2.3 release
Fixed a problem where the previous DD wouldn't reload after quitting
and restarting InDesign. (Windows only)
Added support for Unicode price style files. The file must be
prefaced with an appropriate byte order mark (BOM) in order for
InCatalog to treat the text as Unicode. For example, the BOM for a
UTF-8 encoded file would be the three character sequence 239 187 191.
Fixed an intermittant problem where the checkboxes in the "Create
Data File..." and "Open Data File..." dialogs could become unselectable
or would disappear entirely. (Windows only)
Fixed a problem where InCatalog would crash when an image was
encountered during a database update. (CS2 only)
New features/changes at 3.2.2/4.2.2 release
The InCatalog 4.x series runs under InDesign Creative Suite 2 (CS 2).
InCatalog now visits master spreads on a full-document
update or extraction.
Fixed a problem with beta 2's new line-ends handling which was generating
errors when loading some DD files.
Fixed a long-standing problem with DOS line-ends handling where the the LF
of the CR LF sequence was being treated as part of the next record. Existing
.x files created from data snapshots using DOS line-ends will need to be
regenerated. If you're importing data from a data file and notice that all
fields are coming in empty, please close the data file, delete the data
file's .x file, then re-open the data file.
Closing the tagger, closing the current document, opening a new document
and re-opening the tagger no longer causes a crash.
Added support for links in table header and footer cells.
For data, DD, and price styles files, InCatalog now recognizes Unix/Mac OS
X-style line-ends (a single line-feed, character 10) in addition to DOS and
MacOS (Classic) line-ends.
Extracting a plain (non-tagged) text field containing one or more style
changes no longer elicits an out-of-memory error.
Fixed a problem that was causing a crash when an update of a multi-page
table left the table one or more pages shorter than it was prior to the
update.
Fixed an update problem where a paragraph style wasn't being applied to
the final paragraph of a text field if that paragraph wasn't terminated with
a return character.
Using the "no style" character or paragraph style in a tagged text field
now works correctly.
Worked around an InDesign CS problem where paragraph rules could conceal
link markers.
On startup, InCatalog now attempts to load any previously loaded DD
silently (i.e. without UI), so if the DD was mounted on a foreign (server) volume
and is no longer available, InCatalog will no longer "hang" InDesign forever.
(Mac OS X only)
Added the DD qualifier ' (single quote) to trigger forced quoting when
extracting text fields through broken MacOS ODBC drivers that don't properly
quote bound data themselves.
Selecting a layout guide no longer crashes InCatalog.
Added on-line FileMaker Pro 7 support. (MacOS only)
When extracting styled price data, InCatalog now ignores tracking as well
as kerning changes. I.e., if you track or kern your prices, you no longer
have to worry about InCatalog seeing the character property change as a
whole/fractional break point.
When updating unstyled prices (text links marked as prices but with style
"None"), InCatalog is no longer fooled by an initial decimal point. E.g.,
when updating ".99", InCatalog will now properly understand the whole part
to be "" (empty) and the fractional part to be "99". Before, it would assume
the "99" was the whole part.
Fixed a long-standing problem where changes to InCatalog's shortcuts (in
the UI Preferences dialog) wouldn't stick unless InDesign's Keyboard
Shortcuts dialog had been opened first.
New features/changes at 2.2.1/3.2.1 release
Fixed a problem which could cause a crash when an error was reported.
Added new %"..." ODBC character encoding field qualifier. The value
(Windows, Macintosh, UTF-8, or UTF-16) applies to all fields in the DD and
specifies the format of characters sent to and received from a database via
ODBC (and only ODBC).
Reinstated field quoting (the "Q" field qualifier) for ODBC-based
exports.This really shouldn't be necessary due to the bind/exec sequence
we're using to transfer data. Some ODBC drivers, however, appear to paste
the data into the SQL update command directly without first wrapping the
data in quotes, which then causes the update to fail. If your database
updates are failing with mysterious errors, try adding the "Q" qualifier to
the appropriate fields. Conversely, if you're seeing quotes appear in your
database after an update then be sure to remove the "Q" qualifier from those
fields.
Fixed an ODBC import problem so that DOS-style line-ends (CR LF) are now
treated as a single new-paragraph character rather than two.
Fixed an import problem where invalid characters (like nil) in un-tagged
text fields were not being ignored.
Added UTF-32 character support to our tagged text machinery.
When importing tagged text, paragraph and character overrides are no longer
cleared when a paragraph marker is encountered. Instead, applying a
paragraph style will clear all paragraph and character-level overrides as
well as reset the active character style (to No Style, currently). Applying
a character style will now clear only character-level overrides. Otherwise,
extant styles and overrides persist across paragraph markers.
Exporting a multi-paragraph link as tagged text no longer emits all
possible paragraph and character level tags for each new paragraph after the
first. Now, only the minimal set of required tags (to describe the style and
any local overrides) are produced.
Exporting a link as tagged text no longer emits a tag for the link itself
(since the presence of the link should be transparent).
When exporting a multi-paragraph link, the "I" (independently tagged)
field qualifier may now be used to force the generation of a paragraph style
tag for the initial paragraph. Without the "I" field qualifier, a tag for
the initial paragraph's style will never be emitted. In both cases,
remaining paragraphs will be prefaced with a style tag only if their style
differs from the preceding paragraph's.
Added "using InCatalog" suffix to all scripting event descriptions to make
InCatalog-specific events easier to find.
Cleaned up the tagger palette a bit by making dropdown heights and label
positions conform to InDesign standards.
The "About" dialog entry in the InDesign (on MacOS) and Help (on Windows)
menus has been moved from an "About Plug-ins" sub-menu to a new "About Em
Software Plug-ins" sub-menu.
New features/changes at 2.2/3.2 release
Added Unicode and long filename support for DDs, data snapshots, and
imported pictures. (Unicode and long filenames are not available in
2.2 when running InDesign 2 in MacOS 9 or as a Classic application in
Mac OS X.)
In a quoted field, a doubled quote character followed by the end-of-field
character no longer produces a spurious end-of-field.
Fixed a long-standing problem that would produce a "fatal error" on
document update or when closing a newly created/updated data file (a "can't
get data error") when a field's size exceeded about 4,000 characters.
Linked place-holder characters, created by importing an empty field, are
now exported as an empty field rather than a "?" (question mark).
(Windows only)
Fixed a problem where tables cells not in the table's originating text
frame were being ignored.
Fixed a performance problem where all cells in a table were being visited
(potentially) more than once during a document update.
Using an empty key field when importing a link as tagged text no longer
results in an error so long as the specified keytype is other than "from
link".
The current selection is now properly restored after an update.
Shortcut keys now work properly when key focus is on the tagger palette.
(Windows only, CS only)
Due to new features and
limitations in InDesign CS, we made some changes to InCatalog's scripting
language which may or may not affect you.
On Mac OS (InDesign CS only) we've had to eliminate our use of the
so-called "direct object",
but we've managed to do this without changing the event syntax .
Unfortunately, compiled scripts will need to be recompiled.
What were update document using file and update document using string
have become the single event update document with new, optional parameters
using file and using string. What was update data using file is now
update data with the required parameter using file. All other events
remain unchanged.
The using file parameter (of both events) may specify a file alias or text
(which InCatalog will coerce to an alias). The using string parameter must
specify text.
When using update document, one (and only one) of using file and using
string must be present. If both are present, the string reference is
currently ignored; however, we may change this and issue an error in the
future.
Under Windows, the only change was the removal of the InCatalog prefix
from the scripting methods. For example, what was
InCatalogUpdateDocumentUsingFile is now UpdateDocumentUsingFile. Except
for additions noted below, the parameter list remain the same. (NB: Unlike
the changes to Mac OS scripting, this change applies to both the 3.2 and 2.2
versions of InCatalog for Windows.)
Added new update document and update data boolean parameters selected
frame and selected group which limit the effect of the update (in either
direction) to the currently-selected frame or the currently-selected group,
respectively.
For example, using AppleScript, the code:
update document using file alias("...") ¬
with selected frame
would update just the currently-selected frame.
These options mimic the behavior of the interactive update palette exactly
(i.e., only the currently-selected frame's contents are updated in the
selected frame case (and not any other part of a story, if it's a text frame
and part of a text chain), and the entire outermost containing group is
updated in the selected group case. Likewise, undo is not disabled for
selected frame and selected group updating.
If there is no such selected item, an error results.
Note that these "limits" can't be used in conjunction with page or spread
first/last limits.
On Windows, these parameters have been introduced in the limits group,
immediately following the lastSpread parameter:
...
[optional, in] VARIANT lastSpread,
[optional, in] VARIANT selectedGroup,
[optional, in] VARIANT selectedFrame,
[optional, in] VARIANT ignorePictures
...
Added support for multiple ODBC managers, selectable from the Open ODBC
Connection... dialog, the DD (see new "^" qualifier, below), or via a
script parameter. Support for Data Direct and OpenLink driver managers is
built-in. When only one of these managers is available, it will be used as
the default manager. When both a Data Direct and an OpenLink manager are
available, the user will be prompted to select one in the Open ODBC
Connection... dialog if a manager hasn't been specified in the DD.
Added a manager parameter for scripting control of which ODBC manager
is used. (Mac OS only)
Added a new DD field qualifier, ^"...", where an ODBC driver manager
library may be specified. For example, [^"iODBC CFM Bridge"] would specify
the OpenLink manager, [^"ODBC Driver Manager"] would specify Data Direct's
MacOS 9 manager, and [^"ODBC DriverMgr PPC"] would specify Data Direct's Mac
OS X manager. This qualifier is only useful when multiple ODBC managers are
present, in order to avoid having to choose one in the Open ODBC
Connection... dialog. (Mac OS only)
Note that, in theory, any provider's manager library may be specified, so
long as it exports the ODBC functions required by InCatalog.
Note also that the manager name specified is actually the library's "load"
name, which isn't necessarily its file name. (The load name should be that
of the first exported symbol.)
InCatalog Pro no longer crashes InDesign on startup if no ODBC manager is
present. Instead, it will run with ODBC options disabled (like the non-Pro
InCatalog) until a manager is made available.
The DD's DSN field qualifier &"..." may now be used to specify a
connection string which is passed directly to the ODBC manager's
SQLDriverConnect() service. The DSN qualifier will be treated as a
connection string if (and only if) it doesn't name an existing user or
system DSN and it contains at least one equals sign (=). For example, a
file DSN named "foo.dsn" may be specified using the qualifier
[&"FILEDSN=foo"]. For more information on SQLDriverConnect()-compatible
connection strings, see
this document
on Microsoft's site. (Microsoft defined the ODBC standard.)
Added the ?"..." DD field qualifier, allowing the specification of a
field's default value in the event of a missing key. For text, the
qualifier's value is unquoted tagged text which is inserted in place of the
missing data. For pictures, the value is the path of an alternative image to
be loaded or a hyphen (?"-") to specify that the picture frame be cleared.
Note that missing key errors are logged regardless of this qualifier's
setting.
Added D"..." qualifier support to DD map entries, to complete the F/D pair
(field name/containing database or table name) for maps.
Pressing a tagger shortcut key which applies a field containing an
indirect key type preset (e.g. L"C") now automatically applies the link
regardless of the "Add/change link on field hot key" setting.
Pressing a tagger field shortcut key now immediately updates the tagger's
key type, price fields, and tagged text fields to reflect any field presets
in the current DD.
The tagger field shortcuts no longer disappear when a plug-in is added or
removed.
The tagger field shortcuts are tracked more accurately in the UI
Preferences panel, which now allows their reinstatement after the active
keyboard shortcuts set is switched.
An alert issued by the tagger for an illegal field value no longer resets
the field to its previous value. (Windows only)
Reinstated an audible alert when a (key or field) prompt or error is
issued by the tagger.
The Fill frame maintaining aspect ratio picture positioning method now
uses both the image width and height when fitting the image to the frame.
Previously, only the image width was used, which--for wide images--could leave
gaps at the top and bottom of the frame.
Fixed a potential crash when using database or table names longer than 31
characters.
Undo is now disabled during scripted updates.
New features/changes at 2.1 release
Fixed a problem that was causing all script-based ODBC update requests to
immediately fail with an "unspecified" error.
Fixed a serious, long-standing bug that would produce a "fatal error" on
document update (an error 4), when leading or trailing spaces are used in
key values. (They're ignored, otherwise, by default.)
Fixed a bug with FileMaker on-line access where we were ignoring the
FileMaker "found set" in a document update, but only if the DD specified a
particular database by name for a given field; now, we always look up things
in the current found set, no matter how the field is specified. (This gives
the user ultimate control over what is or isn't seen in the document
update.)
None of this affects document-to-database update, which ignores the found
set (since it has to create a new record if something isn't found, and that
only makes sense on a whole-database basis).
Fixed a serious performance problem which was causing updates to take much
longer than necessary, which for long documents could mean hours rather than
minutes.
The tagger palette's key and field editboxes are now stacked, which should
make working with long key and field names easier.
The tagger palette now flags invalid entries (e.g. empty key or no field
selected) and prompts for correction rather than simply ignoring them.
The tagger palette now enforces subfield entry for repeating fields.
Subfields are no longer treated as individual fields and a subfield
delimiter character is no longer left on the end of an injected subfield.
The first field hot key (F1 or Num-1) will now correctly select the first
field specified in the DD rather than "(No Link)".
The "Add/change link on field hot key" now attempts to automatically apply
a link. Previously, the user had to press Enter to make the link apply.
When scripting, a trailing backslash on the ddset path no longer causes
the update to fail. (Windows only)
Fixed a problem which was causing shortcuts to disappear after
opening any of InCatalog's preferences dialogs.
Fixed a problem which was causing InDesign to crash when a new tool
was selected immediately after modifying a tag's key field.
Copying and pasting table cells no longer causes indirect keys in
the pasted cells to disappear.
Text files created in Mac OS X are now selectable in InCatalog's
"Select Data Descriptor..." and "Open Data File..." dialogs. (Mac OS only)
InCatalog will now auto-sense Unicode data that begins with a byte
order mark even if the Data Snapshot Preferences specify a Mac OS or Windows
character set.
Fixed a problem where some InDesign tags, including the encoding
tag (e.g. <ASCII-WIN>), the version tag (Version/vsn), and the feature set tag
(FeatureSet/fset), were being treated as plain text rather than being
absorbed.
New features/changes at 2.01 release
New features/changes at 2.0 release
InCatalog no longer crashes when opening the Select Data Desciptor
or Open Data File dialogs. (Mac OS 10.2 (Jaguar) only)
Implemented menus and dialogs accelerators. (Windows only)
Added buttons to the User Interface Preferences panel that clear
the Edit hot key and Alternate tab key fields.
Changed the scripting interface to return the number of items walked as
the direct result. The "worst" error, if there is one, is available
in the scripting error clause as the error message (Mac OS)
or is available in Err.Description. (Windows)
Added tips for the palette's active DD and data file fields that show
the entire (unabridged) contents, as these fields are often clipped or
ellipsized.
Fixed InCatalog's About entry in the Plug-ins menu.
Modified the palette's cell icon to differentiate it more clearly
from the table icon.
Links no longer disappear when updating text marked as tagged.
Fixed a crash that could occur when working with tables.
Pressing the "Update Spread" button with no (text or object) selection
will no longer crash.
The key types "key from group", "key from text <<", and "key from text >>"
now support tables and nested inline objects.
Key from group, when used in a
table, will now search the entire table (left to right, top to bottom)
before preceeding up to the table's owning text. (Groups encountered on the
way up are also still searched.)
Key from text, when used in a table, first
searches for a key in that cell's table row (in the specified direction). If
no key is found, the search is continued in the text containing the table
starting at the table's anchor point and moving in the specified direction.
These key type searches also now handle nested text
frames, groups, and tables correctly.
When auto-update (InCatalog | Preferences | User Interface | Update
linked element when add/change link) is enabled, the entire table is now
updated when one of its cells is modified.
InCatalog Pro now supports ODBC in both Mac OS 9 and Mac OS X using
DataDirect Connect ODBC v4.0 drivers, which we supply.
(This also fixes the crash on startup
when trying to use InCatalog Pro under Mac OS X.) (Mac OS only)
The error logging facility now actually displays any logged
problems rather than an empty report. (Mac OS only)
Updating images will no longer cause some subsequent operations,
like Export as PDF, to crash.
The undo menu item now shows more appropriate text for undoing applied,
removed, or cleared links.
Removing a zero-length link (one set on an insertion point rather than a
range of text) at the end of a story no longer leaves the link on the
end-of-story marker.
The palette's "update table" and "update cell" icons have been enlarged to
increase their legibility.
The tagger palette now displays itself correctly when closed and
then re-opened (buttons look active but are disabled).
Table cells and cell content may now be tagged, updated, and extracted.
An entire table may be updated or extracted using the new "table"
button on InCatalog's palette. This button replaces the "group"
button when a table cell (or its content) is selected.
A single table cell (and its contents) may be updated or extracted
using the new "cell" button on InCatalog's palette.
This button replaces the "frame" button when a table cell
(or its content) is selected.
InFlow is no longer required to view the error log (but is still
bundled to handle the case where the log is longer than one page).
Fixed possible crash when opening preferences dialog.
Fixed crash when tables (or index entries) are present.
Dialogs and palette now look & work better in Mac OS X.
In particular, the tagger palette's interactive update buttons
now sport icons rather than text (and therefore are quite a bit
more compact and fit in better with other InDesign palettes).
Fixed possible crash when opening a data snapshot file.
Now properly ignores InData prototypes.
Tagger palette's "Field" edit box now supports auto-completion.
Shortcuts for activating the link editing palette,
tabbing through the palette, and
selecting fields now work,
and can be set in the UI preferences dialog.
The font's typeface is no longer arbitrarily set to "Normal"
during the update of tagged text.
Kerning is now correctly set to the default kerning (typically auto)
rather than to zero when updating a price where no old price is found. This
was causing problems down the road where a price's fractional part was being
put in front of the decimal point (e.g. $1050.50 instead of $10.50).
Add a new set of flags, 1 2 3 4 5, to price style definitions,
which control how many fractional price digits are used for the price style
in question (from 1 through 5, though anything other than 2 or 3 would be
very non-standard). E.g.,
Euros3 3T ^W^.^F
(where tabs are separating the three fields) would define a price style
"Euros3" using 3 fractional digits and thousands separators. The default is
still two digits, so nothing changes unless you ask for it.
Fix a potentially crashing, but at least data-corrupting bug when
eliding root markers from keys. (Windows only)
New features/changes at 1.2 release
Added auto page number and section marker support.
When extracting text for key from contents or when exporting
untagged text, the actual page name or section marker value
is used. Exported tagged text will now contain
the proper magic character for auto page number or section
marker generation, so that on import the auto page number
or section marker will be restored.
Fixed ODBC export, which before was sending only half of
the field's data.
Fixed create records checkbox on palette so that it now
disables record creation when it is unchecked.
Before it was leaving create records
enabled even when unchecked.
Changed page name generation to always use the page format
(arabic, alphabetic, or roman numerals) specified in the
section rather than always using arabic.
Fixed ODBC tagged text export so that it targets the
current platform's character set rather than always
targetting Mac-ANSI.
Fixed the export of some composite Unicode characters
(e.g. "C" w/ circumflex) that may have been disappearing
in both tagged and untagged text.
(Windows only)
Fixed a misspelling in the picture position menu's
Fit to frame maintaining... entry.
|
|
|
Try / Buy InCatalog
$800, Pro $1200
|
|