I copy-paste Gedit-hash (#) in a part of filepath into internet browser to read PDF file unsuccessfully: no file found with Gedit-hash symbol. Inputing there directly the hash symbol from the keyboard is consireded correct. Copy-pasting the gedit-hash to Vim shows Ascii 035 correctly, also tested on the ASCII tool here. Example filepath misinterpreted in Internet browser where # expands to %23 wrongly/home/masi/Documents/Edition.pdf#page=605Do Copy the filepath to GeditCopy the filepath from GeditPaste the filepath to any internet browserOutput: # symbol is expanded to %23Methods inserting filepath which are correctly interpretedtype hash directly to the internet browser fieldOS: Debian 8.7Internet browsers: Google Chrome 58.0.x, Firefox latest    
Why Gedit's hash symbol is expanded and interpreted wrongly in internet browsers?
debian;character encoding;gedit;ascii
UNIX filenames are not URLs.You can see that '#' is not interpreted in unix filenames, but it is in URLs.$ ls '/home/masi/Documents/Edition.pdf#page=605'ls: cannot access '/home/masi/Documents/Edition.pdf#page=605': No such file or directory$ curl '/home/masi/Documents/Edition.pdf#page=605'curl: (3) <url> malformed$ curl 'file:///home/masi/Documents/Edition.pdf#page=605'curl: (37) Couldn't open file /home/masi/Documents/Edition.pdfFirefox is applying the correct escaping, to protect the filename character # from being interpreted as delimiting a fragment in the URL.