-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Support all BibLaTeX date formats for parsing #2753
Comments
Further examples that should be parsed successful: |
Some examples from the biblatex manual, Section 2.3.8. Biblatex follows the EDTF-Standard |
I don't know if this report belongs here under #2753, because I think it's not about date parsing as such, but about the entry editor. But here goes: Biblatex permits strings in the date field of the form "1899~" and "1899?" and even "1899?~". The current snapshot of JabRef doesn't allow such strings to be entered in the "Required fields" tab. If one tries, then the content of the field disappears. But one can enter the strings in the "biblatex source" tab. And the data is preserved and even displays in the "required fields" tab. Desired behaviour: allow the entry editor's "Required fields" tab to accept "date" field strings in all legal Biblatex formats, including Biblatex's "Enhanced date specifications" as listed in the Biblatex manual, table 5 (as well as tables 3, mentioned in the previous post @Siedlerchr, and 4 "unspecified date parsing"). Best, JabRef 4.0-dev--snapshot--2017-07-19--master--2f12fecfb |
JabRef 4.0-beta3
Thanks! |
Please note that the EDTF draft standard has been superseded by the upcoming ISO8601 novella, so |
@moewew Thank you very much for your information, helps a lot. So I suggest we make us compatible. Summary:
|
In case you want to read up on what PLK has done to implement these changes, a few comments are scattered in plk/biblatex#540, plk/biblatex#644, plk/biblatex#656. The dev branch of |
We decided in the devcall, that we follow the Biblatex team and use the new ISO8601 standard without backwards compatibility to EDTF. https://github.com/plk/biblatex/wiki Addtionally, there is an EBNF in Annex A in the spec doc: |
this doesn't make sense @LinusDietz |
Would like to take this issue. |
Meanwhile, newest development version of JabRef uses JDK 19. See d3bb827 |
Current state: the: The following date formats do not yet work and need to be added and tested and the parsing might need to be adjusted
|
Hi, I'm interested in this issue and would love to work on it. Can I get assigned to this issue? |
Sure, go ahead :-) |
As a general advice for newcomers: check out Contributing for a start. Also, guidelines for setting up a local workspace is worth having a look at. Feel free to ask here at GitHub, if you have any issue related questions. If you have questions about how to setup your workspace use JabRef's Gitter chat. Try to open a (draft) pull-request early on, so that people can see you are working on the issue and so that they can see the direction the pull request is heading towards. This way, you will likely receive valuable feedback. |
This would be a followup for #2731, which was at #2731 (comment) by @Siedlerchr:
A PR would have to investigate possible date patterns from the standard and then implement them with some tests
The text was updated successfully, but these errors were encountered: