Since releasing EdiCue v1 nearly 12 years ago to the day, I’ve received an abundance of user feedback and feature requests for the application. As I live in Australia, I would implement an update while clients slept, where possible, so they could wake up to an email containing a link to download a pre-release version. Other requests required extra patience.

Being able to transfer ADR cue data from one system or application to another can save hours of manual cueing, or copy and pasting of individual data fields. However, the most common way of transferring this data is via a text file, and there are several things about this method that can get you stuck. When dealing with non-English text, or transferring between different operating systems, there’s a good chance your data won’t come across as expected.

Following on from my previous post explaining the background on how text files work, here I will go into examples of how to manage text files and prepare them for import into EdiCue.

While printing ADR cues in EdiCue, text characters can sometimes be displayed incorrectly. If this is happening to you, you probably have a 'text encoding' issue.