Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add more relational operators to mathtext #25045

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

Closed
wants to merge 1 commit into from

Conversation

oscargus
Copy link
Member

@oscargus oscargus commented Jan 20, 2023

PR Summary

Fixes #25042

Putting this as draft as I should go through this more systematically at some stage and check e.g. https://oeis.org/wiki/List_of_LaTeX_mathematical_symbols and https://garsia.math.yorku.ca/MPWP/LATEXmath/node8.html

Also, it would be useful to group the symbols a bit better to see what is possibly missing. As part of this, the layout/spacing will be improved.

PR Checklist

Documentation and Tests

  • Has pytest style unit tests (and pytest passes)
  • Documentation is sphinx and numpydoc compliant (the docs should build without error).
  • New plotting related features are documented with examples.

Release Notes

  • New features are marked with a .. versionadded:: directive in the docstring and documented in doc/users/next_whats_new/
  • API changes are marked with a .. versionchanged:: directive in the docstring and documented in doc/api/next_api_changes/
  • Release notes conform with instructions in next_whats_new/README.rst or next_api_changes/README.rst

@story645
Copy link
Member

story645 commented Jan 22, 2023

Can you add restriction to this batch or is out of scope here? ef860db98a830ac54b7f9a3a324504cc4b90ca7c.png

@anntzer
Copy link
Contributor

anntzer commented Jan 22, 2023

That one wouldn't need spacing around it.

@story645
Copy link
Member

story645 commented Jan 22, 2023

That one wouldn't need spacing around it.

So out of scope here :/ I'll see if opening my own PR is feasible then...

ETA: it's already implemented, just as the \harpoon and not w/ the amssymb name. 😅

@devRD
Copy link
Contributor

devRD commented May 16, 2023

I think the command \geqslant is missing from the list. Are there any other changes/tests required that I can help with to complete this patch?

@oscargus
Copy link
Member Author

oscargus commented May 16, 2023

@devRD you are correct! I think the way is really to try to organize the operators in some way and then systematically check some lists, e.g. the ones in the description above.

Feel very much free to complete it. I do not really remember how I did, but I guess one should also make sure that we have defined some mapping for the symbol as well. However, I think that the doc build takes this list and creates documentation from it, so it would show up there if something is not defined(?).

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

Successfully merging this pull request may close these issues.

[Bug]: \geqslant, \leqslant and \eqslantgtr are not spaced like their non-slanted versions
4 participants