LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

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

Print Reply
Will Robertson <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Thu, 10 Jan 2019 09:43:35 +0800
text/plain (37 lines)
Hi Kelly

Good question! 

There is one and only one (I think) direct advantage from using the text commands instead of the symbols, which is that you can use alternate encodings (see fontspec manual) to check that the symbol exists and/or replace it with something else. 

It’s also pretty safe for Unicode symbols to make them active and add some extra logic to them if you like. 

(Sent from phone; please excuse brevity.) 

> On 10 Jan 2019, at 5:03 am, Kelly Smith <[log in to unmask]> wrote:
> Hello,
> 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.
> Warmly,
> Kelly