MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <AANLkTikP4qMZiiQhF5+vKg36BVuvuHnexsPgnX0bbdw6@mail.gmail.com>
Message-ID:  <19806.13404.2362.385720@morse.mittelbach-online.de>
Date:         Fri, 18 Feb 2011 09:57:00 +0100
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@listserv.uni-heidelberg.de>
Sender: Mailing list for the LaTeX3 project <LATEX-L@listserv.uni-heidelberg.de>
From: Frank Mittelbach <frank.mittelbach@LATEX-PROJECT.ORG>
Subject: Re: Fully expandable "x" argument (was "expandable \uppercase...")
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <AANLkTikP4qMZiiQhF5+vKg36BVuvuHnexsPgnX0bbdw6@mail.gmail.com>
Precedence: list
Status: R

Hi Bruno,

 > As Joseph asked, I wrote some documentation.
 >     http://users.aims.ac.za/~bruno/LaTeX/.l3ctab/l3ctab.pdf
 > (and the usual .ins, .dtx, .sty) I hope that naming it "l3..." is not an
 > issue.

to be honest I would be grateful if we can keep the l3 prefix (just like the
lt prefix) reserved to the components that are actually being loaded by the
kernel. Of course you are free to choose a name but in the interest of clarity
I would ask you to change it.

At the point where such code gets integrated into the kernel the name can
easily change if necessary.

frank