-
Notifications
You must be signed in to change notification settings - Fork 178
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
How to include another CSL? #242
Comments
Our current recommendation is to edit the line in Line 23 in ed4158c
You should be able to point this at a URL. You can find available styles at https://github.com/citation-style-language/styles or https://www.zotero.org/styles. If using a style from GitHub, make sure to replace You can also edit |
Let's add these instructions to We may also want to revisit #189 to discuss longer term plans for customizing the build process (CSL, plugins, etc.) through a config file, environment variables, or something else that is less technical than editing a bash script. |
For any future Manubot users who came here because this is the top Google result for "Manubot CSL", this fix is no longer valid. The updated method for changing CSL files can be found here: #334 (comment) tl;dr go to |
@agitter as a note here, the manifesto "USAGE.md" is outdated, and still points to build.sh: |
That's because the manufesto paper is using a very old version of rootstock. It looks like it hasn't been updated since 2019. I could update it but will need to wait until I can set aside some time to resolve merge conflicts. |
Ah I can also update manufesto. I expect the underlying issue here is that @lubianat googled something like "manubot usage github" and the rootstock USAGE is not even listed on the first page! I wonder why. |
I wasn't able to find in the documents how I can implement another CSL file to render my references based on some specific requirements.
I think modifying the line
CSL_PATH=build/assets/style.csl
inbuild.sh
is the way. Is there an easier way without changingbuild.sh
?The text was updated successfully, but these errors were encountered: