Closed drscotthawley closed 1 year ago
Thanks for opening your first issue here! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out EBP's Code of Conduct. Also, please try to follow the issue template as it helps other community members to contribute more effectively.
If your issue is a feature request, others may react to it, to raise its prominence (see Feature Voting).
Welcome to the EBP community! :tada:
I've heavily edited this Issue from its initial version. The initial version showed my specific document, and issues such as myst
not finding any of the references defined in my BibTex file.
To make things more reproducible for developers, I've removed much of that and replaced it with what you get if you just try the template documents provided by the journal.
One problem with this approach is that JAES zip file includes multiple (at least two) .tex files, which could be confusing for the parser. For my initial report using my document, there was only one .tex file in the directory.
If you want to see my original version, then presumably GitHub provides a way for you to view the edit-history of this Issue.
I went back and installed jupyter-book
. It didn't make any difference to errors reported. But here's the version info:
$ jupyter-book --version
Jupyter Book : 0.13.1
External ToC : 0.2.4
MyST-Parser : 0.15.2
MyST-NB : 0.13.2
Sphinx Book Theme : 0.3.3
Jupyter-Cache : 0.4.3
NbClient : 0.5.13
Note the error message ""myst-transforms" was not found in your node_modules. Did you forget to install it?
. All I did was follow the installation instructions, i.e.
$ npm install -g myst-cli
Thanks for the feedback, and taking the time to detail and make this reproducible!! There is a ton more to do on the latex parsing side to make this fully usable in all situations, the hard error in the rendering is something that we should fix, and at least you should have seen a partially rendered document that would have been pretty good I think.
As you suspected the currently supported workflow is in the other direction (MyST + Template --> TeX --> PDF):
write a document starting in MyST-markdown, and then use a LaTeX templates
We are madly writing docs and onboard guides!! I have already fixed up those two spurious "was not found in your node_modules" which are a problem with a library upgrade we did and they are not real errors. We also need to do a better job on the differences between JupyterBook and myst.tools, they use the same syntax but completely different engines.
This is really helpful feedback as I start to create the intro slides for next Wednesday. Hope to see you there. :)
MyST + Template --> TeX --> PDF will serve my needs very well.
Looking forward to Wednesday!
Feel free to close this issue if you like.
I will fix some of the easy things in that template and then close this off. Looking to make progress on the LaTeX parsing side as well, so that at the very least the initial experience doesn't end in an error screen!!
I'm going to close this issue, as much of it was based on misunderstanding.
Describe the bug
(EDIT: edited to show standard/reproducible JAES template, rather than my specific document.)
context Hi guys. Saw Steve's post about "Writing a Scientific Paper in MyST Markdown" and Rowan's seminar next week. Since I'm starting two new scientific papers, I decided to try MyST.
Followed the instructions https://curvenote.com/blog/how-to-use-latex-with-myst-markdown, ...downloaded a ZIP of my stuff from Overleaf, using the template files from the Journal of the Audio Engineering society.
Installed myst via npm, ran it in the directory where my .tex file is and....
expectation I expected to get a wonderful rendering of my scientific document.
bug But instead lots of errors occur .
The web server shows this image:
problem This is a problem for _people doing any kind of scientific publishing_ because we will need to be producing results in accordance with an approved template from a publisher or conference___. If we have to write two different versions of our document, one for true publishing, and one in Markdown just for... IDK I'm not trying to make a website, I'm trying to write a journal article, ... then user adoption of MyST will be limited. (i.e. if I should just write the LaTeX version if MyST can't help me, then...I have no reason to use MyST)
Clarification
I did not try to write a document stariting in MyST-markdown, and then try to import the LaTeX templates for the purposes of rendering a PDF. Such was my original expectation for authoring a scientific paper using MyST markdown.
But then when I read the page about using LaTeX and MyST I got the impression that I was just supposed to read in my .tex files. Rowan will probably clarify this at the seminar, and perhaps this whole Issue is just resulting from a big misunderstanding on my part!
Reproduce the bug
myst init
myst start
List your environment
There was no mention of jupyter-book when I followed the MyST installation instructions. If we need jupyter-book, please update the installation instructions.