-
Notifications
You must be signed in to change notification settings - Fork 255
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
Fix critical bug #5
base: master
Are you sure you want to change the base?
Conversation
Fixed bug "Can't locate scigen.pm in @inc [...] at ./make-latex.pl line 21." & similar bugs by including current directory as library.
Heh, did you just casually port this to nodejs? And here I was wondering if it would be worth figuring out perl and deploying it to heroku with minimal changes. Excellent work! |
Yes! Thank you for your nice words :) It is possible to run the main part in the browser, without any server involved. There is some more explanation and a demo at scigen.js. The bottleneck of the browser-only approach is the creation of the PDF from the Latex code that is produced by scigen.js. While the Latex core is ported to Javascript, Bibtex (for the bibliography) and As long as there is no workaround for Ghostscript, it may still make sense to run scigen.js on a server that also runs Latex (including Ghostscript!) -- I don't know if this is possible on Heroku? For this, you could use the scigen.js version on NPM, where, I believe, the generation of new figures is still enabled. Perl would not be needed, then. Edit: It's about Ghostscript, not about |
Fix critical bug
Can't locate scigen.pm in @inc [...] at ./make-latex.pl line 21.
& similar bugs at running./make-latex.pl
(as described on the homepage) by including current directory as library.