User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
References: <4A2F5FE3.3030205@morningstar2.co.uk>           
            <qunzxqiuyjyg.dlg@nililand.de>           
            <4A300B9E.4000608@morningstar2.co.uk>           
            <8C8871A5-B9AF-4EF4-8AAA-F282C1D206A0@gmail.com>           
            <4A30C022.8000201@morningstar2.co.uk>
            <B1C8F8BF-1502-434F-BF7C-ED27ED50502B@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID:  <4A30E83D.3070902@morningstar2.co.uk>
Date:         Thu, 11 Jun 2009 12:19:25 +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: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: Key-value input
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <B1C8F8BF-1502-434F-BF7C-ED27ED50502B@gmail.com>
Precedence: list
Status: R

Will Robertson wrote:
>> (Not sure normalising things is a
>> great idea: as you say, one is correct and the rest are wrong!)
> 
> Or all are correct and none are wrong :)
> But I'm not going to push the idea; it was just a stray thought some
> time back. I probably prefer hyphens but I'm not willing to settle on
> one or the other at this stage.

I see your point. The problem comes if you want to differentiate
something by case or whatever, though.  I'm "minded" to leave case, at
least, alone (removing spaces and hyphens would be pretty easy).

>> On inheritance, I know that the pgf team have looked at things, but I'm
>> not happy that they've got an understandable system.  Could you give an
>> example of how tempate does this: I must have missed it in the docs.
>> Then I can think about it!
> 
> Perhaps I used the wrong word. I guess I'm thinking of the \UseInstance
> type of thing in template. Which is more referring to one template from
> within another.

Okay, I'll see how this actually works: not sure if it is dependent on
the key implementation.

> I'd say that if we don't need it in expl3 then we don't need it in
> template. 

Expect keys3 changes on this!
-- 
Joseph Wright