Filepaths (was Re: Mif2Go graphics question)
Never, really? Only letters and digits? Since I started in the Unix world (oh so long ago), I personally hate the use of spaces in file names and directory paths, but have always used an underscore in its place if really necessary to help clarify the name. Extra periods also can be used, it just looks awkward to my eyes. The plus symbol is very dangerous as you point out, and although legal I don't like using a minus (hyphen) either (as it looks too much like the unix command/param switch to me). Quotes and apostrophes are a disaster IMO as well. Just my $0.02 – Les Smalley --- On Thu, 9/10/09, Jeremy H. Griffith jer...@omsys.com wrote: The next thing I'd do to diagnose is open a Command Prompt window, enter the commands we use by hand, and see if any problem appears: cd C:\rep\documentation\trunk\MEMS+OmniHelp\MEMSplus copy /Y C:\rep\documentation\trunk\MEMSplus\*.jpg copy /Y C:\rep\documentation\trunk\MEMSplus\*.gif See if the files are really copied this time. If not, the path is wrong. But I suspect they will be copied. When we do the copy, we add one more part, the destination path, to each copy: C:\rep\documentation\trunk\MEMS+OmniHelp\MEMSplus Why would that be a problem? Because + has a meaning to the copy command, and will make the whole line mean something else. That is why you should NEVER, NEVER, NEVER use any characters in a file or path name other than letters and digits... HTH! -- Jeremy H. Griffith, at Omni Systems Inc. jer...@omsys.com http://www.omsys.com/ ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: Filepaths (was Re: Mif2Go graphics question)
On Fri, 11 Sep 2009 06:05:05 -0700 (PDT), Les Smalley l_c_smal...@yahoo.com wrote: Never, really? Only letters and digits? Yes. There are a few more that you can use under most (but not all( circumstances, and several that only bollix one or two commands, but nobody can remember which ones thay are. ;-) So the only *safe* rule is to use none at all. That, people *can* remember. ;-) Since I started in the Unix world (oh so long ago), I personally hate the use of spaces in file names and directory paths, Yes. Those are not fully supported in Frame either, despite claims to the contrary, probably because of Frame's UNIX roots. but have always used an underscore in its place if really necessary to help clarify the name. Some UNIX systems will object, and if they turn up in a CHM's TOC you will have problems, but otherwise they are reasonably safe. Personally, I prefer CamelCase; it's harmless in Windows (where file and path names are case-insensitive), and OK in UNIX (which *is* case-sensitive, as in Web names) if you use it consistently. Extra periods also can be used, it just looks awkward to my eyes. It can also throw some applications that check extensions off, but, again, it's *mostly* safe. ;-) The plus symbol is very dangerous as you point out, and although legal I don't like using a minus (hyphen) either (as it looks too much like the unix command/param switch to me). It *is* the switchchar, and is even accepted as that in Windows. Quotes and apostrophes are a disaster IMO as well. Yes, and commas, and much more. Which is why I say, Avoid them all! -- Jeremy H. Griffith, at Omni Systems Inc. jer...@omsys.com http://www.omsys.com/ ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Filepaths (was Re: Mif2Go graphics question)
Never, really?? Only letters and digits?? Since I started in the Unix world (oh so long ago), I personally hate the use of spaces in file names and directory paths, but have always used an underscore in its place if really necessary to help clarify the name.? Extra periods also can be used, it just looks awkward to my eyes. The plus symbol is very dangerous as you point out, and although legal I don't like using a minus (hyphen) either (as it looks too much like the unix command/param switch to me).? Quotes and apostrophes are a disaster IMO as well. Just my $0.02? ? Les Smalley --- On Thu, 9/10/09, Jeremy H. Griffith wrote: The next thing I'd do to diagnose is open a Command Prompt window, enter the commands we use by hand, and see if any problem appears: cd C:\rep\documentation\trunk\MEMS+OmniHelp\MEMSplus copy /Y "C:\rep\documentation\trunk\MEMSplus\*.jpg" copy /Y "C:\rep\documentation\trunk\MEMSplus\*.gif" See if the files are really copied this time.? If not, the path is wrong.? But I suspect they will be copied.? When we do the copy, we add one more part, the destination path, to each copy: ? C:\rep\documentation\trunk\MEMS+OmniHelp\MEMSplus Why would that be a problem?? Because "+" has a meaning to the copy command, and will make the whole line mean something else. That is why you should NEVER, NEVER, NEVER use any characters in a file or path name other than letters and digits... HTH! -- Jeremy H. Griffith, at Omni Systems Inc. ? ? http://www.omsys.com/
Filepaths (was Re: Mif2Go graphics question)
On Fri, 11 Sep 2009 06:05:05 -0700 (PDT), Les Smalley wrote: >Never, really?? Only letters and digits?? Yes. There are a few more that you can use under most (but not all( circumstances, and several that only bollix one or two commands, but nobody can remember which ones thay are. ;-) So the only *safe* rule is to use none at all. That, people *can* remember. ;-) >Since I started in the Unix world (oh so long ago), I personally >hate the use of spaces in file names and directory paths, Yes. Those are not fully supported in Frame either, despite claims to the contrary, probably because of Frame's UNIX roots. >but have always used an underscore in its place if really necessary >to help clarify the name.? Some UNIX systems will object, and if they turn up in a CHM's TOC you will have problems, but otherwise they are reasonably safe. Personally, I prefer CamelCase; it's harmless in Windows (where file and path names are case-insensitive), and OK in UNIX (which *is* case-sensitive, as in Web names) if you use it consistently. >Extra periods also can be used, it just looks awkward to my eyes. It can also throw some applications that check extensions off, but, again, it's *mostly* safe. ;-) >The plus symbol is very dangerous as you point out, and although >legal I don't like using a minus (hyphen) either (as it looks too >much like the unix command/param switch to me).? It *is* the switchchar, and is even accepted as that in Windows. >Quotes and apostrophes are a disaster IMO as well. Yes, and commas, and much more. Which is why I say, "Avoid them all!" -- Jeremy H. Griffith, at Omni Systems Inc. http://www.omsys.com/
