# Xtags for XPress

## Release: Xtags 3.7 for QuarkXPress 8/9

### Changes

• Adds a new C code letter for the sizing specs field of an anchored or as-anchored box tag’s width and height parameters. C may not be combined with S or R but may be used with F to size the box’s contents to the column as well. Sizing-to-column is allowed for anchored box tags, as-anchored box tags (unanchored, but with both x and y parameters left empty), and line tags.

Unlike S, which is only allowed to shrink a box, C is only allowed to grow a box to fit its column. Thus, its initial size is its minimum size, and what was the minimum (4th) parameter therefore becomes the box’s maximum size.

For example, <&pb((32pt,CF),(128,S),,,,,,,,,C,,,,,,,”p1234.jpg”)> would create an anchored frame with its width sized to the insertion point’s column, with the picture’s width scaled to the frame’s (and therefore the column’s) width, and with the frame’s height set to that of the picture.

• Removes Xcatalog’s link marker guard characters (for Xcatalog’s enhanced text link editability feature) from copied/saved tagged text so that tags for catalog links aren’t littered with unnecessary <\z>‘s.
• Fixes a problem where OpenType features tags (o(...)) were being generated with incorrect feature names.

## Release: Xtags 8/9.3.6 for QuarkXPress 8/9

### Changes

• Added support for relative line sizing, so that relatively-placed lines can now be sized relative to their referenced boxes. Lines always shrink (they never grow) towards their start point (the referenced corner) and their direction is always maintained.
• Added support for UNIX/POSIX-style paths (like /Volumes/Macintosh HD/Users/Chris/Pictures/Rhubarb.jpg). Note that, for backward compatibility with MacOS/HFS-style paths, a path must contain at least one slash (/) and may contain no colons (:) to be treated as a POSIX-style path. (Mac only)
• Fixed a long-standing problem where a relatively-placed box could, in rare situations, be sized incorrectly.
• Restored support for the box lock flag.

## Release: Xtags 8/9.3.5.1 for QuarkXPress 8/9

### Changes

• Fixed support for universal serial numbers.

## Release: Xtags 8/9.3.5 for QuarkXPress 8/9

### Notes

With this release, the QuarkXPress 9 XTension now requires a valid Xtags 9 serial number. If you have a license for a version of Xtags prior to 9, please contact Em Sales to obtain an upgrade serial number. Em Software’s upgrade policies and free upgrade cut-off dates can be found here.

Older versions of Xtags for QuarkXPress 6/7 can be downloaded from the Xtags 6/7/8.3.4 Release page. While we will no longer fix problems in or add features to these older versions, we will continue to support folks using them.

## Release: Xtags 6/7/8.3.4 for QuarkXPress 6/7/8

### Changes

• Added native support for hyperlinks and text anchors. The new tags are:
• &Ys marks the start of a text hyperlink
• &Ye(hyperlink name, page number, style name) ends a text hyperlink and creates a page reference
• &Ye(hyperlink name, URL, style name) ends a text link and creates a URL reference
• &Ye(hyperlink name, #anchor name, style name) ends a text link and creates an anchor reference
• &Yb(relative box ref, ...same as any of &Ye parameters)
• &Ya"anchor name" drops a named text anchor

To put these into use, we would recommend creating some hyperlinks in a scratch document, generating their tags via Edit > Copy with Xtags and then modifying those tags to meet your needs.

The <&Ya"foo">quick brown fox jumps <&Ys>over<&Ye("foo hyperlink", "#foo")> the lazy dog. will generate a text anchor named “foo”, then create a hyperlink named “foo hyperlink” to that anchor on the text “over”. (Note that text anchor references must be prefaced with a #.)

The quick brown fox jumps <&Ys>over<&Ye(, "http://emsoftware.com")> the lazy dog. will create an anonymous URL hyperlink on the text “over” to our website.

• Added support for multiple imports into named boxes via a new "@xtagsimport" parameter modifier. (Server only)

Our import parameter mimics the QuarkXPress Server Modifier XT’s "@dataimport" format as

<box-name> "&xtagsimport=" (<text> | "file:" <path>)

where <box-name> is an extant text box <text> is literal tagged text and <path> is either a platform-style absolute path (like "file:c:\foo\bar.txt" or "file:Macintosh HD:foo:bar.txt") or a doc pool-relative partial path using either platform or URL/Unix separators (like "file:xtags:bar.txt" and "file:xtags/bar.txt").

This format allows for multiple imports, like

http://localhost:8080/jpeg/testdoc.qxp?tb1@xtagsimport=SomeText&tb2@xtagsimport=file:foo.xtg&reporterrors=1

Note that hard errors (like <box-name> not found, <box-name> not a text box, <path> not found or import failure) are ignored. (Which also mimics the Modifier XT, and allows all imports to complete as best they can.)

• Addressed a performance issue in Q7/8 so that text containing anchored boxes now imports just about as quickly as it does in Q4/6.
• Made Pro features (table generation, namely) available in Demo mode.

## Release: Xtags 6/7/8.3.3.5 for XPress 6/7/8

### Changes at 6/7/8.3.3.5 release

• At-signs (@) appearing in, for example, e-mail addresses, within the body of a paragraph are no longer treated specially, so long as there is an end-of-paragraph or some other tag-like character(s) (less-than (<), greater-than (>), and at-sign (@)) between it and the next (if any) colon (:). Meaning, so long as an @ doesn’t look like a paragraph style application, it will not be treated as one. For example, in
@pstyle1:Some text and abc@mnop.xyz: Some more text.


Xtags will attempt to apply the paragraph style mnop.xyz, because the @mnop.xyz: looks like a paragraph style application, and there are no other special characters intervening. However, in

@pstyle1:Some text and abc@mnop.xyz. Some more text.


only pstyle1 will be applied since the use of the @ no longer looks like a style application (there’s no colon between it and the end of the paragraph). Previously, all of the text from the @ to the end of the paragraph would be lost.

If a colon must follow the e-mail address, as in the first example above, then you’ll need to continue escaping the at-sign, as in:

@pstyle1:Some text and abc<\@>mnop.xyz: Some more text.


unless there are other intervening characters that make it clear this is not a style application, as in:

@pstyle1:Some text and abc@mnop.xyz. Some more text.<\c>@pstyle2:In a new column now.


### Changes at 6/7/8.3.3.4 release

• Fixed a problem where text beneath a placed unanchored box wasn’t always properly reflowing around the placed box.

### Changes at 6/7/8.3.3.3 release

• Fixed a problem in QuarkXPress 8 where the missing picture’s proxy image (the red question mark) wasn’t being scaled properly to fit its box.
• Fixed a problem where the filenames of placed missing pictures could sometimes show up in QuarkXPress 8′s Picture Usage dialog with trailing garbage characters.
• Changed the handling of missing pictures in QuarkXPress 8 because references to missing pictures were sometimes being lost and displayed as “No Disk File” in the Utilities > Usage > Pictures dialog.

In versions prior to QuarkXPress 8, a reference to a missing picture was always retained exactly as it was specified.

Now, on Mac OS, a full path to a missing picture ("Macintosh HD:Users:me:Pictures:cat.jpg", for example) is retained only if each folder in the path actually exists. If any folder of a full path is missing, or the missing picture is specified with a partial path (like "cat.jpg" or ":Pictures:cat.jpg"), then just the picture’s filename ("cat.jpg") is retained, relative to either the current document, if the document has ever been saved, or to the user’s home folder.

On Windows, a full path to a missing picture is always retained. Partial/relative paths to missing pictures are retained as being relative to either the current document, if the document has ever been saved, or to the user’s home folder.

• Corrected the positions of the Xtags copy and paste menu items in QuarkXPress 8.1 for Mac OS X.

### Changes at 6/7/8.3.3.2 release

• Fixed a problem where overwriting an existing file while saving tagged text was sometimes leaving extra characters after the newly exported tagged text.
• Fixed a problem where *h tags (for H&J) weren’t always being output correctly in QuarkXPress 7 and 8.
• Fixed a problem where attempting to import a missing picture could produce a filename with trailing garbage characters in the Picture Usage dialog. (QuarkXPress 8, Mac OS X only)

### Changes at 6/7/8.3.3.1 release

• Fixed a problem with importing hidden text A(...) tags, where the resulting hidden text could be incorrect.

### Changes at 6/7/8.3.3 release

• Added support for QuarkXPress Server 8.0.
• Added support for <\z>, QuarkXPress 7′s undocumented zero-width space special character tag.
• Added support for Xcatalog’s new Unicode-supporting links. If you plan on exporting links created using Xcatalog 6/7/8.3.2 or later, or Xdata 6/7/8.4.1 or later, then you must upgrade to this Xtags release.
• Fixed a problem that would sometimes cause a mysterious crash after placing an anchored table. (Pro only)
• Fixed a problem where pictures specified with paths relative to the document template’s folder weren’t being found in QuarkXPress Server 7.
• Additional text file types entered in the Xtags Preferences dialog are now also used as filename extensions in Mac OS X. (They’ve always been treated as filename extensions in Windows.)

### Changes at 6/7/8.3.2.4 release

• Fixed a problem where batch control (.xbc) files were being ignored but still deleted.

### Changes at 6/7/8.3.2.3 release

• Added support for importing and pasting tagged text into a text frame selected with the item tool. Note that, since there’s no insertion point with the item tool, all imported/pasted text is simply appended to any existing content.
• Fixed a problem where placing an anchored table box could cause the document to become unstable. (Pro only)
• Worked around an issue where text wasn’t always flowing properly after applying a master page. (XPress 7+ Mac OS X only)
• On export, tags for empty and non-file-based pictures boxes are now generated with an empty file name rather than No Disk File. (XPress 7+ only)
• Batch folders, which were inadvertently disabled for the 6/7/8.3.2 release, have been re-enabled.
• Reverted the default encoding of text exported via our “classic” XT-to-XT API to always be platform-native (MacRoman/WinLatin) so that existing callers aren’t suddenly confronted with UTF-8-encoded text in Q7+ environments. To export text in newer encodings (like UTF-8), recompile your XTension to use our newer export API.
• 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 QuarkXPress.

### Changes at 6/7/8.3.2.2 release

• Shrinking boxes to fit their content now works again. (We broke it back in 6/7.3.2.)

### Changes at Xtags for QuarkXPress 6/7.3.1 release

• Boxes being placed under a relatively-referenced box are now put behind the referenced box before being auto-sized so that the shrink-to-contents will account for any runaround on the referenced box. Prior to this change, auto-sized text boxes were becoming overset when sent behind a referenced box.
• Added support for additional picture box runaround types including auto image, embedded path, alpha channel, non-white areas, same as clipping and picture bounds. The expanded runaround parameter of an unanchored picture box tag takes the form of a sub-list:
..., (type, flags, index, noise, smoothness, threshold),...


where type is one of n (none), i (item), a (auto image), e (embedded path), c (alpha channel), w (non-white areas), s (same as clipping), b (picture bounds). flags may specify any (or none) of the following: I (invert), E (include inner edges), O (let path extend outside the box). index specifies the embedded path or alpha channel when one of those types is selected. noise, smoothness and
threshold specify the tolerance settings for auto image, alpha channel and non-white runaround.

• Fixed a problem where text box background colors other than “None” were being ignored.
• Fixed a problem where the last character of any Copy-as-Xtags‘d text was being ignored when pasted (via Edit > Paste) back into a text box. (Windows, QXP7 only)
• Added table gridlines. (Pro only)

### Changes at Xtags for QuarkXPress 6/7.3.0.3 release

• Boxes may now be placed relative to a named box that is anywhere in the document, on the current spread or on the current page. If the named box is not found, the box creation fails and an error is generated. If the name is prefaced with a question mark, the creation is considered conditional: if the named box is not found then no box is created and no error is reported.

Where the named box is looked for can be specified by setting a new parameter in the relative reference sub-list to ‘D’ (to search the document’s layout), ‘S’ (to search the current spread) or ‘P’ (to limit the search to the current page). The default search location is the current spread.

E.g., <&pbu2((0,TL,"sidebar"),0,...)> looks for a box named “sidebar” on the current spread and places this new box on top of it. If “sidebar” isn’t found, the tag fails and an error is generated.

E.g., <&pbu2((0,TL,"?sidebar"),0,...)> also looks for a box named “sidebar”, but if one can’t be found no error is issued.

E.g., <&tbu2((0,TL,"background",D),0,(1,R,0),(1,R,0),...)> searches the document for a box named “background” and creates a same-sized text box on top of it.

Note that you can name a box on a master page and then position boxes on each document page relative to where the named master page box lies. This could be handy when tagged elements’ placements need to be determined by the layout rather than the tags. For example, something like

<&tbu2((0,TL,"?left-page-footer",P),0,(1,R,0),(1,R,0),...)>


might be used to place a left-page footer only on left pages. Since no box named “left-page-footer” would exist on the right page master, the tag would silently fail on right-side pages.

• Added a new unanchored box flag, ‘U’, which may be used to send a relatively placed box behind (under) its referenced box. If both the U and K (send to back) flags are specified for a relatively-placed box, the K flags will be ignored.

For example, the tags sequence:

<&tbu2((0,TL,"fancybox",S),0,(1,R,0),(4",S,6),0,0,,...)>Some text.<&tbe>
<&pbu2((0,TL,1),0,(1,R,0),(1,R,0),0,0,U,...)>


would create a text box aligned with (and as wide as) the current spread’s “fancybox”, shrink the box’s height to its contents, then slide a same-sized picture box in behind that text box to provide a background graphic.

• Tags referencing H&J and L&F names with accented characters are now saved/copied correctly to Unicode. Previously, accented characters were being converted to unknown or invalid Unicode code points. (7.3.0.3 only)
• Fixed a problem introduced in 6/7.3.0.2 which caused table start tag parameters above the 7th (text-align/runaround) to fail.
• Attempting to use a table tag without a Pro serial number now produces a “table tags require a Pro serial” error message rather than the previous builds’ “unknown” error.

### Changes at Xtags for QuarkXPress 6/7.3.0.2 release

• Added PDF page and cropping support to the picture box tags &pb, &pbu and &pbu2). The picture path name parameter may now specify a sub-list with the format
(filename, page number, cropping style)


where filename is the absolute or relative path to the PDF, page number is the number of the page to be imported and cropping style is the type of the cropping method to be applied.

Page numbers are integers in the range 1 … n where n is the number of the last page in the PDF. Values larger than n are clamped to n while a value smaller than 1 will cause both the page and cropping pameters to be ignored. If not otherwise specified, Xtags will load the the PDF’s first page.

The cropping style parameter may be 0 (media), 1 (contents, the default), 2 (bleed) or 3 (trim).

Xtags will silently ignore the use of these parameters on non-PDF images.

This is an Xtags 7-only feature. Versions of Xtags prior to 7.3.0.2 will silently ignore these parameters.

• Fixed a problem where incorrect style names were being generated when exporting tagged text from some documents.
• Improved the handling of shrink-to-fit baseline-aligned anchored boxes where a negative baseline offset places the box either partially or completely below the baseline. Previously, the box would always maintain the negative offset by shrinking towards its bottom edge. Now, if the offset is large enough to place the pre-sized box completely below the baseline, then the resized box will shrink
towards the baseline–meaning the gap between the baseline and the box’s top, if any, will be maintained. For example, the tags

<*R><&tb(30,(3",S),(b,-3"-6pt))>@:Sidebar: some interesting fluff<&te>


will now create an anchored text box sized to its contents hanging 6 points below the baseline. (Before it would shrink towards the box’s bottom, leaving a variably-sized gap between the baseline and the box’s top.) In this case, the box is pushed to the right edge of the page in its own paragraph such that it floats next to the next paragraph like a sidebar.

If the negative offset would leave the pre-sized anchored box straddling the baseline, then the resized box will now shrink about the baseline proportionally. For
example, the tag

<&pb((40,S),(40,S),(b,-20),,,,,,,,,,,,,,,"photo.jpg")>


will create an anchored picture box vertically centered on the baseline. After being fit to the image, the resized box will now remain centered on the baseline.

• Changed the minimum allowable baseline-alignment offset from -.5″ to -11″. The maximum allowable offset remains +11.5″.
• Unanchored lines created with <&lbu> may now be sent-to-back using the K flag.
• Fixed a problem where index entries made via <XI> in a text box created with <&tb> or <&tbu> were being placed in the main story rather than in the created box’s story.
• The angle field of the &tsu() tag is no longer ignored, allowing unanchored tables to be rotated. (Xtags Pro only)

### Changes at Xtags for QuarkXPress 6/7.3 release

• Fixed a box placement problem where attempting to place an unanchored box relative to the most-recently-anchored box (e.g. &lt&pbu2((1,TL,0),0,...)>) would instead place the unanchored box relative to the most-recently-created unanchored box, if there was one, or issue the error “Xtags error: No such previous box: tag &pb[u2]” if not.
• Added support for Unicode characters in box and layer names, though QuarkXPress’s UI won’t always handle them properly. (7.x only)
• Added support for text encodings–including Unicode–and direct-from-memory imports and exports to the XTensions interface. (7.x only)
• Fixed a problem where Xtags would issue an error for every box placed on the “Default” layer.
• Fixed a minor memory leak that could occur with each import.
• Added support for the <$$>, <a> and <a$$> tags. For a description of these tags see QuarkXPress Help / Appendices / Using XPress Tags / Defining and Applying Style Sheets / Additional XPress Tags for Style Sheets.
• Added support for 7.0′s opacity parameter in the paragraph rules tags. For tags marked as <v7.00> or later, the 5th (new) parameter in the *ra‘s and *rb‘s parameter list now specifies the opacity of the rule. (7.x only)
• Added support for 7.0′s new character-based language tag <n>. (7.x only)
• Added support for 7.0′s new ligatures tag <G>. (7.x only)
• Added support for 7.0′s OpenType Feature tag <o(...)>. (7.x only)
• Added support for Quark’s new XPress Tags 7.0 space character tags, including: en <\e>, 3-per-em <\5>, 4-per-em <\$>, 6-per-em <\^>, figure <\8>, thin <\[>, hair <\{> and word joiner <\j>. (7.x only) • Added support for Quark’s new XPress Tags 7.0 em dash character tag <\_>. In <v7.00> sources, this tag replaces <\m> as the em dash tag (see <\m>’s new 7.0 meaning, below). (7.x only) • The <\f> and <\m> tags now conform to Quark’s XPress Tags specification and produce a flex space and an em space, respectively, when imported from a <v7.00> source rather than an en space an a em dash as they do in prior tag versions. (7.x only) • Xtags 7.x now supports the import and export of tagged text encoded as Mac Roman, Windows Latin, UTF-8 or UTF-16. On import, UTF-16-encoded files are always automatically detected and any <e> tag in the file is ignored. UTF-8 files must either begin with a byte order mark (BOM) or contain the tag <e9>. Otherwise, the file is assumed to be encoded as Mac Roman (on Mac OS) or Windows Latin (on Windows) unless an <e> tag specifies otherwise (<e0> for Mac Roman or <e1> for Windows Latin). (7.x only) On export, the desired encoding may be specified in the Save Text as Xtags dialog’s new Encoding: pop-up menu. If a given Unicode character does not translate to the specified encoding (Mac Roman or Windows Latin), it will be converted to a <\#Uxxxx>. (7.x only) • Xtags now supports Unicode translation files and macros using Unicode characters. (7.x only) • The Apple Script interface now accepts and generates Unicode strings. (7.x only) • Boxes created by Xtags now take their default values from the document’s appropriate tool defaults: the rectangular text box tool for <&tb>, <&tbu> and <&tbu2> tags and the rectangular picture box tool for the <&pb> and <&pbu> tags. • Added the <p%> tag to support text opacity in QuarkXPress 7. For example, The <p50>ghostly<p$> owl


would import with the word “ghostly” with its opacity set to 50%. (7.x only)

• Accented characters in color, style, language, line, frame, H&J and layer names are now translated to and from Unicode correctly. (7.x only)
• We’ve added support for the <\#Uxxxx> (and <\#U+xxxx>) tag that was first introduced in our Xtags for InDesign product. With it, any character may be specified using its Unicode code point value. For example, an em-dash may be specified as <\#U2014> or <\#U+2014>.
• What was File > Get Text with Xtags… has been changed to File > Import Text with Xtags… and what was File &gt Save Text with Xtags… has been changed to File > Save Text with Xtags… to better align with QuarkXPress 7′s updated terminology. (7.x only)
• Requests to shrink anchored text boxes to fit their contents are now attempted in additional situations (including when overset) in order to address a problem where some imports were seeing a portion of their anchored text boxes left unshrunk for no apparent reason.
• Added support for layers so that unanchored boxes may now be created on a specific document layer using the tag’s layer name parameter. From the Xtags User’s Guide:
<&tbu2(x, y, width, height, box angle, box skew, flags,
item runaround, frame width, frame color, frame shade,
frame style, background color, background shade,
text outset, columns, gutter, text inset, baseline offset,
baseline minimum, vertical alignment, interparagraph maximum,
box name, layer name)>...Text to be placed in the box,
typically containing other tags...<&te>


and

<&pbu2(x, y, width, height, box angle, box skew, flags,
item runaround, frame width, frame color, frame shade,
frame style, background color, background shade, text outset,
placement, picture scale x, picture scale y,
picture offset x, picture offset y, picture angle, picture skew,
picture path name, picture type, box name, layer name)>


If the specified layer does not yet exist, it is created with default color and visibility. If the layer cannot be created, the box is placed on the currently selected (active) layer.

• Fixed a problem where a crash could occur upon File > Get Text with Xtags… if the initial folder contained a file lacking a Classic designation (‘TEXT’, for example) and having a name ending with a period. (Mac OS X only)
• The character resulting from a numeric escape tag is now governed by the <e> tag and mapped into the current platform’s character set. So a Mac-based numeric escape tag like <\#17> now properly generates the TM symbol on Windows rather than a superscripted “a” character.
• When exporting Xtags text, a missing font’s name is now included in the <f"..."> tag rather than being substituted with a question mark. For example, Xtags will now generate <f"Minion Pro Med"> rather than <f"?"> for the missing font Minion Pro Medium.
• Fixed an export problem which was occasionally preventing the generation of certain character attributes applied to text within a “none”-style paragraph with no character style applied. For example, the <cW> tag might not be generated for a span of white text within a “none”-style paragraph with no character style applied.
• Reverting to the paragraph style’s character attributes via <@$p> no longer applies a random font/size/color if the paragraph style references a character style for its character attributes. • Fixed a problem where loading a picture using a relative path of the form ":a folder:a picture file with a very long name.tif" or ":a picture file with a very long name.tif" would result in a file not found error even if the picture file actually existed. (Mac OS only) • Worked around a problem caused by non-conforming XTensions (like PSD Import) where loading a picture was causing Xtags to emit incorrect text in its error messages • A problem in QuarkXPress 6 where the document’s home folder is “forgotten” when the document was opened on a network volume has been worked around (the problem arises because XPress now copies a remote documents to a local version before working on it). Now Xtags will find pictures relative to the document’s folder even when that document is on a network volume. (Documents on a local volume were never a problem.) • When importing tags from a file, both the document’s folder and the source file’s folder will be searched when looking for pictures specified using a relative path, in that order. (What’s new is searching in the source file’s folder.) • Exporting a group containing a box with an illegal shape no longer crashes. Instead, the export will fail with error code -27 (unsupported box shape). • Translation tables now allow the vertical tab escape \v to represent character 11 ( <\#11>). • The “No style” character style is now used instead of “Normal” when a reverting to a “No style”-styled paragraph’s default character style using the <@$p> tag.
• The correct tags are now generated after a <@\$p> tag is emitted within a “No style”-styled paragraph.

## Release: Xtags 4/6.2.1 for XPress 4/6

### Changes

• Get Text with Xtags… no longer hangs with a spinning beachball in QuarkXPress 6.5. (Mac OS only)
• The Get Text with Xtags… dialog now allows the selection of any file with a valid filename extension (e.g., “.txt” and “.xtg”). (Mac OS only)
• Xtags now supports input and output of the full QuarkXPress index tags (XO, XC and XI) when Quark’s Index XTension is present. (Without the Index XTension present and the Index palette open, all index tags will be lost on input or output with Xtags, the same as with Quark’s XPress Tags filter.)

For full index tag documentation, see the appendix in the file Guide to QuarkXPress.pdf (which lives in the appropriate language sub-folder of the Documents folder in the XPress 6.x folder).

Known issue: If you select text containing index entries (index tags), and import or paste over it with Xtags (Get Text with Xtags… or Paste Xtags Text), the index database gets confused. This appears to be a generic problem with all XTensions, not just Xtags, and we’re pursuing it with Quark. One work-around appears to be to close and re-open the Index palette, though that seems to also lose index tag information (and not just with Xtags–it also happens with their own XPress Tags support). Another is to manually delete what you’re replacing, before importing or pasting with Xtags.

• Xtags now properly handles the save text as xtags AppleScript event in the presence of long file names or file names containing Unicode characters. (Mac OS X (6.x) only)
• Xtags once again supports a simple pathname string as a direct argument in AppleScript, working around a change in the Quark system-level coersion handlers. Previously, you’d have to coerce the pathname string with alias. (Mac OS X (6.x) only)
• Xtags now properly outputs text with both paragraph and character style set to “No style”. (Before, it would crash.) (Mac OS only)
• Xtags now supports long file names (greater than 31 characters in length) under Mac OS X. (Mac OS X (6.x) only)
• Xtags now imports pictures with full (72 dpi) preview resolution rather than half-resolution (36 dpi).
• Xtags now supports an Upgrade button in its About… dialog that allows you to re-enter your new serial without hunting around the file system for the old serial storage and deleting it by hand, if you need to upgrade your serial to increase the number of simultaneous copies, etc.
• Xtags now handles multiple text inset values in text box creation properly (it was working before, but the XPress UI wasn’t being notified, so you couldn’t see the settings interactively). (6.x only)
• Xtags now allows the full 2″ maximum on frame corner radii, instead of a 1″ maximum.
• Xtags now properly labels the import option Delete file after successful import rather than …after successful input, in both its preference and Get Text with Xtags… dialogs.

WordPress.org