Skip to content
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

Be more relaxed when handling file paths #52

Closed
koppor opened this issue Nov 25, 2015 · 5 comments
Closed

Be more relaxed when handling file paths #52

koppor opened this issue Nov 25, 2015 · 5 comments

Comments

@koppor
Copy link
Owner

koppor commented Nov 25, 2015

Our main user base seems to use Windows. These users are not used to escape path separators. E.g., they use C:\xxxx\yyyy\zzzz\somefilename.pdf. Instead of throwing exceptions etc., JabRef should be able to treat such path specifications. Possibly, if on Windows, replace \ followed by a non-\ by \\ before letting the String really be handled by Java.

Refs JabRef#184 (comment) and #98

@matthiasgeiger
Copy link
Collaborator

Those paths are escaped by JabRef (and even Zotero) by default - however, JabRef 2.11 GUI currently breaks completely if (somehow) an unescaped path is stored in the file. In 3.0dev the UI is not affected, but the file field does not contain sensible information due to the unescaped delimiter ":" in C:\...

@simonharrer
Copy link

This requires too much strange logic to support.

@koppor
Copy link
Owner Author

koppor commented Mar 17, 2023

Note that in recent JabRef versions this is fixed. See BibtexParserTest.java#L596

@koppor koppor removed the freeze label Oct 10, 2023
@ror3d
Copy link

ror3d commented Feb 13, 2024

I would suggest to normalize paths to unix-style instead. Windows supports it, and it would make files work well between systems.

@koppor
Copy link
Owner Author

koppor commented Mar 6, 2024

Follow-up at JabRef#10871

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants