Start basing mathtext tutorial on mathtext parser #26102
Conversation
oscargus
force-pushed
the
mathtextdocgeneration
branch
3 times, most recently
from
3163ba8
to
5294112
Compare
oscargus
force-pushed
the
mathtextdocgeneration
branch
from
5294112
to
4fd4c1a
Compare
oscargus
force-pushed
the
mathtextdocgeneration
branch
from
4fd4c1a
to
63e60ef
Compare
|
May I ask @devRD, @anntzer, and/or @jklymak to consider this? The idea is to, in the end, get consistency. If an operator is listed in a particular section (like relational operator), it will be documented as such. Currently, some are documented as relational operators, but not with the additional spacing required, some have the spacing but are not documented as supported. To only keep one list seems like a better idea. (Of course with the possibility to add more to the documentation in case some should not be spaced, although probably better to add them as an unused set in _mathtext.py). It will probably take more than one PR to get there, but one will for sure find inconsistencies on the way. For example, the additional integral symbols were not dealt with correctly, although listed as supported. |
|
Would it not be easier for math_symbol_table.py to just access the private lists in _mathtext.py (further splitting these lists if necessary) rather than maintaining two separate copies of the lists? |
|
Which is the idea?
Den fre 16 juni 2023 07:41Antony Lee ***@***.***> skrev:
… Would it not be easier for math_symbol_table.py to just access the private
lists in _mathtext.py (further splitting these lists if necessary) rather
than maintaining two separate copies of the lists?
—
Reply to this email directly, view it on GitHub
<#26102 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB55CQICZCMQT7JQ5MFYBKTXLPWXNANCNFSM6AAAAAAZBWUALY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
To clarify my comment. That is exactly the idea. Where there is such a list in |
|
Ah yes, sure, misread it. |
PR summary
See #14766 (comment)
With this, the
\*cornerdelimiters are no longer documented. Not sure if they should be included in the parsers list of delimiters or what we mean by delimiters here? Options are to include them manually in the docs or in a different section.It would be easy to include relational operators and arrows as well, but the discrepancy between those are quite big....
Also adds a few misc symbols to the documentation and makes double and triple integral signs drop the subscript to get correct rendering. Adds quadruple integral symbol
\iiiintand Unicode symbol for already supported\bigsqcup.PR checklist