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
When uncommenting usetex=True the output is:
I.e. the accents are rendered correctly now, but the vertical bars are for some reason rendered as horizontal bars suddenly. Not sure if I should open yet another issue for that?
Just for comparison, this is what codecogs renders:
Also as indicated in the sourcecode \underline{...}\overbrace{...}\underbrace{...} don't work at all. I tested those, because they were in the same "accent"(?)-category in the codecogs equation editor.
fixes the positioning of the \check, but a similar fix does not work for \not (it ends up positioned "higher" than the character, at the "accent" position).
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!
I'd have a look at #23189 that adds support for check and a few other accents. However, it got stuck as I added the feature of "properly" combining accents, i.e., using the composite Unicode character rather than "visually pasting two characters on top of each other". I think that is really the correct way to go, but it will change the rendering (to the better...). The good thing is that this will also support accents independent of the location (currently we cannot do things like not or accents placed below the character) and it uses the correct version of the accent, for check looks different dependent on letter, see e.g. d here: https://www.compart.com/en/unicode/U+030C. But it is not optimal in that there must be a corresponding character defined for this to work in all cases (my PR falls back to the old behavior otherwise).
Still, getting the additional accents from #23189 should be simple (I thought I had done that already, but apparently it was only suggested and I think I wanted to discuss replacing the whole mechanism before ditching it).
Edit: I'll see if I can find some time to extract the accents over the weekend. The idea is not to ask @devRD to finish all my abandoned PRs...
Activity
anntzer commentedon Mar 27, 2019
Looks like
fixes the positioning of the \check, but a similar fix does not work for \not (it ends up positioned "higher" than the character, at the "accent" position).
As for the vertical vs. horizontal bar thing: https://tex.stackexchange.com/questions/193216/vertical-bar-turning-horizontal
oscargus commentedon Jun 1, 2022
Similar problems appear for Hungarian umlaut, all accents positioned underneath the character, like cedilla and ogonek, and for tie. See https://en.wikibooks.org/wiki/LaTeX/Special_Characters
github-actions commentedon Jun 2, 2023
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!
story645 commentedon Jun 2, 2023
@devRD is this in scope for you?
devRD commentedon Jun 2, 2023
@story645 Yeah, I think it is in my scope of work
oscargus commentedon Jun 2, 2023
I'd have a look at #23189 that adds support for check and a few other accents. However, it got stuck as I added the feature of "properly" combining accents, i.e., using the composite Unicode character rather than "visually pasting two characters on top of each other". I think that is really the correct way to go, but it will change the rendering (to the better...). The good thing is that this will also support accents independent of the location (currently we cannot do things like not or accents placed below the character) and it uses the correct version of the accent, for check looks different dependent on letter, see e.g. d here: https://www.compart.com/en/unicode/U+030C. But it is not optimal in that there must be a corresponding character defined for this to work in all cases (my PR falls back to the old behavior otherwise).
Still, getting the additional accents from #23189 should be simple (I thought I had done that already, but apparently it was only suggested and I think I wanted to discuss replacing the whole mechanism before ditching it).
Edit: I'll see if I can find some time to extract the accents over the weekend. The idea is not to ask @devRD to finish all my abandoned PRs...