-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Auto-linking files with safe character replacements #9267
Copy link
Copy link
Closed
Labels
[outdated] type: bugConfirmed bugs or reports that are very likely to be bugsConfirmed bugs or reports that are very likely to be bugscomponent: external-filesgood first issueAn issue intended for project-newcomers. Varies in difficulty.An issue intended for project-newcomers. Varies in difficulty.
Metadata
Metadata
Assignees
Labels
[outdated] type: bugConfirmed bugs or reports that are very likely to be bugsConfirmed bugs or reports that are very likely to be bugscomponent: external-filesgood first issueAn issue intended for project-newcomers. Varies in difficulty.An issue intended for project-newcomers. Varies in difficulty.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Done
JabRef version
5.7 (latest release)
Operating system
Windows
Details on version and operating system
Windows 11 22H2
Checked with the latest development build
Steps to reproduce the behaviour
When using characters in the citation key or publication title that are unsafe for the file system (such as e.g. a colon ":"), the automatic file renaming replaces those characters with an underscore.
However, the auto-linking feature does not seem to respect this behaviour. After automatically renaming a file with an unsafe character and unlinking it, it is not being recognized by the auto-linking feature.
Changing the citation key to the "safe" string by manually replacing the colon with an underscore makes JabRef find the file again.
Auto-linking files didn't work at all for me in the development version, so I couldn't actually reproduce the behaviour there.
Appendix
...
Log File