In versions prior to QuarkXPress 8, a reference to a missing picture was always retained exactly as it was specified. 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.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.Fixed a problem in QuarkXPress 8 where the missing picture’s proxy image, the big red question mark, wasn’t being scaled properly to fit its box.Fixed a problem where updates from FileMaker Online would, on some systems, include a leading garbage character.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.Software where it will be available only to that user. Registration information for users lacking administrative privileges remains in HKEY_CURRENT_USER/Software/Em 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.Meaning, so long as an doesn’t look like a paragraph style reference, it will not be treated as one. At-signs appearing in, for example, e-mail addresses within the body of a paragraph of an XPress Tagged field are no longer treated specially, so long as there is an end-of-paragraph or some other tag-like character between it and the next (if any) colon (:).Fixed a problem introduced in 6/7/8.3.2 where updating a link with an empty field with Xcatalog’s “enhanced link editability” preference enabled would corrupt the link or cause it to disappear. ![]() This means that if one person updates from 6/7/8.3.1 (or older), everyone with whom they share documents will need to update their copy of Xcatalog as well. Important: versions prior to 6/7/8.3.2 will not recognize or display links created in 6/7/8.3.2 (or later) due to the addition of full Unicode support in the 6/7/8.3.2 release. This set of release notes covers the whole Xcatalog 6/7/8 series. GDocs comments import as InDesign notes.Release: Xcatalog 6/7/8.3.3.2 for QuarkXPress 6/7/8 Most of the text-level formatting in the GDocs document will import naturally, and GDocs block-level styles are mapped automatically to InDesign styles. After each update, you can open the story editor with change marks showing, to see who changed what. ![]() Any changes on the GDocs side are merged into the the story, even if the latter has been changed. When the GDocs document is edited, you'll see the link's status change to "modified" (showing a yellow alert icon), and you can update the story from GDocs with a double-click on the icon. With DocsFlow, both the InDesign story and the Google Docs (GDocs, below) document can be edited independently, and the links palette will show you the status of both at any point. Further, DocsFlow builds on the built-in InDesign story linking machinery to avoid any learning curve on the design side. And using DocsFlow means you need no special resources to build, maintain or learn the editorial side (which is just Google Docs). ![]() The breakthrough concept embodied by DocsFlow is to marry freely-available and popular web-based editing tools (Google Docs for now) to InDesign, giving you a zero-cost per-seat editorial workflow solution that is extraordinarily easy to manage. Em DocsFlow brings the collaborative editing power of Google Docs to InDesign, providing dynamic linking from any InDesign story to a target Google Docs document, along with the almost magical ability to re-weave any Google Docs document changes into the linked story, on update.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |