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
Lars Hellström <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Tue, 1 Sep 2009 17:40:26 +0200
text/plain (29 lines)
Will Robertson skrev:
> I'm going to be a bit quiet over the next little while, but after that I 
> may try to put together a "template-alt-alt" along these lines to see 
> how things turn out.

Then I might dig up another idea I had concerning classical template, 
namely to use braces in the names of control sequences implementing 
instances (and other things). Concretely, that could mean we roughly 
(e.g. forgetting about collections for the moment) have the definition

   \cs_set_nopar:Npn \UseInstance #1#2 {
      \use:c{ UseInstance { #1 } { #2 } }

The idea here is that if TeX emits some error message about the macro 
in question, then it will refer to (say) \UseInstance{hj}{flushleft}, 
which tells the casual user where something is going wrong (with the 
flushleft instance of template type hj), even though he may not 
understand how TeX intended the error message to be parsed.

LaTeX2e has something similar going on with font names. TeX's overfull 
hbox messages contain strings like \OT1/cmr/m/it/10 which (if you know 
a bit of NFSS) are fairly easy to interpret as "here we switch to 
medium italic 10pt of OT1-encoded Computer Modern Roman" -- it is not 
so obvious (or relevant) that \OT1/cmr/m/it/10 is also the low-level 
control sequence which when executed will switch to that font.

Lars Hellström