Metadata: using dash (hyphen) or underscore?

Is there any difference between using a dash or hyphen, and an underscore, in filenames?

For example SKB-B6739-CHOIR or SKB_B6739_CHOIR ?

I ask as I've a client who claims he's having problems opening JPG images on a CD I supplied; the images are all in the format "SKB-B6739-CHOIR". He went on to say that I'm using dashes and not underscores. He also commented that I'm using Mac for processing and he's trying to open them on a PC. I don't see how this last comment could have anything to do with opening a JPG file. It's quite possible that the CD is simply corrupt and a burning a new one would sort it out.

Have not come across this issue before.

My regular importing tool organizes date folders with an underscore; and Lightroom organizes everything with a dash/hyphen, the fundamental reason for my using a dash is that I'm switching to using LR full time, and wanted to be consistent in folder and file naming. Howevdr, previous clients/recipients have not reported any issues in opening my JPGs (formatted with a dash).

Any suggestions, help or advice appreciated.

I've used dashes, underscores, & combinations of both in filenames on both PC & Mac. Never had an issue such as what you describe. Seems like a problem with either his computer or the disk.

Just in case, double check the file to ensure that the .jpg is in the filename extension.

Regarding his point "using Mac for processing;" in the end, a .jpg is readable on both mac & pc. (Just tell him Mac's are better and he's missing all the fun )

You could post a sample of the problem file so members can test on multiple platforms in a matter of minutes.

You're best bet would be to use the "Batch Rename" feature in Bridge to remove the dashes (just to make your client happy) and burn the images on a new disk (which is more than likely the problem). You can still keep your folder & file naming consistent by giving the client a renamed "copy" of your source image folder. (You can also include the original filenames in the comments area of the metadata in the .jpg file)

Hope this helps,

--Chris

I've always avoided dashes in filenames if possible while underscores seem to be ok. There are some websites that do not like dashes (along with some other characters) but the underscore has been ok on those same sites. With this in mind, I have just quit using them.

Under the scenario that you explain there shouldn't be a problem opening the files with the dash in them. I have however found that files on CD/DVD are unreliable and even though it says the copy went fine, I cannot open some of the files off of the disk. This is why I don't rely soley on this for backup but use an external hard drive.

Thanks Sheldon, that's kinda annoying alright. Might have to switch to the underscore if they 'just seem to be ok'.

Backup wise, yes I have two external HDs and burn to cd/dvd too. Clients get their images on cd/dvd and sometimes via download. Luckily this client lives pretty close by so getting another copy to him shouldn't be too taxing.

The hyphen, underscore, period, numbers and letters are all okay in filenames. Some older operating systems may require the 8.3 naming convention. You shouldn't use a period or hyphen as the first character however. On a Mac the period at the front makes the file invisible. Most other characters are disallowed in XMP metadata just as they are in filenames. This is because they have some meaning programmatically. Don't use: / \ : ! @ # $ % ^ < > , [] { } & * ( ) + = in metadata or filenames. The issue with characters is also with compatibility with ISO-9660 Level 1, a standard that is very important to CD reading and writing.