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

Suggestion for bibliography #45

Closed
tjiagoM opened this issue May 2, 2017 · 8 comments
Closed

Suggestion for bibliography #45

tjiagoM opened this issue May 2, 2017 · 8 comments

Comments

@tjiagoM
Copy link
Contributor

tjiagoM commented May 2, 2017

What about changing the bibliography style from plain to plainnat?
This would allow us to use some handy things like \citeauthor{}
What do you think, @urbas ?

@urbas
Copy link
Member

urbas commented May 14, 2017

I think plain is a bit safer default choice as it produces shorter citation references (see this PDF) and (from what I've seen) it is a more commonly use citation style in Computer Lab's PhD theses.

Users can still change that, but I'd vote to leave plain as default.

I'll close this for now. We can reopen if more people vote on this one.

@urbas urbas closed this as completed May 14, 2017
@chatcannon
Copy link

For what it's worth, I used unsrtnat, which sorted the references in the correct order for Chemistry theses, but had to edit the .bib files to remove all fields which shouldn't appear in the bibliography, and also to standardise names (e.g. only initials and surname). In the process, I discovered that BibTeX files downloaded from publishers are often full of errors, so going over them manually should be necessary anyway.

@tjiagoM
Copy link
Contributor Author

tjiagoM commented May 15, 2017

@chatcannon You can try JabRef because it has an option to create the bibtex from the DOI, or similar tool online, I had the same problem as you: http://www.doi2bib.org/#/doi

@tjiagoM
Copy link
Contributor Author

tjiagoM commented May 30, 2017

@urbas I've been searching a bit about the differences between plain and plainnat and as far as I could understand plainnat is basically plain plus some useful stuff.

I'm definitely using plainnat now because while I'm writing it is very useful to use stuff like \citeauthor{}, but can you please explain what you meant by "it produces shorter ciration references"? Because I tried with both plainnat and plain and couldn't find any difference in my bibliography section.

@urbas
Copy link
Member

urbas commented Jun 10, 2017

@tjiagoM: if you look at the first paragraph on page 13 of this PDF you'll see the long author list of the citation (the PDF was generated from this commit). The citation in this example uses \cite{example} and \bibliographystyle{plainnat}.

Shorter citation styles (that look like [1]) cause fewer line-overfullness problems, that's why I'd vote for plain.

@tjiagoM
Copy link
Contributor Author

tjiagoM commented Jun 11, 2017

Ah, now I get it. But that's why I use \usepackage[numbers]{natbib} when i want the plainnat option.

This way I have the same things as plain with the perks that I mentioned in the beginning, without any side effects, I think.

@urbas
Copy link
Member

urbas commented Jun 11, 2017

I see now. Yes that definitely sounds good. 👍 Reopening this issue. Btw, feel free to create a PR for this.

@urbas urbas reopened this Jun 11, 2017
tjiagoM added a commit to tjiagoM/thesis that referenced this issue Jun 13, 2017
…ridge#45). Comments on thesis.tex file to include the colleges crests. Removed a file that doesn't exist from the READ inside the clean sample folder
urbas added a commit that referenced this issue Jun 18, 2017
Bibliography style modified for the samples, with examples(Issue #45)…
@urbas
Copy link
Member

urbas commented Jun 21, 2017

PR #47 addressed this issue.

@urbas urbas closed this as completed Jun 21, 2017
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

3 participants