LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 9 Jan 2019 14:03:45 -0700
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
MIME-Version: 1.0
Message-ID: <[log in to unmask]>
Content-Transfer-Encoding: quoted-printable
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
From: Kelly Smith <[log in to unmask]>
Parts/Attachments: text/plain (23 lines)

I know that text commands (as defined by \DeclareTextCommand) have
been important because of the various font encodings that arose over
LaTeX’s history, but it seems that the situation is quite different
for the XeTeX and LuaTeX engines.

Given that both XeLaTeX and LuaLaTeX accept UTF-8 input and use only
the TU font encoding, is it acceptable to forgo \DeclareTextCommand
for most—if not all—cases?

For example, ® can simply be included directly in the document source,
so \textcopyright is not much more than an ASCII alias.

As for less common symbols, one could simply wrap the text in a
document command.

Excuse my naîveté, as there are probably important advantages to the
text command approach that I’ve completely overlooked.