-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JabRef 3.3 file links containing blanks are broken if non-default viewer is set #1381
Comments
Thanks for your report! Confirmed if a PDF viewer is set manually in the "Manage external file type" dialog (not only sumatra but also other PDF viewers). System default works with whitespace in the file names. |
Seems to be a problem with the settings than, because I worked on a fix for this in the opening methods. |
Thank you for your report 👍 |
👍 works for me. |
…t viewer is set * Fix JabRef#1381 File links containing blanks are broken if non-default viewer is set * Consistently use ProcessBuilder instead of Runtime.exec
JabRef version 3.3 on Windows 10. After upgrading from version 3.1 all the file links containing blanks are broken when using Sumatra PDF. When trying to open a pdf file containing blanks, the pdf reader consider each piece of the file name as an independent file (each piece meaning each non-blank piece). This worked fine in 3.1. Tried to place quotes around the file name without success.
Steps to reproduce:
Ideally can configure Jabref to place quotes around the file name, when invoking the external reader.
The text was updated successfully, but these errors were encountered: