Honor user-selected keyword delimiter in MedlinePlainImporter.java

[ryan-carpenter]

Is your suggestion for improvement related to a problem? Please describe.
Jabref inserts commas between keywords imported from PubMed files, even if the user has specified another delimiter in File > Preferences > Entries. This is a problem with PubMed files, because Medline's subject headings (MeSH terms) include commas that should not be interpreted as delimiters.

Describe the solution you'd like
If the user has specified a non-default delimiter in settings and has designated the keywords field as one of the affected fields, then the importer should apply the specified delimiter instead of always using commas as the delimiter.

Additional context
See examples and additional description here: https://discourse.jabref.org/t/preserve-pubmed-subject-headings-on-import/4362/2. That discussion is about improving the usability of imported keywords. This GitHub issue only concerns the incorrect parsing of keywords due to the presence of commas in the source data.

This problem does not apply to PubMed records retrieved through JabRef's Web Search functionality. In this case, Jabref applies the user-specified delimiter, allowing correct parsing of the imported keywords.

https://github.com/JabRef/jabref/blob/af73e4e78985eefa7d0fb94c472a99a00c323d8d/src/main/java/org/jabref/logic/importer/fileformat/MedlinePlainImporter.java#L185C5-L192C1

[Siedlerchr]

Thanks for creating that issue, I was about to create one based on your reporting as well :)
It was just a quick fix: (includes the importer module issues fixes as well)
https://builds.jabref.org/pull/11414/merge

[ryan-carpenter]

It was just a quick fix: (includes the importer module issues fixes as well) https://builds.jabref.org/pull/11414/merge

Ah, but what an improvement! Thanks.