It’s common to use ℰ (U+2130, or \mathcal{E}
) as the symbol for EMF. There are a number of variations of Δ, but in unicode-math
, stix
or stix2
, the upright math operator is \increment
. In ISO style, both Φ and N are variables rather than constants, and so should be slanted. (Under the default settings, though, capital Greek letters appear upright.)
Here’s how I’d do that in the modern toolchain:
\documentclass[varwidth]{standalone}
\usepackage{mathtools}
\usepackage[math-style=ISO]{unicode-math}
\newcommand\Emf{\mathcal{E}}
\begin{document}
\[ \Emf = -N \frac{\increment \Phi}{\increment t} \]
\end{document}
If you want to replace the symbol ℰ with the word Emf or EMF, replace the definition of \Emf
with
\newcommand\Emf{\operatorname{Emf}}
This is spaced like the operator log or sin if you try to write something like 2 Emf t. (Eta: egreg correctly brings up that this breaks \Emf \cdot t
, so you would need to insert a \!
in front of a binary operator.)
If you want something visually distinct from either an operator or the product of variables named e, m and f, you might go with small caps:
\mathop{\text{\normalfont\scshape\selectfont emf}}
This departs from ISO style, in which variables are always slanted, unless you select slanted small caps, such as:
\documentclass[varwidth]{standalone}
\usepackage{mathtools}
\usepackage[math-style=ISO]{unicode-math}
\defaultfontfeatures{Scale = MatchLowercase}
\setmainfont{Libertinus Serif}[Scale = 1.0]
\setmathfont{Libertinus Math}
\newcommand\Emf{\mathop{\text{\normalfont\scshape\itshape\selectfont emf}}}
\begin{document}
\[ \Emf = -N \frac{\increment \Phi}{\increment t} \]
\end{document}
If you prefer your capital Greek letters upright, remove the [math-style=ISO]
option from \usepackage{unicode-math}
.
If you’d rather have a slanted Δ, write \mathit{\Delta}
.
If you have to (or prefer to) use PDFLaTeX instead of LuaLaTeX or XeLaTeX, load your font package of choice. Many math font packages have a slantedgreek
option. If you aren’t using stix
or stix2
, you might replace \increment
with either \Delta
or \triangle
.
Best Answer
I think what Harish was intending to suggest in his comment is that you can use single dollar-sign delimited strings to shift into math mode and insert a formula.
So if you wanted to typeset "The expected rate of events is λ." you would write
Were you to instead use
\[ … \]
or$$ … $$
to delimit your text, it would put the formula on the next line because this defines a displayed equation, which is placed on its own line, and (usually) centered.See below (On
\[ … \]
vs.$$ … $$
) for a further explanation of why you would choose between\[ … \]
and$$ … $$
.The quick heuristic would be:
\[ … \]
$$ … $$
.So were you to typeset the previous example as:
that would be rendered as:
Note that the period is also placed after a new line because of the way that equation environments work.
--Edit--
As pointed out by Ethan in the comments, often if you are going to use this notation, it is more common to type:
This makes explicit in the plaintext representation of your maths that you intend it to be on its own line.
See the attached image for a rendered example of what I mean.
On
\[ … \]
vs.$$ … $$
Though using double dollar signs (
$$
) to delimit displayed math mode in LaTeX is discouraged — see Why is\[ … \]
preferable to$$
? — this is not always feasible if you want your LaTeX to be rendered appropriately by MathJax based LaTeX interpreters that are common on web based text editors that provide maths typesetting support.For example, the Jupyter notebook is designed to display both code and markup stored in JSON format, where mathematical content is LaTeX formatted plaintext that is interpreted via MathJax. However, if you use
\[ … \]
instead of$$ … $$
your LaTeX will refuse to render correctly because of the way that JSON requires escaping slashes (\
). You can instead use\\[ … \\]
but then this can cause other issues with interpreting LaTeX inside the delimiters forcing you to use nonvalid LaTeX to be able to write (for example) subscripts by escaping underscores. In this case and with other JSON based storage solutions for encoding plaintext,$$ … $$
is preferable in order to avoid these issues around\
and escaping.Note: the Cross Validated StackExchange website explicitly encourages the use of
$$ … $$
. Or – more accurately – it encourages using: