Bug Updates: 6.0.1

When it comes to bug fixes, seeing is believing. After installing the 6.0.1 update on my Mac, here's what I saw.

I finally got around to installing the update to InDesign CS4 (6.0.1) this afternoon, and the first thing I did was check the status of some of the bugs I’d seen in 6.0. I know certain fixes have already been reported, I just sleep better having seen them with my own eyes.

1. The Missing Master Page Items in Placed INDD. I placed 10 pages worth of INDD, containing master page items (both overridden and not), plus a variety of local items. Everything appeared, updated, and output as expected. Same results when the placed file was from CS3.
Bug Verdict:
Squashed.

2. Missing Images in INX. I exported to INX format with missing images. When I opened the INX, the new document contained garden variety missing links, with the names intact. No “fo” nonsense in the Links panel. Yay!
Bug Verdict:
Squashed.

3. The Reluctant Book Panel. I created a new document and a new book. Tried to drag the document from its title bar icon into the book with the two windows overlapping. Same as before, nothing happened. But if I move the book so it does not touch the document window, I can drag the document in. This is a pretty minor one; it just annoys me that it should work but doesn’t.
Bug Verdict:
Alive and Wriggling.

4. Export as plain text with a text variable. I don’t think this one has been described here so far. If you have content that includes text variables, and try to export in Text Only format using Default Platform encoding, InDesign quits. I created a new document, added some placeholder text and a text variable. Tried to export as Text Only, with Default Platform encoding. Zap! InDesign vaporized.
Bug Verdict:
Alive and Wriggling. But there is an easy workaround for this one: just choose either UTF8 or UTF16 encoding and the export works fine with text variables.

Bookmark
Please login to bookmark Close

This article was last modified on December 19, 2021

Comments (7)

Leave a Reply

Your email address will not be published. Required fields are marked *

Loading comments...