Support for (biblatex) langid field in entry editor #10868 #11049
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue Link
This pull request resolves [#10868](https://github.com/JabRef/jabref/issues/10868) (Support for (biblatex) langid field in entry editor)
Issue description
The field
langid
is missing among the standard fields, which is used for hyphenation and whether sentence casing is applied.Modifications and Results
At
org.jabref.model.entry.field.StandardField#StandardField
, the enumStandardField
was missing the constantlangid
which was added. It is now possible to add thelangid
field to an entry type through the preferences menu.Tests Added
No new tests were added, as the only change was adding a constant to an enum. Also, no tests relating to other standard fields were found in
test.org.jabref.model.entry.field.StandardField#StandardField
.Mandatory
Discussion
langid
field?