To be, or CSV, that is the delimiter

From time to time I receive emails requesting support for some of the scripts that I offer through the site. Since InDesign began to support semicolon separated text files for data merge, one particular issue began to receive more requests than normal.

The emails were consistent in nature – users had downloaded the data merge single or pro script and ran the script on files they had prepared. Instead of users being able to select from the fields to the left, all of the fields appeared in one line.

This behaviour usually occurs when the script runs a data merge database that had a CSV extension, but was actually separated by semicolons rather than commas. I’d explain this back to the user and ask them to try a different CSV export from Excel, or use my preferred file export of UTF-16 text from Excel.

However, many users who had exported from Excel to CSV said that this did not change the issue and the problem persisted. Usually the problem was that – despite choosing CSV from Excel’s export options, the software was still using semicolons as a delimiter rather than commas. Luckily, exporting to UTF-16 text usually resolved the issue.

On that note, I was uncomfortable with this issue and tried to replicate an Excel export from CSV that would use semicolons as delimiters rather than commas, but I couldn’t replicate this behaviour. But then I stumbled across the following article.

In short, the article says that Excel uses the user’s locale to determine what delimiter to use for CSV files. In short, if you use a comma to separate a dollar value from cents rather than a full-stop, then a CSV will likely export with semicolon delimiters rather than commas.

Adjusting this setting is not so simple, especially for Mac users like me – the adjustment is to change a system preference that uses the appropriate currency format, but that changes lots of other related information, so this isn’t an option.

Ultimately, if you are using the data merge to single record script, and are doing so with data exported from Excel, I highly recommend that you do so with a UTF-16 Unicode Text format.

I’ll admit this was a phenomenon I was unfamiliar with, and somewhat frustrated that a file format that itself stands for comma separated variables – isn’t actually separated by commas but is in fact separated by semicolons… depending on what system locale your computer is set to and that Microsoft Excel obeys.

Highlighting the benefit of GREP… literally

I’m a fan of the GREP feature of the Find/Change dialog box in Adobe InDesign as it allows me to search for patterns of characters within text based on regular expressions.

As handy as this feature is, I always require assistance writing my GREP searches, just in case my patterns are either too greedy; or not greedy enough. For example, I have a GREP search to find duplicate entries and remove them, but in InDesign the only way to know if I have this correct is to press the Find Next button in the search.

A better way to identify if I have my GREP search correct is to see it in real-time. Luckily, text editors such as BB Edit have this feature.

InDesign’s latest rival, Affinity Publisher, not only has its own flavour of GREP, but also shows all results in the Find and Replace dialog box, though I have to click on each result in this dialog to see where they are.

But it would be great if InDesign highlight the GREPs ahead of time like these two applications. The good news is that it can, but it requires the GREP editor script from Peter Kahrel that has been featured on Colecandoo before.

Thanks to Peter’s GREP editor, I’m now able to see that in this example there are three search results and they are all highlighted.

This tool comes in very handy as it assists me to write more complicated GREP searches, such as this one that is looking for time formatting. This lets me know in real-time if my selection is selecting too much information, or not enough – and in this example, it isn’t enough as the times without the minutes aren’t getting selected.

As for longer, more complicated chains of GREP code, there are resources out there that have pre-baked search chains that other users have already submitted to sites such as RegExLib.com or the Treasures of GREP Facebook group.

Stop Press!

After this article was initially published, I was alerted to another InDesign javascript by Kerntiff Publishing System that has a similar behaviour to Affinity Publisher’s search. The script is called GREP Xtra.

There is also an additional script released in 2013 by Roland Dreger that performs as a combination between Peter Kahrel’s script and the InDesign user interface. That script is called Highlight GREP.

Page Size Lies

UPDATE 2021-10-08: Enfocus Pitstop has released an update that now resolves the error that was brought about by the update of Adobe Acrobat DC. However, I will leave the article posted for posterity.

Have you ever received a client’s InDesign file and sent it to PDF or print, only to measure the document and realise it is a different size to the one that was in InDesign’s document setup?

What could cause this issue to arise?

The page tool has been used

It is likely that at some stage between the initial creation of the file and receiving the file, at least one page size in the document has been changed using the page tool.

Preflight should tell me… right?

Well, that depends. If you are using either of InDesign’s default preflights (i.e. [Basic] or Digital Publishing) then preflight will not flag a warning.

I’ve discussed my frustrations with InDesign’s default preflights in Episode 19 over on the Colecandoo Youtube channel. However, if you are using a more comprehensive preflight such as the VIGC profiles, then this is detected as an issue:

More comprehensive preflights such as the VIGC profiles look for much more than InDesign’s default preflights e.g.:

As a side-note, the Document portion of the Preflight Profiles dialog box is also handy for authors who are making saddle stapled publications that must have page-counts in multiples of four (an issue I’ve faced several times) e.g.:

Or for larger offset publications where folded page signatures are likely to be prepared in minimum multiples of eight e.g.:

There are also scripts to highlight this

I’m working on a startup script that – upon export or print – should provide an alert dialog box warning that there are size discrepancies… but in the meantime there are some other scripts that work by providing alerts to a document’s page sizes, or a script hosted over on Kasyan Servetsky’s curated list that makes a list of the page sizes in a document (look for “Check all pages” once the link loads).

What I think would ultimately help everyone would be if the Document Setup window would change once page sizes in a document were no longer the same, such as this mockup e.g.:

PDF spreads from InDesign: radio button vs dropdown

When proofing PDFs of books to clients, it is often important that the client sees the proof as a series of left and right page spreads. PDFs made with any of InDesign’s default settings (these are the options in the Export Adobe PDF dialog box in the top dropdown field in square brackets) will show the PDF in Adobe Acrobat as it’s default view – single pages.

Adobe Acrobat does allow for pages to be presented in two-page appearance, but this is controlled by the user. If the user is unaware of this feature, then they will be viewing the PDF using Acrobat’s default single page view.

It is possible to change the view settings of a specific PDF while in Adobe Acrobat and this is done from the Properties option from the File menu.

The page viewing defaults of Acrobat itself can also be changed, but this will view any PDF that has not had its preferences changed when the PDF was made.

It is worth noting though that prior to 2015, the widely accepted method to prepare a PDF as readers spreads was to do this from InDesign’s Spreads radio button in the Export Adobe PDF dialog box.

While this does prepare what appears to be readers spreads, it does so with some disadvantages:

  • The centre spread line cannot be seen. This can be addressed by using the page border script from Indiscripts that applies a page border to all pages. Run this script prior to exporting the PDF to generate the page border and then export the PDF, then rerun the script to turn the border off.
  • The page count is incorrect. The folios will still appear to be correct within the PDF, but the page navigation itself will show the page count as half the number of original pages plus one (e.g. a 16pp file saved as spreads will now show up as 9pp in the PDF’s navigation).

However, from June 2015 it has been possible to set the default view options when exporting a PDF from InDesign for viewing in Adobe Acrobat.

This allows PDFs to contain the correct page count and to also show the page split between the spreads while still showing the pages as spreads.

Should be problem solved, right?

Unfortunately, no. Despite the dropdown now being available, there’s no ideal way to prepare readers spreads to suit all PDF readers or platforms.

  • Unless InDesign users read all of InDesign’s patch notes (maintained by James Wamser) or were otherwise made aware of this change, then normal habits would persist, and users would continue to prepare spreads using the spreads radio button.
  • If the dropdowns had been used, this only makes viewing the spreads possible in Adobe Acrobat (Reader or Pro), but unfortunately this software is no longer the preferred option for viewing PDFs. Besides Mozilla Firefox and Adobe Acrobat, most PDF readers only support single page view.
  • Even if Acrobat or Firefox are being used, users can still override the view either manually, or using Acrobat it can be done by default using accessibility in the preferences

So what can be done?

There are effectively four options:

First option is to prepare PDFs based on an audience using Acrobat only as their reader and use the dropdown option for spreads. If the PDF is exported from InDesign using a PDF/X standard, Acrobat will also show the PDF as it appears in InDesign’s overprint preview.

Second option is to prepare a PDF using the pre-2015 method of using the spreads button and the Indiscripts page border script.

Third option is to lobby the manufacturers of the non-Adobe PDF reader software to bring their software into line with the PDF specifications set out by Adobe itself (and while they are doing that, also update their readers to also accept form fields and commenting functions!).

Last option is to do nothing and leave the pages as single spreads… and that isn’t necessarily a bad option. If the PDF is being created for onscreen viewing only, and the viewer must see something that is intentionally spread over two pages such as an image that crosses over two pages, then single pages should be fine.

Last word

It is of note that people are not just consuming information on a single desktop monitor, but may have two or more monitors in which software windows are being juggled around; or on a mobile device that is more natural to be held in a portrait fashion. Social media apps such as TikTok and Instagram are designed for mobile devices to be held in a portrait orientation. It’s hard for me to admit, but left and right hand pages are just a legacy of printed books as their assembly creates this phenomenon. Unless there is a crossover between the two pages, a reader will usually read the content on one page, adjust their gaze and read another – their focus of vision can’t be on both pages at the same time.

Also, if the PDF is intended for print by a printing company, don’t provide them a PDF as readers spreads as they won’t be able to impose the pages for printing without breaking the PDF back into single pages.

%d bloggers like this: