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.
In that specific example, I think that "Share a Custom View using a
URL" is more clear and easier to translate.
Yes, that rewrite is still in passive voice; it could be "Use a URL to
send a Custom View". Also, gerunds can be a translation issue as well:
THREE reasons to go with "Use a URL to send a Custom View". ANNND that
works with the typical 'swing thought' for titling a task topic: the
title completes the phrase "How do I...?" But does the communication
method matter more to the reader than the goal? Perhaps "Send a Custom
View' is the actual ideal; and let the fact that a URL is the
communication method 'emerge' in the shortdesc/intro and in the body?
[RE the earlier post about weirdness in IBM Style Guide, they think
translation first and foremost (35 languages in my last post there).
You can get into all kinds of issues once right-to-left or vertical (or
both!) languages enter the mix. "Below" and "above", for instance, are
-------- Original Message --------
Subject: Re: "via" - why often verboten ?
From: Monique Semp <monique -dot- semp -at- earthlink -dot- net>
Date: Thu, August 03, 2017 10:50 am
To: Robert Lauriston <robert -at- lauriston -dot- com>, Lauren
<lauren -at- writeco -dot- net>
Cc: TECHWR-L Writing <techwr-l -at- lists -dot- techwr-l -dot- com>
>On the rare occasions I use "via," it's precisely to emphasize the
>something is accessed. For example, you can do certain operations
>an object in the UI but others only via the command line.
Yes, exactly. I didn't include my text in the original post, so here it
is. It's a heading, "Share a Custom View via URL". The way the user
shares a custom view (in a web browser dashboard) is to set everything
up and then copy the resultant URL, which encodes all sorts of info
about what to show in the custom view. So the user is sharing by view
"by way of" sharing the resultant URL.