-
Notifications
You must be signed in to change notification settings - Fork 59
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
Improve citation ordering #7
Comments
The order of the bibliography depends on the style we use. If we want to use order in appearance vs. chronological, for example. We could use IEEEtranN for the unsorted and with natbib support. I prefer to have the group of citations sorted, since it helps checking the group. And with the numerical styles have them in order of appearance. But that is a style preference. Regarding the support for the bibliography and citations, we should consider porting the whole system to biblatex instead of bibtex as well. But that is better for another issue. |
I think biblatex we can do for next year. I had started, but was taking me too long. |
@sroth-visinf to comment on this. |
I agree with @Tayia here. I had also wanted to switch to BibLaTeX already in 2022, but adjusting the formatting of the entries so that they conform to the usual style proved rather tedious. I had started but found that there are loads of corner cases. Plus this needs to be thoroughly tested before it is rolled out. CVPR/ICCV/etc. program chairs cannot possibly provide LaTeX support to sort out people's issues. Aiming to do this next year with sufficient lead time is probably best. |
If you can provide a list of the test entries, I can work on them (depending on how troublesome they are to iron out). Also, since the base biblatex style comes from IEEE, my guess is that it should be less problematic unless there have been style choices made along the way. In the attempt to port (#10) you can see what has been ported and how it is working so far. |
Removed this comment from end of
\subsection{Miscellaneous}
subsection of the author-kit, and converted it into an issueThe text was updated successfully, but these errors were encountered: