Punctuation marks in file names
in [Mac Systems]
|
From: Fred Moore on 19 Jan 2010 17:30 In article <hj3773$p2u$1(a)news.eternal-september.org>, Wes Groleau <Groleau+news(a)FreeShell.org> wrote: > Barry Margolin wrote: > > There are 3 OSes in common use these days: Windows, Unix/Linux, and Mac > > OS X. I think 67% of them allow that filename. > > Two out of three O.S. families allow a slash in a filename? > Really? Here is a handy reference for keeping this all straight: <http://www.comentum.com/File-Systems-HFS-FAT-UFS.html> In my personal experience with OS 10, I have found that the Finder usually keeps things straight for files or folders containing a slash(/); but often times applications do not. Overall, I found it easier to avoid problems by not using a slash in a folder or file name in 10 though I often did in 9 and previous. (RIP, A/V ƒ)
From: Warren Oates on 19 Jan 2010 18:13 In article <fmoore-049832.17303019012010(a)feeder.eternal-september.org>, Fred Moore <fmoore(a)gcfn.org> wrote: > In my personal experience with OS 10, I have found that the Finder > usually keeps things straight for files or folders containing a > slash(/); but often times applications do not. Overall, I found it > easier to avoid problems by not using a slash in a folder or file name > in 10 though I often did in 9 and previous. (RIP, A/V ƒ) I still don't even put spaces in filenames that might leave our Macs. Our sever is BSD, most of our clients use Windows (some Mac); we use underscores instead of spaces, only one extension (and one that makes sense), and no punctuation (no kangaroos and one redeemer). -- Very old woody beets will never cook tender. -- Fannie Farmer
From: Paul Sture on 20 Jan 2010 06:22 In article <018cbe48$0$11351$c3e8da3(a)news.astraweb.com>, Warren Oates <warren.oates(a)gmail.com> wrote: > In article <paul.nospam-8041E4.13054118012010(a)pbook.sture.ch>, > Paul Sture <paul.nospam(a)sture.ch> wrote: > > > ISO style dates for me every time, so they sort in ascending order. > > > > Here's some bash to produce file names with YYYY-MM-DD-HHMM > > > > NOW=$(date +"%Y-%m-%d-%H%M") > > TARFILE="$HOME/backups/accounts-$NOW.tar.gz" > > The validation cops like this kind of thing: > > 2010-01-18T09:27:57-05:00 > > True -- that's how they want you to do dates in xml stuff; there's a > whole bunch of duration/period arithmetic lets you get it to CCYY-MM-DD. > Fortunately, php5 has a constant that produces it. It's certainly > sortable. Methinks that might be problematic if you are dealing with multiple time zones, but then you are probably getting into application or business specific areas. -- Paul Sture
From: Paul Sture on 20 Jan 2010 09:15
In article <1jckafg.1hi5a9gqq9n23N%dempson(a)actrix.gen.nz>, dempson(a)actrix.gen.nz (David Empson) wrote: > Microsoft has a knowledge base article which explains the above for > Windows 95, 98 and NT 4.0 but I can't find anything official which > covers more recent operating systems. From an experiment and evidence > from other web sites, XP has the same restrictions. I don't have access > to Vista or Windows 7 but haven't seen any comments to suggest the rules > have changed. > > http://support.microsoft.com/kb/177506/en-us I don't think NTFS has had any significant changes since NT 4.0, so don't expect Vista or Windows 7 to be any different here. -- Paul Sture |