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

User-defined keyword separator does not apply to Merge Groups #12535

Open
2 tasks done
ryan-carpenter opened this issue Feb 20, 2025 · 5 comments
Open
2 tasks done

User-defined keyword separator does not apply to Merge Groups #12535

ryan-carpenter opened this issue Feb 20, 2025 · 5 comments
Assignees
Labels
📍 Assigned Assigned by assign-issue-action (or manually assigned) component: groups component: preferences

Comments

@ryan-carpenter
Copy link

JabRef version

Latest development branch build (please note build date below)

Operating system

GNU / Linux

Details on version and operating system

openSUSE Tumbleweed

Checked with the latest development build (copy version output from About dialog)

  • I made a backup of my libraries before testing the latest development version.
  • I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

The user-defined "Keyword separator" applies to keywords and groups in the entry table, but not in the Merge/Find duplicates window. The correct separator is used to merge keywords, but not groups.

  1. Set a non-default keyword separator in Preferences > Entry
  2. Notice that the keyword separator also applies to the groups field (as intended)
  3. Create two entries with at least one group per entry but not identical group sets.
  4. Select the two entries and click Quality > Merge Entries
  5. In the merge window, Click the icon for Merge Groups
  6. Notice that the groups are joined using the default separator (comma) instead of the user-defined character.

The keyword separator is applies to keywords and groups, so I expect the same separator to be used for merging keywords or merging groups.

Appendix

JabRef 100.0.0
Linux 6.12.8-2-default amd64
Java 23.0.1
JavaFX 23.0.2+3
...

Log File
Not applicable
@ryan-carpenter
Copy link
Author

The separator is explicitly defined in the group merger.

The keyword merger uses getKeywordSeparator.

Character delimiter = bibEntryPreferences.getKeywordSeparator();

@Siedlerchr
Copy link
Member

@HoussemNasri Do you remember why the Groups Separator is hard coded?

@HoussemNasri
Copy link
Member

Hmmm, probably because this was implemented before we made the separator dynamic.

@patriciagam
Copy link

/assign-me

@github-actions github-actions bot added the 📍 Assigned Assigned by assign-issue-action (or manually assigned) label Mar 3, 2025
Copy link
Contributor

github-actions bot commented Mar 3, 2025

👋 Hey @patriciagam, 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.

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! 🚀

⏳ Please note, you will be automatically unassigned if the issue isn't closed within 45 days (by 17 April 2025). A maintainer can also add the "📌 Pinned"" label to prevent automatic unassignment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📍 Assigned Assigned by assign-issue-action (or manually assigned) component: groups component: preferences
Projects
Status: Free to take
Status: Normal priority
Development

No branches or pull requests

4 participants