MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <4C93A430.1020103@morningstar2.co.uk>
            <20100917180303.GA7348@oberdiek.my-fqdn.de>
            <19603.49961.484432.456512@morse.mittelbach-online.de>
            <4C93DCDA.3010707@morningstar2.co.uk>
Message-ID:  <19604.28880.24959.737588@morse.mittelbach-online.de>
Date:         Sat, 18 Sep 2010 09:57:04 +0200
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: Option parsing bug or 'feature'?
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <4C93DCDA.3010707@morningstar2.co.uk>
Precedence: list
Status: R

Joseph Wright writes:
 > On 17/09/2010 20:36, Frank Mittelbach wrote:
 > > since you already looked at the different implementations, any suggestion on
 > > how to best improve the LaTeX2e behaviour?
 > 
 > I take it that this does possibly count as a bug then, rather than as a 
 > 'feature'?

it doesn't count as a bug I would say, for the simple reason that per
specification the optional argument of \usepackage doesn't support a key value
list but just a list of option names (that themselves have no spaces)
separated by comma. Only  later packages appeared that internally added
something like keyval and manipulated the received option list from
\usepackage as a key/val list, but that happens after \usepackage has already
removed spaces and unfortunately in this case also the braces.

pragmatic approach:

 you state that one needs to say ={,}  to make things work as this is a fairly
 seldom issue

more elaborate approach

 change \@pass@ptions so that it only removes spaces up front, around a comma
 and at the end

problem with the latter is that the current definition of \@pass@ptions is at
the core of what LaTeX does, ie it is used by every package and any change in
its behaviour might result in unexpected changes somewhere.

so at the moement I'm a bit reluctant to make a change on the 2e-level for the
sake of of one very specific case unless it is fairly minimal and appears to
be "save". But I'm open to suggestions which is why I asked

frank