improve LaTeX processing. Fix inconsistencies in the docstring format#1327
improve LaTeX processing. Fix inconsistencies in the docstring format#1327
Conversation
|
A brief look at this and it looks good. But I'd like to try it out in detail tomorrow. I'm thinking that after all of the documentation stuff is fixed we might make a minor release of Mathics Kernel. Your thoughts? |
|
@rocky, I agree: after finishing with the documentation, we can move to a 8.0.1 release or something like that. |
mathics/builtin/system.py
Outdated
| # I have to comment out this to pass the | ||
| # "precommit". @rocky, any idea about how to | ||
| # remove the comment? | ||
| # breakpoint() |
There was a problem hiding this comment.
@rocky, please check if you are able to uncomment this without complains from precommit.
|
LGTM. Tried it and it works great! |
|
@rocky, before the before the new release, please give me the chance to pass over all the documentation to adjust the quotations in |
No problem. Also, Look form places were we have |

This is another pass through the documentation system. The PR includes
DocumentEntry.latex(). Almost all special characters are now handled by the mathicsscanner tables.$character in docstrings. Now it must be explicitly escaped.escape_latexfunction was improved.'Head'[$var_1$,$var_2$]now are formatted as expected ('Head'as a code variable, and$var_1$as a LaTeX expressions).