Long Hours of Design

One of the tremendous things about working as a Creative is—well, the creativity.

Over my years working as a graphic designer, I’ve had the opportunity to work on projects for all kinds of clients—from political direct mail, to non-profits, to very large corporations. Variety is the “spice of life” and so it is for a designer.

And I’ve also gained the ability to be completely flexible, showing my muscle in InDesign one moment, and jumping into CSS the next.

While most of my formal training comes from the school of hard knocks, time and again I’ve proven myself as a competent, creative, hard working, and ever patient designer.

I consistently receive rave reviews from peers, managers, and clients; and I constantly work to improve and learn, and to satisfy an unquenchable thirst to be the best designer I can be.

Never a round peg in square whole, I lend myself to malleability and will never back down from tackling projects I’ve never tackled before.

All this is creativity in it’s purest form—molding yourself and your projects to make something out of nothing.

You know you’ve had waaaay too much time working when you start seeing faces in abstract paper paterns.

I’m going to the gym.

Phenomenal, gigantic projects! Itty bitty versioning system. ^{[ 1 ]}

Of course, when we think of a version control system (usually intended for source code), we think of Subversion, CVS, Adobe Version Cue, and their ilk, and generally regard such systems as multi-user entities.

However, even the solo-designer needs some kind of versioning system — even as simple as a “Version 1”, “Version 2” etc naming convention. Many design groups I’ve worked with use such a convention.

This system works fine for the solo designer and the normal design group for a few reasons:

1. The learning curve for other systems (Version Cue, etc.) is relatively high and can be a lot of time to invest.
2. While there might be multiple people working on similar projects (in a print arena), generally there is only one person working on a single file at a time.
3. Source code versioning tools such as “diff and merge” are useless for print design projects; thus, any extra overhead involved in CVS, etc is unnecessary.

So, if we are going to use some kind of simple versioning system, it should at least be A. consistent — versions are updated the same throughout the system. And should be B. relatively easy to implement and use.

I decided to solve this problem with a simple AppleScript ^{[ 2 ]}

Open this script in Script Editor

or

Download this Script

Select a file (or files) in the Finder and then run this script. This script duplicates that file(s) and adds “v2”  to the new file. Run the script on that file, and it duplicates and names “v3”. It also asks you for version comments, which are added to the file.

Easy and consistent.

Et violå! An “itty-bitty” versioning system.

GREP: Add Periods to End of Paragraph

GREP: Add Periods to End of Paragraph

Find What: ((?<!.)(w|[!?)])(?!.)$)|((?<!.)( )$)

Change to: $1.

What: This GREP query finds paragraphs which don’t end in a period. The “Change to” adds a period at the end of the paragraph.

Why: Often, I get text from a Word document with missing periods. It’s rare that these occur MID paragraphs; they are often left off before line breaks.

Or, fragments (like bullet points or cell contents) get turned into full sentances, and periods need to be added.

I wouldn’t recommend running this query as a “change all” on your whole document, but run it one to the next.

Doing this by hand isn’t always all that tedious, but using the “Find / Change” panel, especially for discontinuous paragraphs, is substantially faster.

How:

1. “Negative Look-behind” — “This text only when is is NOT preceded by…”

1A. A period. ^{[ 1 ]}’

Sometimes you have a whitespace character after a period. So we ignore those.

2. Any word character

2A. - or -

2B. Either ! or ? or )

The paragraph is either going to end with a letter (a “word character”) an exclamation mark, a question mark, or a close parens. So we’re searching for one of those.

3A. “Negative Look-Ahead” — “ONLY if this is NOT followed by…”

3B. A period

We don’t want to find characters followed by a period — those don’t need to be fixed. So we find ones without.

4. Search for this at the END of a paragraph

OR ( | )

5. “Negative Look-behind” — “This text only when is is NOT preceded by…”

5A. A period.

Sometimes we find the end of a paragaph, with a hanging whitespace and no period. So, we want to search for this. It’s easier to look for it as an “or” statement. In addiiton, when we place a period in, we don’t want to keep that extra space. Doing it this way allows us to do that.

6. A space

7. Search for this at the END of a paragraph

I’m generally on my Mac, and if I’m on a PC, I rarely am doing anything serious or designerly. So I never knew this:

To add the ellipsis ^{[ 1 ]} punctuation mark to text, hit Option-semicolon (Mac) or Alt-0133 (Windows).

Really? You have to type Alt-0133? ^{[ 2 ]}

I’m glad I don’t have to remember that.

Underline-y Goodness

Paragraph rules and underlines are highly under-appreciated.

Here’s a fun little underline technique for creating a tag exclaiming the newness of an item.

"New" Tag

"New" Tag

This is pretty simple.

1. Type “New” with a space before and a space after.
2. I’ve styled this with small caps and brought the size down a bit.
3. Now, we create an underline, staring with the space before NEW and ending with the space after. Make the “Weight” about the same size as the rest of the body text. Adjust the offset until it looks right.
   
   New Tag Underline Settings

   New Tag Underline Settings

   That’s it!