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.
> As we all know, one uploads a file from a PC or similar device to a
> If a resource exists on a server, it is downloaded to the PC (or
> similar device).
Ok, but "upload" doesn't simply mean "away from a PC", and download
doesn't simply mean "toward a PC".
> John living in his own siloed/silo'd world, everythingâincluding his
> GUIâis PLC-centric. Therefore, one uploads binaries *from* the PLC
> to the PC for editing/viewing, then can *download* them back to the
> These two terms, upload and download, are used in a way that's
> counter-intuitive to the rest of us who understand the PCâserver
I've been uploading data from small embedded devices to PCs, and
downloading files back to the devices from PCs, for decades. John's
usage is certainly not counterintuitive to me, and it might be
equally familiar to John's customers. You might want to ask.
> It's one thing for me to make the changes in the manual, but
> retooling the GUI is a far bigger kettle of fish that will likely
> meet with much resistance.
If you do make changes, consider replacing "upload" and "download"
with "transfer" followed by an explicit direction.
=== Andrew Warren - awarren -at- synaptics -dot- com
=== Synaptics, Inc - San Jose, CA
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word | http://bit.ly/doctohelp2015