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.

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

Support LaTeX files #7

Open
krassowski opened this issue Jul 16, 2021 · 4 comments · May be fixed by #58
Open

Support LaTeX files #7

krassowski opened this issue Jul 16, 2021 · 4 comments · May be fixed by #58

Comments

@krassowski
Copy link
Owner

krassowski commented Jul 16, 2021

It would be great to integrate with jupyterlab-latex nicely https://github.com/jupyterlab/jupyterlab-latex.

@krassowski
Copy link
Owner Author

krassowski commented Sep 15, 2021

The citations processor that is used in this extension already supports LaTeX output:

*/
export type OutputMode =
| 'html'
| 'text'
| 'rtf'
| 'asciidoc'
| 'fo'
| 'latex';

"outputFormat": {
"title": "Format of citations and bibliography",
"type": "string",
"default": "html",
"description": "One of: html, text, rtf, asciidoc, fo, latex",
"enum": ["html", "text", "rtf", "asciidoc", "fo", "latex"]
}

but more changes will be needed. The pre-requisite would be #8.

CC @ktaletsk

@jochym
Copy link

jochym commented Jun 13, 2022

Second that! This would be the last obstacle to fully "close the loop" for me. After implementation of RTC in lab and jupyterlab-latex the only missing feature for a full research/collaboration/publication workflow is lack of the support for citations. I have tried if I can function with text exported from notebooks and conversions, but it is too complicated to force my colleagues to use it and the result is not suitable for submission to the journal. So I am stuck with writing in overleaf and constantly copying data/figures etc. instead of having everything under one roof.
What will be required for such extension @krassowski ? How can I help to make it happen? And thanks for an already very useful tool!

@krassowski krassowski linked a pull request Jun 19, 2022 that will close this issue
6 tasks
@krassowski
Copy link
Owner Author

Hi @jochym I pushed a very rough draft in #58 but it requires more work. Briefly, the LaTeX world and citeproc processor world are quite incompatible and I am still looking at ways to build a bridge that would not take away from the benefits of either.

@jochym
Copy link

jochym commented Jun 19, 2022

Thanks for your efforts! That was quick. Shall I test something already? Unfortunately, I am really not good with TS. And BTW, from my POV the perfect solution will allow for using \cite{nameYear} in the text. Just my two cents.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants