View source for Caratheodory-π solution


=== Pros of TeX ===

# {{TeX}} is semantically more precise than HTML.
## In {{TeX}}, "<source lang="latex" enclose="none">x</source>" means "mathematical variable <math>x</math>", whereas in HTML "<source lang="latex" enclose="none">x</source>" is generic and somewhat ambiguous.
## On the other hand, if you encode the same formula as "<source lang="html5" enclose="none">{{math|<var>x</var>}}</source>", you get the same visual result {{math|''x''}} and no information is lost. This requires diligence and more typing that could make the formula harder to understand as you type it. However, since there are far more readers than editors, this effort is worth considering if no other rendering options are available (such as [[w:MathJax|MathJax]], which is available to logged in users as an [[Special:Preferences#mw-prefsection-rendering|preferences]] opt-in).
# One consequence of point&nbsp;1 is that {{TeX}} code can be transformed into HTML, but not vice-versa.{{ref|dilHTML}} This means that on the server side we can always transform a formula, based on its complexity and location within the text, user preferences, type of browser, etc. Therefore, where possible, all the benefits of HTML can be retained, together with the benefits of {{TeX}}. It is true that the current situation is not ideal, but that is not a good reason to drop information/contents. It is more a reason to [[#Bug reports|help improve the situation]].
# Another consequence of point&nbsp;1 is that {{TeX}} can be converted to [[w:MathML|MathML]] (e.g. by MathJax) for browsers which support it, thus keeping its semantics and allowing the rendering to be better suited for the reader’s graphic device.
# {{TeX}} is the preferred text formatting language of most professional mathematicians, scientists, and engineers. It is easier to persuade them to contribute if they can write in {{TeX}}.
# {{TeX}} has been specifically designed for typesetting formulae, so input is easier and more natural if you are accustomed to it, and output is more aesthetically pleasing if you focus on a single formula rather than on the whole containing page.
# Once a formula is done correctly in {{TeX}}, it will render reliably, whereas the success of HTML formulae is somewhat dependent on browsers or versions of browsers. Another aspect of this dependency is fonts: the serif font used for rendering formulae is browser-dependent and it may be missing some important glyphs. While the browser generally capable to substitute a matching glyph from a different font family, it need not be the case for combined glyphs (compare&nbsp;‘&nbsp;''{{IPA|a&#773;}}''&nbsp;’ and&nbsp;‘&nbsp;''a̅''&nbsp;’).
# When writing in {{TeX}}, editors need not worry about whether this or that version of this or that browser supports this or that HTML entity. The burden of these decisions is put on the software. This does not hold for HTML formulae, which can easily end up being rendered wrongly or differently from the editor’s intentions on a different browser.{{ref|browsupp}}
# {{TeX}} formulae, by default, render larger and are usually more readable than HTML formulae and are not dependent on client-side browser resources, such as fonts, and so the results are more reliably WYSIWYG.
# While {{TeX}} does not assist you in finding HTML codes or Unicode values (which you can obtain by viewing the HTML source in your browser), copying and pasting from a {{TeX}} PNG image in Wikipedia into simple text will return the LaTeX source.

: <small>{{note|dilHTML}} unless your wikitext follows the style of point&nbsp;1.2</small>
: <small>{{note|entHTML}} The entity support problem is not limited to mathematical formulae though; it can be easily solved by using the corresponding characters instead of entities, as the character repertoire links do, except for cases where the corresponding glyphs are visually indiscernible (e.g. &amp;ndash; for &lsquo;&ndash;&rsquo; and &amp;minus; for &lsquo;&minus;&rsquo;).</small>