You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rob Beezer left the following comment on the sage-edu announcement post:
If the following are important for your project,
Consistency between PDF and HTML versions
Standard notation
Easy-to-navigate HTML version
Automated testing of Sage code
Eventual no-effort versions for the Sage Notebook and Sage Math Cloud
Avoiding a lot of LaTeX idiosyncracies
then you might want to be an early adopter of MathBook XML for authoring your
project. There are some experienced folks (including myself) on the Google
Group who can help you over the rough patches.
If the Sage in the book is just going to be words on a page, then having LaTeX as
the source may be adequate. But if you want to automatically generate Sage cells
or a Sage notebook, then your best option would be to convert to Mathbook XML (MBX),
as described in Rob's post.
I have been thinking about modifying my code to convert to MBX instead of HTML,
and would consider using this calculus book as a test case.
Posted here solely to keep documentation of conversation with github project. I'll looking into Matchbook before beginning development.
The text was updated successfully, but these errors were encountered:
The more I read about MathBook the more interested I am. I think I might try one chapter as a test (chapter 2, since it's nearly finished in the LaTeX format and has a good sample of nearly everything).
Rob Beezer left the following comment on the sage-edu announcement post:
David Farmer then followed up with:
Posted here solely to keep documentation of conversation with github project. I'll looking into Matchbook before beginning development.
The text was updated successfully, but these errors were encountered: