User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.17)
            Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
References: <4DF7CBEF.6080402@arcor.de>           
            <20110614221243.GA9520@oberdiek.my-fqdn.de>
            <4DF8B044.2040903@morningstar2.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID:  <4DF8B872.8050904@morningstar2.co.uk>
Date:         Wed, 15 Jun 2011 14:49:38 +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: xparse and hyperref: Token not allowed in a PDF string (PDFDocEncoding)
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <4DF8B044.2040903@morningstar2.co.uk>
Precedence: list
Status: R

On 15/06/2011 14:14, Joseph Wright wrote:
> There are a number of ways we could handle this. One way would be to
> have a \DeclareBookmarkableCommand (or similar) macro, which would work
> in the form
> 
>    \DeclareBookmarkableCommand\foo{m}
>      {Standard code}
>      {Bookmark code}

One issue this approach would raise is whether the two implementations
(expandable and non-expandable) should be tied together. You can imagine
using the \DeclareDocumentCommandImplemenation idea to separate out
expandable and protected versions of a macro without needing to create
both at the same time.

One approach might then be

  \DeclareBookmarkCommand \foo { m } { Bookmark code }

which checks for an existing \foo, checks that the arg. spec. is the
same, then does what Heiko suggested and sets things up to allow a
selection of route.
--
Joseph Wright