Skip to content

Commit

Permalink
forgot to add \DeclareUnicodeCommand and Symbol
Browse files Browse the repository at this point in the history
  • Loading branch information
FrankMittelbach committed Dec 12, 2021
1 parent c96328f commit 5151f07
Show file tree
Hide file tree
Showing 3 changed files with 165 additions and 153 deletions.
3 changes: 2 additions & 1 deletion base/changes.txt
Expand Up @@ -10,7 +10,8 @@ are not part of the distribution.

* ltoutenc.dtx (subsection{Definitions for the TU encoding}):
\DeclareUnicodeAccent now makes the encoding argument implicit
as it is already done for other Unicode encoding commands (gh/253)
as it is already done for other Unicode encoding commands.
Also added \DeclareUnicodeCommand and \DeclareUnicodeSymbol (gh/253).

2021-12-11 Frank Mittelbach <Frank.Mittelbach@latex-project.org>

Expand Down
7 changes: 6 additions & 1 deletion base/doc/ltnews35.tex
Expand Up @@ -267,7 +267,7 @@ \subsection{Croatian character support}
\subsection{Cleanup of the Unicode declaration interface}

When declaring encoding specific commands for the Unicode (TU)
encoding most declarations (e.g., \cs{DeclareUnicodeSymbol}) do not
encoding some declarations (e.g., \cs{DeclareUnicodeComposite}) do not
have an explicit argument for the the encoding name, but instead use
the command \cs{UnicodeEncodingName} internally. There was one
exception though: \cs{DeclareUnicodeAccent} required an explicit
Expand All @@ -277,6 +277,11 @@ \subsection{Cleanup of the Unicode declaration interface}
arguments if the second argument is \texttt{TU} or
\cs{UnicodeEncodingName}. Once all packages have been updated this
code branch will get removed.

At the same time we added \cs{DeclareUnicodeCommand} and
\cs{DeclareUnicodeSymbol} for consistency. They also use
\cs{UnincodeEncodingName} internally, instead of requiring an encoding
argument as their general purpose counterparts do.
%
\githubissue{253}

Expand Down

0 comments on commit 5151f07

Please sign in to comment.