Jump to content

Template talk:Intmath

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Improving the result with a dollop of CSS

[edit]

Suggestions to improve the code of the template.

Code suggestions for ∫

[edit]

Code suggestions for ∫ (text style)

[edit]

The [suggested] code (for ∫, not for other integrals)

: {{math|Γ(''z'') {{=}} <!--
--><span style{{=}}"position: relative; font-size: 1.0em;"><!--
  --><span style{{=}}"vertical-align: -0.15em; font-style: italic; font-size: 1.35em; margin-right: -0.05em;">∫</span><!--
  -->{{su
     | b = <span style{{=}}"vertical-align: -0.1em; font-size: 0.9em; margin-left: 0.0em;">0</span>
     | p = <span style{{=}}"vertical-align: -0.5em; font-size: 0.9em; margin-left: 0.2em;">∞</span>
     }}<!--
--></span><!--
--> ''e''<sup>−''t''</sup> ''t''  <sup>''z'' − 1</sup> ''dt''
}}

yields the text style HTML+CSS

Γ(z) =
0
ett  z − 1dt

The code

: <math>\textstyle \Gamma(z) = \int_{0}^{\infty} e^{-t} t^{z-1} dt</math>

yields the text style LaTeX

Code suggestions for ∫ (display style)

[edit]

The [suggested] code (for ∫, not for other integrals)

: {{math|Γ(''z'') {{=}} <!--
--><span style{{=}}"position: relative; font-size: 1.4em;"><!--
  --><span style{{=}}"vertical-align: -0.25em; font-style: italic; font-size: 1.6em; margin-right: -0.05em;">∫</span><!--
  -->{{su
     | b = <span style{{=}}"vertical-align: -0.6em; font-size: 0.7em;">0</span>
     | p = <span style{{=}}"vertical-align: -0.6em; font-size: 0.7em;  margin-left: 0.3em;">∞</span>
     }}<!--
--></span><!--
--> ''e''<sup>−''t''</sup> ''t''  <sup>''z'' − 1</sup> ''dt''
}}

yields the display style HTML+CSS

Γ(z) =
0
ett  z − 1dt

The code

: <math>\Gamma(z) = \int_{0}^{\infty} e^{-t} t^{z-1} dt</math>

yields the display style LaTeX

Code suggestions for other integrals

[edit]

Code suggestions for other integrals (text style)

[edit]

The [suggested] code (for other integrals, not for ∫)

: {{math|<!--
--><span style{{=}}"position: relative; font-size: 1.0em;"><!--
  --><span style{{=}}"vertical-align: -0.1em; font-style: italic; font-size: 1.4em; margin-right: -0.15em;">∲</span><!--
  -->{{su
     | b = <span style{{=}}"vertical-align: -0.25em; font-size: 0.9em; margin-left: -0.1em;">''C''</span>
     | p = <span style{{=}}"vertical-align: 0em; font-size: 0.9em; margin-left: 0.4em;">(cw)</span>
     }}<!--
--></span><!--
--> ''F''('''x''') ∙ ''d'''''x'''  {{=}} (...)
}}

yields the text style HTML+CSS

(cw)
C
F(x) ∙ dx = (...)

The code

: <!-- \varointclockwise not supported --><math>\textstyle \oint_{C}^{\rm (cw)} F(\boldsymbol{\rm x}) \sdot d\boldsymbol{\rm x} = (\ldots)</math>

yields the text style LaTeX

Code suggestions for other integrals (display style)

[edit]

The [suggested] code (for other integrals, not for ∫)

: {{math|<!--
--><span style{{=}}"position: relative; font-size: 1.6em;"><!--
  --><span style{{=}}"vertical-align: -0.1em; font-style: italic; font-size: 1.5em; margin-right: -0.25em;">∲</span><!--
  -->{{su
     | b = <span style{{=}}"vertical-align: -0.45em; font-size: 0.6em; margin-left: -0.3em;">''C''</span>
     | p = <span style{{=}}"vertical-align: 0em; font-size: 0.6em; margin-left: 0.85em;">(cw)</span>
     }}<!--
--></span><!--
--> ''F''('''x''') ∙ ''d'''''x'''  {{=}} (...)
}}

yields the display style HTML+CSS

(cw)
C
F(x) ∙ dx = (...)

The code

: <!-- \varointclockwise not supported --><math>\oint_{C}^{\rm (cw)} F(\boldsymbol{\rm x}) \sdot d\boldsymbol{\rm x} = (\ldots)</math>

yields the display style LaTeX

— Preceding unsigned comment added by 132.204.185.45 (talk) 23:48, 12 March 2016‎ (CET)

Tentacles mailto:Tentacles 20:38, 13 March 2016 (UTC)[reply]

Do I get the approval to modify the {{intmath}} template for text style HTML+CSS only (using the above tested code)? I don't think Wikipedia wants the display style HTML+CSS option, since LaTeX works nicely for display style. — Tentacles mailto:Tentacles 20:53, 13 March 2016 (UTC)[reply]

The purpose of this template is to serve as alternative to using the <math>...</math> tag. There are a number of problems with the math tag which depend on the options used. There are three main different modes available, in particular nologged in users use the rather ugly PNG output. The following shows what an IP will see
note the aliasing problems and the dropped baseline with the <math>. Until the math rendering is sorted out inline <math>...</math> will still look bad to some users, which is why editors still want to use css for some inline equations.--Salix alba (talk): 21:36, 13 March 2016 (UTC)[reply]
I totally know about all the issues of [inline] text style LaTeX PNG's, that's why I'm working hard on improving the presentation of the [inline] text style HTML+CSS rendering of the integrals. The reason why I have the LaTeX renderings above is to compare my HTML+CSS renderings with the LaTeX renderings to fine tune my CSS code, so that the HTML+CSS renderings look as good as LaTeX renderings. — Tentacles mailto:Tentacles 22:23, 13 March 2016 (UTC)[reply]

Suggestion of new template code

[edit]

Here is the (tweaked and/or optimized for use inside the {{math}} and {{bigmath}} templates) latest (April 09, 2016) code that I propose. (∫ is treated separately because it renders in a different font, which also have a higher vertical alignment.)

Suggested code for {{intmath}} (now in {{intmath/sandbox}}):

<includeonly>{{#switch: {{#if: {{{1|}}} |{{{1}}}|int_roman}}
| iint | iiint | iiiint | oint| varointclockwise  | ointctrclockwise | oiint 
| oiiint = <span style{{=}}"display: inline-block; position: relative; line-height: 0.715em; height: 0.715em; margin: {{#ifeq: {{{4|}}} |tiny|-0.8|-1.0}}em 0 {{#ifeq: {{{4|}}} |tiny|0.2|0}}em 0<!-- trbl -->; padding: {{#ifeq: {{{4|}}} |tiny|0.2|0}}em 0 {{#ifeq: {{{4|}}} |tiny|0.2|0}}em 0<!-- trbl -->; font-size: {{#ifeq: {{{4|}}} |tiny|0.6|1.0}}em; {{#ifeq: {{{4|}}} |tiny|vertical-align: 0.32em;}}"><!--
--><span style{{=}}"vertical-align: -0.075em; font-style: italic; font-size: 1.4em; line-height: 0.715em; height: 0.715em; margin-top: -1.0em; padding-top: 0; margin-right: -0.15em;"><!--
-->{{#switch: {{{1|int}}}
   | iint = {{Unicode|∬}}
   | iiint = {{Unicode|∭}} 
   | iiiint = {{Unicode|⨌}} 
   | oint = {{Unicode|∮}}
   | varointclockwise = {{Unicode|∲}} 
   | ointctrclockwise = {{Unicode|∳}}
   | oiint = {{Unicode|∯}}
   | oiiint = {{Unicode|∰}}
   }}<!--
--></span><!--
  -->{{su
     | b = <span style{{=}}"vertical-align: -0.25em; font-size: 0.9em; margin-left: -0.1em;">{{{2|}}}</span>
     | p = <span style{{=}}"vertical-align: 0em; font-size: 0.9em; margin-left: 0.4em;">{{{3|}}}</span>
     }}<!--
--></span>
| int_italic | int_oblique 
| int = {{intmath/int/sandbox|{{{2|}}}|{{{3|}}}|{{{4|}}}}}<noinclude><!--

  *****
 
  This code, which shall be in Template:Intmath/int subtemplate (so we can call it to implement the idotsint option), is now in
  Template:Intmath/int/sandbox (obviously, with {{{2|}}}, {{{3|}}}, {{{4|}}} replaced by {{{1|}}}, {{{2|}}}, {{{3|}}})   

  *****

--><span style{{=}}"display: inline-block; position: relative; line-height: 0.715em; height: 0.715em; margin-top: -1.0em; padding: 0; font-size: {{#ifeq: {{{4|}}} |tiny|0.75|1.0}}em; {{#ifeq: {{{4|}}} |tiny|vertical-align: 0.3em;}}"><!--
--><span style{{=}}"display: inline-block; vertical-align: -0.11em; line-height: 0.715em; height: 0.715em; padding-top: 0; margin-right: -0.15em;"><!--
--><span style{{=}}"font-size: 1.4em; line-height: 0.715em; height: 0.715em; {{transform-rotate|18.5}} vertical-align: -0.13em; margin-top: -1.0em; padding-top: 0; margin-right: -0.25em;">{{Unicode|∫}}</span><!--
  -->{{su
     | b = <span style{{=}}"vertical-align: 0.0em; font-size: 0.9em; margin-left: 0.3em;">{{{2|}}}</span>
     | p = <span style{{=}}"vertical-align: 0.0em; font-size: 0.9em; margin-left: 0.9em;">{{{3|}}}</span>
     }}<!--
--></span></span>

</noinclude>
| idotsint = {{intmath/int/sandbox|||{{{4|}}}}}{{nbsp|2}}⋯<!-- ⋯ --> <!-- hair space --><!--
-->{{intmath/int/sandbox|{{{2|}}}|{{{3|}}}|{{{4|}}}}}  <!-- 2 hair spaces -->
| int_roman | int_normal 
| #default = <!--
--><span style{{=}}"display: inline-block; position: relative; font-size: {{#ifeq: {{{4|}}} |tiny|0.75|1.0}}em; {{#ifeq: {{{4|}}} |tiny|vertical-align: 0.3em;}} line-height: 0.715em; height: 0.715em; margin-top: -1.0em; padding: 0;"><!--
  --><span style{{=}}"vertical-align: -0.15em; font-style: italic; font-size: 1.35em; margin-right: -0.06em;">{{Unicode|∫}}</span><!--
  -->{{su
     | b = <span style{{=}}"vertical-align: -0.1em; font-size: 0.9em; margin-left: 0.1em;">{{{2|}}}</span>
     | p = <span style{{=}}"vertical-align: -0.5em; font-size: 0.9em; margin-left: 0.2em;">{{{3|}}}</span>
     }}<!--
--></span><!--
-->}}</includeonly><noinclude>
{{documentation}}
</noinclude>

Suggested code for {{intmath/int}} (now in {{intmath/int/sandbox}}):

<noinclude>Sandbox for italic int which shall be implemented in <code>{{tl|intmath/int}}</code> subtemplate so that it can be called from <code>{{tl|intmath}}</code> to implement the <code>idotsint</code> option, e.g.

<code>{{math| H {{=}} {{intmath/sandbox|idotsint|''n''-ball}} ''dH'' }}</code> yields the HTML text style {{math| H {{=}} {{intmath/sandbox|idotsint|''n''-ball}} ''dH'' }}

<code>{{bigmath| H {{=}} {{intmath/sandbox|idotsint|''n''-ball}} ''dH'' }}</code> yields the HTML display style  

:{{bigmath| H {{=}} {{intmath/sandbox|idotsint|''n''-ball}} ''dH'' }}
</noinclude><includeonly><!--

Italic int implemented as Template:Intmath/int subtemplate so that it can be called from Template:Intmath to implement idotsint.  

--><span style{{=}}"display: inline-block; position: relative; line-height: 0.715em; height: 0.715em; margin-top: -1.0em; padding: 0; font-size: {{#ifeq: {{{3|}}} |tiny|0.75|1.0}}em; {{#ifeq: {{{3|}}} |tiny|vertical-align: 0.35em;}}"><!--
--><span style{{=}}"display: inline-block; vertical-align: -0.11em; line-height: 0.715em; height: 0.715em; padding-top: 0; margin-right: -0.15em;"><!--
--><span style{{=}}"font-size: 1.4em; line-height: 0.715em; height: 0.715em; {{transform-rotate|18.5}} vertical-align: -0.13em; margin-top: -1.0em; padding-top: 0; margin-right: -0.25em;">{{Unicode|∫}}</span><!--
  -->{{su
     | b = <span style{{=}}"vertical-align: 0.0em; font-size: 0.9em; margin-left: 0.3em;">{{{1|}}}</span>
     | p = <span style{{=}}"vertical-align: 0.0em; font-size: 0.9em; margin-left: 0.9em;">{{{2|}}}</span>
     }}<!--
--></span></span></includeonly>
Tentacles mailto:Tentacles 22:23, 13 March 2016 (UTC)[reply]
I would suggest putting the code into Template:Intmath/sandbox and creating some testcases in Template:Intmath/testcases. If you do that we can then examine the results and compare it with current version. See Wikipedia:Template sandbox and test cases for instructions on how to format there. Once everyone is ok with the changes we can then make things go live.--Salix alba (talk): 20:40, 15 March 2016 (UTC)[reply]
I've created the above sandbox and testcases. On my browsers and fonts the, iint, iiint oint, oiint varients all look better. There are problems with the int versions as the sub and superscripts overlap the integral sign. It might need a bit more rightmargin space, or it could be rendered not in italic which also seems to cure the overlap problem.--Salix alba (talk): 20:19, 20 March 2016 (UTC)[reply]
The code is tweaked and/or optimized for use inside the {{math}} template. — Tentacles mailto:Tentacles 17:55, 21 March 2016 (UTC)[reply]
In Firefox 37.0.2 and IE 11 (Windows), the int version worked fine for me (the sub and superscripts did not overlap the integral sign). — TentaclesTalk or mailto:Tentacles 21:59, 21 March 2016 (UTC)[reply]
Also, it bugs me somehow that int is not italic while all the others are (it's not consistent). — TentaclesTalk or mailto:Tentacles 21:59, 21 March 2016 (UTC)[reply]
I rotated the int symbol with a CSS transform (does Wikipedia approve using CSS transforms?) but there is an issue of too much line height then. (Now, the default option gives a non-rotated int as a fallback.)TentaclesTalk or mailto:Tentacles 01:45, 22 March 2016 (UTC)[reply]
I can't yet get int_italic to work properly (using CSS transform: rotate or transform: skewX) on both browsers... any hint would be helpful! (Unless we can get int_italic to work properly, int will have to default to int_normal.)
  • Firefox 37.0.2 (Windows)
  • IE 11 (Windows)
TentaclesTalk or mailto:Tentacles 19:51, 22 March 2016 (UTC)[reply]
CSS transform: rotate or transform: skewX somehow work on IE 11 (it actually rotates and skews) but there seems to be an issue with transform-origin: because the integral symbol goes up by a huge amount. Any help from a CSS transform expert would be great! — TentaclesTalk or mailto:Tentacles 20:21, 22 March 2016 (UTC)[reply]
Whatever I try doesn't make any difference in IE 11!? How could that be? I keep purging the server cache to make sure. — TentaclesTalk or mailto:Tentacles 21:09, 22 March 2016 (UTC)[reply]
I resolved the issue. The sandbox code now appears to work well in Windows with Firefox 37.0 and IE 11. Do you have any objection with the code (is it OK that I use a CSS transform to rotate the integral symbol)? Do you consider the code ready to be made live? — TentaclesTalk or mailto:Tentacles 20:31, 24 March 2016 (UTC)[reply]
The italic int looks OK in Chrome/Firefox on my Macbook machine, there is still overlap on first upright testcase. A big thing which should be checked is mobile, as about a quarter of view are now from mobile.
For whats its worth the reported fonts are a combination of Helvatica and "Apple Symbols". I've a few nice maths fonts on my systems LatinModernMath-Regular, DejaVu Sans.--Salix alba (talk): 21:30, 24 March 2016 (UTC)[reply]
Do you consider the {{intmath/sandbox}} and {{intmath/int/sandbox}} code ready to be made live? I tested the code in Firefox 37.0.2 and IE 11 (both on Windows) and everything seems OK. If I get the approval I'll make it live. — TentaclesTalk or mailto:Tentacles 20:16, 30 March 2016 (UTC)[reply]
Look at {{intmath/testcases#Text style inline formulae}}: Line spacing in lorem ipsum text is undisturbed. (There is no more excess of space above.) I will make the code live. Any objections? — TentaclesTalk or mailto:Tentacles 23:44, 9 April 2016 (UTC)[reply]
Please don't. There is no consensus for this change. Also, I see nothing wrong with the current code, and there are issues with yours. For instance, the line-height might not be affected, but the oint symbols now overlaps the over- and underlying text instead. I also see double-italizised symbols due to the transform-rotate. I already tried explaining that micro-tweaking, while it may look good on your own system, will not work as intended on other systems due to inconsistencies in font metrics, so the generic code is the best solution for now. -- [[User:Edokter]] {{talk}} 07:57, 10 April 2016 (UTC)[reply]
OK, I won't. Is it the case that everything that could have been tried to improve the typesetting of HTML+CSS math has already been attempted? If that's the case, it means that we essentially have to live with lots of lame HTML+CSS typesetting and that attempts to improve things are quite futile and a waste of one's time. (The fact that there is not even a consensus to use the {{math}} and {{bigmath}} templates when typesetting math in HTML+CSS only makes the typesetting lamer.) I tested on Firefox 37.0 and IE 11 (both on Windows) and the Gauss's Law integral oiint symbol does not overlap the over- and underlying text and the line spacings are undisturbed. I also do not see double-italizised symbols. On which device and/or system and/or browser do you see the issues that you mention? — TentaclesTalk or mailto:Tentacles 18:24, 10 April 2016 (UTC)[reply]
Chrome 49 on Windows XP, but also Windows 7. The fact there is no consensus to use the math templates does not mean it is ignored. I devised {{math}} back in the days when TeX stil used HTML for simple formulae, and spent quite some time fine-tuning it to suit the widest array of devices. Your approach may look fine on your system, but does not account for any ohter platforms where ohter default fonts may display different; the {{unicode}} template does nothing outside XP, and different Windows versions have different built-in support for oint characters, using different substituted fonts alltogether. Sorry for all that work you put in. -- [[User:Edokter]] {{talk}} 19:30, 10 April 2016 (UTC)[reply]
I just checked on Chrome 49 (Windows 7) and the the lorem ipsum test in {{intmath/testcases#Text style inline formulae}} has no overlap and no line spacing disturbance. The only case of overlap I see is when the {{math}} template is not used for the Maxwell's equations in the No {{math}} section. When using the {{math}} template, the issue does not appear. I know that there are lots of other platforms... Now, I'm at a loss on how I could try to improve the HTML+CSS math typesetting, since CSS fine-tuning is not an option... — TentaclesTalk or mailto:Tentacles 23:44, 10 April 2016 (UTC)[reply]

∫ doesn't render in the same font and vertical alignment as the other integral symbols

[edit]

∫ doesn't render in the same font as the other integral symbols, although on (Mathematical Operators – Unicode)[1], they all render in the same really nice font. Furthermore, the font in which ∫ renders doesn't have the same vertical alignment as the font in which other integral symbols render.

Integral symbols shown in HTML+CSS (font-size: 2em) using the {{math}} template
int iint iiint oint varointclockwise ointctrclockwise oiint oiiint

NB:

  • Applying font-style: italic; or font-style: oblique; to the int integral symbol (which currently renders in a different font, which also have a higher vertical alignment) has no effect in Firefox (it remains upright), while it italicizes all the other integral symbols. E.g.
    <span style="font-style: normal;">∫ ∬ ∭ ∮ ∲ ∳ ∯ ∰</span> yields ∫ ∬ ∭ ∮ ∲ ∳ ∯ ∰;
    <span style="font-style: italic;">∫ ∬ ∭ ∮ ∲ ∳ ∯ ∰</span> yields ∫ ∬ ∭ ∮ ∲ ∳ ∯ ∰;
    <span style="font-style: oblique;">∫ ∬ ∭ ∮ ∲ ∳ ∯ ∰</span> yields ∫ ∬ ∭ ∮ ∲ ∳ ∯ ∰.

Tentacles mailto:Tentacles 22:48, 13 March 2016 (UTC)[reply]

The integral symbols used are highly dependent on the fonts installed on your computer. Since int is quite common, but the others aren't, they may differ in rendering. Not much we can do about it, as forcing a specific font (or CSS metrics) may cause failure on other systems. -- [[User:Edokter]] {{talk}} 10:10, 14 March 2016 (UTC)[reply]
In IE, except for int, all the integrals seem to render in the beautiful font 'Lucida Sans Unicode', but in Firefox we get this ugly font (it is passable for text style, but would be really ugly in display style)! In which [ugly] font do the integral symbols, other than int, render? Also, in which font does int render? Finally, which font can we assume to be installed on the typical user's computer? — Tentacles mailto:Tentacles 18:01, 21 March 2016 (UTC)[reply]
You can't asume any font being installed, especially when it comes to unicode. Modern browsers like Firefox, but also Windows 7 and beyond, decide by themselves which font to use when a glyph is not part of the default font. Forcing a font may negate that functionality and actually break the display of non-common characters. That is the reason why the {{unicode}} template has been disabled recently. -- [[User:Edokter]] {{talk}} 18:39, 21 March 2016 (UTC)[reply]

Notes

[edit]

References

  1. ^ "Mathematical Operators – Unicode" (PDF). Retrieved 2013-04-26.

Beautiful integral symbols in font-family: 'Lucida Sans Unicode';

[edit]

Look at how beautiful the integral symbols are in font-family: 'Lucida Sans Unicode';!

Integral symbols with font-family: 'Lucida Sans Unicode'; rendered using the {{math}} template.
[for text style (above), and for display style (below)]
int iint iiint oint varointclockwise ointctrclockwise oiint oiiint

The [suggested] code

: before {{math|Γ(''z'') {{=}} <!--
--><span style{{=}}"position: relative; vertical-align: -0.1em; font-size: 0.75em;"><!--
  --><span style{{=}}"vertical-align: 0.0em; font-family: 'Lucida Sans Unicode'; font-style: italic; font-size: 1.6em; margin-right: -0.05em;">∫</span><!--
  -->{{su
     | b = <span style{{=}}"vertical-align: 0.0em; font-size: 1.25em; margin-left: -0.125em;">0</span>
     | p = <span style{{=}}"vertical-align: 0.0em; font-size: 1.25em; margin-left: 0.375em;">∞</span>
     }}<!--
--></span><!--
--> ''e''<sup>−''t''</sup> ''t''  <sup>''z'' − 1</sup> ''dt''<!--
-->}} after

yields the text style HTML+CSS

before Γ(z) =
0
ett  z − 1dt
after

The code

: before <math>\textstyle \Gamma(z) = \int_{0}^{\infty} e^{-t} t^{z-1} dt</math> after

yields the text style LaTeX

before after

The [suggested] code

: before {{math|<!--
--><span style{{=}}"position: relative; vertical-align: -0.1em; font-size: 0.75em;"><!--
  --><span style{{=}}"vertical-align: 0.0em; font-family: 'Lucida Sans Unicode'; font-style: italic; font-size: 1.6em; margin-right: -0.05em;">∲</span><!--
  -->{{su
     | b = <span style{{=}}"vertical-align: 0.0em; font-size: 1.25em; margin-left: -0.125em;">''C''</span>
     | p = <span style{{=}}"vertical-align: 0.0em; font-size: 1.25em; margin-left: 0.375em;">(cw)</span>
     }}<!--
--></span><!--
-->  ''F''('''x''') ∙ ''d'''''x'''  {{=}} (...) <!--
-->}} after

yields the text style HTML+CSS

before (cw)
C
F(x) ∙ dx = (...)
after

The code (using \oint instead of the unsupported \varointclockwise)

: before <!-- \varointclockwise not supported --><math>\textstyle \oint_{C}^{\rm (cw)} F(\boldsymbol{\rm x}) \sdot d\boldsymbol{\rm x} = (\ldots)</math> after

yields the text style LaTeX (using \oint instead of the unsupported \varointclockwise)

before after

It's too bad we can't rely on font-family: 'Lucida Sans Unicode'; being installed on a user's computer... — Tentacles mailto:Tentacles 20:18, 15 March 2016 (UTC)[reply]

I wonder whether or not I did the right thing: I created this page (Template_talk:Intmath/doc) but I wonder whether I should have created Template_talk:Intmath instead. What is the rule/convention? Should we move this page to Template_talk:Intmath or is it OK as it is? — Tentacles mailto:Tentacles 16:41, 21 March 2016 (UTC)[reply]

Yes its more standard to have it as Template_talk:Intmath. I've now moved the page there with a redirect so people should be able to find the discussion. --Salix alba (talk): 17:17, 21 March 2016 (UTC)[reply]