As soon as the old version vanish (and the users have reset their preferences), additional configuration is only required for special casesĬ) This causes much effort (at least 20h) and is only because there are users not updating their software. We could add a button "make database ready for sharing" or, even better, set a suitable default JabRef configuration. Side comment: At "database properties", one can add the file sorting options. I see the following options:Ī) Remove all configuration options and introduce a "one size fits all" formatĪ) This increases testability (as less configuration combinations have to be tested) and eases sharing of BibTeX files across JabRef users.ī) We still have to add test cases. GNOMEv3, where they removed various configuration options. I think, this is the discussion GNOMEv2 vs. Should we drop all these options and define "the one and only" serialization? What about being as minimal intrusive as possible? For instance, when a group of researchers uses different tools to manage their bibliographies? Field sorting options: alphabetic, unsorted, user-defined orderįurthermore, one can configure the ordering of the entries: See "Database properties": Save as configured globally, original order, order as specified.See Options -> Preferences -> File -> "Field saving options" Maybe we should start a wiki page with all possible formats and vote on the preferred format and implement that. I got used to it, but no one else offers such a format. We can discuss whether we remove the casing again. Otherwise, we produce a kind of a binary format, which is hard to handle in version control systems (see versioned. bib files can be put under version control, compared, quickly edited, etc. I think, we should enable readability as the. Provide formatter (Example: Remove tabs / newlines / duplicate spaces) that can be enabled by a user for specific fields onLoad / onSave.No longer perform any changes of field content (no more space/tab/newline elimination, etc.).Field keys are formatted in lower case only.Bibtex entry keys are written in camel case, starting upper case.The value part is indented to one space past the longest field key name + = (so that all values are aligned). The = is appended directly to the field key.Fields are sorted as stated in the Bibtex / Biblatex manuals.Dropping all field saving options (Preferences -> File -> Field saving options)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |