User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.13)
            Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
References: <AANLkTinjH5Ppg2QWWBTDBBU9u3Vvdsjnrrr1OvPvWfnA@mail.gmail.com>     
            <DA7C7068-6B67-41E9-87F2-21C9E58249A8@gmail.com>           
            <AANLkTimhF5fTJJoT3eKHrd=DZE4kOmg60R62pvqxDwDX@mail.gmail.com>     
            <4028010D-1144-415D-A984-E3684A7E3EDE@gmail.com>
            <AANLkTi=Wj6whfFRMyr7jkmz+oG1CzO15S=DC2Zf=X_1A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID:  <4D5B770A.2000401@morningstar2.co.uk>
Date:         Wed, 16 Feb 2011 07:04:42 +0000
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: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: Expandable versions of \uppercase, \MakeUppercase, \lowercase, \MakeLowercase
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <AANLkTi=Wj6whfFRMyr7jkmz+oG1CzO15S=DC2Zf=X_1A@mail.gmail.com>
Precedence: list
Status: R

On 15/02/2011 22:47, Bruno Le Floch wrote:
> For your information, using the code I mentionned for \Uppercase, I
> have now two more things.
> 
> - (Expandable) version of \tl_reverse:n that preserves spaces, and
> goes into brace groups, namely after two steps,
> 
> \UL_reverse:n{\a{ b \) cd\(e}f}  ->  f{e\(dc \) b }\a

Could you post this here? (Or at least the bits that get added to your
existing posts).

> - Expandable full-expansion code (which takes care of course of
> \unexpanded and \noexpand, and \protected commands).
>          \fullyexpand:n{<some tl>}
> is then equivalent to
>          \edef\tmpa{<some tl>} \tmpa

Again, post the code :-) I wonder what exactly you mean here. With the
\expanded primitive (pdfTeX 1.50 or LuaTeX) you can do

  \edef\a{\expanded{\def\a{b}}}

and have \a => 'b'. I can't see that this can work without the extra
primitive. So some examples would be nice.

> I'm not too sure where I should go next.

Put all of the stuff you've written together with some documentation,
sticking to expl3 conventions, and send it to the list for addition to
expl3 :-) (Serious point: I'll probably do something like this over the
next day or so.)
--
Joseph