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

fix nand and nor latex symbols #1366

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

fix nand and nor latex symbols #1366

wants to merge 2 commits into from

Conversation

mmatera
Copy link
Contributor

@mmatera mmatera commented May 9, 2021

No description provided.

@mmatera
Copy link
Contributor Author

mmatera commented May 10, 2021

Update: the problem is the following. In the title of a section associated with an operator, the character of the operator is put inside a ``\code{\lstinline 'char' }```. As \lstinline expect verbatim code, it fails to understand math mode expressions.
In this PR I just removed `\lstinline` in a way that LaTeX accepts LaTeX code.

@rocky rocky force-pushed the master branch 2 times, most recently from b007e8c to ef16eb6 Compare May 19, 2021 22:40
@rocky
Copy link
Member

rocky commented Jun 1, 2021

@mmatera in #1399 I used your observation that the problem was that the text is inside "inline" text and I revised the doc string so that the operators are now outside. In fact there are many places as far as formatting goes that when you have an operator expression like:

$expr1$ \u22BD $expr2$ \u22BD ...

I am not seeing any benefit in using the quotes at all. The benefit is only when there is an name like Nand (and maybe including the bracket. As a convenience to minimize the use of the quote I think the quote was extended to the closing bracket.

In that PR I also moved forward in using unicode in more of the operators that have no ASCII equivalent.

I am (slowly) moving towards the idea of replacing the ASCII operators like == too, but really, better would be to hook in all of that with mathics-scanner and have some way for it to fallback to the ASCII operators when the front end doesn't support that.

Should this PR be closed?

@rocky rocky force-pushed the master branch 5 times, most recently from 8367d69 to 83bb068 Compare June 7, 2021 21:01
@rocky rocky force-pushed the master branch 2 times, most recently from 9570fdd to 499f1bf Compare June 26, 2021 14:12
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 this pull request may close these issues.

2 participants