18

I would argue that MathJax in titles should be kept to the minimum required, and as readable as possible, but if it is integral to writing a good title for the question then it should very much stay there. In other words, if a title requires explicit mathematics, then those explicit mathematics should stay there. Our site has a bunch of questions that are ...


17

I see two relevant classes of users here: The user in question is a relative newcomer, and they've come to rely on other people fixing posts with substantial amounts of mistyped math for them as if by magic. After a first few occurrences, a sharp indication that they need to do the formatting themselves is in order, followed by downvotes if the poster ...


13

Abbreviations and acronyms should be explained, especially if in the title. Avoid abbreviations in titles, such as, e.g., TDR, BGK, GTO, EFE, etc. Spell them out instead (as editors have later done in some of the above examples). Believe it or not, but the most important part of the Phys.SE community is actually not the questioners nor the answerers but ...


10

Note that \tag, \label, and \eqref all play different roles in the process, and you would need to use all three to accomplish your goal. The \tag{x} macro adds an equation number that appears at the right of the equation; it does not create any symbolic name for use with \eqref. That is done through \label{y} which assigns the name y to the tag that is ...


9

Yes, you should edit and/or leave a comment in these cases because Images are fixed size and will display poorly in small browser windows, particularly on phones. MathJax is searchable, although the search functionality is usually not all that useful. MathJax provides a uniform style for typesetting, while the typesetting in images can vary wildly depending ...


9

From our editing guidelines: Edits are expected to be substantial and to leave the post better than you found it. Common reasons for edits include: To fix grammar and spelling mistakes To clarify the meaning of the post (without changing that meaning) To include additional information only found in comments, so all of the information relevant ...


8

This is a site for questions about physics concepts, not about code. The community has decided that "physics concepts" extends to high-level descriptions of algorithms or procedures for physics-related computation, but not to implementation details. In practice, this usually means that most questions shouldn't have code samples in them, and the few that do ...


7

The hat fits me, and also it would fit older users . Everybody ages, and with age memory is not the same, particularly short term memory. I do try to use dollar signs around simple formulae, (since I found out that two $*$ in the paragraph turn everything into italics and destroy the simple formula ! ). The same care I take in spelling and syntax. (syntax ...


7

Yes, mathjax in titles is allowed and even encouraged for better readability/clarity. The main priority is to optimize the user experience for Phys.SE. The HNQ is separate from the Phys.SE and has lower priority. The HNQ is only relevant for a day or two, while the Phys.SE repository is permanent.


7

You can include TeX comments. For example, the Einstein equation is $$ E = %\gamma mc^2 $$ $$ E = %\gamma mc^2 $$ where most people don't include the $\gamma$ that describes the dynamics.


5

Second, I assumed that the standard formatting for post titles would follow that of most other written works - capitalize nouns, verbs, and other major words but don't capitalize prepositions, conjunctions, or articles unless they are the first word in the title. That is incorrect. We discussed titles at length in the meta. One of the things the FAQ says is ...


5

If you're running into length problems because of MathJax then you should probably be posting an answer instead, so I don't find this a compelling argument. However it does annoy me that when I post links in comments the link URL is counted in the comment length. To this extent I agree with AFT's post.


5

It works the same way you did it earlier in the answer, when you had a matrix and vector: just write the markup for the matrices one after another. $$\begin{pmatrix}...\end{pmatrix}\begin{pmatrix}...\end{pmatrix}\begin{pmatrix}...\end{pmatrix}$$ They don't all have to be on the same line, but as with any other MathJax expression, you can't have a blank ...


5

However, does this mean that without use of MathJax, my question will never be answered? The short answer is no, it doesn't mean that. But there's more going on here than just MathJax. From what you described, it sounds like your question actually had a much more severe problem, which is that you posted images of something that could be typed out. That's a ...


5

Plagiarism and violations of copyright are two different ideas. Plagiarism is the use of another persons words or ideas without giving proper credit. It's an academic idea and a violation of academic ethics. Plagiarism is against the rules, and physics being an academic discipline, the users of this site mostly take those rules very seriously. You can ...


4

You can just define an empty tex macro and wrap your code in that. Like this: $$\def\ignore #1{} \ignore{\begin{tikzpicture} \draw (0,0) -- (1,1) ; \end{tikzpicture}}$$ Which looks like this: $$ \def\ignore #1{} \ignore{\begin{tikzpicture} \draw (0,0) -- (1,1) ; \end{tikzpicture}} $$


3

I use \:\mathrm{<units go here>} $E=120\:\mathrm{kgm^2s^{-2}}$ gives I also use this userscript. It lets me enclose stuff with the dollar signs via Alt-M, and Alt-S does \:\mathrm{<selected text here>} for SI units. (there also are options for vector fields and double-dollarifying) If you want mathjax on meta, upvote MathJax on Meta


3

This was answered on Meta.StackExchange a number of years ago. There are two answers Method 1: Using <pre></pre> tags to manually position the HTML image call (in this case, <img src="http://i.stack.imgur.com/Y9ETl.png alt="http://i.stack.imgur.com/Y9ETl.png" title="CENTERED!">). As an example, look here: ...


3

It's probably technically possible, but nobody has bothered to do so yet because it would (presumably) be quite difficult. But all it really needs is for someone to undertake the work of porting the package, and then to convince either the SE dev team or the MathJax developers to include it.


3

An alternative to pasting invisible code is to simply post the code to a Latex sharing site, such as ShareLatex or Overleaf, and then link to it below the image. Then interested users could go see it without having to clicking the edit button (though it is forcing someone off-site). Even repositories such as GitHub or PasteBin would work, though you wouldn'...


3

If a user's posts are still a net positive to the community, there's no need to "deal with" them. Edit in the MathJax if you have the inclination, and, if not, someone else will probably do it eventually. Looking through the history of the Suggested Edits queue, it seems like we have a decent number of people willing to typeset a few equations here and there....


2

My opinion: I am perfectly ok with editing posts to comply with stylistic standards and, in particular, I agree commas look silly in science. But: If you are a <2k user, don't suggest an edit just to remove commas. A reviewer will have to go through your edit and, if minor, it will only waste their time. Make the edit significant or don't do it. If you ...


2

It's not a bad idea, but I doubt this will be implemented because it would make the comment system much more complicated under the hood for little gain. It's not something we (i.e. this community) can do ourselves; it would require the time of an SE developer. I don't think it's a really important feature to have, for a couple of reasons: first, with ...


2

The First Law of Editing: if an edit makes your question less clear (to readers, not necessarily just to you), revert it. That being said, your assumption that post titles follow the capitalization conventions of titles in other works is not correct, because the titles of SE questions are more like summaries, not actual titles per se. A question post's ...


2

The number one priority for the site is that we have members prepared to work at posting good questions and good answers. Right now we have a serious deficit of the former, and while we have lots of people working hard at the latter more are always welcome. Compared to this any debates about about capitalisation in titles are utterly trivial. The idea that ...


1

This is a pretty long post, but if you want to just get the gist, you can read the bolded lines and the summary at the end. Before I begin, I'll mention that I don't disagree with most of the statements that have been made in this thread or in others; however, I do take issue with some of the more pointed ideas. In this post, I will lay out what I think the ...


1

\operatorname, \mbox, \mathrm, \text achieve essentially the same purpose. There's also \fbox (if you want an actual $\fbox{box}$), \mathbf (which achieves this and bolds stuff too) and \bf (essentially the same thing).


Only top voted, non community-wiki answers of a minimum length are eligible