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.

Sign up for GitHub

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

Jump to bottom

bibtext-parser vs bibtexparsejs #12

Closed
TuningGuide opened this issue Aug 6, 2016 · 4 comments
Closed

bibtext-parser vs bibtexparsejs #12

TuningGuide opened this issue Aug 6, 2016 · 4 comments

Comments

@TuningGuide
Copy link

Could you outline whats the difference between the two repos?
@rcpeters
Copy link
Contributor

rcpeters commented Aug 6, 2016

We forked it and fixed several issue we were running into. Additionally we made it run in both node and the browser.

@rcpeters rcpeters closed this as completed Aug 6, 2016
@TuningGuide
Copy link
Author

Could you append it to the readme for others? Or did you create a pull request?

@rcpeters
Copy link
Contributor

rcpeters commented Aug 6, 2016

Why don't you do a pull request. Yey open source.

On Aug 6, 2016 8:16 AM, "TuningGuide" notifications@github.com wrote:

Could you append it to the readme for others? Or did you create a pull
request?

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALx5JsYau3VzABC4smlaqT86PY8lLrfks5qdKVQgaJpZM4JeQGI
.

@TuningGuide
Copy link
Author

Good point ^^,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rcpeters @TuningGuide