<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">%! TEX program = lualatex
\ProvidesFile{unicode-math-input.tex} [2024/01/25 v0.1.1 ]
\PassOptionsToPackage{hyphens}{url}
\RequirePackage{fvextra}
\documentclass{l3doc}
\usepackage[svgnames]{xcolor}
\EnableCrossrefs
\CodelineIndex
\fvset{breaklines=true,gobble=0,tabsize=4,frame=single,numbers=left,numbersep=3pt}
\AtBeginDocument{\DeleteShortVerb\"}
\MakeOuterQuote{"}
\usepackage{cleveref}
\usepackage{fontspec}
\setmonofont{DejaVu Sans Mono}[Scale=0.8]
\usepackage[bold-style=ISO]{unicode-math}
\tracinglostchars=3
\newcommand\csref[1]{\texttt{\hyperref[doc/function//#1]{\textbackslash #1}}}
\newcommand\varref[1]{\texttt{\hyperref[doc/function//#1]{#1}}}
\usepackage{precattl}
\begin{document}
\precattlExec{
\NewDocumentEnvironment{option}{v}{\begin{variable}{#1\cO\}\iffalse}\fi Package option.\par}{\end{variable}}
}

\hfuzz=1pt
\GetFileInfo{\jobname.tex}

\title{\pkg{unicode-math-input} --- Allow entering Unicode symbols in math formulas\thanks{This file
	describes version \fileversion, last revised \filedate.}
}
\author{user202729%
%\thanks{E-mail: (not set)}
}
\date{Released \filedate}

\maketitle

\begin{abstract}
Allow entering Unicode symbols in math formulas.
\end{abstract}

\section{Introduction}

This package allows entering Unicode symbols in math formulas.

\subsection{Existing packages}

There are several existing packages, but other than |unicode-math| (which also changes the output encoding)
they does not cover a lot of characters and/or does not handle several issues well.

We compare the situation with several existing packages:

\begin{itemize}
	\item \pkg{commonunicode}:
		\begin{itemize}
			\item defines all characters to be active, which means it breaks usage of |Î±| in \pkg{fancyvrb}'s |Verbatim| environment for example.
			\item changes the behavior of e.g. |Â½| in text mode in PDF\LaTeX.
			\item does not always select best option, for example |âˆ„| always get mapped to |\not\exists| even though the outcome is worse than |\nexists|.
			\item fakes several symbols such as |â‰| even when there's better option e.g. |\eqdef|,
			\item uses |\ensuremath| extensively, which means no error message when it's used in text mode,
			\item not as good symbol coverage.
		\end{itemize}
	\item \pkg{unixode}:
		\begin{itemize}
			\item defines |â€²| to be |\prime| which is big and not usable, it should be |^{\prime}|
				similar to |'|'s definition.
			\item defines |â€“| (en dash) to be nothing, which breaks the character even in text mode.
			\item does not define |Ã—| or |Â±| (they're already valid in text mode in \LaTeX, but will be
				silently omitted in math mode)
			\item does not handle consecutive superscript/subscript characters.
			\item you need to manually patch the source code a bit in order to make it work with PDF\LaTeX. And even after that it will raise lots of warnings about redefining Unicode characters.
		\end{itemize}
	\item \pkg{utf8x}:
		\begin{itemize}
			\item incompatible with lots of packages.
			\item does not define $\bigoplus$ (|\bigoplus|)
			\item also does not handle consecutive superscript/subscript characters.
		\end{itemize}
\end{itemize}

See also \url{https://tex.stackexchange.com/a/628285}.

\subsection{Features}

\LaTeX's implementation of input encoding and font encoding is \emph{very} complicated, necessitated by the fact that non-Unicode \TeX\ engines handles each UTF-8 character as multiple tokens and enc\TeX\ extension is not enabled in \LaTeX.%
\footnote{Refer to \url{https://tex.stackexchange.com/a/266282/250119} for a way to force-enable enc\TeX\ extension in
\LaTeX\ if you're interested.}

There's a few other issues that we don't really need to deal with, because they are in the next layer:

\begin{itemize}
	\item \href{https://tex.stackexchange.com/q/31640/250119}{What is the use of the command \texttt{\textbackslash IeC}?}
	\item \url{https://tex.stackexchange.com/a/239575/250119}

\end{itemize}

We don't need to deal with |\IeC| as since \TeX\ Live 2019, the mechanism is no longer used and the Unicode character itself
is written to auxiliary files.
%\immediate\openout 5=a.tex
%\makeatletter
%\let \protect \@unexpandable@protect
%\immediate\write 5{a Ã¡ b}

We need to get the following things correct:

\begin{itemize}
	\item |\leftâŸ¨|

		In Lua\LaTeX\ in order to implement this we need to hard code the |\Udelcode| of the character,
		so if |\langle| is redefined, the change will not follow.

		An alternative is to overwrite the definition of |\left| built-in, but this is not used.

	\item |\bigâŸ¨| (in \pkg{amsmath} package or outside)

		In PDF\LaTeX\ there's an issue of argument-grabbing (|\big| etc. is a macro so they will
		only grab the first octet of the |âŸ¨| character), so the macro must be patched.

		Furthermore, the patching is done |\AtBeginDocument| in case |amsmath| etc. is loaded after this package.
		
		We handle |\big \Big \bigg \Bigg| and the |\bigl|, |\bigr| variants etc.

		Pass the option \varref{ignore-patch-delimiter-commands} to disable the behavior in case of package clash.

	\item in \pkg{unicode-math}, |a`| renders as |a^{\backprime}| i.e. $a^{\backprime}$.
		We will not modify the default behavior i.e. $a\text{`}$ in this package.

	\item |\section{$1 Ã— 2$}| (for writing to auxiliary file in table of contents) -- as mentioned above,
		since \TeX\ Live 2019 this is correct by default.
	\item Some characters such as |Ã—| or |Â½| in PDF\LaTeX\ are already
		usable outside math mode, we try to not break the compatibility.
	\item The symbol should work correctly when appear at the start of an alignment entry,
		e.g., the start of an |align*| cell.
	\item |$2Â³â´$| (consecutive Unicode characters for superscript/subscript, refer to \url{https://tex.stackexchange.com/q/344160/250119}.) Also need to handle |'| similarly.

	\item This packages does modify the default definition of |'| to allow |G'Â²| to work however.
		Pass the option \varref{ignore-patch-prime} to disable the behavior in case of package clash.

	\item The original implementation of |'| is somewhat interesting that it allows sequences such as |G'^\bgroup 123\egroup| to work,
		we will not emulate it here.

	\item Also need to handle Unicode prime symbols |â€²|, |â€³| etc.

	\item To minimize errors, we make |â‰¢| default to |\nequiv|, but fallback to |\not\equiv|
		if the former is not available.

		We should also take care of aliases -- for example, |â‰°| should check |\nle| and |\nleq| before fallback to |\not\le| or |\not\leq|.

		Note that by default (or with \pkg{amsmath} or \pkg{amssymb}),
		|\not| does not smartly check the following symbol,
		however with some packages such as \pkg{unicode-math},
		\pkg{txfonts} the |\not| does do that -- in particular, it checks for the presence of control sequences named
		|\notXXX| and |\nXXX| where |XXX| stands for the original control sequence/character.

		It would be beneficial for \pkg{amssymb}
		to make |\not| smart, as for example |\not\exists| looks worse than |\nexists|,
		however the package does not touch |\not|.

	\item Similarly, |''| default to |^{\dprime}| if available, else fallback to |^{\prime\prime}|.

	\item Whenever possible, we do not make the symbols have active catcode, only change the mathcode,
		that way usage of the symbols in places such as |fancyvrb| environment is minimally affected. (see test files for an example)
	\item We try to make minimum assumptions about the internal implementation details of \LaTeX\ packages; nevertheless this is not always possible.

	\item Combining modifiers (such as |U+00305 COMBINING OVERLINE| in |aÌ…|, which corresponds to |\overbar|) are difficult to support
		(although with whole-file scanning + \pkg{rescansync} or Lua\TeX's |process_input_buffer| callback
		it's not impossible; an alternative is to use Lua\TeX\ callback to modify the math list
		after it's constructed, see \url{https://github.com/wspr/unicode-math/issues/555#issuecomment-1045207378}
		for an example),
		plus |unicode-math| does not support them anyway,
		so they will not be supported.

		They're difficult to support because normally the modifier appear after the character that it modifies
		but \TeX\ requires the command (e.g. |\overbar|) to appear \emph{before} the character that it modifies.

		As a special case, the 4 commands |\enclosecircle| |\enclosesquare| |\enclosediamond| and |\enclosetriangle|
		are supported (simply because the \TeX\ command can appear after the character it modifies)

	\item The fraction slash |U+2044 FRACTION SLASH|, as in |1|â„|2| rendering $\frac{1}{2}$, is also not implemented
		because of similar difficulty as above.
	\item Symbols such as |âˆš| or |âˆ›| will be equivalent to |\sqrt| command (taking an argument to draw a square root)
		instead of |\surd| (the symbol itself), unlike \pkg{unicode-math}.

		While sequences such as |âµâˆš{67}| may feasibly be supported without breaking too many things,
		implementation is difficult and we don't see much use for it.
	\item Similarly, one might expect that $âŸ$ |U+23DF BOTTOM CURLY BRACKET| get mapped to |\underbrace|,
		but the behavior of such command would be a bit unexpected (you need to
		write $âŸ$|{123}_{456}| to get $\smash{\underbrace{123}_{456}}$), so this will not be the default.

	\item the Unicode character is mapped indirectly to the control sequence,
		so that when the user/some package redefines a control sequence such as |\pi|, the
		corresponding Unicode character (|Ï€|) will also change. This will incur a small loss in efficiency however.

		(modulo the issue with |\Udelcode| mentioned above)

	\item The character |â‹¯| is mapped to |\cdots| and |â€¦| is mapped to |\ldots|. Note that |\dots| behaves
		the same as |\ldots| without \pkg{amsmath} package loaded, but with it it smartly detect which variant to use
		depends on the following character, for example |$\dots +$| prints $\dots +$ but |$\dots ,$| prints $\dots ,$.

		There's another discrepancy with the spacing around these 2 characters,
		see \url{https://github.com/wspr/unicode-math/issues/571}.
\end{itemize}

There are some issues however:
\begin{itemize}
	\item \textsf{\rlap{0}\kern 1.2pt\relax 0} |U+1D7D8 MATHEMATICAL DOUBLE-STRUCK DIGIT ZERO|
gets translated to |\mathbb{0}|, but this is incorrect by default
unless the blackboard bold font happens to have such a character.

(nevertheless, it's difficult to change math font in the middle of the document anyway.
Refer to \url{https://tex.stackexchange.com/q/30049/250119}.)

\item In the \pkg{unicode-math} source code there's this remark:

	\begin{quote}
	The catcode setting is to work around (strange?) behaviour in Lua\TeX\ in
which catcode 11 characters don't have italic correction for maths. We don't adjust
ascii chars, however, because certain punctuation should not have their catcodes
changed.
\end{quote}

This feature is currently unimplemented.

\item At the moment, following a Unicode superscript character, double superscript will not be defined --
	that is, |GÂ²^3^4| will just display as |G^{234}| --
	while this is fixable, we don't see much point in detecting this error.
\end{itemize}

\section{Usage}

Simply include the package.

\begin{verbatim}
\usepackage{unicode-math-input}
\end{verbatim}

Because by default the \pkg{unicode-math} package will already allow entering Unicode symbols in math formulas, this package will raise an error if \pkg{unicode-math} is already loaded.

\section{Advanced commands and options}

\begin{function}{
		\umiMathbf,\umiMathit,\umiMathbfit,\umiMathscr,\umiMathbfscr,\umiMathfrak,\umiMathbb,\umiMathbbit,\umiMathbffrak,\umiMathsf,\umiMathsfbf,\umiMathsfit,\umiMathsfbfit,\umiMathtt
	}
	\begin{syntax}
		|\umiMathbf {...}|
		|\umiMathit {...}|
	\end{syntax}
	These functions are not to be used directly. But you can redefine them to customized behavior of bold/italic/etc. Unicode characters.

	For example you can |\renewcommand\umiMathbf[1]{\mathbf{#1}}| which is the default behavior.

	Or you can execute, for example, |\renewcommand\umiMathscr[1]{\mathcal{#1}}| to use the calligraphic instead of the script alphabet for script characters.

	More usefully, you may want to |\renewcommand\umiMathbf{\bm}| to make entered characters such as
	$ðš$ appear bold italic in the output, remember to load package \pkg{bm} if you want to do so (which is |unicode-math| behavior
	with |[bold-style=ISO]| package option).
\end{function}

\begin{function}{\umiFrac}
	\begin{syntax}
		|\umiFrac {1} {2}|
	\end{syntax}
	Not to be used directly, but you can redefine it such as 
	|\let\umiFrac\tfrac| (or more clearly, |\renewcommand\umiFrac[2]{\tfrac{#1}{#2}}|)
	to customize the appearance of Unicode characters like |Â½|.

	If you want to customize the appearance of individual symbols, consider using \csref{umiDeclareMathChar}.
\end{function}

\begin{function}{\umiDeclareMathChar}
	\begin{syntax}
		|\umiDeclareMathChar {Î±} {\alpha}|
	\end{syntax}
	Does what it says. Will override existing definitions, if any.

	Note that the Unicode character must be braced.

	(You may choose to call \csref{umiPatchCmdUnicodeArg}| \umiDeclareMathChar|
	beforehand so bracing is not necessary, but this is not really recommended)

	This might or might not destroy the existing text-mode definition. For now,
	one way to preserve it is |\umiDeclareMathChar {Â²} {\TextOrMath{\texttwosuperior}{^2}}|.
\end{function}

\begin{function}{\umiDeclareMathDelimiter}
	\begin{syntax}
		|\umiDeclareMathDelimiter {âŸ¨} \langle|
	\end{syntax}
	You must use this in order to use the Unicode character with |\left|, |\big|, |\bigl| etc.
	(because of the internal detail being that in Xe\LaTeX\ and Lua\LaTeX,
	as this package does not change the character catcode to be active,
	it's necessary to set the |delcode| as mentioned before)

	In that case the second argument must be a single token.

	Unfortunately, the command does not always work -- it must detect the second argument to be a delimiter, but
	if the detection fails it may not work.
\end{function}

\emph{Note}: There's no need to provide |\umiDeclareMathAlphabet|, |\umiDeclareMathAccent| or |\umiDeclareMathRadical|, for |\umiDeclareMathChar| suffices.
It's not supported to define \emph{control sequences}, for that the typical |\RenewDocumentCommand|
or |\RenewCommandCopy| suffices.

\begin{function}{\umiRefreshDelimiterList}
	\begin{syntax}
	    |\umiRefreshDelimiterList|
	\end{syntax}
	You should normally not need this command.

	As mentioned before, in Lua\LaTeX\ once a command is redefined, the Unicode character does not automatically update.

	This command will check all the normal delimiter Unicode characters. In PDF\LaTeX\ this command does nothing.

	Another way is to use \csref{umiDeclareMathDelimiter} to manually refresh individual Unicode characters,
	this is also useful if you define an Unicode character that is not "normally" a delimiter.
\end{function}

\begin{option}{ignore-refresh-delimiter-list}
	\csref{umiRefreshDelimiterList} will be run |\AtBeginDocument|. Pass this to disable it running.

	Only needed if there's some package clash or if there's spurious warning on "not determined to be a delimiter" etc.
\end{option}

\begin{function}{\umiPatchCmdUnicodeArg,\umiUnpatchCmdUnicodeArg}
	\begin{syntax}
		|\umiPatchCmdUnicodeArg \sqrt|
		|\umiUnpatchCmdUnicodeArg \sqrt|
	\end{syntax}
	After executing this command, the command specified in the argument (|\sqrt| in this example)
	can be called with one argument being an Unicode character without needing a brace.

	(i.e. you can write |\sqrt Î±| instead of |\sqrt{Î±}|.)

	Because of implementation detail,
	\begin{itemize}
		\item |\sqrtÎ±| (without the space between |\sqrt| and |Î±|) works in PDF\LaTeX\ but not Lua\LaTeX. (so this form is not recommended.)
		\item |\sqrt Î±| works in Lua\LaTeX\ without needing the patch. In other words, the patch does nothing in Unicode engines.
	\end{itemize}

	The command being patched must take at least one mandatory argument as the first argument, and it only affect that first argument.
	In other words, |\sqrt[3]Î±| cannot be patched this way unless you do e.g. |\newcommand\cbrt[1]{\sqrt[3]{#1}}| then |\umiPatchCmdUnicodeArg\cbrt|,
	then |\cbrt Î±| works (but |\sqrt[3]Î±| still doesn't).
\end{function}

\begin{function}{\umiPatchCmdUnicodeTwoArgs}
	\begin{syntax}
		|\umiPatchCmdUnicodeTwoArgs \frac|
		|\umiUnpatchCmdUnicodeArg \frac|
	\end{syntax}
	Similar to above, but for commands with (at least) two mandatory arguments.

	Only affects these 2 mandatory arguments.
\end{function}

\begin{function}{\umiPatchCmdUnicodeArgExtraGroup}
	\begin{syntax}
		|\umiPatchCmdUnicodeArgExtraGroup \Big|
	\end{syntax}
	Don't use this command unless you know exactly what you're doing.

	Similar to |\umiPatchCmdUnicodeArg|, but open an implicit group before executing anything and close the group after.

	The command being patched must take exactly one argument.

	This is useful because some \TeX\ primitives such as |^| or |\mathopen|
	requires either a single "character" or a group braced with |{...}| / |\bgroup...\egroup| --
	in particular, |\Big|'s original definition is such that |\Bigl| being defined
	as |\mathopen \Big| can work, and we must ensure it still work after the patch.
\end{function}

\begin{option}{ignore-patch-delimiter-commands}
	Pass this to avoid patching |\Big| etc. with the command above (only needed if there's some package clash).
\end{option}

\begin{function}{\umiBraceNext}
	\begin{syntax}
		|\umiBraceNext {abc...} Î±xyz...|
	\end{syntax}
	In the example above, after some steps of execution of \TeX, the state will be
	|abc... {Î±}xyz...|.

	Formally: if the character following the first argument to |\umiBraceNext| is not representable in a single byte
	and the engine is not Unicode, the character will be braced, otherwise nothing happens. Then the argument
	is put back in the input stream.

	This is an internal command mainly useful for defining the command above, for example after
\begin{verbatim}
\let\oldbig\big
\def\big{\umiBraceNext{\oldbig}}
\end{verbatim}
then |\bigâŸ¨| will eventually execute |\oldbig{âŸ¨}| which is the desired behavior (that |\oldbig| expects one braced argument).
\end{function}

\begin{option}{ignore-patch-prime}
	Do not patch the default definition of |'| in math mode.

	By default it's patched to allow |G'Â²| and |GÂ²'| to work. Only use this when there's some package clash.
\end{option}

\begin{function}{\umiPatchPrime,\umiUnpatchPrime}
	\begin{syntax}
		|\umiPatchPrime|
		|\umiUnpatchPrime|
	\end{syntax}
	As mentioned above, by default |\umiPatchPrime| is run |\AtBeginDocument|. But it can be patched
	and unpatched manually.

	Note that it's undefined behavior if some package modifies the definition of active |'|
	while it's patched. To resolve conflict, unpatch |'|, load the package, then patch again.
\end{function}

\section{Compatibility}

This package should have tested with various \TeX\ distribution versions on Overleaf.

\section{Advanced remarks}

As mentioned before, by design this package defines the Unicode character in math mode to do whatever the corresponding
\LaTeX\ command does \emph{at the time of use}, so if you redefine the meaning of |\alpha|, then the Unicode character |Î±|
will change as well.

The other "standard" way to define commands in \LaTeX\ is to assign the mathcode to the character/control sequence directly,
using |\DeclareMathSymbol| etc. which is used to define almost all the standard control sequences.
For efficiency reasons or other reasons, you may want to \emph{copy} the definition of an existing control sequence
(this way the definition of the Unicode character is not changed when the control sequence changes),
you can do that by:

\begin{function}{\umiDeclareMathCharCopy}
	\begin{syntax}
		|\umiDeclareMathCharCopy {Â±} \pm|
	\end{syntax}
	Does what it says.

	The second argument must be a single control sequence.
\end{function}

\begin{function}{\umiDeclareMathDelimiterCopy}
	\begin{syntax}
		|\umiDeclareMathDelimiterCopy {â€–} \Vert|
	\end{syntax}
	Does what it says. Refer to \csref{umiDeclareMathDelimiter} for difference between this command and \csref{umiDeclareMathCharCopy}.
\end{function}

In case you want to explicitly specify a font/slot pair for an Unicode character, you can use |\DeclareMathSymbol| etc.
directly, then use one of the commands above to copy it to the Unicode character.

Useful resources:

\begin{sloppypar}
	\hbadness=10000
\begin{itemize}
	\item \url{https://tex.stackexchange.com/questions/98781/create-a-font-table-for-all-available-characters-for-a-particular-font}
	\item \url{https://tex.stackexchange.com/questions/380775/font-table-for-opentype-truetype-fonts}
	\item \url{https://ctan.org/pkg/fonttable} (need double quotes if font name has spaces: \url{https://tex.stackexchange.com/a/506246/250119})
	\item Although there's always |texdoc encguide| for the default (non-Unicode) encodings.
\end{itemize}
\end{sloppypar}


\PrintChanges
\PrintIndex
\Finale

\end{document}
</pre></body></html>