https://bugs.kde.org/show_bug.cgi?id=418758
--- Comment #4 from Richard Ferguson <fergusonricha...@gmail.com> --- OS Name Microsoft Windows 10 Home Version 10.0.18363 Build 18363 Okular version 1.9.2. It does not matter whether the characters following the "#" are blank, numbers or letters. As soon as Okular parses to the "#" it stops parsing and because the file name is incomplete, the file cannot be opened. On Fri, Jun 26, 2020 at 3:59 PM Jack <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=418758 > > Jack <ostrof...@users.sourceforge.net> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| > |ostroffjh@users.sourceforge > | |.net > > --- Comment #3 from Jack <ostrof...@users.sourceforge.net> --- > (reposting from one of the duplicate bugs) I just tested on (Gentoo) > Linux, > okular 1.9.3 (I see 1.10 is out) and it works fine. I also tested 1.9.2 > (latest available in the Windows Store) in a Wind 10 guest in VirtualBox, > and > it also works fine whether # is at the beginning or in the middle of the > file > name. What version of Windows are you on? > > Might the behavior depend on whether what is after the # are just digits, > or > non-digit alpha characters. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.