Login  |  Register          Free Newsletter Subscription
industry leaders
Subscribe to Graphic Arts Monthly
Premedia Trends   


Link This | Email this | Blog This | Comments (7)


Concatenation got your tongue?
July 21, 2008

A couple of days ago I began a rant about file naming. This is a continuation of that rant.

Yesterdayday I shot 463 photos of a bicycle race in my town. It was a good day for bicycle race photography. In the regular course of business, I shoot a lot of photos. Last Friday afternoon I shot 63 photographs for a catalog of paintings. These paintings are as large as nine feet by three, and as small as three feet square. I named the photos after the names of the paintings, and added the artist’s name to each one.


One of my 463 bicycle race photos. For this blog I have named it SLOCriterium281.jpg. In my archive I named it SLO Criterium 2008 281.dng. I use the concatenated file name only when I must, and this blog envitonment – which is HTML-based – requires a concatenated name. Otherwise I wouldn't do it.
I do this so much that I have developed a discipline that is pretty close to fool-proof. I use simple words. I never abbreviate (except for common abbreviations like St., Blvd., Ave.). I never use cute words or nicknames. And, I put spaces between the words.

Now, some of you Windows brethren are thinking “But Windows requires you to concatenate words in filenames.” NONSENSE!! Just try it! You can type over 1,000 characters in a file name in Windows, and word spaces are perfectly legal. It’s the Macintosh operating system (based on UNIX) that is the laggard here. Hell’s bells... I tested this the other day, and I discovered that I could write a whole paragraph as a filename on a Windows machine (MS Word still inflicts unnecessary filename limitations on both Mac and Windows).

And, to test this on the Mac, I just named a folder “We, the people of the United States, in order to form a more perfect Union, establish justice, provide for the common defence, promote the general welfare, and secure the blessings of liberty to ourselves and out posterity, do ordain and establish this Co”.

Oh, rats! I couldn’t use the entire preamble to the Constitution as a folder name.

So, when you’re saving that customer project, a library of photos, illustrations, color separations, plate files or whatever it is you’re about to save... wouldn’t it be easier to name it with ITS NAME than some stupid concatenation of job ticket number, and some made-up abbreviation that you’ll never remember when you’re tearing your hair out trying to find the file three years from now?

How about Job number, customer name, date, and job description in complete words separated by word spaces?

Which makes more sense?

Prtwkpst08fnl.indd

or

Printing Week Poster 2008 final.indd

I promise that two months (or two hours) from now you will never remember how you abbreviated Prtwkpst08fnl. It’s just impossible. So, give yourself a break and introduce words and spaces to your file names.

Almost every day I search for files, photos, illustrations and projects that I did a few months or a few years ago. My searches are usually uneventful – and successful. When I need to search for an Illustration of the American Flag, I search for “American Flag” and – I find it! What a concept!

And, be careful not to be too generic! If bicycle race is good, how about adding the date of the bicycle race? It won’t be the last bicycle race in history, and it will make it a hell of a lot easier to identify one year’s bicycle race from another when you are searching for photos in 2011.

I rest my case.

Posted by Brian Lawler on July 21, 2008 | Comments (7)


July 21, 2008
In response to: Concatenation got your tongue?
Coopkev commented:

Thankyouverymuchforthegoodadvice.




July 21, 2008
In response to: Concatenation got your tongue?
RifRaf_IA commented:

Should we add an asterisk* and be sure to include a footnote regarding troublesome characters across platforms? The ones that stick out are / \ : for file naming (there are others, I am sure). Also, what about software programs that aren't so friendly to certain characters? You mentioned HTML and the Internet, but many a download of PDF from the web substitutes %20 for a space, what is up with that, and can't we get those programmers to fix? For old timers like me, the willingness to embrace 'illegal' characters and spaces is as much rooted in naming convention problems from software than anything else. I'd be happy to use and will probably expand my use of spaces more, because I agree with your 'plain talk' naming! It would be nice to get wider, consistent acceptance. To show my willingness to consider change, let's change my display name to: Rif Raf, IA




July 21, 2008
In response to: Concatenation got your tongue?
Brian Lawler commented:

UNIX servers substitute the %20 for spaces, and there is no getting around that. But, in the normal course of business – archiving and storing everyday work, there is no problem with word spaces.




July 22, 2008
In response to: Concatenation got your tongue?
blekenbleu commented:

>> UNIX servers substitute the %20 for spaces NOT! Webservers and others make these restrictions. Solaris, BSD and linux allow filenames such as: oh, what a beautiful morning .. although you will need to quotate when using in shell commands.




July 24, 2008
In response to: Concatenation got your tongue?
Brian Lawler commented:

My apologies. It is in fact the Web server that makes the substitution, not the UNIX server itself.
That does not make the problem go away. We should ask Mr. Berners-Lee to go back in time and repair that flaw in the system.
Brian P. Lawler




July 28, 2008
In response to: Concatenation got your tongue?
Bill commented:

I saved a file that someone had named with a really LONG filename. I could NOT move it, or delete the subfolder, until I went thru DOS and manually renamed the file to a shorter length. So beware the ultra long file name. (This was under WindowsXP) There IS a limitation to the number of characters.




August 6, 2008
In response to: Concatenation got your tongue?
Brian Lawler commented:

Bill's comment is valid... there may be limits still in file naming (perhaps this occurred between different versions of Windows). But I still argue that file names should be clear, unabbreviated, and easy to read, search for, and find.





POST A COMMENT
Display Name or Registered Users Login Here.
Please restrict submissions to less than 7,000 characters (including any HTML formatting).

Before submitting this form, please type the characters displayed above. Note the letters are case sensitive:


Advertisement

Advertisements




linkExperts


About Us   |   Advertising Info   |   Site Map   |   Contact Us   |   FREE Subscription   |   Industry Links   |   RSS
© 2008 Reed Business Information, a division of Reed Elsevier Inc. All rights reserved.
Use of this Web site is subject to its Terms of Use | Privacy Policy
Please visit these other Reed Business sites