Add eprint support for LingBuzz and ROA #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alecshaw
force-pushed
the
eprint-support
branch
from
4b575ed
to
d3bc3d7
Compare
added 2 commits
May 8, 2018 13:27
Implements support with the `eprint` and `eprinttype` fields for the LingBuzz and Rutgers Optimality Archive (ROA) repositories.
|
I have fixed this up to leave the One outstanding question is where it would be most appropriate to document this feature. I've read the documentation, but I'm not certain which section would be most appropriate, or if a new section should be created. |
|
I think it makes sense to add documentation of this to Point 17 ("On-line materials") in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements support with the
eprintandeprinttypefields for theLingBuzz and Rutgers Optimality Archive (ROA) repositories.