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.
Open a a web browser, and go to a URL. Experienced network users would
naturally know what you mean when you say ftp to
ftp://<forsure>.<theyknow>.<howto/downloads.
If you're giving this a lot of thought because you have hand-holding
responsibility for new users on the network, I imagine you can assume
they're using browsers and they will go to.
But you know what? FTP is a mainstay of network file serving. It has a
rich variety of FTP tools grown up around it. For heaven's sake, take
your pick, on any operating system, of stand-alone download managers,
and FTP GUIs and command line FTP with its own set of FTP commands, to
name a few ways that experienced users might find more convenient than a
browser.
So as usual, and with flame-proof suit on to say this, it might depend
on who your users are. Find out who needs to do it, and that will tell
you a lot about whether to give them the baby talk (go to) or the rich
heritage version (ftp to, or connect to).
I hope someone else can give you advice on the prevailing approach to
FTP these days. If browsing is the predominant approach for everyone
anymore, and your FTP URL is web browser friendly, you could tell
everyone to go to, and so get away without all the heritage hoopla. I
don't know about that, but someone else will.
BTW, where are these variations you're seeing? If it is in documentation
that you consult for examples of the corporate style at your workplace,
then I hope the time is nigh when you can't take no mo' stale metaphors
for using a network. To my tin ear, the time "sounds" ripe for a style
guide crusade to weed out those awkward variations you're seeing.
Good luck.
Ned Bedinger
doc -at- edwordsmith -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-