JabRef version
Latest development branch build (please note build date below)
Operating system
macOS
Details on version and operating system
macOS Tahoe Version 26.2
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
This issue follows Issue 13701. JabRef now accepts suffix letter in the page ranges such as 436S--439S. However, the official biblatex supports more flexible page ranges variation (e.g. Roman Numerals) than the ranges JabRef supports. Please refer to p. 255 \ifnumerals, \ifpages and p. 268 \rangelen in The biblatex Package for more concrete examples.
- open New example library
- click an entry (e.g. Cocoa and Cardiovascular Health)
- go to "Optional field" and enter page ranges such as
14/15.
- warning appears.
One possible fix is to further relax the checkerSINGLE_PAGE_PATTERN.
As a another potential direction, we could also discuss whether page validation should be more configurable in the UI instead of relying entirely on hard-coded rules #13701 comments. For example, some kind of guided input might help in this case, though I am not sure a dropdown is the right solution yet given that valid page formats can be quite diverse.
JabRef version
Latest development branch build (please note build date below)
Operating system
macOS
Details on version and operating system
macOS Tahoe Version 26.2
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
This issue follows Issue 13701. JabRef now accepts suffix letter in the page ranges such as
436S--439S. However, the official biblatex supports more flexible page ranges variation (e.g. Roman Numerals) than the ranges JabRef supports. Please refer to p. 255\ifnumerals,\ifpagesand p. 268\rangelenin The biblatex Package for more concrete examples.14/15.One possible fix is to further relax the checker
SINGLE_PAGE_PATTERN.As a another potential direction, we could also discuss whether page validation should be more configurable in the UI instead of relying entirely on hard-coded rules #13701 comments. For example, some kind of guided input might help in this case, though I am not sure a dropdown is the right solution yet given that valid page formats can be quite diverse.