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.
I guess it all depends on the number of ways you can share a custom view. I
stand by my statement that you aren't sharing the view. You're sharing the
URL that opens the view.
Then there might be other things you would share by sending its URL. So
"share a URL to a custom view" would also work.
Does the target audience get URL? And what does the interface say? Do we
need to say "send a link to a custom view"?
-Tony
On Thu, Aug 3, 2017 at 13:25 Robert Lauriston <robert -at- lauriston -dot- com> wrote:
> The task is sharing a custom view. Copying the URL is how you do that.
> I agree that if that's the only way to do it there's no reason to say
> "via URL."
>
> On Thu, Aug 3, 2017 at 12:58 PM, Tony Chung <tonyc -at- tonychung -dot- ca> wrote:
> > The specific action is to share the URL. The custom view is merely
> > adjectival in this case.
> >
> > -Tony
> >
> > On Thu, Aug 3, 2017 at 12:37 Gene Kim-Eng <techwr -at- genek -dot- com> wrote:
> >
> >> How many different ways are there to share a custom view? If URL is the
> >> only way, there's no need to say anything more than "Share a custom
> view."
> >>
> >> Gene Kim-Eng
> >>
> >>
> >> On 8/3/2017 12:14 PM, Tony Chung wrote:
> >> > Just to be a pest: why not just say "Share a custom view URL"? After
> all,
> >> > that's what it is.
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com