In the same way that different political or religious views can polarise a group of people, so can one specific InDesign feature: Light or Dark interface.
Introduced into InDesign CC in 2013, this change brought InDesign in line with other Creative Cloud products that had a dark interface. That said, I was not a fan and chose to remain a user of the light interface.
Many years later and
Apple released the macOS Mojave with its Dynamic Desktop and Dark mode. The
Dynamic Desktop feature shows a bright desktop during daylight hours and a dark
desktop during the dark hours. In addition, popular apps also followed suit
allowing users to switch from the usual view to a “night mode”.
In addition, I have found myself working late into the night on projects, and have found that a darker interface during these hours is easier on my eyes. That said, I still like to use a light interface when working in daylight hours.
With this in mind, I wondered if it was possible to create an InDesign startup script that – upon performing a common task such as opening a file – would check the time of day and if it was beyond a certain time of the day, would invoke the dark interface… and it was.
This refers to the color of the pasteboard. The number 1 will match the pasteboard color to the interface, whereas 0 will leave the pasteboard white.
So technically it’s not a night-mode per se, but for those who like the light interface until the night-time hours, this script may be something to consider.
In my last article “My Calendar Caffuffle“, I’d mentioned that I was working on a wall planner script for a Christmas release, but due to many factors I was unable to release this script and instead opted for a smaller script that – for many regulars to this site – didn’t really feel like much of a Christmas gift.
To this end, I felt like I let my supporters down and had to make sure that amends were made in the new year. On that note, I was able to work through the issues that held back the script, and I can now release the script free to the public:
This script will create a twelve month planner based on a start month and year, and to an output size in millimetres. There are one of four ways to display the planner based whether the months should appear in rows or columns, and whether the planner should be condensed or expanded. For example:
Before you say “I don’t like the colour”, note that the script creates the necessary styles so that the wall-planner can be tailored to your needs:
Don’t fancy starting the calendar in January? That’s no longer an issue either, the planner can start on any month:
So that’s the free version of the script that can be downloaded from the downloads page now.
Want more? Well, I’m also working on a pro-version of the wall-planner script that will have additional features such as:
highlight school days from known dates, a customised range, OR a text file;
add events from a text file that contains the dates and events;
(in expanded format) begin the planner on any day, not just Monday;
highlight cells based on Find/Change or GREP searches;
additional formatting options (appearance of months and days).
Lastly, speaking of pro-versions, I’ve also been busy improving my long-popular Data Merge to Single Record script for its pro-version release. Don’t panic, the free version will remain, but to access features shown in the dialog box below, the pro-version will be a paid release.
If you’re interested in the pro-versions of the scripts mentioned in this article, please contact me through the contact page.
In the latest Colecandoo Youtube episode, four Data Merge specific features are covered, namely:
Adding faux-returns to a data merge field to split over lines, and subsequent limitations of this technique;
Using GREP styles to swap a character for a glyph during a Data Merge;
Highlighting field codes so that they are easier to see when not showing live data; and
A bug that occurs when a double-quote is at the start of any field in a Data Merge text file.
Faux returns within a field
The faux-returns technique is written about elsewhere, so rather than spoil their presentations, please read the articles directly from the appropriate sources:
I’m a fan of this trick, but emphasise that this is a workaround rather than a long-term solution, given that formatting is limited and there are more appropriate ways of accomplishing this task such as dedicated plug-ins or an XML workflow.
Swap characters for glyphs
Daniel Solis also features a clever trick to swap phrases with glyphs during a Data Merge that uses both GREP styles and ligatures. Again, rather than simply repeat the technique, please see his original video here.
A similar method can be employed using Indiscripts’ Indyfont script, but rather than swapping phrases with glyphs, will swap single characters.
Highlight Field Codes
The video also shows a method for highlighting field-codes when Data Merge is not in the preview mode. It relies on the [Basic Paragraph] style using a GREP style that contains a large highlight, and that any other styles in the document are based off of the [Basic Paragraph] style. It also means the document has to be styled correctly.
I’d demonstrated this technique following a real-world example of a live file where fields were very hard to see, and the file had to have an offset shell printed with variable data printed afterwards, so making sure the shell had no variable data on it was crucial. Using this technique would make finding the field codes much easier to see.
Double Quote bug
Also featured in the video was an issue that once again arose from a real-world example where a customer had provided a database that had double-quotes at the beginning of fields, but no closing quotes, resulting in rather unusual results.
You finally have an approval on that print project you’ve been working on for the last few months. All that’s left to do is make a PDF for the printer and be done with it, right?
Nope. It’s time to do some housekeeping on the file. Let me use this metaphor, once you’ve made dinner, you don’t leave your dirty pots and pans in the sink, do you?
It’s time to do some housekeeping, and in this episode of “must haves” on the Colecandoo Youtube channel, we’ll look at several scripts to keep your files nice and tidy.
Disclaimer
One word of caution with any of the scripts shown in the video. They are all destructive in nature. That is, they intentionally remove items from a document. Make sure you save your work prior to running these scripts, just in case they have a catastrophic impact on your artwork. I’m showing these scripts for educational purposes only, this is not a tutorial on how to use these scripts.
The first script removes items from the pasteboard. Run the script and select the distance from the trim edge and importantly whether threaded text on the pasteboard should be removed.
I can hear some of you now saying “but what if I’ve left important notes on the pasteboard for the next person who works on the artwork”? Well, either don’t use this script, or put your notes on after you’ve run this script.
This script removes any purely empty frames, that is no fill or stroke that have no special settings applied such as text wrap or text on a path. Once run, it scans the document and removes all of these empty frames.
The next script resamples all images over a given resolution to a more appropriate resolution. It’s great for projects such as yearbooks where the resolution of images is often far greater than it needs to be.
Now, I was in two minds to whether I show this script or not. Out of the scripts being shown in this video, this is both the most powerful and potentially most destructive of them. Ultimately, read the instructions before using this script, and make sure you have access to backups in case things go wrong.
Colour
Next, let’s address some colour issues that may have come about from selecting registration by mistake, or left-over swatches from a Microsoft Word import.
Unlike many scripts I’ve shown previously, most of these scripts are buried in forum posts, so it’s a matter of reading the post, finding the script, copying and pasting into a text editor and saving as a .jsx file.
It’s worth noting that all of these scripts only affect colours generated within InDesign, so won’t fix colour issues in links such as PDFs or photoshop files.
Add unnamed colours
Let’s start off with this easy one-line script that adds all unnamed colours to the swatches palette. True, it’s just as easy to select this from the swatches menu. Regardless how it’s run, this should be the first step to cleaning up the swatches. You can cut and paste it from below:
app.menuActions.item("$ID/Add All Unnamed Colors").invoke();
This script launches a prompt that allows you to search for colours that are a given percentage different from each other and merge them to the swatch that appears higher in the swatches panel.
If you’re using a special knockout black swatch and don’t want it to become the default black, perhaps make it a spot colour while running these scripts.
I explain the differences between these colours in more depth in Episode 14.
I’ve written a script that converts RGB and LAB values that appear as shades of grey to equivalent shades of Black, while leaving other swatches alone to be dealt with by another script.
There are two scripts that can take faux black values and convert them either to 100% black or rich black. The faux black is determined by CMYK values beyond certain percentages. In this case, any swatch that is over 70 Cyan, 60 Magenta, 60 Yellow and 90 Black will be converted to either 100% black or rich black. You can dig into the script if you like, and redefine what constitutes a rich black or faux black.
Next is this script that removes any layers that contain no artwork.
Remove unused styles and groups
This is a series of scripts that removes any styles not used in the artwork, as well as unnecessary style groups that may have been left, whether deep in folders or not. In the video it is combined into one “catch-all” script for convenience, but it is the work of many authors, so it’s not right for me to host it. Links to the originals can be found here, here, here, here and here.
Lastly, this script removes all guidelines in a document. I can see that there would be some use for guidelines to remain in a document, but felt it was worth demonstrating.
Preflight
To be sure that the artwork is completely free of issues, we want to make sure that there are no prepress issues. To make sure that the artist complied with the preflight that was associated with the document, there’s the preflight enforcer.
As shown on the Colecandoo Youtube channel before, I’ve prepared two scripts that will either warn or prevent a user from printing or exporting to PDF until all preflight issues are resolved.
So there you have it, over ten scripts that will help make housekeeping of InDesign files a lot easier. If there’s any that I’ve missed or you feel would be worthy of a future video, let me know via my contact page.
