Handle alternative keyword separators when importing bibtex data

[ThiloteE]

Initial (naive) issue statement:

There are journals that (wrongly) publish bibtex data with keywords containing ; as separator. Example: keywords = {keyword1; keyword2}, which goes against the standard of bibtex as originally defined (see #15521 (comment)) but may be tolerated or even desirable in some edge cases, such as keywords related to mathematical formulas. When pasting those into JabRef, there is no keyword separation. I wish there was. It would also be ok to replace the ; with , during the import process. Maybe this should be optional in the preferences, but probably not as I cannot imagine any words containing ;, but maybe I am wrong.

Summary of my annoyance: The users workflow is slowed down when trying to paste multiple keywords at the same time into JabRef, because they will be treated as a single keywords instead of multiple keywords.

Example Journal:

https://hal.science/hal-02055158
https://hal.science/hal-02055158v1/bibtex

hal API: https://api.archives-ouvertes.fr/docs

Newest solution proposal:

#12974 (comment)

This issue now covers more than just , and ;, but also other potential wordboundary separators.
I have listed some test-cases at #12974 (comment).
How LibreOffice handles separators during import: #12974 (comment)

[ThiloteE]

Overall, I now think it definitely should be managed via a preference.
Both ";" and "," should be added there as default, but should be able to be modified by the user. By the way, I believe we alread y have it. It is the keyword separator preference for fields:

Would need to be adapted to allow multiple keywordseparators per field. Bonus points for allowing users to modify keyword separators for single fields.

From a standartization standpoint, it's better to only use one keyword separator, otherwise sharing .bib library files to colleagues withotu the proper preferences will be a hassle. We could treat those journals as rogue.

So that means, it's best to let users set multiple keyword separators in the preferences for IMPORT only and then convert them to ","

[koppor]

Since multiple journals may have different separators, all of these should be handled.

We should "jsut" hard-code the keyword separation and migrate old data.

Alternative: #8701

[ryan-carpenter]

When the input contains only one keyword per line, as in RIS data, JabRef could check the keywords that would conflict with the specified separator. It isn't as obvious in Bibtex data where there are multiple keywords on the same line. A non-standard separator that preserves delineation between keywords is better than a standard one that is unclear. I think this is why some sources use semicolons instead of commas. For example, chemical formulas contain commas and hyphens intrinsic to the formula, so you would not want to substitute another character for these but commas or hyphens would be inappropriate keyword separators.

[tushar-2320]

/assign-me

[github-actions]

👋 Hey @tushar-2320, thank you for your interest in this issue! 🎉

We're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.

For questions on JabRef functionality and the code base, you can consult the JabRef Guru or ask on our Gitter chat.

In case you encounter failing tests during development, please check our developer FAQs!

Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.

Happy coding! 🚀

[koppor]

This refs #8701 somehow