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

LaTeX: natbib doesn't recognize "authoryear" option #19

Open
erikbgithub opened this issue Oct 4, 2013 · 3 comments
Open

LaTeX: natbib doesn't recognize "authoryear" option #19

erikbgithub opened this issue Oct 4, 2013 · 3 comments

Comments

@erikbgithub
Copy link
Contributor

For some reason my HTML generates citations with "authoryear" but my PDF doesn't. I'd really prefer to use this variation because I feel it is more commonly used in Germany. Adding some debugging prints to the natbib/__init__.py doesn't yield any output at all (only when processing the HTML generation). Any ideas what could be done here?

@jterrace
Copy link
Owner

jterrace commented Oct 4, 2013

In footer._tex, it uses \bibliographystyle{refstyle}. You can change that to use a different style file

@erikbgithub
Copy link
Contributor Author

Suddenly all our disagreements in recent issues make sense. Is it correct that you mostly want the LaTeX to work fine and the Python/Sphinx stuff around it is just tooling that helps you write faster LaTeX? I have a totally different approach. For me Sphinx is the major tool and LaTeX is only one of its outputs. If it is correct then it would make sense to sometimes develop in different directions in our forks, because we try to fulfill 2 different usecases. What do you think?

Examples:
In my eyes Pygments should work fine and it doesn't matter if LaTeX generates a Verbatim box with styled text parts inside or a lstlisting environment with literal source code inside.
In my usecase its also a major bug if the conf.py file doesn't allow changing the citation style, while in your usecase it is actually perfect to change a footer tex file. In your usecase it even makes sense for me.

@jterrace
Copy link
Owner

I wouldn't say that it's meant just to be tooling around latex. I still want HTML to have first-class support, but latex is still a very important output, since most thesis are submitted using it.

In this case, I think it makes sense to have the conf.py change the style. I just took the approach that people are generally going to need and want to tweak the latex output themselves anyway.

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

No branches or pull requests

2 participants