[O] Org mode clockview links failing with spaces

[Shawn Way]

I have an org file with a clocktable located at the head of the file. The 
clocktable is able to pull together a great table, however, the links on the 
table do not work, if they have spaces in them.

Sample org file
==============================================================
* Work Table
  #+BEGIN: clocktable :maxlevel 4 :scope file :block today :link t :tags 
"-NONWORK"
  #+CAPTION: Clock summary at [2017-01-03 Tue 15:18], for Tuesday, January 03, 
2017.
  | Headline                                     | Time   |      |      |
  |----------------------------------------------+--------+------+------|
  | *Total time*                                 | *2:19* |      |      |
  |----------------------------------------------+--------+------+------|
  | [[file:c:/Users/sway/Desktop/dummy2.org::Work%20Table][Work Table]]         
                          | 2:19   |      |      |
  | \_  [[file:c:/Users/sway/Desktop/dummy2.org::Email%20(E30)][Email (E30)]]   
                           |        | 2:19 |      |
  | \_    
[[file:c:/Users/sway/Desktop/dummy2.org::Email%20to%20Kim%20at%20%5B2017-01-03%20Tue%2012:35%5D][Email
 to Kim at {2017-01-03 Tue 12:35}]] |        |      | 1:41 |
  | \_    
[[file:c:/Users/sway/Desktop/dummy2.org::Email%20to%20Mel,%20Bill,%20etc%20at%20%5B2017-01-03%20Tue%2014:32%5D][Email
 to Mel, Bill, etc at...]]          |        |      | 0:38 |
 #+END:



** Email (E30)
   :PROPERTIES:
   :CODE:     E30
   :END:
   :LOGBOOK:
   :END:
*** Email to Kim at [2017-01-03 Tue 12:35]
    :LOGBOOK:
    CLOCK: [2017-01-03 Tue 12:35]--[2017-01-03 Tue 14:16] =>  1:41
    :END:
     RE: Internal Water Quality
*** Email to Mel, Bill, etc at [2017-01-03 Tue 14:32]
    :LOGBOOK:
    CLOCK: [2017-01-03 Tue 14:32]--[2017-01-03 Tue 15:10] =>  0:38
    :END:
    RE: 9692 Startup.


===========================================================

I have the following version of org:

Org mode version 9.0.3 (9.0.3-elpa @ 
c:/Users/sway/AppData/Roaming/.emacs.d/elpa/org-20161224/)

This is a fairly new development, but I cannot point out the exact time it 
started.

Any thoughts as to what may be the issue?


Thank you kindly,

Shawn Way, PE