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

Better rendering for Conjugate [post 1.1] #952

Open
suhr opened this issue Oct 7, 2020 · 9 comments
Open

Better rendering for Conjugate [post 1.1] #952

suhr opened this issue Oct 7, 2020 · 9 comments

Comments

@suhr
Copy link
Contributor

suhr commented Oct 7, 2020

Currently it is rendered as Conjugate[x], but it would be nice to render it as x^{*} instead.

@suhr suhr changed the title Better rendering for Conjugate Better rendering for Conjugate [post 1.1] Oct 7, 2020
@GarkGarcia
Copy link
Contributor

@suhr Is this something Mathematica does?

@suhr
Copy link
Contributor Author

suhr commented Oct 13, 2020

It seems so. At least it has x^{*} syntax: https://reference.wolfram.com/language/ref/Conjugate.html.

@weakit
Copy link
Contributor

weakit commented Oct 17, 2020

image

I just checked, and Mathematica doesn't do the formatting.

We already have the conjugate symbol btw:

"Congruent": "\u2261",
"Conjugate": "\uF3C8",
"ConjugateTranspose": "\uF3C9",

Works as expected too:

image

but it would be nice to render it as x^{*} instead.

I agree, but I also think that might be confusing. Might be better if we stick with what Mathematica does.

Maybe we can close this issue?

@suhr
Copy link
Contributor Author

suhr commented Oct 17, 2020

So we need to implement TraditionalForm.

@weakit
Copy link
Contributor

weakit commented Oct 18, 2020

TraditionalForm is the pretty much rendered TeXForm:

image

TeXForm in mathics is kinda incomplete, there's a lot of formatting that's missing—including conjugate:

mathematica mathics
image image

The only thing I think TeXForm properly formats is Sqrt, Power, Times and Plus. I don't think it does anything else.

image

I actually tried to get TeXForm to work a long time ago (before @GarkGarcia started working on it and mathics dev was kinda dead) and couldn't. I don't really know/understand (I'm kinda stupid lol) the internals well enough to help with that. I do know a bit more now that I've done some research, and I'm pretty sure this is going to be a lot of work.

Good Luck, and I'll try to help as much as I can.

@rocky
Copy link
Member

rocky commented Oct 18, 2020

To set expectations on getting stuff like this fixed, it is much harder find people to fix problems than it is to find problems.

#912 has my views of the biggest, and most worthy problems to address (at least for me) as of about a month ago. You can also use that as a gauge for how fast progress has been (although most of these are post 1.1.0 items)

Personally, I can't imagine I'd ever personally desire a need for better rendering of conjugate or using/improving TeXForm, or TraditionalForm. But hey, I don't have a crystal ball, so you never know.

If there is something that is broken and it bothers you, the most likely way to get it fixed is to work on it.

@weakit
Copy link
Contributor

weakit commented Oct 21, 2020

Personally, I can't imagine I'd ever personally desire a need for better rendering of conjugate or using/improving TeXForm, or TraditionalForm. But hey, I don't have a crystal ball, so you never know.

The mathics web interface uses TeXForm to display results, iirc.
Maybe that's important enough for someone to consider patching up TeXForm.

Also, I think we should probably swtich from using TeXForm to something else for the web interface. We should be using StandardForm instead.

@rocky
Copy link
Member

rocky commented Oct 21, 2020

The mathics web interface uses TeXForm to display results.

If I have it correct, at least for graphics, Django interface uses XML which is MathML

Also, I think we should probably swtich from using TeXForm to something else for the web interface. We should be using StandardForm instead.

In general, if you look at #912, unless someone is interested in that, this will be fading in favor of a Jupyter interface, and mathicsscript which are each in their own repositories.

There is a lot of talk about what we could be doing. As I've said before, to turn this in to something that is done, just start working on whatever it is that interests you.

For myself, the backlog for getting things I am interested in done is already too long and already has too many things that need to be unblocked before I can get to what I am more interested in.

@weakit
Copy link
Contributor

weakit commented Oct 22, 2020

If I have it correct, at least for graphics, Django interface uses XML which is MathML

Eh, guess I was wrong, They both have the same amount of functionality tho. It would be pretty easy to extend the other if you could figure out how to get either one working.


For myself, the backlog for getting things I am interested in done is already too long and already has too many things that need to be unblocked before I can get to what I am more interested in.

It's ok lol I don't think that there's really any expectation of you, or any of us to help out. It's great that you are. We're all doing this for our own individual reasons, but that doesn't really matter—either way, it's helping the project out.

Mathics was pretty much dead a while ago, so development is going to be slow, and it will take a good while before it picks up pace.

There is a lot of talk about what we could be doing. As I've said before, to turn this into something that is done, just start working on whatever it is that interests you.

Even making an issue, and active discussion counts as progress imo. This isn't something that I can work on, especially right now. But this issue and the discussion that happened here might be useful to someone else that's trying to fix this in the future. That someone might even end up being me.

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

No branches or pull requests

4 participants