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

Blank lines between required and optional fields #115

Closed
koppor opened this issue Aug 19, 2015 · 6 comments
Closed

Blank lines between required and optional fields #115

koppor opened this issue Aug 19, 2015 · 6 comments

Comments

@koppor
Copy link
Member

koppor commented Aug 19, 2015

JabRef 2.10 introduced a new serialization format, where there is a line break between required and optional field. That is strange for some users. Should we keep that behavior, make it configurable or drop it? Should we generally rethink the serialization?

Bug reports at sourceforge:

@stefan-kolb
Copy link
Member

  1. Hm, personally I don't see any real benefit by introducing a blank line to separate mandatory and optional fields. This should be solely managed by JabRef. Therefore, I vote for a removal of this behaviour.
  2. About serialization (see Define optimal serialization format and variations (dropping or reviving the 2.9.2 format) #116)

@johanvanr
Copy link

  1. I agree with stefan-kolb.
    As an additional argument (may be quite personal):
    The "required" fields in a reference as printed in a journal (for example) may well differ from those used in JabRef, making the latter somewhat arbitrary. For practical use in the JabRef GUI, the current approach is nice. In the *.bib files (etc.), I would prefer one block of lines per entry instead of blank lines at "arbitrary" locations.
  2. I have no opinion, except maybe: Keep it simple.

@koppor
Copy link
Member Author

koppor commented Aug 24, 2015

@johanvanr What about the ordering of the fields within the entry? They might be perceived as arbitrary, too? We currently write out the title, then the required fields in alphabetical order, and then the optional fields. For me, that was always OK. Without a blank line inbetween, it might get confusing.

@johanvanr
Copy link

@koppor: At this moment, the current approach for the field ordering seems fine to me. I do not mind a blank line and then an alphabetic restart. However, I would not like it if, for example, the (relatively long) "Abstract" comes before the "author", "year", etc. Apart from that, an alphabetic order has never been required by any *.bib-file processing code as far as I know (but my experience is too small to make a generically valid statement about that).

@lenhard
Copy link
Member

lenhard commented Aug 25, 2015

4330d94 removes the blank line between required and optional fields.

@koppor: You can close the bug reports on source forge. Further discussion can carry on here.

@stefan-kolb
Copy link
Member

Fixed by 4330d94.
Please refer to #116 for discussion about the serialization format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants