https://bugs.kde.org/show_bug.cgi?id=495839
Will Sierzputowski <wsi...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #6 from Will Sierzputowski <wsi...@gmail.com> ---
Thanks for the steps. I can duplicate this behavior on Windows 11 (Okular
24.11.80).
I will have to look more into what could cause this, but here is a summary of
what I tested.
- I can only cause this behavior when the file is opened through Windows
explorer with 'Right Click->Open With->Okular'. It does not happen when the
file is opened from inside of Okular(File->open) and does not happen when the
file is opened by dragging the PDF into an already running Okular instance. A
short-term solution would be opening the file in one of these other ways.
- If only happens when the folder has a ‘#’ in the first position, or when ‘.#’
are the first two positions. Names such as 't#est\test.pdf' work correctly.
- This happens when opened from the commands line too ‘okular.exe test.pdf’ if
the above regarding ‘#’ is true about the file directory. This also happens
when the file is hard linked i.e. ‘okular.exe D:\#test\test.pdf’.
- The same behavior occurs if Okular is invoked with path to the directory the
PDF file is in. ‘okular.exe D:\#test’. This works with out without # and I
believe is intended behavior
My tentative conclusion is this is an issue with parsing the command line
parameter (Windows invokes the call for ‘open with’ through command line
parameters) which causes the PDF file to be ignored when the directory starts
with #. When I look more into it, I will see if the issue Windows only or also
persists on a Linux system.
--
You are receiving this mail because:
You are the assignee for the bug.
