-
Notifications
You must be signed in to change notification settings - Fork 5
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
Change the way that eprint repository prefixes are processed. #15
base: master
Are you sure you want to change the base?
Conversation
The previous technique was smart, but did _not_ match the stipulations in http://arxiv.org/help/faq/references -- these require that the specific string arXiv:yyyy.nnnn, with a leading space, and warn not to have a '{' just before the 'arXiv:' (who knows...). The previous version did have a close-up '{'. This technique is slightly clumsier in some ways, but is more straightforward in the .bst file, and requires no LaTeX magic in the style file. Incidentally changed the test framework in the test/ directory, to support multiple independent tests rather than a compendium test-everything one..
That ref is talking about inline arXiv references not those in bib files. You aren't going to be able to insist that the bib entry has a leading space in the |
Indeed: this is about how the arXiv:yyyy.nnnn appears in the bibliography -- in the .bbl file, not the .bib file. And the point is so that no-one has to insist on anything in the .bib file. And this is written so that if there's no This is so that authors can in principle indicate different eprint repositories (such as ASCL). |
Hi both If it works and doesn’t break anything else then there appears to be little harm in following arXiv’s request. I note that mn2e is already adding \eprint to all of these, which inserts a clickable link already whenever possible. Keith From: Norman Gray [mailto:[email protected]] Indeed: this is about how the arXiv:yyyy.nnnn appears in the bibliography -- in the .bbl file, not the .bib file. And the point is so that no-one has to insist on anything in the .bib file. And this is written so that if there's no arxiv: prefix in the .bib entry (which is the common case, and in particular the case for references that appear from ADS), then it presumes arXiv. This is so that authors can in principle indicate different eprint repositories (such as ASCL). — |
@keithtsmith the paper I submitted the other day (I see that you are the receiving editor!) uses the current bib style and your latest class file. |
Yes, I noticed! It made me smile, thanks. Good to see it works for a real paper! Remind me in a week and I’ll send you some further updates. Keith From: Tim Jenness [mailto:[email protected]] @keithtsmithhttps://github.com/keithtsmith the paper I submitted the other day (I see that you are the receiving editor!) uses the current bib style and your latest class file. — |
Conflicts: mnras.bst
The previous technique was smart, but did not match the stipulations in
http://arxiv.org/help/faq/references -- these require that the specific string
arXiv:yyyy.nnnn, with a leading space, and warn not to have a '{' just before
the 'arXiv:' (who knows...). The previous version did have a close-up '{'.
This technique is slightly clumsier in some ways, but is more straightforward in
the .bst file, and requires no LaTeX magic in the style file.
Incidentally changed the test framework in the test/ directory, to support
multiple independent tests rather than a compendium test-everything one..