Release: Xtags 6/7/ for InDesign CS4/5/5.5/6

June 28, 2012 by

This release of Xtags for InDesign adds support for InDesign CS6, officially ends support for CS4, improves compatibility with InDesign’s Smart Text Reflow and fixes an issue with the &it tag.


With this release, the CS6 plug-in now requires a valid Xtags 8 (CS6) serial number.

This release bundles our InFlow companion plug-in, which may be required for your tagged text imports to automatically add pages properly. Note that InFlow is not installed by the Xtags zxp installer; instead, you’ll need to double-click the separate InFlow zxp installer file.


  • Adds support for InDesign CS6.
  • Adds support for new version 7 XPress Tags: p (opacity, ignored), n (language), G (ligatures), \e (en space) and version 7 paragraph rules (opacity parameter, ignored). Note that Quark changed the meaning of a couple of their special character tags with its move to version 7 tags. The \m tag is now an em space (was an em dash), and the \f tag is now a flex space (was an en space) which is converted to a regular space in InDesign.
  • Adds a \k special character tag to insert an InDesign style break character, since Quark is now using \e as an en space tag in version 7. The \e tag will still produce a style break in pre-version 7 tags (imported tags prefaced with a <v2.0> tag), while the \k tag will produce a style break in all tag versions.
  • Defaults to version 7 tags on import, if no version is specified in the imported tags with a <v...> version tag. Add a <v2.0> at the start of your tagged text to retain pre-version 7 behavior.
  • Exports all tagged text as version 7 tags.
  • Improves compatibility with InDesign’s Smart Text Reflow feature, such that page additions are now performed as part of the import. Scripts that drive tagged text imports should no longer need to pause (to let the document settle) before saving the document.
  • When importing InDesign Tagged Text using the &it tag, a start file tag is now allowed and, if present, indicates the desired encoding of the import. A narrow-encoding start tag like <ASCII-MAC> at the beginning of the tagged text now forces the tagged text to be treated as Roman/Latin characters. Likewise, a wide-encoding start tag like <UNICODE-MAC> forces the tagged text to be treated as Unicode characters.

    Note that the special character tag <0xNNNN> is recognized by only the ASCII and Roman/Latin (i.e. non-Unicode) encodings.

    For example, <&it"""<ASCII-WIN>bullet character: <0x2022>."""> will now properly place the bullet character.

    The default encoding, when no start file tag is provided, has not changed and is still <UNICODE>.

© 2010 Em Software - Business WordPress Theme by ThemeShift