JabRef version
5.15 (latest release)
Operating system
Windows
Details on version and operating system
No response
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Description
While testing JabRef author parsing using parameterized JUnit tests, I observed inconsistent parsing behaviour for certain non-Latin scripts.
Chinese and Cyrillic author names are parsed correctly into familyName and givenName components, but Hindi and Arabic names are interpreted as namePrefix values instead of familyName.
Reproducible Example
Input: हिंदी, परीक्षण
Observed result:
- namePrefix = हिंदी
- familyName = null
Input: العربية, اختبار
Observed result:
- namePrefix = العربية
- familyName = null
Comparison
The following inputs parse correctly:
Expected Behaviour
All comma-separated author names using the format:
Lastname, Firstname
should be parsed consistently regardless of script.
Environment
- JabRef version: latest master branch
- Java version: 21
- Testing framework: JUnit 5 parameterized tests
Additional Notes
The issue was observed during automated parameterized testing of AuthorList.parse() behaviour.
Appendix

JabRef version
5.15 (latest release)
Operating system
Windows
Details on version and operating system
No response
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Description
While testing JabRef author parsing using parameterized JUnit tests, I observed inconsistent parsing behaviour for certain non-Latin scripts.
Chinese and Cyrillic author names are parsed correctly into familyName and givenName components, but Hindi and Arabic names are interpreted as namePrefix values instead of familyName.
Reproducible Example
Input: हिंदी, परीक्षण
Observed result:
Input: العربية, اختبار
Observed result:
Comparison
The following inputs parse correctly:
Expected Behaviour
All comma-separated author names using the format:
Lastname, Firstname
should be parsed consistently regardless of script.
Environment
Additional Notes
The issue was observed during automated parameterized testing of
AuthorList.parse()behaviour.Appendix