Spaces in URLs problem w/ new Reader X and XI updates

Question

Can anyone else confirm that with the new Reader X and XI updates, spaces in URLs get encoded as %2520 instead of %20 causing errors when the links are followed?  This  was/is not a problem with the earlier version of X nor with other pdf viewers.  I believe that this is a bug.

Answer 1

I am having the same problem. Details ....
I have created two PDFs in the same folder (I used Power Point to create the contents, and saved as PDF). I want to be able to click a link in the first PDF and cause the second PDF to be opened.
Everything works fine if there are no blank spaces in the filename of the second PDF (i.e., the target of the link in the first PDF), and no blank spaces in any part of the full path to the second PDF.
The problem occurs if there are blank spaces in the second PDF's filenames or full path.
If there are blank spaces (in either filename or path), then when I open the first PDF and hover over the link to the second (target) .... I can see that FOR THE PATH, each blank space has been converted to a %20. FOR THE FILENAME of the target PDF, the blank space shows as a blank space (i.e., not shown as a %20).
When I click the link in the first PDF, my default browser (Firefox 19.0.2) opens and displays a dialog box tells me that it cannot find the file in question (i.e., the second PDF).
The file name in the dialog box has each blank space (in both filename and path) converted to a %20 .... HOWEVER, the contents of the browser's address bar has each blank space converted to a %2520.
It is that address of the second PDF shown in the browser's address bar (with each blank replaced by a %2520) that cannot be found. If I manually alter the contents of the address bar, and remove each 25 (so that each blank is replaced only by a %20) and then hit the Enter key, the second PDF is successfully displayed in the browser.
Firefox now has it's own PDF viewer. However, I disabled the internal Firefox PDF viewer, and set the default PDF viewer to the Adobe viewer. Problem did not go away. So, I do not think the fault is in the Firefox PDF viewer.
The previous post stated that Adobe has acknowledged this as a bug. Any word on when/if the bug will be fixed.
The only work-around I have found is to use filenames and paths that have no blanks. But if one is creating PDFs for customers, then while one might be able to use filenames with no blanks, one cannot insure that customers will not place the PDFs into folders that have noblanks in their paths.
Any other suggestions while we wait for a fix?
EDIT: I found a similar thread here: http://forums.adobe.com/thread/1053575?tstart=0