TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
RE: Needed: a convention to indicate a path for Windows, Linux, and Mac
Subject:RE: Needed: a convention to indicate a path for Windows, Linux, and Mac From:"Leonard C. Porrello" <Leonard -dot- Porrello -at- SoleraTec -dot- com> To:"Combs, Richard" <richard -dot- combs -at- Polycom -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 5 Mar 2008 09:11:42 -0800
Thanks Richard.
BTW, ellipses are used in C++ code.
Leonard C. Porrello
SoleraTec LLC
www.soleratec.com
-----Original Message-----
From: Combs, Richard [mailto:richard -dot- combs -at- Polycom -dot- com]
Sent: Tuesday, March 04, 2008 10:15 AM
To: Leonard C. Porrello; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: Needed: a convention to indicate a path for Windows, Linux,
and Mac
Leonard C. Porrello wrote:
> The applications I am documenting runs on Windows, Linux, and
> Mac. In several places, I need to indicate to users that the
> files they need are located at the application installation
> location on the hard drive. In Windows, this is "c:/Program
> files/Product_Name/Folder/File.cfg". In Linux, the path is
> different, starting from the fact that there is no "c:".
>
> I need a convention to indicate path prior to
> "/Product_Name/Folder/File.cfg". The convention needs to work
> for Windows, Linux, and Mac.
Not only do all three use different directory separators -- backslash,
forward slash, and colon, respectively -- but the location itself won't
be the same (and may not be the same for all installs on a given OS).
So, don't specify an absolute path, always specify the path relative to
the installation directory. In descriptive text, just refer to "the
Folder subdirectory of the Product_Name installation directory."
In code or path examples, I'd use the forward slash as separator because
that's the UNC (Universal Naming Convention) standard, it works for both
Linux/UNIX and (usually) DOS/Windows, and the Mac-heads should
understand it. You might use a variable for the installation directory,
putting it in italics, angle brackets, or both:
"<_ProductHome_>/Folder/File.cfg"
>
> I currently have ellipses (".../Product_Name/Folder"), but my
> development lead tells me that this won't do as ellipses are
> sometimes used literally. Does anyone have any other ideas?
One and two dots in a path have special meanings: "./Folder" means "the
Folder subdirectory of the current directory," and "../Folder" means
"the Folder subdirectory of the current directory's parent directory."
If three dots has a special meaning, it's news to me.
HTH!
Richard
------
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
------
rgcombs AT gmailDOTcom
303-777-0436
------
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-