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

Sensible default settings for "Enable save actions" and "Cleanup" #128

Closed
1 task done
koppor opened this issue Jul 8, 2016 · 2 comments
Closed
1 task done

Sensible default settings for "Enable save actions" and "Cleanup" #128

koppor opened this issue Jul 8, 2016 · 2 comments
Labels

Comments

@koppor
Copy link
Member

koppor commented Jul 8, 2016

The old clean up dialog contained sensible defaults. The current "save actions" in the database properties dialog seem to be different.

Originial dialog:
grabbed_20160708-205241

Current default settings- when clicking "reset" at the Database properties dialog:
grabbed_20160708-204806

This differs from the global defaults:
grabbed_20160708-205409

This should be made consistent. It is not understandable, why these two defaults differ.

Also add documentation (including example) for each formatter at https://help.jabref.org

List

(this list is work in progress)

  • title and booktitle: Ordinals to LaTeX superscript
@koppor koppor added the feature label Jul 8, 2016
@koppor koppor changed the title Sensible default settings for "Enable save actions" Sensible default settings for "Enable save actions" and "Cleanup" Jul 12, 2016
@koppor
Copy link
Member Author

koppor commented Sep 13, 2016

Related: All tasks described at the top of #60. Although the issue is closed, these tasks still remain.

@koppor
Copy link
Member Author

koppor commented Jan 30, 2017

With JabRef#2051 this should be solved, even I am unsure whether the tasks of #60 are all done.

@koppor koppor closed this as completed Jan 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant