Gold Member
- 4,458
- 3,265
I'm getting firefox script errors. It's probably my lack of understanding how to use it.
dlgoff said:I'm getting firefox script errors. It's probably my lack of understanding how to use it.
indeedFredrik said:Works fine for me now. It looks good. I would prefer a slightly bigger size for the stuff we'd normally use tex tags for, but I assume that sort of thing can be tweaked later.
nopeFredrik said:Will we still be using tex and itex tags as before?
Fredrik said:I can't tell if this will solve the problems we have right now.
What happens when you try? (It's working fine for me).Kurdt said:Still not working.
Fredrik said:What happens when you try? (It's working fine for me).
Greg Bernhardt said:ok try now at https://www.physicsforums.com/mathjax/test/preview.html
Fredrik said:The LaTeX code for new line is \\, but it doesn't seem to work in the default environment. It does however work in the align environment, so I would suggest that you use that. For example,
\begin{align} x &= 1\\
y &=2
\end{align}
Alternatively, I'm guessing that we're going to have to put some kind of tags around the math expressions, so you could just put separate tags around expressions that are to appear on different lines. This is of course how we do this now.
[tex]1[/tex]
[tex]2[/tex]
VietDao29 said:Did you try this page?
It's the same for me. I just assumed that the app is working as it should, and that the text is wrong about what you should do.Borek said:What does "press RETURN" means? Or more precisely - what it DOES? I know how to hit Enter, but unless I click outside of the edit field (as it was required previously) nothing happens.
Does it work when you try it in another browser?Kurdt said:Errors on page, then nothing.
You rarely need newlines in LaTeX expressions in a forum post, but a button or a key combination (like Ctrl+A) that insertsVietDao29 said:Yeah, I think there should be some kind of tags, or there may be some way to work around, like enabling \\ by putting \begin{align}, and \end{align} at 2 ends of every post.
Thanks for that Fredrik. I think I can even learn how to do this.Fredrik said:I think eqnarray is considered more or less obsolete. align is easier to use and the output looks better. See e.g. this blog post.
Fredrik said:I did a "view source" on one of their demo pages. It appears that the tags to begin and start a math expression are \( and \) respectively.
Greg Bernhardt said:Won't be necessary. We will look into switching to mathjax once 1.1 is out of beta.
Borek said:
The Stack Exchange network uses MathJaX with $ (inline) and $$ (block) as the delimiters, so it definitely should be possible to change that. At worst I'd imagine it's a matter of changing a couple of constants in the source code.Greg Bernhardt said:Could be wrong but I bet that is something we can easily change. In fact, thinking about it, we'll need to change it to our tex tags so past equations are preserved on once the old latex images are gone.
Whatever is done, it'll have to also work for people who don't have an AltGr key (i.e. most US keyboards).Fredrik said:It would be nice to have delimiters that are easier to type than [noparse][/itex][/noparse]. $ and $$ are easy enough, but \( and \[ are not. An Alt Gr shortcut would be an OK alternative. For example, if you type "Alt Gr+i" now, "[noparse][/noparse]" is typed, and the cursor is placed between the tags. If you select some text first, the tags are placed around that block of text. We could have e.g. Alt Gr+f and Alt Gr+d for the tags. Assuming of course that this can be configured in vBulletin. If function keys can be used this way, then I would suggest F8 and F9 (or F4 and F5).
If we have different delimiters, then Greg will have to ensure that the tex and itex tags used in all previous posts be automatically changed to the new ones, so we don't lose the ability to read old TeX. I don't know if that is trivial to do.Fredrik said:It would be nice to have delimiters that are easier to type than [noparse][/itex][/noparse].
They don't have Alt Gr keys!?diazona said:Whatever is done, it'll have to also work for people who don't have an AltGr key (i.e. most US keyboards).
I expect that it will only be trivial if we can have several different delimiters mean the same thing.Gokul43201 said:If we have different delimiters, then Greg will have to ensure that the tex and itex tags used in all previous posts be automatically changed to the new ones, so we don't lose the ability to read old TeX. I don't know if that is trivial to do.